Administrator's Guide


Importing Data from Sequential Media Volumes

Before you import data to a new target server, you must:

  1. Install ADSM on the target server. This step includes defining disk space for the database and recovery log.

    For information on installing ADSM, see ADSM Quick Start.

  2. Define server storage for the target server.

    Because each server operating system handles devices differently, ADSM does not export server storage definitions. Therefore, you must define initial server storage for the target server. ADSM must at least be able to use a drive that is compatible with the export media. This task can include defining libraries, drives, device classes, storage pools, and volumes. See the ADSM Administrator's Guide that applies to the target server.

After ADSM is installed and set up on the target server, a system administrator can import all server control information or a subset of server control information by specifying one or more of the following import commands:

This section guides you through the entire process of importing all server control information and file data from tape volumes to a new target server. This process includes:

After you understand how to import server control information and file data information, you can import any subset of data to the target server.

Step 1: Previewing Information before You Import Data

Before you import any data to the target server, preview each import command to determine what data you want to import to the target server. You can import all or a subset of export data from tapes.

When you set PREVIEW=YES, tape operators must mount export tape volumes so that the target server can calculate the statistics reported by the use of this parameter.

For example, to preview information for the IMPORT SERVER command, enter:

import server devclass=tapeclass preview=yes
volumenames=dsm001,dsm002,dsm003,dsm004

Figure 59 shows an example of the messages sent to the server console and the activity log.

Figure 59. Sample Report Created by Issuing Preview for an Import Server Command

+--------------------------------------------------------------------------------+
|ANR0402I Session 3 started for administrator SERVER_CONSOLE (Server).           |
|ANR1363I Import volume DSM001 opened (sequence number 1).                       |
|ANR0610I IMPORT SERVER started by SERVER_CONSOLE as process 2.                  |
|ANR0612I IMPORT SERVER: Reading EXPORT SERVER data from server ADSM exported    |
|05/07/1996 12:39:48.                                                            |
|ANR0639I IMPORT SERVER: Processing domain ENGPOLDOM.                            |
|ANR0640I IMPORT SERVER: Processing policy set ACTIVE in policy domain           |
|ENGPOLDOM.                                                                      |
|ANR0640I IMPORT SERVER: Processing policy set STANDARD in policy domain         |
|ENGPOLDOM.                                                                      |
|ANR0641I IMPORT SERVER: Processing management class STANDARD in domain          |
|ENGPOLDOM, set ACTIVE.                                                          |
|ANR0641I IMPORT SERVER: Processing management class MCENG in domain             |
|ENGPOLDOM, set STANDARD.                                                        |
|ANR0641I IMPORT SERVER: Processing management class STANDARD in domain          |
|ENGPOLDOM, set STANDARD.                                                        |
|ANR0643I IMPORT SERVER: Processing archive copy group in domain                 |
|ENGPOLDOM, set ACTIVE, management class STANDARD.                               |
|ANR0643I IMPORT SERVER: Processing archive copy group in domain ENGPOLDOM,      |
|set STANDARD, management class MCENG.                                           |
|ANR0643I IMPORT SERVER: Processing archive copy group in domain ENGPOLDOM,      |
|set STANDARD, management class STANDARD.                                        |
|ANR0642I IMPORT SERVER: Processing backup copy group in domain ENGPOLDOM,       |
|set ACTIVE, management class STANDARD.                                          |
|ANR0642I IMPORT SERVER: Processing backup copy group in domain ENGPOLDOM,       |
|set STANDARD, management class MCENG.                                           |
|ANR0642I IMPORT SERVER: Processing backup copy group in domain ENGPOLDOM,       |
|set STANDARD, management class STANDARD.                                        |
|ANR0638I IMPORT SERVER: Processing administrator DAVEHIL.                       |
|ANR0638I IMPORT SERVER: Processing administrator PENNER.                        |
|ANR0635I IMPORT SERVER: Processing node TOMC.                                   |
|ANR0636I IMPORT SERVER: Processing file space OS2 for node TOMC as file         |
|space OS1.                                                                      |
|ANR0636I IMPORT SERVER: Processing file space DRIVED for node TOMC as file      |
|space DRIVE1.                                                                   |
|ANR0636I IMPORT SERVER: Processing file space OS2VDISK for node TOMC as file    |
|space OS2VDIS1.                                                                 |
|ANR1365I Import volume DSM001 closed (end reached).                             |
|ANR1363I Import volume DSM002 opened (sequence number 2).                       |
|ANR1365I Import volume DSM002 closed (end reached).                             |
|ANR1363I Import volume DSM003 opened (sequence number 3).                       |
|ANR1365I Import volume DSM003 closed (end reached).                             |
|ANR1363I Import volume DSM004 opened (sequence number 4).                       |
|ANR1365I Import volume DSM004 closed (end reached).                             |
|ANR0617I IMPORT SERVER: Processing completed successfully.                      |
|ANR0620I IMPORT SERVER: Copied 1 domain(s).                                     |
|ANR0621I IMPORT SERVER: Copied 2 policy set(s).                                 |
|ANR0622I IMPORT SERVER: Copied 2 management class(es).                          |
|ANR0623I IMPORT SERVER: Copied 6 copy group(s).                                 |
|ANR0625I IMPORT SERVER: Copied 2 administrator(s).                              |
|ANR0626I IMPORT SERVER: Copied 1 node definition(s).                            |
|ANR0627I IMPORT SERVER: Copied 3 file space(s), 0 archive file(s) and 462       |
|backup file(s).                                                                 |
|ANR0629I IMPORT SERVER: Copied 8856358 bytes of data.                           |
|ANR0611I IMPORT SERVER started by SERVER_CONSOLE as process 2 has ended.        |
+--------------------------------------------------------------------------------+

Use the value reported for the total number of bytes copied to estimate if you have sufficient storage pool space on the server to store imported file data.

For example, Figure 59 shows that 8 856 358 bytes of data will be imported. Ensure that you have at least 8 856 358 bytes of available space in the backup storage pools defined to the server. You can use the QUERY STGPOOL and QUERY VOLUME commands to determine how much space is available in the server storage hierarchy.

In addition, the preview report shows that 0 archive files and 462 backup files will be imported. Because backup data is being imported, ensure that you have sufficient space in the backup storage pools used to store this backup data. See "Step 3: Tailoring Server Storage Definitions on the Target Server" for information on identifying storage pools on the target server.

For information on specifying the PREVIEW parameter, see "Using Preview before Exporting or Importing Data". For information on reviewing the results of a preview operation, see "Monitoring Export and Import Processes".

Step 2: Importing Definitions

Next, you want to import server control information, which includes:

However, do not import file data at this time, because some storage pools named in the copy group definitions may not exist yet on the target server.

Before you import server control information, do the following:

Then import the server control information from specified tape volumes. See "Importing Server Control Information".

Determining Whether to Replace Existing Definitions

By using the REPLACEDEFS parameter, you can specify whether to replace existing definitions on the target server when ADSM encounters an object with the same name during the import process.

For example, if a definition exists for the ENGPOLDOM policy domain on the target server before you import policy definitions, then you must specify REPLACEDEFS=YES to have ADSM replace the existing definition with the data from the export tape.

Definitions that can be replaced include administrator, client node, policy, or schedule definitions. The default is to not replace existing definitions on the target server.

Understanding How ADSM Imports Active Policy Sets

When ADSM imports policy definitions, the following objects are imported to the target server:

If ADSM encounters a policy set named ACTIVE on the tape volume during the import process, it uses a temporary policy set named $$ACTIVE$$ to import the active policy set.

After $$ACTIVE$$ is imported to the target server, ADSM activates this policy set. During the activation process, the server validates the policy set by examining the management class and copy group definitions.

ADSM reports on the following conditions, which result in warning messages during validation:

After each $$ACTIVE$$ policy set has been activated, ADSM deletes that $$ACTIVE$$ policy set from the target server. To view information about active policy on the target server, you can use the following commands:

Results from issuing the QUERY DOMAIN command show the activated policy set as $$ACTIVE$$. ADSM uses the $$ACTIVE$$ name to show you that the policy set which is currently activated for this domain is the policy set that was active at the time the export was performed.

Directing Import Messages to an Output File

The information generated by the validation process can help you define a storage hierarchy that supports the storage destinations currently defined in the import data.

You can direct import messages to an output file to capture any error messages that are detected during the import process by starting an administrative client session in console mode before you invoke this import command.

For example, to direct messages to an output file named IMPSERV.OUT, enter:

> dsmadmc -consolemode -outfile=impserv.out

Importing Server Control Information

Now you are ready to import the server control information. Based on the information generated during the preview operation, you know that all definition information has been stored on the first tape volume named DSM001. Specify that this tape volume can be read by a device belonging to the TAPECLASS device class.

From an administrative client session or from the server console, enter:

import server filedata=none devclass=tapeclass
volumenames=dsm001

Step 3: Tailoring Server Storage Definitions on the Target Server

After you import definition information, use the reports generated by the import process to help you tailor storage for the target server.

To tailor server storage definitions on the target server, complete the following steps:

  1. Identify any storage destinations specified in copy groups and management classes that do not match defined storage pools:

  2. If storage destinations for management classes and copy groups in the ACTIVE policy set refer to storage pools that are not defined, do one of the following:

Depending on the amount of client file data that you expect to import, you may want to examine the storage hierarchy to ensure that sufficient storage space is available. Storage pools specified as storage destinations by management classes and copy groups may fill up with data. For example, you may need to define additional storage pools to which data can migrate from the initial storage destinations.

Step 4: Importing File Data Information

After you have defined the appropriate storage hierarchy on the target server, you can import file data from the tape volumes. File data includes file space definitions and authorization rules. You can request that file data be imported in any of the following groupings of files:

Before you import file data information:

Then you can import file data to the target server.

Understanding How Duplicate File Spaces Are Handled

When ADSM imports file data information, it imports any file spaces belonging to each specified client node. If a file space definition already exists on the target server for the node, ADSM does not replace the existing file space name.

If ADSM encounters duplicate file space names when it imports file data information, it creates a new file space name for the imported definition by replacing the final character or characters with a number. A message showing the old and new file space names is written to the server console and to the activity log.

For example, if the C_DRIVE and D_DRIVE file space names reside on the target server for node FRED and on the tape volume for FRED, then the server imports the C_DRIVE file space as C_DRIV1 file space and the D_DRIVE file space as D_DRIV1 file space, both assigned to node FRED.

Deciding Whether to Use a Relative Date When Importing File Data

When you import file data, you can keep the original creation date for backup versions and archive copies, or you can specify that ADSM use an adjusted date.

Because tape volumes containing exported data might not be used for some time after the export operation that created them, the original dates defined for backup versions and archive copies may be old enough that files are expired immediately by policy when the data is imported to the target server.

To prevent backup versions and archive copies from being expired immediately, specify DATES=RELATIVE on the IMPORT NODE or IMPORT SERVER commands to adjust for the elapsed time since the files were exported to tape.

For example, assume that data exported to tape includes an archive copy archived five days prior to the export operation. If the tape volume resides on the shelf for six months before the data is imported to the target server, ADSM resets the archival date to five days prior to the import operation.

If you want to keep the original backup and archive dates set for backup versions and archive copies, then use DATES=ABSOLUTE, which is the default. If you use the absolute value, then any files whose retention period has passed will be expired shortly after they are imported to the target server.

Issuing an Import Server or Import Node Command

You can import file data, either by issuing the IMPORT SERVER or IMPORT NODE command. When you issue either of these commands, you can specify which type of files should be imported for all client nodes specified and found on the export tapes. You can specify any of the following values to import file data:

All
Specifies that all active and inactive versions of backed up files, archive copies of files, and space-managed files for specified client nodes are imported to the target server

None
Specifies that no files are imported to the target server; only client node definitions are imported

Archive
Specifies that only archive copies of files are imported to the target server

Backup
Specifies that only backup copies of files, whether active or inactive, are imported to the target server

Backupactive
Specifies that only active versions of backed up files are imported to the target server

Allactive
Specifies that only active versions of backed up files, archive copies of files, and space-managed files are imported to the target server

Spacemanaged
Specifies that only files that have been migrated from a user's local file system (space-managed files) are imported

For example, suppose you want to import all backup versions of files, archive copies of files, and space-managed files to the target server. You do not want to replace any existing server control information during this import operation. Specify the four tape volumes that were identified during the preview operation. These tape volumes can be read by any device in the TAPECLASS device class. To issue this command, enter:

import server filedata=all replacedefs=no
devclass=tapeclass volumenames=dsm001,dsm002,dsm003,dsm004

Considerations When Importing Data

You can use an import command to copy a subset of the information on export tapes to the target server. For example, if a tape was created with EXPORT SERVER, you can import only node information from the tape by using IMPORT NODE.

While ADSM allows you to issue any import command, data cannot be imported to the server if it has not been exported to tape. For example, if a tape is created with the EXPORT POLICY command, an IMPORT NODE command will not find any data on the tape because node information is not a subset of policy information.

Table 19 shows the commands you can use to import a subset of exported information to a target server.

Table 19. Importing a Subset of Information from Tapes
If tapes were created with this export command: You can issue this import command: You cannot issue this import command:
EXPORT SERVER

IMPORT SERVER
IMPORT ADMIN
IMPORT NODE
IMPORT POLICY

--

EXPORT NODE

IMPORT NODE
IMPORT SERVER

IMPORT ADMIN
IMPORT POLICY

EXPORT ADMIN

IMPORT ADMIN
IMPORT SERVER

IMPORT NODE
IMPORT POLICY

EXPORT POLICY

IMPORT POLICY
IMPORT SERVER

IMPORT ADMIN
IMPORT NODE

Recovering from Errors during the Import Process

During import processing, the server may encounter invalid data due to corruption during storage on tape or in the database prior to the export operation. If invalid data is encountered during an import operation, the server does the following:

The server reports on the affected objects to the server console and the activity log during import and export operations. You should query these objects when the import process is complete to see if they reflect information that is acceptable to you.

Each time you run the IMPORT NODE or IMPORT SERVER command with the FILEDATA parameter equal to a value other than NONE, ADSM creates a new file space and imports data to it. This process ensures that the current import does not overwrite data from a previous import. For information on how ADSM handles duplicate file spaces, see "Understanding How Duplicate File Spaces Are Handled".

A file space definition may already exist on the target server for the node. If so, an administrator with system privilege can issue the DELETE FILESPACE command to remove file spaces that are corrupted or no longer needed. For more information on the DELETE FILESPACE command, refer to the ADSM Administrator's Reference.

Renaming a File Space

An imported file space can have the same name as a file space that already exists on a client node. In this case, the server does not overlay the existing file space, and the imported file space is given a new system generated file space name. This new name may match file space names that have not been backed up and are unknown to the server. In this case, you can use the RENAME FILESPACE command to rename the imported file space to the naming convention used for the client node.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]