Examples

This section provides examples dealing with the following subjects:

• The HSMS administrator performs a central full backup of the local BS2000-UFS and several passive workstations

• The HSMS administrator restores a node file to a passive workstation

• A nonprivileged user restores selected file trees to the local BS2000-UFS

• The HSMS administrator archives the file tree of a passive workstation

The HSMS administrator performs a central full backup of the local BS2000-UFS and several passive workstations

Perform preparatory activities:

/START-HSMS
//MODIFY-NODE-PARAMETERS -  ———————————————————————————————————————————  (1) 
//   NODE-ID=*BS2000-UFS, -
//   HSMS-CONTROL=*YES(SYSNODEBACKUP=*STD)
//MODIFY-NODE-PARAMETERS -  ———————————————————————————————————————————  (2) 
//   NODE-ID=WORKSTA1, -
//   HSMS-CONTROL=*YES(SYSNODEBACKUP=*STD)
//MODIFY-NODE-PARAMETERS -
//   NODE-ID=WORKSTA2, -
//   HSMS-CONTROL=*YES(SYSNODEBACKUP=*STD)
//MODIFY-NODE-PARAMETERS -
//   NODE-ID=WORKSTA3, -
//   HSMS-CONTROL=*YES(SYSNODEBACKUP=*STD)
//CREATE-ARCHIVE -  ———————————————————————————————————————————————————  (3) 
//   ARCHIVE-NAME=CENTRAL, -
//   ALLOWED-USAGE=*NODEBACKUP, -
//   USER-ACCESS=*ALL-USERS, -
//   DIRECTORY-NAME=NODEBACKUP.CENTRAL.DIR, -
//   RETENTION-PERIOD=150, -
//   S2-DEVICE-TYPE='TAPE-C4', -
//   OPERATION-CONTROL=*PARAMETERS(PARALLEL-RUNS=2)
//MODIFY-ARCHIVE -  ———————————————————————————————————————————————————  (4) 
//   ARCHIVE-NAME=CENTRAL, -
//   VOLUMES=*ADD(VOLUMES=(VOLUM1,VOLUM2,...))
//MODIFY-HSMS-PARAMETERS -  ———————————————————————————————————————————  (5) 
//   VALID-PERIOD=*PERMANENT, -
//   DEFAULT-HSMS-STORAGE=*PARAMETERS(SYSNODEBACKUP=CENTRAL)
//END

(1)	The local BS2000-UFS is placed under HSMS management. The default system archive SYSNODEBACKUP is assigned to this local UFS.
(2)	The workstations WORKSTA1, WORKSTA2 and WORKSTA3 are placed under HSMS management. The default system archive SYSNODEBACKUP is assigned to them. Backup takes place using NFS.
(3)	The archive CENTRAL is set up as a public archive for backing up node files with read privilege. The node files which are backed up cannot be deleted for 150 days. Magnetic tape cartridges are specified as the target volumes in order to use a robotic archive connected to the system. Two backup tasks are to execute simultaneously. Note In order for nonprivileged users to use the directory file, it must be shareable (USER-ACCESS=*ALL-USERS or *SPECIAL).
(4)	Magnetic tape cartridges are added to the pool of free volumes of the CENTRAL archive.
(5)	The CENTRAL archive is defined as the global default system archive for backing up node files.

Create a list of the path names which are to be backed up:

Contents of the SAM file "PATH.LIST":

 ——————————————————————————————————————————————————————————————————————  (6) 
<bs2000-ufs path-name1>
<bs2000-ufs path-name2>
<bs2000-ufs ...>
WORKSTA1:/<path-name2>
WORKSTA1:/...
WORKSTA2:/<path-name1>
WORKSTA2:/<path-name2>
WORKSTA2:/...
WORKSTA3:/<path-name1>
WORKSTA3:/<path-name2>
WORKSTA3:/...

(6)	Since only a single path name can be specified in the BACKUP-NODE-FILES statement, the HSMS administrator creates the SAM file PATH.LIST, which contains the path names of the node files to be backed up.

Start full backup:

/START-HSMS
//BACKUP-NODE-FILES -  ————————————————————————————————————————————————  (7) 
//   PATH-NAMES=*FROM-FILE(LIST-FILE-NAME=PATH.LIST), -
//   ARCHIVE-NAME=*SYSNODEBACKUP, -
//   SELECT-FILES=*ALL-FILES(FROM=LATEST-BACKUPS-OR-S0), -  ———————————  (8) 
//   OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=FULL.BACKUP)
//END

(7)

The path names of the node files which are to be backed up are read from the PATH.LIST file. A full backup is made to the default system archive *SYSNODEBACKUP.

(8)

For performance reasons, the operand FROM=*LATEST-BACKUPS-OR-S0 is specified for the backup. Node files which have been modified since the last backup are backed up from the node S0; unmodified node files are copied from their last backup in the same archive. The operand FROM=*LATEST-BACKUPS-OR-S0 must not be specified for the very first full backup since it is first necessary to create the backup environment.

The HSMS administrator performs a decentralized full backup of a workstation

The workstation is mounted in POSIX under /HSMS/WORKSTA3 and can be accessed via NFS.

Perform preparatory activities:

/START-HSMS
//MODIFY-NODE-PARAMETERS -  ———————————————————————————————————————————  (1) 
//   NODE-ID=WORKSTA3
//CREATE-ARCHIVE -  ———————————————————————————————————————————————————  (2) 
//   ARCHIVE-NAME=WORKSTA3, -
//   ALLOWED-USAGE=*NODEBACKUP, -
//   USER-ACCESS=*ALL-USERS, -
//   DIRECTORY-NAME=NODEBACKUP.WORKSTA3.DIR, -
//   RETENTION-PERIOD=150, -
//   S2-DEVICE-TYPE='TAPE-C4'
//CREATE-ARCHIVE -  ———————————————————————————————————————————————————  (3) 
//   ARCHIVE-NAME=WS3DIR, -
//   ALLOWED-USAGE=*BACKUP(SAVE-FILE-STRUCTURE=*SEVERAL-SVID), -
//   DIRECTORY-NAME=BACKUP.WS3DIR.DIR, -
//   RETENTION-PERIOD=150, -
//   S2-DEVICE-TYPE='TAPE-C4'
//MODIFY-ARCHIVE -  ———————————————————————————————————————————————————  (4) 
//   ARCHIVE-NAME=WORKSTA3, -
//   VOLUMES=*ADD(VOLUMES=(VOLUM1,VOLUM2,...))
//END

(1)	The workstation WORKSTA3 is assigned.
(2)	The archive WORKSTA3 is defined as the backup archive for node files. All users have read privilege. Note In order for nonprivileged users to use the directory file, it must be shareable (USER-ACCESS=*ALL-USERS or *SPECIAL).
(3)	The archive WS3DIR is defined as the destination for the backup of the directory file NODEBACKUP.WORKSTA3.DIR since a directory file (BS2000 file) cannot be stored in the same save file as the node files (UNIX files). Each of the archive’s save files may contain multiple save versions. It is expedient to specify the same retention period for the directory-file archive (WS3DIR) as for the node-file archive (WORKSTA3).
(4)	Magnetic tape cartridges are added to the pool of free volumes of the WORKSTA3 archive.

Create a list of the path names which are to be backed up:

Contents of the SAM file "WORKSTA3.PATH.LIST":

 ——————————————————————————————————————————————————————————————————————  (5) 
WORKSTA3:<path-name1>
WORKSTA3:<path-name2>
WORKSTA3:...

(5)	The HSMS administrator creates the SAM file WORKSTA3.PATH.LIST, which contains the path names of the node files to be backed up.

Start full backup:

/START-HSMS
//BACKUP-NODE-FILES -   ————————————————————————————————————————————————  (1) 
//   PATH-NAMES=*FROM-FILE(LIST-FILE-NAME=WORKSTA3.PATH.LIST), -
//   SELECT-FILES=*ALL-FILES, -
//   ARCHIVE-NAME=WORKSTA3, -
//   OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=FULL.BACKUP, -
//                         WAIT-FOR-COMPLETION=*YES) 
//BACKUP-FILES -   —————————————————————————————————————————————————————  (2) 
//   FILE-NAMES=NODEBACKUP.WORKSTA3.DIR, -
//   ARCHIVE-NAME=WS3DIR, -
//   TO-STORAGE=*S2-STORAGE-LEVEL(VOLUMES=DIRTAPE), -
//   OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=NODEBACKUP.DIR)
//END

(1)	The path names of the node files which are to be backed up are read from the file WORKSTA3.PATH.LIST. All node files are backed up in the archive WORKSTA3.
(2)	The directory file NODEBACKUP.WORKSTA3.DIR is backed up in the archive WS3DIR on storage level S2.

The HSMS administrator restores a node file to a passive workstation

The node file was backed up in a central backup by means of the BACKUP-NODE-FILES statement.

/START-HSMS
//RESTORE-NODE-FILES -  ———————————————————————————————————————————————  (1) 
//   PATH-NAMES=*PATH-NAME(PATH=/DIR/FILE, -
//      NODE-ID=WORKSTA2), -
//   SELECTION-BOUNDARY=*SPECIFIED-PATHS, -  ——————————————————————————  (2) 
//   REPLACE-FILES=*YES, -  ———————————————————————————————————————————  (3) 
//   SELECT-SAVE-VERSIONS=*BY-ATTRIBUTES -  ———————————————————————————  (4) 
//      (SAVE-VERSION-DATE=00-08-27(TIME=22:19:15)), -
//   OPERATION-CONTROL=*PARAMETERS(WAIT-FOR-COMPLETION=*YES, -
//      REPORT=*FULL,OUTPUT=FULL.RESTORE)
//END

(1)	The node file with the path name /DIR/FILE is restored to the passive workstation WORKSTA2.
(2)	If the node file is a directory, only the inode will be restored. The files contained in this directory will not be restored.
(3)	Any existing node file with the same path name will be overwritten during the restore.
(4)	This specification is required only if the node file backup which is to be restored is not the latest one.

A nonprivileged user restores selected file trees to the local BS2000-UFS

The file trees were backed up centrally by means of the BACKUP-NODE-FILES statement.

/START-HSMS
//SELECT-NODE-FILES -   ————————————————————————————————————————————————  (1) 
//   PATH-NAMES=*PATH-NAME(PATH=*), -
//   OUTPUT=PATHNAMES.LIST
//END

/START-EDT ————————————————————————————————————————————————————————————  (2) 
@READ ‘PATHNAMES.LIST‘        Deletion of all path names which are not to be restored
@WRITE ‘PATHNAMES.LIST‘
@HALT

/START-HSMS
//RESTORE-NODE-FILES -   ———————————————————————————————————————————————  (3)
//   PATH-NAMES=*FROM-FILE(LIST-FILE-NAME=PATHNAMES.LIST), -
//   SELECTION-BOUNDARY=*SPECIFIED-PATHS, -
//   REPLACE-FILES=*YES(PROTECTION-RESPECTED=*NONE), -
//   OPERATION-CONTROL=*PARAMETERS(WAIT-FOR-COMPLETION=*YES)
//END

(1)	First, all the files of the local BS2000-UFS are selected to obtain a complete list of file names. The list of file names is output to the file PATHNAMES.LIST.
(2)	An editor such as EDT is then called to delete the path names which should not be restored from the file PATHNAMES.LIST.
(3)	All the path names still present in the file PATHNAMES.LIST are restored. Any existing files with the same path names are overwritten during the restore.

The HSMS administratot transfers files from a workstation to an “empty” workstation

The workstation is mounted in POSIX under /HSMS/WORKSTA3 and can be accessed via NFS.

To do this, the decentralized full backup is used.

/START-HSMS
//RESTORE-NODE-FILES -  ———————————————————————————————————————————————  (1) 
//   PATH-NAMES=*FROM-FILE(LIST-FILE-NAME=WORKSTA3.PATH.LIST), -
//   SELECTION-BOUNDARY=*ALL-FILE-SYSTEMS, -  —————————————————————————  (2) 
//   NEW-PATH-NAMES=*BY-RULE(NEW-NODE-ID=WORKSTA9), -  ————————————————  (3) 
//   OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=WORKSTA9.LIST)
//END

(1)	All files listed in the file WORKSTA3.PATH-LIST are transferred to the workstation WORKSTA9.
(2)	In addition, all node files and directories on the subordinate levels of the directories listed in WORKSTA3.PATH.LIST are transferred.
(3)	This attempt to transfer files succeeds only if the workstation WORKSTA9 was placed under HSMS management beforehand, using the HSMS statement MODIFY-NODE-PARAMETERS.

The HSMS administrator archives the file tree of a passive workstation

Perform preparatory activities:

//START-HSMS
//CREATE-ARCHIVE -  ———————————————————————————————————————————————————  (1) 
//   ARCHIVE-NAME=ARCHIVAL, -
//   ALLOWED-USAGE=*NODEARCHIVAL, -
//   DIRECTORY-NAME=ARCHIVAL.DIR, -
//   RETENTION-PERIOD=30
//MODIFY-ARCHIVE -  ———————————————————————————————————————————————————  (2) 
//   ARCHIVE-NAME=ARCHIVAL, -
//   VOLUMES=*ADD(VOLUMES=(VOLUM1,VOLUM2,...))
//MODIFY-NODE-PARAMETERS -
//   NODE-ID=WORKSTA1, -
//   HSMS-CONTROL=*YES
//END

(1)	Sets up the ARCHIVAL archive for the long-term archiving of node files. By default, only the owner of the archive has access to it. The directory file is named ARCHIVAL.DIR. The archived node files cannot be deleted for 30 days. Note In order for nonprivileged users to use the directory file, it must be shareable (USER-ACCESS=*ALL-USERS or *SPECIAL).
(2)	Enters volumes in the pool of free volumes of the ARCHIVAL archive.

Start archiving:

//START-HSMS
//ARCHIVE-NODE-FILES -   ———————————————————————————————————————————————  (3) 
//   PATH-NAMES=*PATH-NAME(PATH=/DIR,NODE-ID=WORKSTA1), -
//   SELECTION-BOUNDARY=*ALL-FILE-SYSTEMS, -
//   ARCHIVE-NAME=ARCHIVAL, -
//   OPERATION-CONTROL=*PARAMETERS(REPORT=*FULL,OUTPUT=ARCHLIST)
//END

(3)

Archives the directory /DIR of the workstation WORKSTA1. Also archives all the node files and directories located on the subordinate levels of the directory /DIR (SELECTION-BOUNDARY=*ALL-FILE-SYSTEMS). The files and directories are stored in the ARCHIVAL archive. A full report is output, including a list of all archived node files. The report is written to the output file ARCHLIST.