Re: Moving our TSM Server off MVS/ZOS to Win2003
Who is the business partner? Bob Martoncik Lucas County Information Services 419-213-4633 >>> [EMAIL PROTECTED] 5/23/2006 10:56 AM >>> Huh ? More expensive ? What were they trying to sell youAIX ? I thought that IBM was big into endorsing Linux ? Sounds like your "business partner" doesn't know Linux ? Shannon Bach <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/19/2006 02:03 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Moving our TSM Server off MVS/ZOS to Win2003 Mark Stapleton asked, "(*Why* are you moving to Windows?)" That is the platform the IBM business partner consultants recommended as we only have one TSM Server. I was pushing for a UNIX but that came in at a much higher price. Shannon
Re: Moving our TSM Server off MVS/ZOS to Win2003
Huh ? More expensive ? What were they trying to sell youAIX ? I thought that IBM was big into endorsing Linux ? Sounds like your "business partner" doesn't know Linux ? Shannon Bach <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/19/2006 02:03 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] Moving our TSM Server off MVS/ZOS to Win2003 Mark Stapleton asked, "(*Why* are you moving to Windows?)" That is the platform the IBM business partner consultants recommended as we only have one TSM Server. I was pushing for a UNIX but that came in at a much higher price. Shannon
Re: Moving our TSM Server off MVS/ZOS to Win2003
Just finished doing the same thing. We created a new TSM server on RH Linux 4 (We had too many issued with Windows not wanting to share Fibre-Channel attached tape drives) and either: 1. Performed EXPORT TO SERVER 2. Created new same named nodes and then deleted the old backups from the zOS server. Sure, moving some nodes took many days (around 100GB per 24-hours is what we could get out of the MF, since it only has a 10/100Mb nic). We had about 12TB to move. This has been in progress for 3-4 months. Shannon Bach <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/19/2006 12:56 PM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Moving our TSM Server off MVS/ZOS to Win2003 We recently received the okay to move our current TSM Server off the MVS/ZOS mainframe to a Windows server. Along with this, we will be getting an IBM 3584 Library with (6)TS1120 Jaguar tape drives ...this will be exclusive to TSM and may be located at an offsite location (still waiting for decision from above). And I'll have 800 GB's of disk from an IBM DS6800. I'll have to export/move the current date from a 3594 Magstar ATL and some older archived data on a VTL to the Jaguar. That will consist of moving date from 3590e carts with around 20 GB's of data to cartridges with a capacity of 300 GB's. Having always been a "mainframer" :~)... I am wondering if anyone else here has gone through this transition and wouldn't mind passing on some useful tips. I have been browsing on the Internet for a redbook or white paper... even a checklist of considerations, but haven't found much as yet. Any tips would be greatly appreciated...and feel free to email me directly. Thank you... Shannon Madison Gas & Electric Co Operations Analyst -Data Center Services Information Management Systems [EMAIL PROTECTED] Office 608-252-7260
Re: Moving our TSM Server off MVS/ZOS to Win2003
- Shannon Bach wrote: - >We recently received the okay to move our current TSM Server off the >MVS/ZOS mainframe to a Windows server. Along with this, we will be >getting an IBM 3584 Library with (6)TS1120 Jaguar tape drives ...this >will be exclusive to TSM and may be located at an offsite location >(still waiting for decision from above). And I'll have 800 GB's of >disk from an IBM DS6800. I'll have to export/move the current date >from a 3594 Magstar ATL and some older archived data on a VTL to the >Jaguar. That will consist of moving date from 3590e carts with >around 20 GB's of data to cartridges with a capacity of 300 GB's. > >Having always been a "mainframer" :~)... I am wondering if anyone >else here has gone through this transition and wouldn't mind passing >on some useful tips. I have been browsing on the Internet for a >redbook or white paper... even a checklist of considerations, but >haven't found much as yet. We moved TSM from z/OS to mainframe Linux, which raises most of the same issues. Most of our backups were moved by doing full backups to the new server and keeping the old server around until all inactive backups aged off. This was usually faster than export/import. We used export/import for archives (because they had much longer retention periods than inactive backups) and for backups from a few clients that no longer existed. In cases where export/import is necessary, server to server export/import is much more convenient than tape import/export. The documentation indicates that the server to server facility was introduced with the 5.2 server code. In point of fact, it is also available under later 5.1 maintenance levels. What kind of automation facilities are you using to manage TSM server operations? Depending on the answer, you may have a significant software porting effort ahead of you. Tape handling is likely to be a significant culture shock. The z/OS implementation of TSM relies heavily on the host operating system for tape management facilities. The other implementations are much more dependent on facilities internal to TSM. If you move tapes between the ATL and an offsite vault you will also need to figure out how to integrate the new library into your operations procedures. If you have DR procedures that involve rebuilding the TSM server on replacement hardware you will need to arrange for a new set of replacement hardware. I am guessing that the new server will have a different IP address and DNS name than the old one. If you have a large number of clients managing the necessary client configuration changes will be a significant undertaking. We had a couple of hundred clients when we migrated. I wrote a script to generate customized instructions for each client. It took into account the following dichotomies: 1.Windows versus Unix/Linux 2.AIX versus other Unix/Linux (different location for dsm.sys) 3.DMZ network versus secure network (numeric server address for DMZ clients) 4.Able to run a full backup in one day versus needing two or more days (the later situation requires a scheduler process for each TSM server) In retrospect, I wish I had set up a spreadsheet to keep track of client characteristics and migration dates in a more systematic way.
Re: Moving our TSM Server off MVS/ZOS to Win2003
The TSM db is almost 20 gig with around 70 clients. Wow...Thank you Mark & John! Both of those are going to be very helpful in my planning. Shannon "Vats.Ashok" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/19/2006 01:07 PM Please respond to "ADSM: Dist Stor Manager" To: ADSM-L@VM.MARIST.EDU cc: Subject: Re: Moving our TSM Server off MVS/ZOS to Win2003 How big is you TSM db and Number of client you backup every day.we run on aix with 177 clients and have logpin issues all the time. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Shannon Bach Sent: Friday, May 19, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Moving our TSM Server off MVS/ZOS to Win2003 Mark Stapleton asked, "(*Why* are you moving to Windows?)" That is the platform the IBM business partner consultants recommended as we only have one TSM Server. I was pushing for a UNIX but that came in at a much higher price. Shannon
Re: Moving our TSM Server off MVS/ZOS to Win2003
How big is you TSM db and Number of client you backup every day.we run on aix with 177 clients and have logpin issues all the time. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Shannon Bach Sent: Friday, May 19, 2006 11:04 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Moving our TSM Server off MVS/ZOS to Win2003 Mark Stapleton asked, "(*Why* are you moving to Windows?)" That is the platform the IBM business partner consultants recommended as we only have one TSM Server. I was pushing for a UNIX but that came in at a much higher price. Shannon
Re: Moving our TSM Server off MVS/ZOS to Win2003
Mark Stapleton asked, "(*Why* are you moving to Windows?)" That is the platform the IBM business partner consultants recommended as we only have one TSM Server. I was pushing for a UNIX but that came in at a much higher price. Shannon
Re: Moving our TSM Server off MVS/ZOS to Win2003
IBM Technote 1153886 http://open-systems.ufl.edu/services/NSAM/whitepapers/50ways.html __ John Monahan Consultant Infrastructure Solutions Group Computech Resources, Inc. Office: 952-833-0930 ext 109 Cell: 952-221-6938 http://www.computechresources.com Shannon Bach <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 05/19/2006 11:56 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Moving our TSM Server off MVS/ZOS to Win2003 We recently received the okay to move our current TSM Server off the MVS/ZOS mainframe to a Windows server. Along with this, we will be getting an IBM 3584 Library with (6)TS1120 Jaguar tape drives ...this will be exclusive to TSM and may be located at an offsite location (still waiting for decision from above). And I'll have 800 GB's of disk from an IBM DS6800. I'll have to export/move the current date from a 3594 Magstar ATL and some older archived data on a VTL to the Jaguar. That will consist of moving date from 3590e carts with around 20 GB's of data to cartridges with a capacity of 300 GB's. Having always been a "mainframer" :~)... I am wondering if anyone else here has gone through this transition and wouldn't mind passing on some useful tips. I have been browsing on the Internet for a redbook or white paper... even a checklist of considerations, but haven't found much as yet. Any tips would be greatly appreciated...and feel free to email me directly. Thank you... Shannon Madison Gas & Electric Co Operations Analyst -Data Center Services Information Management Systems [EMAIL PROTECTED] Office 608-252-7260
Re: Moving our TSM Server off MVS/ZOS to Win2003
"ADSM: Dist Stor Manager" wrote on 05/19/2006 11:56:38 AM: > We recently received the okay to move our current TSM Server off the > MVS/ZOS mainframe to a Windows server. Along with this, we will be > getting an IBM 3584 Library with (6)TS1120 Jaguar tape drives ... > this will be exclusive to TSM and may be located at an offsite > location (still waiting for decision from above). And I'll have 800 > GB's of disk from an IBM DS6800. I'll have to export/move the > current date from a 3594 Magstar ATL and some older archived data on > a VTL to the Jaguar. That will consist of moving date from 3590e > carts with around 20 GB's of data to cartridges with a capacity of 300 GB's. > > Having always been a "mainframer" :~)... I am wondering if anyone > else here has gone through this transition and wouldn't mind passing > on some useful tips. I have been browsing on the Internet for a > redbook or white paper... even a checklist of considerations, but > haven't found much as yet. You will find that the export of actual data will take *way* longer than you would care to wait (by several orders of magnitude). Here's a best-practice framework to follow: 1. Get your new TSM server running. 2. Set up server-to-server communication between the old and new servers. 3. Run EXPORT SERVER from the old server and send it to the new server; this will move your entire TSM environment (policies, nodes, etc). Do *not* move filedata. Expect to have to do some cleanup to modify the old environment's definitions to the new environment. 4. Give your new TSM server the IP address used by the old server. (Otherwise, you'll have to touch all of your TSM clients to change their option files.) 5. Run all of your new backups to the new server/library. 6. If you have to do a restore from the old server, change the client's option file to point at the old server and run the restore. 7. After a month or so, modify the retention policies on the old server to get rid of all but the latest copy of all data. Then let the data expire off of the old TSM server for at least several months. *Then* consider running exports of data from the old server to the new server. Clumsy? Yes. Time-consuming? You bet. But it's the only good way to move from one OS to another for your TSM server. (*Why* are you moving to Windows?) -- Mark Stapleton ([EMAIL PROTECTED]) US Bank MR Backup and Recovery Management Office 262.790.3190 -- Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. ==
