BS2000 predominantly uses HSMS and ARCHIVE for logical data backup. HSMS builds on ARCHIVE and, compared to ARCHIVE, offers a more user-friendly user interface and functional enhancements.
Irrespective of whether backups are created with HSMS or ARCHIVE or data is archived with HSMS, or is migrated or exported from the processing level to a background level, a backup file is always created.
This section describes how MAREN manages backup files on tapes.
A backup file can occupy several tapes. It can also be written simultaneously to various tapes (HSMS operand PARALLEL-RUNS or ARCHIVE operand DRIVES). In order to do this, HSMS/ARCHIVE starts a separate subtask for each of the parallel runs. Each subtask is assigned its own SUBSAVE number. Within a parallel run, each subtask may utilize follow-up tapes, each of which receives its own SUBSEQ number.
Overview of the fields involved:
| SAVE-FILE | name of the backup file | |
| SUBSAVE | subtask number | |
| SUBSEQ | serial number of a subtask’s tape |
Example 1: backup using the HSMS statement BACKUP-FILES
//BACKUP-FILES ..,SAVE-FILE=*CONTINUE(SAVE-FILE-ID=S.040301.123651),...,
OPERATION-CONTROl=*PARAMETERS(...,PARALLEL-RUNS=3)
A backup with SAVE-FILE-ID S.040301.123651 and 3 consecutive backup tasks (ARCHIVE subtasks) is started.
Each subtask is assigned its own SUBSAVE number.
Subtask 1 is assigned SUBSAVE number 0
Subtask 2 is assigned SUBSAVE number 1
Subtask 3 is assigned SUBSAVE number 2
Subtask 1 first writes to the tape with the archive number sich01, then to sich04 and finally to sich06.
Subtask 2 first writes to the tape with the archive number sich02 and then to sich05.Subtask 3 first writes to the tape with the archive number sich03.
All of the tapes (from sich01 to sich06) are assigned the same SAVE-FILE-ID because all together they contain one single backup file (SAVE-FILE).
The following table gives an overview of the SUBSAVE and SUBSEQ assignments:
| VSN | SAVE-FILE-ID | SUB-SAVE | SUB-SEQ |
| sich01 | S.040301.123651 | 0 | 1 |
| sich02 | S.040301.123651 | 1 | 1 |
| sich03 | S.040301.123651 | 2 | 1 |
| sich04 | S.040301.123651 | 0 | 2 |
| sich05 | S.040301.123651 | 1 | 2 |
| sich06 | S.040301.123651 | 0 | 3 |
All of the tapes belong to the same backup. The MAREN and MARENADM can process tapes from one backup with consecutive save runs using the following statements:
EXPORT-VOLUME
This example uses the backup file form example 1://EXPORT-VOLUME...,VOLUME=*BY-DIRECTORY(SAVE-FILE-ID=S.040301.123651)MODIFY-VOLUME-ATTRIBUTES
Example://MODIFY-VOLUME-ATTRIBUTES...,
SELECT=*RESERVED(DIRECTORY-NAME=FILE.X(SAVE-FILE-ID=*LATEST))RETURN-VOLUME (MARENADM only)
Example://RETURN-VOLUMES...,
VOLUME=*BY-DIRECTORY(DIRECTORY-NAME=:CATD:$SYSHSMS.DIRECTORYSYSBACKUP)SHOW-VOLUME-ATTRIBUTES
Example for the use of the last save file but three://SHOW-VOLUME-ATTRIBUTES...,DIRECTORY-NAME=FILE.Y(SAVE-FILE-ID=-3))
MAREN can perform such processing provided the backup was created while MAREN was loaded. See the note on "HSMS and ARCHIVE".
If, by way of exception, MAREN was not loaded, the MAREN administrator can update the SAVE-FILE-ID, SUB-SAVE-NUMBER, and SUB-SEQUENCE-NUMBER fields for the tapes of a backup in the MAREN catalog retroactively using the MARENADM statement MODIFY-VOLUME-ATTRIBUTES.
The SAVE-FILE-ID of a backup file can be addressed via its absolute name (in this particular example S.040301.123651) using a directory file or relative to the most recent backup. Note that MAREN operates in a network of systems. A directory file called :CAT:$USER.DIRECTORY, for instance, should be located on System A and another directory file of the same name be located on system B within the same network, then MAREN would mix up the backups. If, for instance, the directory file :CAT:$USER.DIRECTORY exists on System A in one system and another directory file with the same name :CAT:$USER.DIRECTORY exists on System B in the same network as System A, MAREN merges the backups and the unambiguous assignment is lost.
Example 2: backup run performed by HSMS and a detailed description of the process
The example below illustrates how a backup archive is created under HSMS, and how data is saved on four drives in parallel. It also shows how the properties of the save tapes in MAREN change in the case of backup, updating of the backup, and a new backup.
Entry of the HSMS archive MYBACKUP with the directory name
:POPP:$TSOS.MYBACKUP.DIRin HSMS./HSMS
//CREATE-ARCHIVE ARCHIVE-NAME=MYBACKUP,-
// ALLOWED-USAGE=*BACKUP(SAVE-FILE-STRUCTURE=*SEVERAL-SVID),-
// DIRECTORY-NAME=$TSOS.MYBACKUP.DIR,RETENTION-PERIOD=5,-
// S2-DEVICE-TYPE=TAPE-C4,LOCATION=HSMSLOCStarting the first backup using the PARALLEL-RUNS=4 operand. The output tapes are assigned by MARENUCP.
//BACKUP-FILES FILE-NAMES=*FROM-FILE(LIST-FILE-NAME=HOL.PAK),-
// ARCHIVE-NAME=MYBACKUP,TO-STORAGE=*S2-STORAGE-LEVEL,-
// OPERATION-CONTROL=*PARAMETERS(REQUEST-NAME=SFID#001,-
// PARALLEL-RUNS=4,REPORT=*FULL,OUTPUT=REPORT.SFID#001)
% HSM0030 REQUEST 'SFID#001' CREATED IN ENVIRONMENT 'SF' WITH DATE
'<date>' AND TIME '<time>'
% HSM0004 HSMS STATEMENT COMPLETED WITH WARNINGS
//ENDA section of the backup log lists information pertaining to the first backup run and indicates which SUBSAVE number is allocated to which output tape. The subtask of SUBSAVE number 3 is the only subtask to require two tapes (QE0022 and QE0024).
*** BACKUP - FILES HSMS <version> FULL
REPORT *** <date> <time> PAGE 1
...
REPORT *** <date> <time> PAGE 2
...
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.020716.135432',
...
% ARC0033 ARCHIVE SUBTASK TSN '0D9N' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0D9P' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0D9Q' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0D9R' GENERATED
% ARC0815 SUBTASK '0' HAS TRANSFERRED '65294' PAM PAGES FOR '1' FILES
AND.. % ARC0815 SUBTASK '1' HAS TRANSFERRED '74162' PAM PAGES FOR '1'
FILES AND..
% ARC0815 SUBTASK '2' HAS TRANSFERRED '58558' PAM PAGES FOR '1' FILES
AND..
% ARC0815 SUBTASK '3' HAS TRANSFERRED '148912' PAM PAGES FOR '2' FILES
AND..
SAVE FILE IDENTIFIER - S.040716.135432 SAVE-VERSION-DATE=<date> ...
SUBSAVE
NUMBER VSNS
0 QE0020
1 QE0021
2 QE0023
3 QE0022, QE0024
SAVE FILE IDENTIFIER - S.040716.135432 SAVE-VERSION-DATE=<date> ...Output of information concerning the backup tapes to MAREN. Instead of the operand SAVE-FILE-ID=-0, it is also possible to specify SAVE-FILE-ID= *LATEST, since this is the only and last backup. Specifying SAVE-FILE-ID= S.040716.135432 would also have the same effect.
/MARENADM
//SHOW-VOL-ATTR DIRECTORY-NAME=:POPP:$TSOS.MYBACKUP.DIR(SAVE-FILE-ID=0)
% MARM195 NO DIRECT ACCESS TO MAREN CATALOG POSSIBLE
-----------------------------------------------------------------------------
VOLUME USER-ID REQ-NAME DIRECTORY-NAME (SHORTENED) SAVE-FILE-ID SUB-SV/SEQ
-----------------------------------------------------------------------------
QE0020 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 001
QE0021 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 001
QE0023 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 02 001
QE0022 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 001
QE0024 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 002
% MARM120 TOTAL OF 5 MAREN CATALOG ENTRIES PROCESSEDYou obtain detailed information on output tape QE0024 with:
//SHOW-VOL-ATTR VOLUME=QE0024,INFORMATION=*MAXIMUMMARENADM is terminated with:
//ENDHSMS updates the existing backup file (
SAVE-FILE=*CONTINUEoperand)./HSMS
//BACKUP-FILES FILE-NAMES=*FROM-FILE(LIST-FILE-NAME=HOL.PAK2),-
// ARCHIVE-NAME=MYBACKUP,SAVE-FILE=*CONTINUE,-
// OPERATION-CONTROL=*PARAMETERS(REQUEST-NAME=SFID#002,-
// PARALLEL-RUNS=4,WRITE-CHECKPOINTS=*STD,-
// SHADOW-COPY= *ALLOWED,REPORT=*FULL,OUTPUT=REPORT.SFID002)
% HSM0030 REQUEST 'SFID#002' CREATED IN ENVIRONMENT 'SF' WITH DATE
'<date>' AND TIME <'time>'
//ENDThe following section of the backup log lists information pertaining to the backup run and indicates which SUBSAVE number is allocated to which output tape. Tapes which were not fully written in the preceding run are now updated.
*** BACKUP - FILES HSMS <version> FULL
REPORT *** <date> <time> PAGE 1
...
ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.040716.141454', ...
% ARC0033 ARCHIVE SUBTASK TSN '0EGM' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0EGN' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0EGP' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0EGQ' GENERATED
% ARC0815 SUBTASK '0' HAS TRANSFERRED '172831' PAM PAGES FOR '4' FILES ...
% ARC0815 SUBTASK '1' HAS TRANSFERRED '549310' PAM PAGES FOR '2' FILES
AND..
% ARC0815 SUBTASK '2' HAS TRANSFERRED '122446' PAM PAGES FOR '1' FILES
AND.. % ARC0815 SUBTASK '3' HAS TRANSFERRED '309514' PAM PAGES FOR '2'
FILES AND..
SAVE FILE IDENTIFIER - S.040716.135432 SAVE-VERSION-DATE=<date> ...
SUBSAVE
NUMBER VSNS
0 QE0020 QE0028 QE0033
1 QE0021 QE0027 QE0032 QE0035 QE0038 QE0040
2 QE0023 QE0029
3 QE0024 QE0030 QE0034 QE0037
SAVE FILE IDENTIFIER - S.040716.135432 SAVE-VERSION-DATE=<date> ...In MAREN, we now have the following situation. Instead of the operand SAVE-FILE-ID=-0, the operand SAVE-FILE-ID= *LATEST may also be specified, since this is still the only and the last backup version. Specifying SAVE-FILE-ID= S.040716.135432 would also have the same effect.
/MARENADM
//SHOW-VOL-ATTR DIR-NAME=:POPP:$TSOS.MYBACKUP.DIR(SAVE-FILE-ID=-0)
-------------------------------------------------------------------------------
VOLUME USER-ID REQ-NAME DIRECTORY-NAME (SHORTENED) SAVE-FILE-ID SUB-SV/SEQ
-------------------------------------------------------------------------------
QE0020 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 001
QE0028 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 002
QE0033 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 003
QE0021 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 001
QE0027 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 002
QE0032 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 003
QE0035 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 004
QE0038 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 005
QE0040 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 006
QE0023 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 02 001
QE0029 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 02 002
QE0022 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 001
QE0024 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 002
QE0030 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 003
QE0034 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 004
QE0037 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 005
% MARM120 TOTAL OF 16 MAREN CATALOG ENTRIES PROCESSEDThe tape QE0022 was no longer requested because it is already full.
The tape QE0024 is given a new REQUEST-NAME and a new time stamp (including CR-DATE, LAST-ACC-TIME), see
//SHOW-VOL-ATTRVOLUME=QE0024,INFORMATION=*NORMALwhen the backup is continued (see above).MARENADM is terminated with:
//ENDIn HSMS another backup is now stored in a new save file (
SAVE-FILE=*NEWoperand)./HSMS
//BACKUP-FILENAMES FILE-NAMES=*FROM-FILE(LIST-FILE-NAME=HOL.PAK3),-
// ARCHIVE-NAME=MYBACKUP,SAVE-FILE=*NEW,-
// OPERATION-CONTROL=*PARAMETERS(REQUEST-NAME=SFID#003,PARALLEL-RUNS=2,-
// REPORT=*FULL,OUTPUT=REPORT.SFID003)
% HSM0030 REQUEST 'SFID#003' CREATED IN ENVIRONMENT 'SF' WITH DATE
'<date>' AND TIME '<time>'
% HSM0002 HSMS STATEMENT ACCEPTED
//ENDA section of the backup log lists the information pertaining to the backup run and shows which SUBSAVE numbers are allocated to the individual output tapes.
*** BACKUP - FILES HSMS <version> FULL
REPORT *** <date> <time> PAGE 1
...
% ARC0002 STATEMENT ACCEPTED. ARCHIVE SEQUENCE NUMBER 'A.020716.142715',
VERSION '06.0A05'
% ARC0033 ARCHIVE SUBTASK TSN '0EG5' GENERATED
% ARC0033 ARCHIVE SUBTASK TSN '0EG6' GENERATED
% ARC0815 SUBTASK '0' HAS TRANSFERRED '514652' PAM PAGES FOR '3' FILES
AND..
% ARC0815 SUBTASK '1' HAS TRANSFERRED '293046' PAM PAGES FOR '2' FILES
AND..
SAVE FILE IDENTIFIER - S.040716.142715 SAVE-VERSION-DATE=<date> ...
SUBSAVE
NUMBER VSNS
0 QE0044 QE0056 QE0059 QE0061 QE0062
1 QE0048 QE0057 QE0060
SAVE FILE IDENTIFIER - S.040716.142715 SAVE-VERSION-DATE=<date> ...
*** CATALOG - POPP USER - SYSROOT ***In MAREN, we now have the following situation. Instead of the operand SAVE-FILE-ID=-0, the operand SAVE-FILE-ID= *LATEST may also be specified, since this is still the only and the last backup version. Specifying SAVE-FILE-ID= S.040716.142715 would also have the same effect.
/MARENADM
//SHOW-VOL-ATTR DIR-NAME=:POPP:$TSOS.MYBACKUP.DIR(SAVE-FILE-ID=-0)
% MARM195 NO DIRECT ACCESS TO MAREN CATALOG POSSIBLE
-------------------------------------------------------------------------------
VOLUME USER-ID REQ-NAME DIRECTORY-NAME (SHORTENED) SAVE-FILE-ID SUB-SV/SEQ
-------------------------------------------------------------------------------
QE0044 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 00 001
QE0056 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 00 002
QE0059 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 00 003
QE0061 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 00 004
QE0062 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 00 005
QE0048 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 01 001
QE0057 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 01 002
QE0060 TSOS SFID#003 :POPP:$TSOS.MYBACKUP.DIR S.040716.142715 01 003
% MARM120 TOTAL OF 8 MAREN CATALOG ENTRIES PROCESSEDIf the operand value SAVE-FILE-ID=-1 or SAVE-FILE-ID=S.040716.135432 is specified, the information concerning the last but one backup is output (same as the output on "Processing backups"). In each new backup using SAVE-FILE=*NEW, the SAVE-FILE-ID S.040716.135432 moves one position further back.
//SHOW-VOL-ATTR DIR-NAME=:POPP:$TSOS.MYBACKUP.DIR(SAVE-FILE-ID=-1)
-------------------------------------------------------------------------------
VOLUME USER-ID REQ-NAME DIRECTORY-NAME (SHORTENED) SAVE-FILE-ID SUB-SV/SEQ
-------------------------------------------------------------------------------
QE0020 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 001
QE0028 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 002
QE0033 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 00 003
QE0021 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 001
QE0027 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 002
QE0032 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 003
QE0035 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 004
QE0038 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 005
QE0040 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 01 006
QE0023 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 02 001
QE0029 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 02 002
QE0022 TSOS SFID#001 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 001
QE0024 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 002
QE0030 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 003
QE0034 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 004
QE0037 TSOS SFID#002 :POPP:$TSOS.MYBACKUP.DIR S.040716.135432 03 005
% MARM120 TOTAL OF 16 MAREN CATALOG ENTRIES PROCESSEDMARENADM is terminated with:
//END