Comparison of BMC AMI Copy and the IBM Db2 COPY utility
The following table summarizes the differences between the NGT Copy copy functions and the DB2 COPY utility:
Subsequent sections describe the more important NGT Copy functional and operational features that distinguish NGT Copy from the DB2 COPY utility.
Function or task | DB2 COPY | NGT Copy |
|---|---|---|
Produces up to four image copies in a single pass of the table space | x | x |
Produces full and incremental image copies of index spaces | x | |
Optionally registers up to four image copies in SYSIBM.SYSCOPY, including index copies for indexes defined in DB2 with the COPY YES attribute | x | x |
Optionally registers up to four image copies of indexes in a BMC-supplied BMCXCOPY table, including data-set-level, full copies of nonpartitioning indexes, full copies of indexes with the COPY NO attribute, and incremental index copies | x | |
Allows multitasking with tape output to decrease elapsed time | x | x |
Supports Instant Snapshot copies, which use specialized hardware to make data set level copies for quick backup copies, in conjunction with the BMC SNAPSHOT UPGRADE FEATURE (SUF) or EXTENDED BUFFER MANAGER (XBM) product | x | |
Compatible with the DB2 RECOVER and the NGT Recover utility | x | x |
In conjunction with the BMC SUF product, optionally allows groups of spaces to be copied to the same consistent point while making updates | x | |
In conjunction with the BMC SUF and XBM products, supports the XBM Utility Monitor that can be used to view status messages of a copy job as it is running | x | |
Produces full or incremental image copies of table spaces | x | x |
Optionally merges a new incremental copy with a previous copy in one step | x | |
Provides a utility to allow the reinstatement of a merged incremental copy | x | |
Automatically escalates an incremental copy request to a full copy request when prohibited in SYSIBM.SYSCOPY | x | x |
Optionally allows specification of changed page thresholds for conditional image copy creation--full, incremental, or no copy | x (DB2 COPY does not support no copy.) | x |
Optionally optimizes the elapsed time for an incremental copy | x | |
Allows copies of DB2 catalog and directory spaces | x | x |
Copies the DB2 catalog and directory with one command | x | |
Provides a utility to allow backup and recovery site image copies to be made offline | x | x |
Optionally allows dynamic allocation of output copy data sets | x | x |
Supports dynamic tape detection | x | |
Allows wildcard selection of spaces | x | x |
Allows multiple spaces to be explicitly named in the table space or index space specification | x | |
Provides the RUNSTATS option to gather and report statistics and update the DB2 catalog and the BMCSTATS table in the same data pass that is used for the image copy | x | |
Optionally resets modified page indicators for table spaces | x | |
Optionally allows read-only or read-write access by applications during the copy process | x | x |
Supports secondary authorization IDs | x | x |
Automatically determines the most efficient access methods | x | |
Provides data for fine tuning copy performance | x | |
Provides restart capabilities | x | x |
Optionally checks for structural damage in a single pass of the data while the image copy is being made (including the DB2 catalog and directory) | x | |
Allows you to establish a point of consistency prior to or following the copy process | x | |
Optionally prohibits empty incremental image copies of table spaces | x | |
Allows specification of an execution options module, as well as allowing overrides to many installation options at execution time | x | |
Provides options that can make data compression more efficient | x | |
Provides support for delimited identifiers | x | x |
Provides support for the BMC Utility History table (BMCHIST) | x | |
Allows you to specify different allocation for the output of full versus incremental copies using automatic features | x | |
Allows you to specify different allocation for the output of full copies that meet a specified size threshold | x | |
Allows specification of a threshold value with alternate output specifications to automatically change the location of a full copy when the threshold value is met or exceeded | x | |
Allows specification of a threshold value at which index copies will be made automatically | x | |
Allows specification of how to handle error processing for unacceptable status or previously registered copies | x | |
Allows specification of how to handle migrated or archived spaces | x | |
Allows specification of a generation data group (GDG) model by copy type to generate GDG bases when needed | x | x |
Allows specification of a BMC RECOVERY MANAGER object set as an alternative object specification | x | |
Allows specification of application objects, such as those for an SAP R/3 application, as an alternative object specification | x | |
Optionally provides compression of disk copies using the BMC XCA technology when used in conjunction with the BMC PACLOG utility | x | |
Provides the QUIESCE command to allow you to quiesce without making a copy | x | |
Provides the ability to immediately migrate image copy data sets using HSM | x | |
Optionally optimizes the stacking of incremental copies on tape to minimize tape handling and reduce elapsed time for recovery | x | |
Provides the MODIFY command for enhanced SYSCOPY and BMCXCOPY maintenance and ICF catalog synchronization (see Comparison-of-the-BMC-AMI-Copy-MODIFY-command-and-the-Db2-MODIFY-RECOVERY-utility for more information) | x | |
Supports online schema evolution for image copies of application spaces | x | x |
Supports long and Unicode names | x | x |
This section contains the following topics:
Failed to execute the [panel] macro.