The MOVE-SAVE-FILES statement enables both save files and node save files to be moved conveniently from disk or Net-Storage to tape. Moreover, from HSMS V12.0A save files can also be moved from tape to public disk or Net-Storage. The statement combines the steps copying and deletion of a number of save files or node save files from original storage. It is thus also used to reorganize a disk or free tapes (only HSMS as of V12.0A).
In a move request several save files are transferred from one storage to another:
- Save files can be moved from disk, Net-Storage or tape to public disk, Net-Storage or another tape
- Node save files can be transferred from disk to tape.
At the same time, MOVE-SAVE-FILES deletes the save files no longer required from the original storage. As no shadow archives are supported with backups to disk or Net-Storage, the save files are implicitly copied into the shadow archive when they are moved to tape (as with a direct save to tape). An option is available to suppress copying to the shadow archive.
After a save file or node save file has been moved, the same status is achieved as for an original backup directly to the new storage.
A save file or node save file is always copied in its entirety (a reduction as with explicit copying is not possible). It thus also contains all Cataloged-Not-Saved (CNS) entries of the original save file. A restore from the backup archive provides the same result after the move as before.
Note
A direct backup to tape (for this archive) may only be performed after the move request has been completed. Otherwise, problems occur during the move because the continuation on tape would no longer correspond to the sequence of the save versions.
Selecting files for moving
The following criteria are available for selecting the save files to be moved:
Either save files on disk storages (private, public disks and Net-Storage) or save files on tapes are to be moved:
FROM-STORAGE = *DISK(...)FROM-STORAGE = *S2-STORAGE-LEVELMinimum retention time of the save or node save files on disk:
All save or node save files which have been residing on disk for at least the specified number of days or longer are moved.FROM-STORAGE=*DISK(MINIMUM-DAYS-ON-S1=tage, ...)Size of the disk storage space to be released by the move:
Only as many save or node save files are moved from disk to another storage as are required to release the specified number of 2-Kbyte blocks by the move.FROM-STORAGE=*DISK(... ,RELEASE-PAGES=pam-seiten)
Creating or continuing moved save files
- In the case of backup archives with single SVID structure, the save files are created anew when they are moved (default). A new save file is created on tape for each moved save file.
- A number of save files on disk or Net-Storage are combined into one save file. In the case of backup archives with several SVID structure, the last save file created on S2 can be continued. This option is not available if a backup to tape took place after the backup to disk.
- After the move the new save versions have the date of the relevant old ones incremented by 1. This ensures that the sequence of all save versions is guaranteed. The save files are stored in the archive directory with the date of the MOVE-SAVE-FILES time.
For the process from tape to disk, each save version is moved to a separate save file on disk (the save file id (SFID) of the new save file will be the previous save version id (SVID) with its timestamp plus one second).
For the process from S2-storage level to S2-storage level, the result depends on the type of the archive:
- For several-svid archives a new save file is created. All save versions from S2-storage-level are moved to it. Each copy of the save versions receives a SVID equal to the original SVID plus one second.
- For single-svid archives each save version is copied to a separate save file. The copy of save version has a SVID equal to the original SVID plus one second. Each new save file has a SFID with current time stamp.