Hi, it is quite normal for device names to be different when you use library sharing, you only have to define the path on the management server for the client, you dont have to define drives on the client. On the client you only have to make sure that the name for the library is the same as for the manager, i.e. Manager library1, client has to be library1. No paths for the library are defined on the client. No path for the client is defined on the manager for the library the client wants to use. No drives are defined on the client.
for example, Library is an ADIC100 (3583?) Manager is 5.1.xx W2k server library device is lb0.2.0.4 Manager drive device is mt0.2.0.5 Client is AIX 5.1 TSM 5.1.xx library device is lb0 Client drive device is rmt5 Define server to server communication, follow the manual Define lib as shared on manager, define library adic100 libt=scsi shared=yes define path on manager, define path w2k adic100 srctype=server desttype=library device=lb0.2.0.4 define drive on manager, define drive adic100 ltodrive1 element=256 etc. define lib on client, define library adic100 libt=shared primarylibmanager=w2k On the manager define the drives to the client, define path AIX5.1 ltodrive1 srctype=server desttype=drive library=adic100 device=/dev/rmt5 online=YES Thats all, works well for us. Mit freundlichen Grüßen / Best Regards Markus Veit An: [EMAIL PROTECTED] Kopie: Thema: Tape sharing - how does TSM handle duplicate device file names [EMAIL PROTECTED] Received : 18.03.2003 02:15 Bitte antworten an "ADSM: Dist Stor Manager" ----------------------------------------------------------- This email is to be read subject to the disclaimer below. ----------------------------------------------------------- We currently have two TSM environments at separate sites. Each environment has a SAN connected 3494/3590 (via a MacData Switch and two SDG's). Both TSM environments are isolated within separate zones. This segregation means that both environments have the same drive and path configurations defined to TSM (eg DRV0 = /dev/rmt/0stc) We would now like to invoke library sharing so to automagically write our copy pools and database backups offsite. When I combine the two zones, both server will discover another 8 3590 drives and will build the special device files. Now I would have the situation where the physical drive on the 'managing server' will know the OS as /dev/rmt/0stc and the 'client' it will be /dev/rmt/8stc etc etc. Will this cause an issue with the sharing functionality. In other words, does the special file( ie path definition in TSM) to physical hardware association need to be in sync. If it does not matter, how does the managing server tell the client server where the media it requested has been mounted. Peter Griffin Sydney Water ----------------------------------------------------------- Voluntary water restrictions now apply to residents in Sydney, Blue Mountains and the Illawarra. No sprinklers or watering systems between 8am and 8pm. No hosing of paths, buildings or hard surfaces. For more information visit www.sydneywater.com.au ----------------------------------------------------------- NOTICE - This communication contains information which is confidential and the copyright of Sydney Water or a third party. If you are not the intended recipient of this communication please delete and destroy all copies and inform the sender immediately. If you are the intended recipient of this communication you should not copy, disclose or distribute this communication without the authority of Sydney Water. Any views expressed in this communication are those of the individual sender, except where the sender specifically states them to be the views of Sydney Water. Except as required at law, Sydney Water does not represent, warrant and/or guarantee the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. Sydney Water is not responsible for any changes made to a document other than those made by Sydney Water or for the effect of any changes (not made by Sydney Water) on a document's meaning. -----------------------------------------------------------