Hello David,
I think the best option for your case is:
- upgrade existing server to the latest 5.5 version (5.5.4.0 now);
- migrate upgraded instance to new server (just hardware upgrade) or keep it on
existing server at all;
- upgrade all clients to version 6.2.1 (as a preparation for TSM Server
upgrade). Note, it can be quite long action and it depends on current client
versions (no information in your message);
- wait till TSM Server 6.2.X will be matured enough (newer DB2 version, much
newer TSM Client, etc, but quite new now).
In other case, if you are still going to upgrade to 6.X:
1) upgrade to latest 5.5 version will be still required to make upgrade
easier;
2) do not upgrade to version 6.1.X (I think it is obsolete version - still
unstable);
3) upgrade straight way to 6.2.1 (it is supported), but keep in mind:
? 6.2.1 installation is not easy (you need to read all documentation
carefully and special training in test environment is required);
? 6.2.1 upgrade is very complicated task (not straight way, complicated and
long). You have to be ready for some TSM Server downtime ;
? 6.2.1 is much more heavy application from CPU point of view because of
DB2 (especially if you are going to use server side de-duplication). Most
possible 4 cores will be not enough;
? 6.2.1 is much more heavy from I/O point of view (the best option is to
use different locations for database, logs, archives and data (device class
FILE), at least for database, log/archives and data;
? 6.2.1 requires much more space for database (maybe multiplied by 3), logs
(it depends, but you have to be ready to multiply it by 5) and archives (does
not exist in 5.X and has size at least as logs);
? 6.2.1 supports mirroring for logs and archives. Of course mirrored
logs/archives have to be on different disks. I will not advise you to use
mirroring initially;
? 6.2.1 does not support de-duplication on DISK device class - you need to
migrate DISK to FILE;
? 6.2.1 supports de-duplication only from 6.X clients (6.2.1 is preferable).
Kindest regards,
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: Grigori.Solonovitch
AT ahliunited DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
dcpc
Sent: Friday, July 09, 2010 4:59 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Upgrade TSM 5 -> 6 : pre-requisite
Hello,
We'll upgrade soon to TSM 6.x, and we need to change our server too.
Target : HP DL380G6 QuadCore Xeon E5520 at 2.26GHz + 6Go RAM
I'm confused about some pre-requisite found in the doc for the amount of RAM :
* TSM 5.5 : 2Go RAM is enough
* TSM6.x : 6Go Mini, recommanded 10Go !
=> is DB2 so huge ? ?
Otherwise and more complex, about disk and configuration :
By default we'll have 3x300Go SAS (1 hdd can be added)
In local, we'll store the system, TSM server, TSM client, DB and logs.
Which configuration would you recommand for this set of elements :
* type and number of raid(s) ?
* localisation of elements (principally DB and logs ?)
* use duplication for db and logs (mirroir) ?
Some informations about actual configuration on TSM 5.4.3 :
* DB : 13 Go used
* Logs : 2 Go used
* diskpool of 100Go on SAN (35% max used/jour)
* Filepool on SAN with "file tape" of 100Go (65% to 85% of 4To used)
* SCSI Library attached, used almost only for externalisation with DRM (the
file pool never migrate on LTO3).
Other data informations :
* 18 nodes :
- 16 clients (bkp duration between 2min and 2h)
- the tsm server backs up a part of a NAS (netapp) via NFS (4.4M files
analysed, 15Go bkp/day, duration 5h)
- 1 server backs up a part of a NAS (netapp) via CIFS (2M files analyzed, 2Go /
day, duration 1h30)
* 30Go backup / Day
* 88k files backuped / D
* 28k files expired / D
* auditocc : backup used : 5Go
* select count(*) from backup (long !) : 34M objects
Thx for answers !
David
+----------------------------------------------------------------------
|This was sent by dcpc.dev AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
Please consider the environment before printing this Email.
________________________________
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
|
