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 ADSM 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, ADSM 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, ADSM 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, ADSM:
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 a Device Class" for requesting information about the mount limit value for the device class.
For example, to move the files stored in the /dev/vol3 volume to any available volume in the STGTMP1 storage pool, enter:
move data /dev/vol3 stgpool=stgtmp1
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 /dev/vol3 | |(process ID 32). | +--------------------------------------------------------------------------------+
The command may be run in the foreground on an administrative client by issuing the command with the WAIT=YES parameter.
To request information on the data movement process, enter:
query process
Figure 33 shows an example of the report that you receive about the data movement process.
Figure 33. Information on the Data Movement Process
+--------------------------------------------------------------------------------+ | | | Process Process Description Status | | Number | |-------- -------------------- ------------------------------------------------- | | 32 Move Data Volume /dev/vol3, (storage pool BACKUPPOOL), | | Target Pool STGTMP1, Moved Files: 49, Moved | | Bytes: 9,121,792, Unreadable Files: 0, | | Unreadable Bytes: 0. Current File (bytes): | | 3,522,560 | | | | Current output volume: VOL1. | +--------------------------------------------------------------------------------+
You can query the server for volume information to monitor the movement of data between volumes. For example, to see how much data has moved from the source volume in the move operation example, enter:
query volume /dev/vol3 stgpool=backuppool
Near the beginning of the move process, querying the volume from which data is being moved gives the following results:
+--------------------------------------------------------------------------------+ |Volume Name Storage Device Estimated %Util Volume | | Pool Name Class Name Capacity Status | | (MB) | |--------------- ----------- ---------- --------- ----- -------- | |/dev/vol3 BACKUPPOOL DISK 15.0 59.9 On-Line | | | +--------------------------------------------------------------------------------+
Querying the volume to which data is being moved (VOL1, according to the process query output) gives the following results:
+--------------------------------------------------------------------------------+ |Volume Name Storage Device Estimated %Util Volume | | Pool Name Class Name Capacity Status | | (MB) | |---------------- ----------- ---------- --------- ----- -------- | |VOL1 STGTMP1 8500DEV 4,944.0 0.3 Filling | +--------------------------------------------------------------------------------+
At the end of the move process, querying the volume from which data was moved gives the following results:
+--------------------------------------------------------------------------------+ |Volume Name Storage Device Estimated %Util Volume | | Pool Name Class Name Capacity Status | | (MB) | |---------------- ---------- ---------- --------- ----- -------- | |/dev/vol3 BACKUPPOOL DISK 15.0 0.0 On-Line | +--------------------------------------------------------------------------------+