A backup scenario

As discussed in Backup and recovery, you should consider using a combination of incremental and volume backup to fulfill your general availability requirements. Some ways to implement this strategy are:

Dump a full volume at a given interval—perhaps once a week. Use the RESET keyword to reset the data-set-changed indicator. To do full-volume dumps of two volumes at once (in parallel, which is most effective if tapes are on separate channels), code the following:
```
PARALLEL
DUMP INDYNAM(111111) OUTDD(TAPE1) RESET OPTIMIZE(1)
DUMP INDYNAM(222222) OUTDD(TAPE2) RESET OPTIMIZE(2)
```

Dump only changed data sets at a shorter interval—perhaps daily.

DUMP LOGINDY((111111),(222222))  OUTDD(TAPE3) RESET -
    OPTIMIZE(3) DATASET(INCLUDE(**) -
                        BY(DSCHA,EQ,YES))

Use data set naming conventions to set up a dumping scheme that takes account of the relative importance of the data. For example, include CRIT in the first-level qualifier of all your critical data sets. With this convention in place, you can back up your critical data sets as follows:
```
DUMP LOGINDY((111111),(222222))  OUTDD(TAPE4) RESET -
    OPTIMIZE(4) DATASET(INCLUDE(CRIT*.**) -
                        BY(DSCHA,EQ,YES))
```
Other naming conventions can also be used to identify groups of data sets. For instance, you can use department numbers, charge numbers, user initials, or project codes to identify data sets you want to dump together.

For data set operations, SYSPRINT contains the names of all the data sets that were dumped for each run. You should keep them for reference if you have to restore a data set and you want it to be at the latest level. This prints a listing of all the data sets that might be on the restore tape, and you can now find the latest dumped version of a particular data set.