I think I can help. Import and export of nodes is very ticklish. When you export the node, you must issue a q fi nodename f=d to get the numbers of the filespaces. Then, in the export command use the fsid=1,2,3 etc option, and replace the 1,2,3 with the numbers associated with the filespaces you're exporting. Make note of the numbers (in sequence) and the associated unicode filespace names (filespaces that begin with a \\ as opposed to a drive letter). When you execute the command, use filespace=* fsid=1,2,3 etc and unifilespace=\\whatever\whatever,\\whatever\whatever etc, and the rest of the command as presented below.
The same care must be taken on an import. After you move the EXP files to the new server, you must import them. When you import, the nodename should be associated with the desired management class. If your management class dictates which storage pools to use, you should change the default management class to the one you want the imported node to be part of, and then import it. You can set the default management class back to normal after you've completed the import operation. Here's a command to import a normal node. import node foo filespace=* filedata=all unifilespace=\\alpha\c$ preview=no devclass=foodev1 volumenames=/tsm/07062600.exp,/tsm/07066336.exp etc. you MUST import the exp files in the order they were exported. Make sure you have the same estimated max capacity in the two device classes (which must be the same on the two servers) so volume creation will coincide and be easier to track. The order they were exported should be parallel to the order imported, which must be in the same order as the unifilespace= command above. This order can be maintained by using the order presented by the q fi nodename f=d command. Remember to only include the unicode filespace (stuff with a \\ in front of it) in the command above. Let me know if this helps, Kevin. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Hart, Charles Sent: December 6, 2001 12:43 PM To: [EMAIL PROTECTED] Subject: Import Node Question We have two AIX servers w/ TSM 4.1 sharing a 3494Lib. We were able to successfully Export the node from the Source to the Target Server. Once we tried the import the node the Virtual volume that was created from the Export process never seemed to mount so we then canceled the process. We can see that on the Target Server's storage pool (we defined a separate stgpool for this process and a devclass of 3590tape so the export goes to tape) there is a 3590 tape in the stgpool we are using that's allocated and filled with what appears to be the same amount of data as the Export stated. There must be something we're missing here. Is there something else we need to do to get that virtual volume mounted? I've looked all over and can not seem to find the answer. Below is a rundown of events. Any help would be Greatly Appreciated!!! Thanks EXPORT NODE Server Messages: Issued Export command: EXPORT NODE IMCP1 FILESPACE=* DOMAIN=WINNT FILEDATA=ALL PREVIEW=NO DEVCLASS=MSPSTG5 SCRATCH=YES ANR4006I EXPORT NODE: Volume 1 written by process is MSPSTG5.EXP.007578434. 12/05/01 17:14:08 ANR0986I Process 3927 for EXPORT NODE running in the BACKGROUND processed 810011 items for a total of 32,450,171,729 bytes with a completion state of SUCCESS at 17:14:08. Import Node Command import node imcp1 filespace=* domain=winnt filedata=all preview=no devclass=mspstg1 volumename=MSPSTG5.EXP.007578434 IMPORT NODE Server Status 318 IMPORT NODE ANR0648I Have copied the following: (0 errors have been detected). Waiting for mount of input volume MSPSTG5.EXP.007578434 (585 seconds). Volume Name Storage Device Estimated Pct Volume Pool Name Class Name Capacity Util Status (MB) ------------------------ ----------- ---------- --------- ----- -------- K01126 MSPSTG1_IM- 3590TAPE 102,400.0 30.0 Filling PORT
