Exporting server data

When you issue the EXPORT SERVER command, the server exports all server control information. You can also export file data information with the EXPORT SERVER command.

About this task

For example, you want to export server data to four defined tape cartridges, which the TAPECLASS device class supports. You want the server to use scratch volumes if the four volumes are not enough, and so you use the default of SCRATCH=YES.

Procedure

To issue this command, enter:

export server devclass=tapeclass
volumenames=dsm001,dsm002,dsm003,dsm004 filedata=all

During the export process, the server exports definition information before it exports file data information. This order ensures that definition information is stored on the first tape volumes. During the import process, if your goal is to copy only control information to the target server, only a minimum number of tapes must be mounted.

In the preceding example, the server exports:

Administrator definitions
Client node definitions
Policy domain, policy set, management class, and copy group definitions
Schedule definitions and client node associations
File space definitions
File space authorization rules
Important: If you are using wildcard characters when you are retrieving or restoring data, file space authorization rules might prohibit data from being included. Wildcard characters might be ignored if your client access rules also use wildcard characters when the SET ACCESS command is issued. See the Backup-Archive Clients Installation and User's Guide for your platform.
Backed up, archived, and space-managed files

When you are exporting active versions of client backup data, the server searches for active file versions in an active-data storage pool that is associated with a FILE device class, if such a pool exists.