You can move files from one volume to another volume in the same or a different storage pool. The volumes can be onsite volumes or offsite volumes. During normal operations, you do not need to move data. You might need to move data in some situations, for example, when you need to salvage any readable data from a damaged TSM volume.
During the data movement process, the server:
During the data movement process, users cannot access the volume to restore or retrieve files, and no new files can be written to the volume.
Note: | Files in a copy storage pool do not move when primary files are moved. |
Task | Required Privilege Class |
---|---|
Move files from a volume in any storage pool to an available volume in any storage pool | System or unrestricted storage |
Move files from one volume to an available volume in any storage pool to which you are authorized | Restricted storage |
Moving files from one volume to other volumes in the same storage pool is useful:
See Deleting Storage Pool Volumes for information about deleting backed-up, archived, or space-managed data before you delete a volume from a storage pool.
If you want to force the removal of cached files, you can delete them by moving data from one volume to another volume. During the move process, the server deletes cached files remaining on disk volumes.
If you move data between volumes within the same storage pool and you run out of space in the storage pool before all data is moved from the target volume, then you cannot move all the data from the target volume. In this case, consider moving data to available space in another storage pool as described in Moving Data to Another Storage Pool.
You can move all data from a volume in one storage pool to volumes in another storage pool. When you specify a target storage pool that is different than the source storage pool, the server uses the storage hierarchy to move data if more space is required.
Note: | Data cannot be moved from a primary storage pool to a copy storage pool. Data in a copy storage pool cannot be moved to any other storage pool. |
You can move data from random access storage pools to sequential access storage pools. For example, if you have a damaged disk volume and you have a limited amount of disk storage space, you could move all files from the disk volume to a tape storage pool. Moving files from a disk volume to a sequential storage pool may require many volume mount operations if the target storage pool is collocated. Ensure that you have sufficient personnel and media to move files from disk to sequential storage.
You can move data from offsite volumes without bringing the volumes onsite. Processing of the MOVE DATA command for primary storage pool volumes does not affect copy storage pool files.
Processing of the MOVE DATA command for volumes in copy storage pools is similar to that of primary storage pools, with the following exceptions:
When you move files from a volume marked as offsite, the server does the following:
See Updating Storage Pool Volumes for information about updating the access mode of a storage pool volume.
If you need more storage space, define volumes or increase the maximum number of scratch volumes in the specified destination storage pool. See Defining Storage Pool Volumes for preparing volumes to be used for server storage.
See Requesting Information about Device Classes for requesting information about the mount limit value for the device class.
For example, to move the files stored in volume SERVER.STORAGE.POOL001 to any available volume in the BACKTAPE storage pool, enter:
move data server.storage.pool001 stgpool=backtape
When you move data from a volume, the server starts a background process and sends informational messages, such as:
+--------------------------------------------------------------------------------+ |ANR1140I Move Data process started for volume SERVER.STORAGE.POOL001 | |(process ID 5). | +--------------------------------------------------------------------------------+
The command may be run in the foreground on an administrative client by issuing the command with the WAIT=YES parameter.
Note: | A volume may not be totally empty after a move data operation completes. For example, the server may be unable to relocate one or more files to another volume because of input/output errors on the device or because errors were found in the file. You can delete the volume with DISCARDDATA=YES to delete the volume and any remaining files. The server then deletes the remaining files that had I/O or other errors. |
To request information on the data movement process, enter:
query process
Figure 32 shows an example of the report that you receive about the data movement process.
Figure 32. Information on the Data Movement Process
+--------------------------------------------------------------------------------+ |Process Process Description Status | | Number | |------- ------------------- ------------------------------------------- | | 5 Move Data Storage Pool BACKUPPOOL, Volume | | SERVER.STORAGE.POOL001, Target Pool BACKTAPE | | Moved Files: 0, Moved Bytes: 0, Unreadable | | Files: 0, Unreadable Bytes: 0 | +--------------------------------------------------------------------------------+
You can query the server for volume information to monitor the movement of data between volumes. For example, you can see how much data has moved from the source volume in a move operation (SERVER.STORAGE.POOL001) to available volumes in the BACKTAPE storage pool. Query volumes in all storage pools with names that begin with BACK by entering:
query volume * stgpool=back*
The following is an example of output from this command. This example shows that the BACKTAPE storage pool is filling as files are moved from SERVER.STORAGE.POOL001 to available volumes in the backup tape storage pool.
+--------------------------------------------------------------------------------+ |Volume Name Storage Device Estimated Pct Volume | | Pool Name Class Capacity Util Status | | (MB) | |-------------------- ----------- -------- --------- ----- -------- | |SERVER.STORAGE.POOL1 BACKUPPOOL DISK 40.0 36.2 On-Line | |DB0001 BACKTAPE CARTRIDGE 180.0 14.3 Filling | |DB0002 BACKTAPE CARTRIDGE 0.0 0.0 Empty | +--------------------------------------------------------------------------------+