Creating index backups
BMC AMI Copy
can create full and incremental image copies of COPY YES or COPY NO indexes.
For very large indexes, recovery from image copies and log can be significantly faster than rebuilding the indexes. When indexes are recovered from image copies and log, their recovery is no longer dependent on the parent table space recovery, so the two tasks can proceed concurrently.
If you use the IXSIZE parameter to define the index copy threshold, BMC AMI Copy will create index image copies only for those indexes whose size exceeds this threshold. This allows you to set an index image copy policy without making a separate decision for each index. For more information, see Copying-indexes-based-on-size.
Index recovery for COPY NO indexes or using incremental index copies requires the BMC AMI Recover for Db2 product. (Recovery using incremental index copies requires BMC AMI Recover version 8.1.00 or later.) Index recovery using full index copies of COPY YES indexes can be accomplished with either BMC AMI Recover or the IBM Db2 RECOVER utility.
To invoke the index copy functionality
Use any of the following specifications:
- The INDEXSPACE specification with the COPY or COPY IMAGECOPY commands
- The INDEXES keyword with a COPY TABLESPACE or COPY IMAGECOPY TABLESPACE specification
- The INDEX specification with the COPY and COPY IMAGECOPY commands
The authorization needed to make index copies is the same as that described in Required-authorizations.
This section contains the following topics: