Hi Gregory
My comment was to this previous comment: "But, the most important with the 6.x is the architecture of database files. You have to reserve one disk for the database, on for the actlog and one other for the archlog. Having this disks on the same axe may result poor efficientie" What I ment was that it has never been recommended to share the same array / spindle / filesystem between logs and database. If you go back to the TSM v5.5 performance guide, you'll will notice the recommendation to separate log and DB on separate spindles / filesystems / arrays. As for DB2, yes, DB2 is new for v6, but the performance setup isnt. My guess is that if your setup crashed after 2 months, whoever implemented your solution probably shared filesystemspace between the database and some other part of TSM, such as archivelog or log. Since a) the database can now grow "of it's own" I wouldnt place it with something else since you might run out of space b) I wouldnt share archivelog space with something else either since it also "grows of it's own". I cant imagine that your TSM implementation crashed just because the person who implemented it placed the database on a single filesystem. This is technically possible, but not something I would recommend due to performance issues. Best Regards Daniel Sparrman -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- Till: ADSM-L@VM.MARIST.EDU Från: molin gregory <gregory.mo...@afnor.org> Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Datum: 03/25/2011 14:47 Ärende: Re: Ang: Re: Tsm v6 migration question Hello Daniel, You say : ' That's not really something new to TSM v6'. DB2 is now the DBMS for TSM, and if DB2 improve database, DB2 has system requirement who was not the same in previous version My experience: The installer has set up the solution on our site has not implemented the recommendations related to DB2. TSM crash after two months. Best Regards Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Daniel Sparrman Envoyé : jeudi 24 mars 2011 10:17 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Ang: Re: Tsm v6 migration question That's not really something new to TSM v6. For performance reasons, it has always been recommended to separate database and log on different spindles. As with v6, at least for larger implementations, the same rule of thumb applies: Try separating your DB paths on at least 4 different arrays/spindles, preferably 8 or more. Too many will not increase performance, rather reduce it. Put your active log / log mirror on spindles of it's own, as well as your archivelog / failover paths. Watch out for sharing archivelog with something else (like storage) since the database backup trigger will look at the % used on the filesystem. So putting storagepools and then your archivelog in the same filesystem probably isnt the best of ideas. Best Regards Daniel Sparrman -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- Till: ADSM-L@VM.MARIST.EDU Från: molin gregory <gregory.mo...@afnor.org> Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Datum: 03/24/2011 11:06 Ärende: Re: Tsm v6 migration question Hello Gary, Effectively, the database grows between 10 and 20 %. (more if new features, like dedup, are intalled) But, the most important with the 6.x is the architecture of database files. You have to reserve one disk for the database, on for the actlog and one other for the archlog. Having this disks on the same axe may result poor efficientie Cordialement, Grégory Molin Tel : 0141628162 gregory.mo...@afnor.org -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, Gary D. Envoyé : mercredi 23 mars 2011 18:44 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] Tsm v6 migration question We are preparing to migrate our tsm v5,5,4 system to 6.2.2. Are there any rules of thumb for relating db size in v5.5.4 with what we will need under v6? I assume it will be somewhat larger being a truly relational structure. Thanks for any help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system. " "ATTENTION. Ce message et les pièces jointes sont confidentiels et établis à l'attention exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été adressé). Si vous n'êtes pas le destinataire de ce message, vous devez immédiatement en avertir l'expéditeur et supprimer ce message et les pièces jointes de votre système. This message and any attachments are confidential and intended to be received only by the addressee. If you are not the intended recipient, please notify immediately the sender by reply and delete the message and any attachments from your system. "
