Been there, just done this. First all, if you are at 5.1.5, I was told by someone that you could export DIRECTLY to another server, without having to do the bogus export- then-import thing. I would look into that, as it should be easier to implement than what you are doing.
Second, I have had little success in the past using export/import where the target server was at a lower version than the source server (kinda makes sense, since the data base can change from one version to the next), so I don't think this is guaranteed to work. That being said, if you did the setup using the admin guide, there is a step missing. The ONLY place I have found this documented is in the OLD ADSM server-to-server implementation redbook (and it's kinda easy to miss there, too), and I never would have figured it out except by searching the ADSM-L archives (THANK YOU DWIGHT!). On the sourceserver you must do: DEFINE SERVER targetserver But on the target server you must ALSO do: DEFINE SERVER targetserver -- so you define the target server back to itself. If you don't do this the export will work, but the import will not. Here is a copy of the pertinent pieces from my devconfig, if that will help: I was going from an AIX server to a Windows server. Server to Server DEVCONFIG parms for SOURCE SERVER : /* Device Configuration on AIX: */ SET SERVERNAME AIXADSM DEFINE SERVER TSM_WIN COMMMETHOD=TCPIP HLADDRESS=nnn.nnn.nnn.nn LLADDRESS=1500 NODENAME=H801SRVR PASSWORD=zzzzzz DELGRACEPERIOD=0 DEFINE DEVCLASS OVERTHERE DEVTYPE=SERVER MAXCAPACITY=41943040K MOUNTLIMIT=3 MOUNTRETENTION=4 PREFIX=ADSM SERVERNAME=TSM_WIN RETRYPERIOD=6 RETRYINTERVAL=3 Server-to-Server DEVCONFIG parms for TARGET SERVER: /* Device Configuration on Windows: */ SET SERVERNAME TSM_WIN DEFINE DEVCLASS OVERHERE DEVTYPE=SERVER MAXCAPACITY=41943040K MOUNTLIMIT=8 MOUNTRETENTION=0 PREFIX=ADSM SERVERNAME=TSM_WIN RETRYPERIOD=10 RETRYINTERVAL=30 DEFINE SERVER TSM_WIN COMMMETHOD=TCPIP HLADDRESS=newhost LLADDRESS=1500 NODENAME=H801SRVR PASSWORD=zzzzzzzzzzzzzz Also needed on target server: DEFINE NODE H801srvr pwd TYPE=SERVER MAXNUMMP=3 DOMAIN=PDOM_OTHERSRVR Using the above definitions: EXPORT: export node xxxxx filedata=all devclass=overthere IMPORT: import node * filedata=all devclass=overhere vol=TSM_WIN.EXP.nnnnnnnnnnnnn ************************************************************************ Wanda Prather The Johns Hopkins Applied Physics Lab 443-778-8769 [EMAIL PROTECTED] "Intelligence has much less practical application than you'd think" - Scott Adams/Dilbert ************************************************************************ -----Original Message----- From: Allen Barth [mailto:[EMAIL PROTECTED]] Sent: Friday, February 07, 2003 2:23 PM To: [EMAIL PROTECTED] Subject: export/import via virtual vols help Hi list- Due to some restructuring, I need to export node 'x' from TSM server 'k' and then import it to TSM server 'c'. I want to use virtual vols. I set up the server-server comm stuff, devc, and client nodes as needed. I ran the export node 'x' on server 'k' specifying a devc that points to server 'c'. While it took a while, the export completed successfully, and I saved the volusage list to nodex.vols Now on server 'c', I want to IMPORT NODE x I set up devc 'servc' on server 'c' as type=server which points to server 'c' I reg'd server 'c' as a server type client on server 'c' in the same domain as the server 'k' client definition I ftp usedvol list from server 'k' to server 'c' I issue: import node x filed=all preview=yes dev=servc vol=file:nodex.vols preview=yes What happens is server 'c' starts an internal session with itself due to the devc, but I get a message that it cannot mount the volume as read from the nodex.vols. What am I missing? Is this possible? Server 'k' is 5.1.5, server 'c' is 4.1.5, both are AIX. TIA -- Al
