Thomas, I would take issue with your statement of "poor support for platform changes". TSM provides a variety of options for planned changes to the server platform as well as the storage media.
Moving a node's data from one TSM server to another is as simple as running "export nodedata...." from the old server to the new server. I have just completed a 40TB move for one client node and am moving several others with virtually no impact to my production environment. A couple of months ago, I migrated over 400TB of data from a Storage Tek library having both SDLT and LTO3 drives to an IBM TS3500 library with TS1120 drives and encrypted all of the data while doing so. This was accomplished with minimal impact to my production system using the "migrate storagepool..." command. It could also have been done using "move nodedata..." or the "move data..." commands. I am not a expert with other backup and recovery platforms so, cannot comment on their ability to so easily change server platforms or media. Perhaps another ADSM-L'er can supply their experiences with other platforms. Thank you, 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:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: Thursday, November 08, 2007 12:26 PM To: [email protected] Subject: Re: [ADSM-L] Database move -----Paul Zarnowski wrote: ----- >Your avenue is export / import. Not pretty if you have a lot of data. >And I'm talking about the data, not just the database. >As I believe more people will be interested in switching server >platforms as time goes by, I would really like to see IBM provide some >better migration tools for helping sites transition from one server >platform to another. TSM is a high-end solution, and needs better tools >in this area (IMHO). I work for a hospital. We are required to retain some clinical records for as long as 25 years (a former pediatric patient gets a seven year window after his or her eighteenth birthday to decide whether to sue the hospital). We are required to maintain information on employee health for the lifetime of the employee. We can't realistically commit to staying with our current server platform for decades to come, and the prospect of exporting and importing would get increasing daunting as long-lived archives accumulated. We are currently looking at options for long-term archiving of digital data, and the poor support for platformchanges is a major point against using TSM. 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.
