Using COPY IMAGECOPY to make duplicate image copies

You can use the COPY IMAGECOPY command to make and register backup and recovery site copies of your table spaces after making a primary copy and registering it in the Db2 catalog.

The COPY IMAGECOPY command can be used in the same way to make and register index space copies. This minimizes the time needed to copy spaces (assuming the number of tape drives is the limiting factor) by allowing you to run more concurrent copies during the copy window and then, when the spaces are again available for updates, to make the required backup and recovery site copies. If you prefer, you can even make the recovery site backup copy at the recovery site.

Related topic

Managing-multiple-image-copies

We recommend that you make a local site primary copy and a local site backup copy (in case the primary copy is defective) and then use COPY IMAGECOPY to make recovery site copies.

You can use COPY IMAGECOPY with a primary copy made and registered by BMC AMI Copy or by the IBM Db2 COPY utility.

Important

You cannot use COPY IMAGECOPY to make more copies of a:

Before you can make duplicate copies with COPY IMAGECOPY, there must be a primary copy registered in SYSIBM.SYSCOPY or in BMCXCOPY. All of the duplicates are registered with the same START_RBA, SHRLEVEL, ICTYPE, TIMESTAMP, ICTIME, and ICDATE values as the original. If the original is the most recent copy to be registered, you can specify it with the keyword LASTCOPY. You can also specify any original by providing the appropriate START_RBA value.

Copying an image copy requires the same authorization as copying the table space or index space and you can mix both types of copies in the same SYSIN data set. BMC AMI Copy makes no status changes to the space at the time of the copy and dynamically allocates the input copy. BMC AMI Copy also automatically registers the duplicate copies in SYSIBM.SYSCOPY or BMCXCOPY.

Using the COPY IMAGECOPY command, you can:

  • Specify the database, table space, and partitions (or data sets) for which morel copies are required
  • Specify the database, index space, or data sets for which more copies are required
  • Specify the START_RBA value of the original copy
  • Specify which additional copies to make: local site, recovery site, primary, or backup (depending on the type of copy--LB, RP, or RB)
  • Dynamically allocate the output copy data sets, or specify them in the JCL regardless of how the original primary copy was made
  • Specify the page-integrity checking level to use during the copy process for table spaces
  • Make a standard primary copy that is registered in SYSIBM.SYSCOPY from an existing Instant Snapshot copy

BMC AMI Copy installation options that apply to COPY IMAGECOPY include:

  • PLANCOPY
  • CHECKLVL
  • SQUEEZE
  • COMPRESS
  • NBRBUFS
  • DB2WAIT
  • DB2NTRY
  • CHECKERR

All dynamic allocation output descriptor defaults also apply. For more information about the syntax of the command, see COPY-IMAGECOPY-command.

This section contains the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*