Backing up data with remote mirroring

Edit online

When you back up data with remote mirroring, you can create local and remote snapshot backups.

About this task

These steps can be applied to the following scenarios:
  • SAN Volume Controller snapshot backup at the auxiliary cluster with either Metro Mirror or Global Mirror.
  • XIV® snapshot backup at the remote site with either Synchronous Remote Mirroring or Asynchronous Remote Mirroring.

To create local application-consistent snapshot backups with the source volumes of the system that is running remote mirroring, verify that one DEVICE_CLASS section is configured for the primary cluster. The production volumes are on the primary cluster. You can run the setup script to create or change DEVICE_CLASS sections. From the production host, start the local snapshot backup. There are no additional requirements.

To create application-consistent remote snapshot backups with the target volumes of the storage system that is running remote mirroring, complete the following steps. The first few steps do not include all details that are needed to complete the step. These steps are usually completed before you start the following procedure. The information is provided for your convenience. You can verify that you have the environment set up completely before the backup begins.

Procedure

  1. Verify IBM® Storage Protect Snapshot is installed in a supported environment.
    You must have a database that is running on the primary cluster. The primary cluster is mirrored to a remote cluster with the storage feature for remote mirroring.
  2. Use the setup script to configure IBM Storage Protect Snapshot for remote mirroring.
    When you configure for remote mirroring, the following parameters are set in the DEVICE_CLASS section:
    • COPYSERVICES_REMOTE YES
    • COPYSERVICES_REMOTE_SERVERNAME <SERVER_NAME>
    • COPYSERVICES_REMOTE_USERNAME <USER_NAME>
    • TAKEOVER_HOST_NAME <HOST_NAME>
  3. At the end of the setup script, the following question is displayed: 
    Do you want to continue by specifying passwords for the defined sections?

    Enter y for yes.

  4. Verify that the DEVICE_CLASS section that was created for remote mirroring during the configuration process, is selected. To verify, go to the CLIENT section of the profile. In the CLIENT section, the DEVICE_CLASS that is in use is selected.
  5. From the production host, start the remote snapshot backup by typing in the following command:
    DB2® database, remote snapshot backup, single partition database
    db2 backup db dbname use snapshot
    or, DB2 database, remote snapshot backup, multi-partition database
    db2 backup db dbname on all dbpartitionnums use snapshot
    When a snapshot backup is attempted, but the remote mirroring relationships are not synchronized, the backup fails and an error message is displayed. Before you can back up data, the mirroring relationships must be in the consistent synchronized state.

    A snapshot consistency group is created in the remote cluster. The target of the mirroring relationships is the source of this new snapshot consistency group.

    Important: Using some storage systems, the snapshot backup requires available space on the target storage pool so that it can create the snapshot. Increase the capacity on the requested storage pool, or free up items that are using existing capacity, if there is not enough space. Check the message for the exact amount of storage space that is required.
  6. To verify that the backup is complete, from a command prompt window, enter the following command: 
    fcmcli -f inquire_detail

What to do next

When you complete the steps, you can mount and unmount the backup with the following commands:
  • Mount the backup, from a command prompt window, by entering the following command: fcmcli -f mount
  • Unmount the backup, from a command prompt window, by entering the following command: fcmcli -f unmount