To import client node definitions from the Tivoli Storage Manager server to sequential media, first complete the following fields and then click Finish, or click Cancel to end the task.
The imported nodes are associated with the same policy domain as they were on the source server, if you specify a domain and that policy domain exists on the target server. Otherwise, imported nodes are associated with the STANDARD policy domain on the target server.
Enter the list of client node names for which you want to import client node information.
Enter the list of file space names for which data is to be imported.
Enter the file spaces that are known to the server to use Unicode.
Enter the hexadecimal representation of the file space names in UTF-8 format.
Enter one or more policy domain names to limit the import only to nodes in these domains. The domains must have been exported with the node definitions from the source server.
Select a device class. Import data will be read from a device associated with this device.
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 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 a fully qualified name string that is valid for your platform, for example:
|
||||||||||||||||
Optical | Specify 1-32 alphanumeric characters.
Does not apply to Linux or PASE. |
||||||||||||||||
Removable file | Specify 1-6 alphanumeric characters.
Does not apply to PASE. |
||||||||||||||||
Server | Specify 1-250 alphanumeric characters. | ||||||||||||||||
Tape | Specify 1-6 alphanumeric characters. |
Select the type of files to import for all nodes specified and found on the export media. This parameter is optional. The default is None.
None | Only node definitions are imported. The server does not import any files. |
All | The server imports all backup versions of files, all archived files, and all space-managed files (files migrated from a user's local file system). This includes both Unicode and non-Unicode file spaces. |
Archive | The server imports only archived files. |
Backup | The server imports only backup versions, whether active or inactive. |
Backup active | The server imports only active backup versions. |
Allactive | The server imports all active backup versions of files, all archived files, and all space-managed files. |
Space managed | The server imports only space-managed files (files migrated from a user's local file system). |
Select an option for Preview. The default is No.
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. |
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). The default is Absolute.
Absolute | The date for file copies are set to the values specified when the files were exported. |
Relative | The date for file copies are adjusted to the date of import. |
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. The default is No.
Yes | Replace nodes that have the same names as imported nodes. |
No | Do not replace nodes that have the same names as imported nodes. |
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. The default is No.
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. When you select Yes as an option, you must also select Absolute in the Dates field. |
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. |