Importing Node(s)

To import client node definitions from the ADSM server to sequential media, first complete the following fields and then click Finish, or click Cancel to end the task.

Node Name

Enter the list of client node names for which you want to import client node information.

Filespace Name

Enter the list of file space names for which data is to be imported.

Policy Domain

Enter the list of policy domain names to which nodes must be assigned in order for node information to be imported.

Device Class

Select a device class. Import data will be read from this device.

Volume Names

Enter the volume names. Import data will be read from these volumes.

volname The name of one or more volumes used to contain the exported data. You can specify more than one volume by separating each volume with a comma, with no intervening spaces.

Example: To use volumes TAPE01, TAPE02, TAPE03, specify the following: TAPE01, TAPE02, TAPE03

FILE: filename The name of a file that contains a list of volumes to use to store the exported data. Each volume name must be on a separate line within the file. Blank lines and comment lines beginning with an asterisk are ignored.

Example: To use TAPE01, TAPE02, and TAPE03, create a file named TAPEVOL that contains these lines:

TAPE01
TAPE02
TAPE03

You can then enter FILE:tapevol in the Volume Names entry field.

Use the following naming conventions when specifying volumes for each device type:

File Specify any fully qualified name string for your platform, for example:
AIX /imdata/mt1
HP-UNIX /imdata/mt1
MVS im.data.mt1
Sun Solaris /imdata/mt1
Windows NT d:\win32app\ibm\adsm\server\data1.dsm
VM im.data
Optical, WORM, WORM12, WORM14 Specify 1-32 alphanumeric characters.
Removablefile Specify 1-6 alphanumeric characters.
Server Specify 1-250 alphanumeric characters.
3570, 3590, 4mm, 8mm, DLT, DTF, QIC, Generictape, Cartridge, ECartridge Specify 1-6 alphanumeric characters.

The following device types are available on these platforms:

Device Types AIX HP-
UNIX
MVS VM Sun
Solaris
Windows
NT
File, Server X X X X X X
Optical, WORM X       X X
WORM12, WORM14, 8mm, ECartridge X       X  
Removablefile           X
3570, 4mm, DLT X       X X
DTF, QIC X         X
Generictape X X     X X
3590 X X X X X  
Cartridge X   X X X  

File Data

Select the type of files that should be imported for all nodes specified, and found on the export media. This parameter is optional.

None Specifies that no files are to be imported; only node definitions are to be imported. The default is None.
All Specifies that ADSM imports all backup versions of files, all archived files, and all files migrated from a user's local file system.
Archive Specifies that only archived files are to be imported .
Backup Specifies that only backup versions, whether active or inactive, are to be imported.
Backup active Specifies that only active backup versions are to be imported.
Allactive Specifies that ADSM imports all active backup versions of files, all archived files, and all files migrated from a user's local file system.
Space managed Specifies that only files which have been migrated from a user's local file system (space-managed files) are to be imported.

Preview

Select an option for Preview.

Yes Specifies that you want to preview the results of the import operation, without actually importing node information.
No Specifies that the node information is to be imported without a preview. The default is No.

Date/Time

Select whether the recorded backup or archive dates for client node file copies are set to the values specified when the files were exported (Absolute), or are adjusted relative to the date of import (Relative).

Absolute Specifies the date for file copies are set to the values specified when the files were exported. The default is Absolute.
Relative Specifies the date for file copies are adjusted to the date of import.

Replace Definitions

Select whether node definitions that exist on the server should be replaced by imported nodes having the same name. Existing file spaces are not replaced. New file spaces are created when identical file space names are encountered.

Yes Specifies that nodes are to be replaced by the imported nodes.
No Specifies that nodes are not to be replaced by imported nodes. The default is No.