Since Instant Snapshots are made at the data set level,
BMC AMI Copy
does not allow DSNUM ALL Instant Snapshots.
BMC AMI Copy supports DSNUM integer and DSNUM DATASET Instant Snapshots for nonpartitioned, multi-data-set table spaces and index spaces. However, the table space or index space cannot be recovered using a DSNUM ALL recovery unless all of the data sets for the space are copied using Instant Snapshots and are registered at the same RBA or LRSN.
The following table gives a complete list of the restrictions for different values of DSNUM when used with DSSNAP YES or DSSNAP AUTO.
| |
|---|
| Not allowed for any space |
| - Allowed for partitioned table spaces
- Allowed for a partitioning index space and is changed to DSNUM DATASET
- Allowed for a nonpartitioned index space when IXDSNUM DATASET is specified and is changed to DSNUM DATASET
- Not allowed for a nonpartitioned table space
- Not allowed for a nonpartitioned index space when IXDSNUM ALL is specified and is changed to DSNUM ALL
|
| Allowed for all table spaces and index spaces |
| Allowed for all table spaces and index spaces |
- If a nonpartitioned, multi-data-set space is copied as an Instant Snapshot using DSNUM 1, DSNUM 2, and so on, and you want a DSNUM ALL recovery, it is important that all of the data sets are copied, and that the copies are made with GROUP YES to ensure that the copies are registered at the same RBA or LRSN.
- If a nonpartitioned, multi-data-set space is copied using DSNUM DATASET and GROUP NO, a DSNUM ALL recovery is not possible.
- If a nonpartitioned, multi-data-set space is copied using DSNUM DATASET and GROUP YES and some of the data sets are copied as Instant Snapshots and some as standard copies, a DSNUM ALL recovery is not possible.
|