As I recall, it should go something like this: First, set up the library manager instance on the same AIX host on which your current TSM server resides. When you define the library make it Shared=Yes; give the library a DIFFERENT name than what your current instance uses. Define the drives on the library manager; these can be the same names as what you use, but they'll obviously be defined under the new library name. You don't need to define these on your original TSM server. (I think you might also need to define a devclass on the library manager; if you do, use the SAME name as the devclass that's defined on the original TSM server instance.)
You already have the AIX device names for the drives, presumably, because your current TSM server instance has working paths. You'll need to define the TSM server instances to each other, then define paths on the library manager - one from itself (source) to the library (destination), eight from itself to the drives, and eight more from the other TSM server to the drives (same AIX device names). On your original TSM server instance, quiesce all activity while you do the following. Define the new library on the original instance, using the name you used for the library defined on the library manager, libtype=Shared, and primarylibmanager=newTSMserverinstance. Update your existing devclass, changing it to point to the enw library name. Now you need to check the libvols in to the new library, being sure to set status=private and owner=existingTSMserverinstance. Make sure that the original instance can access the data (a move data will do), then you can delete the drives and paths defined on the original TSM server instance, and delete the library - this should delete the libvols, but leave the volumes intact. I haven't done this myself, but we've been considering a similar situation, and that's how we had planned to address it. When you set up the TSM server on the other machine, zone all the drives to the AIX host, and discover them. You'll need to know which drive has what name in AIX, and those rmt names (which will likely be at least in a different order from the ones on your other server) will be the ones you use when you define the paths on the library manager from the new TSM server instance (source) to the drives (destinations). "lscfg -v | grep rmt" on the new AIX server will help a lot; you'll need to know which WWN corresponds to which drive as defined in the library manager. You can deduce this by running the same command on the original AIX host, and comparing to the existing working paths. Again, define the paths on the library manager, not on the new TSM server instance. All the new instance will need is a defined library (libtype=shared), the same devclass name as before, and storage pools using that devclass. The library manager allocates mounts from either server as requested. If you want to dedicate some drives to one server instance, just disable the paths that have the other instance as the source - Never disable the paths that have the library manager as the source. The library manager also allocates scratch volumes to servers, and keeps track of who is using which libvolumes. The libvolumes will show up on the library manager, the volumes on the other TSM servers. Robben Leaf Hi TSMers, We've a single TSM-Server (TSM5.3.4/AIX5.3) and 3494 tape library with eight TS1120 drives. We'll split the environment into two physical servers because our database (actual 200GB) is growing continuously. There should be three TSM instances - one new instance as library manager for 3494 sharing on existing server and two instances (existing instance and a new one on new physical machine) for node access as library clients. Now I'm looking for information how to configure and migrate to this new environment but the documentation for the SAN/AIX part seems to be very poor. To ensure that the data flow over SAN on both physical machines (for migration from disk storage pools to tape) I'd like to build zones within both servers and all of the tapes on the fabric(s) so that the tape drives can be configured as primary/alternate rmt's on each of the two servers. If this is possible and supported next step will be to gather information how to set up the LIBRARY, PATH and DRIVE definitions and how to migrate all the libvolumes from old instance to the new library manager instance. Any suggestions how to do that ? TIA Otto ___________________________________ TSM-Admininstration Medical University of Vienna, Austria ------------------------------------------------------------------------------ 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. ==============================================================================
