Administrator's Reference

EXPORT NODE (Copy Client Node Information to Sequential Media)

Use the EXPORT NODE command to export client node definitions from an ADSM server to sequential media. Each client node definition includes:

Optionally, the EXPORT NODE command exports node data information such as:

This command generates a background process that can be canceled with the CANCEL PROCESS command. If an EXPORT NODE background process is canceled, the sequential media holding the exported data are incomplete and should not be used for importing data. To display information on background processes, use the QUERY PROCESS command.

You can use the QUERY ACTLOG command to view the actual status information indicating the size and the success or failure of the export operation.

Privilege Class

To issue this command, you must have system privilege.

Syntax

>>-EXPort Node---+------------------+--------------------------->
                 |  .-,----------.  |
                 |  V            |  |
                 '----nodename---+--'
 
>---+-----------------------------------------+----------------->
    |            .-,----------------------.   |
    |            V                        |   |
    '-FILESpace=-----+---------------+----+---'
                     '-filespacename-'
 
>---+------------------------------------+---------------------->
    |          .-,-------------------.   |
    |          V                     |   |
    '-DOmains=-----+------------+----+---'
                   '-domainname-'
 
    .-FILEData--=--None--------------.
>---+--------------------------------+-------------------------->
    '-FILEData--=--+-ALl----------+--'
                   +-None---------+
                   +-ARchive------+
                   +-Backup-------+
                   +-BACKUPActive-+
                   +-ALLActive----+
                   '-SPacemanaged-'
 
     .-Preview--=--No----------------.
>----+-------------------------------+-------------------------->
     |         (1) (2)               |
     '-Preview-----------=--+-No--+--'
                            '-Yes-'
 
>----+-----------------------------+---------------------------->
     |          (1)                |
     '-DEVclass------=devclassname-'
 
    .-Scratch--=--Yes-----------.
>---+---------------------------+------------------------------->
    |         (2)               |
    '-Scratch-------=--+-Yes-+--'
                       '-No--'
 
                            .-,--------.
                 (2)        V          |
>----VOLumenames------=--+---volname---+--+--------------------->
                         '-FILE:filename--'
 
>---+---------------------------+------------------------------><
    '-USEDVolumefile--=filename-'
 

1

If PREVIEW=NO, a device class must be specified.

2

If PREVIEW=NO and SCRATCH=NO, one or more volumes must be specified.

Parameters

nodename

Specifies a list of client node names for which information is to be exported. This parameter is optional.

The items in the list are separated by commas, with no intervening spaces. You can use pattern-matching expressions to specify names. All matching nodes are included in the list.

FILESpace=filespacename

Specifies a list of file space names for which data is to be exported. This parameter is optional. The items in the list are separated by commas, with no intervening spaces. You can use a pattern-matching expression to specify a name. All matching names are included in the list.

DOmains=domainname

Specifies a list of policy domain names from which nodes should be exported. This parameter is optional. The items in the list are separated by commas, with no intervening spaces. For a node to be exported it must belong to one of the specified domains. You can use a pattern-matching expression to specify a name. All matching domains are included in the list.

FILEData=filedatatype

Specifies the type of files that should be exported for all nodes defined to the server. This parameter is optional. The default value is NONE.

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 node information. The mount limit value for the device class needs to be set to at least 2.
Note:If client nodes registered as TYPE=SERVER are being exported, FILEDATA=ALL, FILEDATA=ARCHIVE, or FILEDATA=ALLACTIVE must be specified.

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. Possible values are:

ALl

Specifies that ADSM exports all backup versions of files, all archived files, and all files migrated from a user's local file system.

None

Specifies that no files are to be exported; only node definitions are to be exported.

ARchive

Specifies that only archived files are to be exported .

Backup

Specifies that only backup versions, whether active or inactive, are to be exported.

BACKUPActive

Specifies that only active backup versions are to be exported.

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.

SPacemanaged

Specifies that only files which have been migrated from a user's local file system (space-managed files) are to be exported.

Preview=value

Specifies whether you want to preview the results of the export operation, without actually exporting information. You can use this parameter to preview how many bytes of data are transferred, allowing you to determine how many volumes will be required to hold the data. This parameter is optional. The default value is NO. Possible values are:

No

Specifies that the node information is to be exported. If you specify this value, you must specify a value for the DEVCLASS parameter.

Yes

Specifies that you want to preview the results of the export operation, without actually exporting node information. Information on the number and types of objects exported, together with the number of bytes transferred are reported to the server console and the activity log. If you specify this value, you do not need to specify device or volume parameters.

DEVclass=devclassname

Specifies the device class to which export data is to be written. 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.

Scratch=scratchvalue

Specifies whether scratch volumes can be used for export. The default is SCRATCH=YES. Possible values are:

Yes

Specifies that scratch volumes are to be used for export. If you include a list of volumes on the VOLUMENAMES 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.

No

Specifies that scratch volumes cannot be used for export. To determine how many volumes you may need, you can run the command specifying PREVIEW=YES.

VOLumenames=volumespec

Specifies the volumes that are to be used to contain exported data. This parameter is optional. You must specify a volume name if SCRATCH=NO and PREVIEW=NO. If you do not specify a volume name, then scratch volumes are used.

Use the following naming conventions when specifying volumes for each device type.

FILE

Specify any supported file name, directory, or fully qualified directory; for example, /exadata/mt1.

OPTICAL, WORM, WORM12, or WORM14

Specify 1-32 alphanumeric characters.

SERVER

Specify 1-250 alphanumeric characters.

3570, 3590, 4MM, 8MM, CARTRIDGE, DLT, DTF, GENERICTAPE, or QIC

Specify 1-6 alphanumeric characters.

Possible values are:

volname

Specifies the names 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.

For example, to use volumes TAPE01, TAPE02, TAPE03, specify the following:

VOLUMENAMES=TAPE01,TAPE02,TAPE03

FILE:filename

Specifies the name of a file that contains a list of volumes to use to create the export operation. In the file, each volume name must be on a separate line. Blank lines and comments lines that begin with an asterisk are ignored.

For example, to use volumes TAPE01, TAPE02, and TAPE03, create a file named TAPEVOL that contains these lines:

TAPE01
TAPE02
TAPE03

You can then specify the volumes for the command as follows:

VOLUMENAMES=FILE:TAPEVOL

USEDVolumefile=filename

Specifies the name of a file where a list of volumes used in a successful export operation will be stored. See the VOLUMENAMES parameter for volume naming conventions. This parameter is optional.

If the file you specify is created without errors, it can be used as input to the IMPORT command on the VOLUMENAMES=FILE:filename parameter. This file will contain comment lines with the date and time the export was done, and the command issued to create the export.
Note:If you specify this parameter with an existing filename, the existing file will be overwritten with the new information.

Examples

Task

Export the node definitions and active backup data for all client nodes defined in the STANDARD policy domain. Export this information to scratch volumes that belong to the MENU2 device class.

The number and type of objects exported are reported to the system console and in the activity log.

Command:
export node domains=standard filedata=backupactive devclass=menu2 scratch=yes

Related Commands

Table 97. Commands Related to EXPORT NODE
Command Description
CANCEL PROCESS Cancels a background server process.
EXPORT ADMIN Copies administrative information to external media.
EXPORT POLICY Copies policy information to external media.
EXPORT SERVER Copies all or part of the server to external media.
IMPORT NODE Restores client node information from external media.
QUERY ACTLOG Searches for and displays messages from the server activity log.
QUERY PROCESS Displays information about one or all background server processes.


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