Yep, pretty much that simple. Check the tapes out of one library, check them into another. No more complicated than if you are going to a DR site that has a 3584 rather than a 3494. TSM doesn't care.
There are some differences in the library management: If you are talking to the 3494 library interface via TCP/IP now, that changes. (Some people use the TCP/IP interface, some use a serial cable.) TSM talks to the 3584 library via the atape drive over the fibre, it has its own device number/path. Thomas already mentioned that the 3584 can be partitioned into logical libraries. If you have multiple TSM servers or other apps using the 3494, you keep them separated now by 3494 category codes, those go away. You have the logical libraries now instead. Carts get assigned to the logical libraries based on a volser range filter in the library interface. W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Friday, January 25, 2013 2:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape library possible replacement - push/pull We are starting to examine the idea of replacing our aging 3494 (installed 1995) due to difficulty in getting parts and having more frequent outages due to robot issues. Since we have 17-TS1130 drives, the natural transition would be to a TS3500/3584. If we go down this route, one issue might be the floorspace/placement, which might require a weekend eject-push-pull-reload. Never having dealt with any tape library other than the 3494, I am trying to collect as much info as I can on doing a swap-out. Is it as simple as defining the new library, moving the drives/paths to it, changing the devclass to point to the new library, checkin everything (scratch/private)?? Am I missing anything? -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html