Grigori, If deduplication is your driving force, you really need to evaluate if a VTL or NAS appliance may be a better solution for your environment. There are several out there and some have evolved to provide primary storage dedup.
I agree that the massive increase in resources is troubling but, compare current hardware with what was available when TSM V4 first came out. TSM is not for small environments - it is an enterprise solution which requires enterprise resources. The evolution to DB2 was desprately needed not only to help contain TSM server sprawl but to also allow more resources to be dedicated to improving TSM functionality rather than maintaining the old TSM database. I currently have 16 AIX TSM servers in 2 locations and am planning to consolidate to between 4 and 8 servers each having a bit more hardware than the current servers. I will be able to do this because the database will be stable above 500GB. I realize that backups will take a bit of time but hopefully IBM will implement parallel backup processing and I will be able to backup a 1+TB TSM DB in less than 2 hours and restore it in less than 5. Del Hoobler, If you have some input to TSM evolution, please consider a command line switch or server setting which would allow multiple parallel backup and restore processes for the database - similar to what can be done in IBMs Data Warehouse environment. Cheers, Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: Thursday, June 04, 2009 1:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6.1 Installation Problems I have found next disadvantages in TSM 6.1: 1) installation is much more complicated. I think this is coming together with DB2. I was not able to install TSM 6.1 in manual mode. I have used GUI assistant to complete all tasks. In my opinion, it is not good, because I am not a beginner in TSM (10 years!); 2) TSM 6.1 requires much more disk resources. Database is much bigger (not only +40% declared in documentation). Using de-duplication + reclamation produces 2-3 times more logs. In addition, new requirements came for archived logs. Usually archived logs are bigger than logs. There is automatic cleaning procedure for archived logs, which requires 2 or 3 full backups of database. As a result, archived logs are kept at least for 3 days in case of using full backup for database every day. Just imagine if you are using weekly full backup for database!!!???. Note I did not use mirroring for logs and archived logs. With mirroring it will be full crash at all from disk space requirements; 3) TSM 6.1 requires much more CPU and memory resources than TSM 5.5 and not only for de-duplication. During testing I am running backups and copies without de-duplication (numpr=0) and than de-duplication + reclamation after completion of backups and copies. In addition to dsmserv process there is db2sync process which is usually much heavier than dsmserv; 4) I have found very strange TSM behavior during some commands like "delete volume ... discarddata=yes". Command reports successful completion, but process is still running with heavy load from db2sync. I am not sure, but it can be a bug. I hope this information will be interesting for TSM admins. I will deeply appreciate any kind of information (good or bad) about TSM 6.1.X. It looks, we need to implement TSM 6.1 because of de-duplication Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan Forray/AC/VCU Sent: Wednesday, June 03, 2009 4:59 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6.1 Installation Problems Definitely wait for 6.1.2 or a possible 6.1.1.1 release I have been "promised" to address a problem that was possibly introduced in 6.1.1. I agree - way too unstable for production. Watch out for the hidden storage/disk requirements plus the need for 3-FULL DB backups before it purges archived transaction logs! From: Grigori Solonovitch <g.solonovi...@bkme.com> To: ADSM-L@VM.MARIST.EDU Date: 06/03/2009 09:47 AM Subject: Re: [ADSM-L] TSM 6.1 Installation Problems Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> You are completely right. It is much more difficult to install TSM 6.1 in comparison with any previous version. Upgrade is going to be very painful and long as well. I have installed TSM 6.1 under AIX 5.3 - it is very unstable. I have upgraded to TSM 6.1.1 - it looks a little bit better. I am testing 6.1.1 now, but I am going to wait for TSM 6.1.2 before production upgrade. Mike wrote: " The installation of TSM 6.1 is very time-consuming and it makes me insecure if thinking about an 5.5 update. Has anybody else installed or updated the newest release?" Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of mfrank Sent: Wednesday, June 03, 2009 11:58 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM 6.1 Installation Problems The installation of TSM 6.1 is very time-consuming and it makes me insecure if thinking about an 5.5 update. Has anybody else installed or updated the newest release? Mike +---------------------------------------------------------------------- |This was sent by michael.fr...@data-protector.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---------------------------------------------------------------------- Please consider the environment before printing this Email. "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME." "This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME." IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
