HSMS provides for system backups and application backups and in both cases offers the options of full backup, incremental backup and partial backup. HSMS can additionally be used to reorganize the data residing on disk storages.
This type of backup uses backup archives either user archives or system backup archives.
System backups are the prerogative of the HSMS administrator.
Backups may be performed by any user.
A nonprivileged user can back up files to any other user archive if:
the archive is public (i.e. was installed with ACCESS=*WRITE)
the files belong to the archive owner and the job submitter is the co-owner of the files.
the foreign archive and its directories have co-ownership. These can be used as though they were the user’s own. Only archive management, i.e. changing archive properties or deleting obsolete save files, is excluded.
Nonprivileged users can restore files and job variables belonging to their own user ID as well as files and job variables of which they are co-owners:
from his own backup archives or from foreign archives/directories, which he has access to due to co-ownership.
from a public backup archive
The measures to be taken by the HSMS administrator in connection with data backup are described in section "Data backup and migrated files".
The archive owner and the HSMS administrator can use the SAVE-FILE operand of the BACKUP-FILES statement to define whether
the files to be saved are to be written to the archive’s standard save file (*STD), if permitted by the archive definition
a new save file is to be created (*NEW)
an existing save file is to be updated (*CONTINUE).
Files and job variables are backed up using the HSMS statement BACKUP-FILES.
Figure 8: Backup using BACKUP-FILES
The files which are to be stored, which must reside on pubsets, Net-Storage or private disk, can be selected according to
the volume on which they reside (SUPPORT)
the file type for Net-Storage files (FILE-TYPE=*BS2000 / *NODE-FILE)
the backup class assigned to them
(Operand MAXIMUM-BACKUP-CLASS).a list of file names (see section "Selection of BS2000 files, job variables and node files").