IBM Tivoli Storage Manager Extended Edition, Version 7.1

Managing the Disaster Recovery Manager tasks

To protect data, you can use the Disaster Recovery Manager (DRM) during routine operations and during disaster recovery.

AIX operating systems Windows operating systems

Before you begin

If IBM® Tivoli® Storage Manager is set up to use Secure Sockets Layer (SSL) for client/server authentication, a digital certificate file, cert.kdb, is created as part of the process. This file includes the server's public key, which allows the client to encrypt data. The digital certificate file cannot be stored in the server database because the Global Security Kit (GSKit) requires a separate file in a certain format.
  1. Keep backup copies of the cert.kdb and cert256.arm files.
  2. Regenerate a new certificate file, if both the original files and any copies are lost or corrupted. For details about this procedure, see Troubleshooting the certificate key database.

About this task

Ensure that you set up the DRM and perform the daily operations to protect the database, data, and storage pools.

Setup
  1. License DRM by issuing the REGISTER LICENSE command.
  2. Ensure that the device configuration and volume history files exist.
  3. Back up the storage pools by issuing the BACKUP STGPOOL command.
  4. Copy active data to active-data pools by using the COPY ACTIVEDATA command.
  5. Do a full backup the database (for example, a database snapshot backup) by using the BACKUP DB command.
  6. Define site-specific server recovery instructions in the DRM plan file.
  7. Describe priority client machines by using the DEFINE MACHINE command.
  8. Generate the disaster recovery plan.
Daily Preparation Operations
Day 1
  1. Back up client files.
  2. Back up the primary storage pools to copy storage pools.
  3. Copy active data from primary storage pools to active-data pools.
  4. Back up the database (for example, a database snapshot backup).
    Restriction: Ensure that the primary storage pool backup process is complete before you back up the database.
  5. Mark the backup volumes as unavailable to Tivoli Storage Manager.
    Restriction: Ensure that the BACKUP STGPOOL command and the BACKUP DB command are complete before you issue the MOVE DRMEDIA command.
  6. Send the backup volumes and disaster recovery plan file to the vault.
  7. Generate the disaster recovery plan.
Day 2
  1. Back up client files
  2. Back up active and inactive data that is in the primary storage pools to copy storage pools. Copy the active data that is in primary storage pools to active-data pools.
  3. Back up the database (for example, a database snapshot backup).
    Restriction: Ensure that the primary storage pool backup process is complete before you back up the database.
  4. Mark the backup volumes as unavailable to Tivoli Storage Manager.
    Restriction: Ensure that the BACKUP STGPOOL command and the BACKUP DB command are complete before you issue the MOVE DRMEDIA command.
  5. Send the backup volumes and disaster recovery plan file to the vault.
  6. Generate the disaster recovery plan.
Day 3
  1. Automatic storage pool reclamation processing occurs.
  2. Back up client files.
  3. Back up the active and inactive data that is in primary storage pools to copy storage pools. Copy the active data that is in primary storage pools to active-data pools.
  4. Back up the database (for example, a database snapshot backup).
    Restriction: Ensure that the primary storage pool backup process is complete before you back up the database.
  5. Send the backup volumes and a list of expired volumes to be reclaimed to the vault.
  6. The vault acknowledges receipt of the volumes that were sent on the previous day.
  7. Generate the disaster recovery plan.
Disaster and Recovery
Day 4
The server and the client machines are destroyed.
  1. Restore the server by using the latest recovery plan.
  2. Identify the top priority client nodes at the disaster site.
  3. Restore urgently needed client-system files from active-data pools. Restore other, less urgently needed client-system files from copy storage pools.
  4. Restore the primary storage pools from copy storage pools.
    Attention: Restoring a primary storage pool from an active-data pool might cause some or all inactive files to be deleted from the database. Some or all of the inactive files might be deleted if the server determines that an inactive file must be replaced but cannot find it in the active-data pool.
  5. Move database backup, copy storage pool, and active-data pool volumes to the vault.
Daily Operations
Day 5
  1. Back up client files.
  2. Back up the active and inactive data that is in primary storage pools to copy storage pools. Copy the active data that is in primary storage pools to active-data pools.
  3. Back up the database (for example, a database snapshot backup).
  4. Send the backup volumes and a list of expired volumes to be reclaimed to the vault.
  5. Generate the disaster recovery plan.
Parent topic: Disaster recovery manager

Feedback