A backup cluster is a second DB2® pureScale® instance
that is contained within an independent GPFS™ cluster. Tivoli® Storage FlashCopy® Manager uses
the backup cluster to send a snapshot of a DB2 pureScale database
to Tivoli Storage Manager.
A production cluster is the cluster that owns the file systems that
contain the production DB2 pureScale instance
and the production database.
Ensure that the topology of the production and backup cluster are
the same. The backup cluster must have the same number of members
with identical member numbers as the production cluster. This requirement
does not apply to the cluster caching facility (CF) members. You can
create multiple members that are known as logical members on the same
host. Creating multiple logical members, can help reduce the number
of hosts that are required for the backup cluster in comparison to
the production cluster. See the IBM® DB2 Information
Center for information about how to configure multiple members on
the same host.
Tivoli Storage FlashCopy Manager mounts
the GPFS file systems that contain
the snapshot backup on a backup cluster. To allow
Tivoli Storage FlashCopy Manager to
mount the file systems on the backup cluster, the system administrator
issues the following commands:
- On the production cluster:
- Issue the mmauth add command to authorize the
backup cluster to mount one or more file systems of the database that
is protected on the production cluster. Issue this command only once
per cluster.
- Issue the mmauth grant command to grant permission
to the backup cluster to mount the file systems of the database that
are enabled for snapshot-based data protection. Issue this command
only once per file system.
- On the backup cluster:
- Issue the mmremotecluster add command to add
the production cluster to the backup cluster.
Note: The file systems must not already be mounted on the backup
cluster or added to the backup cluster before a Tivoli Storage FlashCopy Manager backup
to Tivoli Storage Manager or
mount operation.