To export client node definitions from an ADSM server to sequential media, first complete the following fields and then click Finish, or click Cancel to end the task.
Enter the list of client node names for which information is to be exported.
Enter the list of file space names for which data is to be exported.
Select a policy domain name from which nodes should be exported.
Select the type of files that should be exported for all nodes defined to the server. This parameter is optional.
None | Specifies that no files are to be exported; only node definitions are to be exported. The default is None. |
All | Specifies that ADSM exports 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 exported. |
Backup | Specifies that only backup versions, whether active or inactive, are to be exported. |
Backup active | Specifies that only active backup versions are to be exported. |
Allactive | Specifies that ADSM exports 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 exported. |
Select an option for Preview.
Yes | Specifies that you want to preview the results of the export operation, without actually exporting node information. |
No | Specifies that the node information is to be exported without a preview. The default is No. |
Enter the device class to which export data is to be written.
Select whether to use scratch volumes for the export.
Yes | Specifies that scratch volumes are to be used for export. If you include a list of volumes on the Volume Names field, then scratch volumes are used only if there is not enough space to store the exported files on the volumes specified. If the device type associated with the specified device class is FILE, file names for scratch volumes are generated based on a time stamp. The default is Yes. |
No | Specifies that scratch volumes cannot be used for export. |
Enter the volume names. Export data will be written to these volumes. You must specify a volume name if you are not using scratch volumes and are not previewing. If you do not specify a volume name, then scratch volumes are used.
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 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:
|
||||||||||||
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 |
Specify the name of a file where a list of volumes used in a successful export operation will be stored.
Note: If you specify this parameter with an existing file name, the existing file will be overwritten with the new information.