To copy the server control information and client file data from export media to the Tivoli Storage Manager server, first complete the following fields and 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 imported for all nodes defined to the server. For sequential media: the device class used to access 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 import 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 versions. An active backup file version is the most recent backup version for a file that still exists on the client workstation. All other backup file versions are called inactive versions.
Select an option for File Data.
All | Specifies that Tivoli Storage Manager imports all backup versions of files, all archived files, and all files migrated from a user's local file system. |
None | Specifies that Tivoli Storage Manager imports no files, only server definitions. The default is None. |
Archive | Specifies that Tivoli Storage Manager imports only archived files. |
Backup | Specifies that Tivoli Storage Manager imports only backup versions, whether active or inactive. |
Backup active | Specifies that Tivoli Storage Manager imports only active backup versions. |
Allactive | Specifies that Tivoli Storage Manager 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 Tivoli Storage Manager imports 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 import operation, without actually importing server information. The Preview=Yes option will require that all export volumes be mounted to generate the preview statistics.
Select an option for Preview.
Yes | Specifies that you want to preview the results of the import operation, without actually importing files. Information on the number and types of objects imported, together with the number of bytes transferred are reported to the server console and the activity log. |
No | Specifies that the server information is to be imported without giving you a preview of the results. The default is No. |
Specify whether the recorded backup or archive dates for client node file versions are set to the values specified when the files were exported (Absolute), or are adjusted relative to the date of import (Relative).
Select an option for Date/Time.
Absolute | Specifies the date for file versions are set to the values specified when the files were exported. The default is Absolute. |
Relative | Specifies the date for file versions are adjusted to the date of import. |
Select whether objects (such as domains, policy sets) that exist on the server should be replaced by imported objects having the same name. Existing file spaces are not replaced. New file spaces are created when identical names are encountered.
Yes | Specifies that objects are to be replaced by the imported objects. |
No | Specifies that objects are not to be replaced by the imported objects. The default is No. |
Enter the volume names that are to be used for the import operation. Volumes must be imported in the same order as they were exported. This parameter is required. Possible values are:
volname | The name of one or more volumes that
contain the data to import. 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 that has the data for the import operation.
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 | Specify 1-32 alphanumeric characters. This field does not apply to Linux or OS/400 for PASE. |
||||||||||||||||
Removable file | Specify 1-6 alphanumeric characters. This field does not apply to OS/400 for PASE. |
||||||||||||||||
Server | Specify 1-250 alphanumeric characters. | ||||||||||||||||
Tape | Specify 1-6 alphanumeric characters. |
Select the device class from which import data is to be read. You cannot use the DISK or NAS device class. If the mount limit for the device class specified has already been reached (all drives are busy) when the import runs, Tivoli Storage Manager automatically cancels lower priority operations, such as reclamation, to make a mount point available for the import.
Specify whether client files are merged into existing file spaces on the target server (if they already exist) or if new file space names are generated. You can only use this option when you have a value entered in the To Server field.
Select an option. This parameter is optional. You can only use this option together with the To Server field.
Yes | You want imported data on the target server merged with the existing file space, if a file space with the same name already exists on the target server. |
No | You want a new file space name generated for the imported data on the target server if file spaces with the same name as that defined for the import data already exist. This is the default. |