Maybe all replies went direct but may also have no answer, so have one. Quote from TSM for AIX MgSysSAN Storage Agent User's Guide (v4.2, p.18): "Map all drives. Problems can occur if you do not define drive mappings on the server for each drive in a library. For example, during backup operations, all drives that have been mapped can be used by storage agents backing up data. Backup operations will fail if you try to use other drives in a library that have not been mapped." So this is expected and documented behavior. Have in mind that agent is just a server with partially disabled functionality (and lower price).
You have two options: - use SAN Data Gateway. Benefits - all drives are SAN-attached thus shareable. Negatives: additional investment (management decision, time, money, etc.) - define two libraries, one over SCSI drives and second over FC drives. 3584 allows you to have more than one library control path. Two suboptions: -- use 3584 partitioning - Benefits: no investment, supported usage. Negatives: you have to plan more carefully how many slots to allocate for each part, some additional complexity - problems may arise if a cartridge is checked into wrong (sub)library -- no partitioning, see the whole lib twice. Benefits (if any): no planing, easy to setup. Negatives: *MANY* and mainly hard to evaluate from theory (never had such a beast just to play in a sandbox with, for sure never tested such a joke with it) - I guess IBM will say this is unsupported usage; how TSM will react seeing already checked in volumes with same label in other library (from its point of view; I think normal and would work); will there be any problems with E/E slots; will TSM update a free slot as occupied when new volume is checked into other part or will fail without retry (I am nearly sure the latter); and probably others I cannot even imagine ... On the other hand might be harmless (again cannot confirm) My personal recommendation - 1 or/and (in some form) 2a. 2b might be dangerous to your data or be the answer - I do not know! You also pointed drivemapping was made only for 2 drives. Why not for the 4 FC ones you have? Zlatko Krastev IT Consultant Please respond to [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: LAN-Free backup: TSM server mounts tape in not-mapped drives Hello, we have a SAN environment with an IBM3584 library (6 SCSI LTO drives, 4 FC LTO drives), running TSM 4.2.2.5, SA 4.2.2.5 and BA 4.2.2.1 for AIX with drive mapping to the 2 FC drives. After bypassing all problems with the IBM documentation (wrong parameters, wrong ports, etc.), I got the LAN free backup working. But there is one thing, that anoys me: When the storage agent requests a tape from the TSM server, the latter starts to mount the requested tape regarding the internal drive usage table also into the SCSI attached drives, which have no drive mapping, and the SA claims, that this drive is not defined to this server (ANR8940E). This causes some transactions to fail due to the delay (storage media inaccessible). Anyone, who can help me with this? Best regards, J�rg Nouvertn� http://home.wtal.de/the_swordsman/
