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.molin AT afnor DOT org
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Daniel Sparrman
Envoyé : jeudi 24 mars 2011 10:17
À : ADSM-L AT VM.MARIST DOT 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 AT VM.MARIST DOT EDU> skrev: -----
Till: ADSM-L AT VM.MARIST DOT EDU
Från: molin gregory <gregory.molin AT AFNOR DOT ORG>
Sänt av: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT 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.molin AT afnor DOT org
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Lee, Gary D.
Envoyé : mercredi 23 mars 2011 18:44
À : ADSM-L AT VM.MARIST DOT 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. "
|
