Keeping and recalling merged incremental copies
If you want to perform a point-in-time recovery that requires a particular merged incremental copy, the BMC AMI Recover utility will detect and use the retained incremental copy. If you use IBM Db2 RECOVER to perform a point-in-time recovery that requires a 'kept' incremental copy, you must reinstate that copy using the BMC AMI Copy RECALL command before you can proceed with the recovery.
The RECALL command has the following syntax:
[DSNUM {ALL/integer}]
ATRBA X'byteString'/ATLOGPOINT X'byteString'
In this example:
- databaseName defaults to DSNDB04.
- DSNUM defaults to DSNUM ALL.
- ATRBA or ATLOGPOINT specify the value contained in the START_RBA column of SYSCOPY for the incremental copy you want to reinstate. This value might be an RBA or LRSN depending on whether the copy was made in a non-data-sharing or a data sharing environment respectively.
BMC AMI Copy reinstates any local or remote primary or backup copies with the same START_RBA value.
After you recall an incremental copy, IBM Db2 RECOVER can use the copy in the normal way.
Because the rows for retained copies are left in SYSIBM.SYSCOPY, they are displayed by any tool or report that displays SYSCOPY information. Also, the BMC C+/MODIFY component of BMC AMI Copy or IBM Db2 MODIFY can clean up these rows in the same way as any other rows in SYSCOPY.
For more information about the KEEP option and the RECALL command, respectively, see Global-COPY-options and RECALL-command.