Using stacked image copies

BMC recommends stacking table space image copies in alphabetical order by database name and table space name. Following all of the copies for each table space should be the copies for any indexes. Partitioned indexes are first in order by database name, index space name, and DSNUM, followed by nonpartitoned indexes in order by database name, index space name, and DSNUM. This ordering allows BMC AMI Recover to optimize when you include the same set of table spaces in one change accumulation group and then run a recovery that uses the stacked image copies and a change accumulation file with log data for all of the table spaces.

You can stack image copies for a set of spaces with BMC AMI Copy, using wildcards to select the spaces and dynamic allocation for the image copies. In this case, BMC AMI Copy automatically stacks the image copies in an order that is compatible with the order in which R+/CHANGE ACCUM writes log record data.