To export server control information and client file data from the ADSM server to sequential media, first complete the following fields and then click Finish, or click Cancel to end the task. You can also view this information from the server console.
Specify the type of files that should be exported for all nodes defined to the server. The device class used by the file data is determined by the device class for the storage pool. If it is the same device class specified in this command, then two drives are needed to export server information. The mount limit value for the device class needs to be set to at least 2. The following descriptions mention active and inactive backup file copies. An active backup file copy is the most recent backup copy for a file that still exists on the client workstation. All other backup file copies are called inactive copies.
Select an option for File Data.
All | Specifies that ADSM exports all backup files, all archived files, and all files migrated from a user's local file system. |
None | Specifies that ADSM exports no files, only server definitions. The default is none. |
Archive | Specifies that ADSM exports only archived files. |
Backup | Specifies that ADSM exports only backup versions, whether active or inactive. |
Backup active | Specifies that ADSM exports only active backup versions. |
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 ADSM exports only files which have been migrated from a user's local file system (space-managed files). |
Specify whether you want to preview the results of the export operation, without actually exporting the server information.
Select an option for Preview.
Yes | Specifies that you want to preview the results of the export operation, without actually exporting server information. This command is used to determine how many bytes of data is transferred. If you select Yes, you do not need to specify device or volume parameters. |
No | Specifies that server information is to be exported without giving you a preview of the results. If you specify this value, you must specify a value for the Device Class parameter. The default is No. |
Selects the device class to which export data is to be written. This parameter is required unless you specified Preview=YES. You cannot specify the DISK device class. If the mount limit for the device class specified has already been reached (all drives are busy) when the export runs, ADSM automatically cancels lower priority operations, such as reclamation, to make a mount point available for the export.
Specify whether scratch volumes can be used for export.
Yes | Specifies that scratch volumes are to be used for export. If you include a list of volumes on the Volume Names parameter, 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. You must include a list of volumes on the Volume Names parameter to contain all of the export data. To determine how many volumes you may need, you can run the command specifying Preview=YES. |
Enter the names of one or more volumes used to contain the exported data.
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.