MOVE NODEDATA (Move data from selected file spaces of a single node)

Use this command to move data for selected file spaces belonging to a single node.

Privilege class

To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the source storage pool. If your authorization is restricted storage privilege and you intend to move data to another storage pool, you must also have the appropriate authority for the destination storage pool.

Syntax


>>-MOVe NODEdata--node_name--FROMstgpool--=--source_pool_name--->

>--+-------------------------------------+---------------------->
   '-TOstgpool--=--destination_pool_name-'   

>--+-----------------------------------+------------------------>
   |               .-,---------------. |   
   |               V                 | |   
   '-FIlespace--=----file_space_name-+-'   

>--+---------------------------------------------+-------------->
   |                  .-,----------------------. |   
   |                  V                        | |   
   '-UNIFILESpace--=----unicode_filespace_name-+-'   

>--+-----------------------------------+------------------------>
   |          .-,--------------------. |   
   |          V                      | |   
   '-FSID--=----filespace_identifier-+-'   

   .-Type--=--ANY--------------.   
>--+---------------------------+-------------------------------->
   '-Type--=--+-ANY----------+-'   
              +-Backup-------+     
              +-ARchive------+     
              '-SPacemanaged-'     

   .-MAXPRocess--=--1-------------.  .-Wait--=--No------.   
>--+------------------------------+--+------------------+------->
   '-MAXPRocess--=--num_processes-'  '-Wait--=--+-No--+-'   
                                                '-Yes-'     

                               (1)     
   .-RECONStruct--=--No or Yes-----.   
>--+-------------------------------+---------------------------><
   '-RECONStruct--=--+-No--+-------'   
                     '-Yes-'

Notes:

The default is NO if either the source or target storage pool is random access. The default is YES if both the source and target storage pools are sequential access.

Parameters

node_name (Required)

Specifies the node name related to the data that is moved with this command. Separate multiple names with commas and no intervening spaces. You can use wildcard characters to specify names.

FROMstgpool (Required)

Specifies the name of a sequential-access storage pool that contains data to be moved. This storage pool must be in the NATIVE or NONBLOCK data format.

TOstgpool

Specifies the name of a storage pool to which data will be moved. This storage pool must be in the NATIVE or NONBLOCK data format. This parameter is optional and does not apply when the source storage pool is a copy storage pool or an active-data pool. That is, if the source storage pool is a copy storage pool the destination must be the same copy storage pool. Similarly, if the source storage pool is an active-data pool, the destination must be the same active-data pool. If a value is not specified, data is moved to other volumes within the source pool.

Important: If you are moving data within the same storage pool, there must be volumes available that do not contain the node data you are moving. That is, the server cannot use volumes that contain the data to be moved as destination volumes.

FILespace

Specifies the name of the non-Unicode filespace that contains data to be moved. Separate multiple names with commas and no intervening spaces. You can use wildcard characters to specify names. This parameter is optional. If you do not specify a value for this parameter and values for UNIFILESPACE or the FSID or both, non-Unicode file spaces are not moved.

UNIFILESpace

Specifies the name of the Unicode filespace that contains data to be moved. Separate multiple names with commas and no intervening spaces. You can use wildcard characters to specify names. This parameter is optional. If you do not specify a value for this parameter and values for FILESPACE or the FSID or both, non-Unicode file spaces are not moved.

FSID

Specifies file space identifiers (FSIDs) for the file spaces to be moved. Separate multiple names with commas and no intervening spaces. This parameter is optional.

Type

Specifies the type of files to be moved. This parameter is optional. The default value is ANY. If the source storage pool is an active-data pool, the only valid values are ANY and BACKUP. However, only the active versions of backup data are moved if TYPE=ANY. Possible values are:

ANY: Specifies that all types of files are moved.
Backup: Specifies that backup files are moved.
ARchive: Specifies that archive files are moved. This value is not valid for active-data pools.
SPacemanaged: Specifies that space-managed files (files that were migrated by an IBM Spectrum Protect™ for Space Management client) are moved. This value is not valid for active-data pools.

MAXPRocess

Specifies the maximum number of parallel processes to use for moving data. This parameter is optional. You can specify a value from 1–999, inclusive. The default value is 1. Increasing the number of parallel processes should improve throughput.

When determining this value, consider the number of logical and physical drives that can be dedicated to this operation. To access a sequential access volume, IBM Spectrum Protect uses a mount point and, if the device type is not FILE, a physical drive. The number of available mount points and drives depends on other IBM Spectrum Protect system activity and on the mount limits of the device classes for the sequential access storage pools that are involved in the move. Each process needs a mount point for storage pool volumes, and, if the device type is not FILE, each process also needs a drive.

Wait

Specifies whether to wait for the server to complete processing this command in the foreground. This parameter is optional. The default value is No. Possible values are:

No

Specifies that the server processes this command in the background. You can continue with other tasks while the command is being processed.

The server displays messages that are created from the background process either in the activity log or the server console, depending on where messages are logged.

To cancel a background process, use the CANCEL PROCESS command. If a background process is canceled, some files may have already moved before the cancellation.

Yes

Specifies that the server processes this command in the foreground. You wait for the command to complete before continuing with other tasks. The server then displays the output messages to the administrative client when the command completes.

Restriction: You cannot specify WAIT=YES from the server console.

RECONStruct

Specifies whether to reconstruct file aggregates during data movement. Reconstruction removes empty space that has accumulated during deletion of logical files from an aggregate. This parameter is optional. If both the source and target storage pools are sequential access, the default value is YES. If either the source or target storage pool is random access, the default is NO.

The parameter is not available or is ignored if any of the following conditions are true:

The data format is NETAPPDUMP, CELERRADUMP, or NDMPDUMP.
The data is in a storage pool that is configured for data deduplication.
The target storage pool for the data movement is configured for data deduplication.

Attention: Reconstruction removes inactive backup files in active-data pools. If you specify RECONSTRUCT=NO when moving the data in an active-data pool that is not configured for data deduplication, inactive backup files remain in the storage pool.

Possible values are:

No: Specifies that reconstruction of file aggregates will not be performed during the move.
Yes: Specifies that reconstruction of file aggregates will be performed during the move. You may only specify this option when both the source and the target storage pools are sequential-access.

Example: Move a node's non-Unicode and Unicode data

Move data for node TOM in storage pool TAPEPOOL. Restrict movement of data to files in non-Unicode file spaces as well as Unicode file spaces, \\jane\d$. Data should be moved to disk storage pool BACKUPPOOL.

move nodedata tom
 fromstgpool=tapepool tostgpool=backuppool
 filespace=* unifilespace=\\jane\d$

Example: Move all node data from tape storage pools to a disk storage pool

Move all data for node SARAH, from all primary sequential-access storage pools (for this example, TAPEPOOL*) to DISKPOOL. To obtain a list of storage pools that contain data for node SARAH, issue either of the following QUERY OCCUPANCY or SELECT commands:

query occupancy sarah

SELECT * from OCCUPANCY where node_name='sarah'

Attention: For this example assume that the results were TAPEPOOL1, TAPEPOOL4, and TAPEPOOL5.

move nodedata sarah
 fromstgpool=tapepool1 tostgpool=DISKPOOL

move nodedata sarah
 fromstgpool=tapepool4 tostgpool=DISKPOOL

move nodedata sarah
 fromstgpool=tapepool5 tostgpool=DISKPOOL

Example: Move a node's non-Unicode and Unicode file spaces

The following is an example of moving non-Unicode and Unicode file spaces for a node. For node NOAH move non-Unicode filespace \\servtuc\d$ and Unicode file space \\tsmserv1\e$ that has a filespace ID of 2 from sequential access storage pool TAPEPOOL to random access storage pool DISKPOOL.

move nodedata noah
 fromstgpool=tapepool tostgpool=diskpool
 filespace=\\tsmserv1\d$ fsid=2