IBM Support

Guidelines for using container-copy storage pools for disaster protection

Product documentation


Abstract

With IBM Spectrum Protect Version 7.1.7, you can protect directory-container storage pools by copying the data to container-copy storage pools, where the data is stored on tape volumes. Before you use container-copy storage pools for disaster protection, review these guidelines.

Content

Table of contents:


Determining whether to use container-copy storage pools for disaster protection


Determine whether container-copy storage pools meet your requirements for disaster protection.

About this task

You can create an offsite copy of your container-copy storage pool for disaster recovery protection or to satisfy regulatory and business requirements for offsite tape copies. Before you decide to use offsite tape copies for disaster protection, carefully consider whether the solution meets your recovery time objective.

Using container-copy storage pools for disaster recovery is suitable when the amount of data in your environment is equal to or less than the following values:
  • 200 TB of total managed data
  • 50 TB of back-end data
  • 37 TB of front-end data
Total managed data
All data that is stored in the directory-container storage pool on the server. This includes active and inactive versions of the data. The number of versions is determined by retention policies.

Back-end data

All data that is stored in the container-copy storage pool.

Front-end data

The current “active” data that is stored in the container-copy storage pool. This is the active data that is used to restore data on client nodes. In a disaster, all or part of the front-end data is required to reestablish production. Front-end data is a percentage of total managed data and is less than or equal to the total managed data, depending on the policy settings in use.

To recover from a disaster within 48 hours, the system environment at the recovery site must meet the minimum hardware requirements for the actions in the following table:

Table 1. Hardware requirements for using container-copy storage pools for disaster recovery
Action
Time required
Minimum requirements
Configure a new IBM Spectrum Protect™ server at a disaster recovery site. To configure the new server, you must complete the following steps:

      1. Provision disks for the server.
      2. Restore the server from backup.
      3. Start the server.
      4. Update the storage and device configurations.
Time to restore the server: 6 hours Use a solid-state drive (SSD) for the server database, with the following requirements:

A minimum of 100 MB per second average combined read/write throughput

A minimum of 12,862 average input/output operations per second (IOPS)
Audit the directory-container storage pool and repair the data from tape.

Tip: If the system meets the minimum hardware requirements, you can repair up to 50 TB of back-end data within 48 hours.
Time to audit the storage pool: 2 hours

Time to repair the storage pool by using a tape copy: 28 hours.

Note: The time estimate applies if you have a maximum of 200 TB of total managed data in the storage pool.
Use Nearline SAS (NL-SAS) drives, as in a medium blueprint server configuration, with a minimum of 700 MB per second write performance to storage pool disk.

Use new generation tape technology such as LTO-7 or better, with a minimum of six drives to allow concurrent read operations from tape volumes.
Restore data on client nodes.

Tip: If the system meets the minimum hardware requirements, you can restore up to 37 TB of front-end data within 48 hours.
Time for client restore operations: 12 hours Use NL-SAS drives, as in a medium blueprint server configuration, with a minimum of 10 restore sessions achieving 3102 GB per hour.

Procedure

1. Estimate the disaster recovery time for your environment by using the following table. Determine whether the recovery time meets your requirements.

Table 2. Recovery time estimates for differing amounts of total managed data
Recovery time objective Total managed data (TB) Number of hours to repair a directory-container storage pool (First Byte Restored) Number of hours to restore client nodes (Disaster Recovery complete)
Up to 1 day 25

50

75
10

13

17
12

16

22
Up to 2 days 100

200
20

34
26

46
Up to 4 days 300

400
48

62
66

86
More than 4 days 500 76 106
Notes:
  • Achievable rates are highly dependent on the workload and the configured environment.
  • The front-end data percentage is relative to the total managed data. Increasing the amount of front-end data increases the total recovery time. Decreasing the amount of front-end data decreases the total recovery time.
2. Estimate the recovery time for your environment by using the following formulas:
  • Estimate the value Hours until directory-container storage pool is repaired (First Byte Restored):
    Time to Client First Byte Restore = 6 hours + 14 hours for every 100 TB of Total Managed Data
  • Estimate the value Hours until client nodes are restored (Disaster Recovery complete):
    Time to Client Restore Complete = Time to Client First Byte Restore + ((Total Managed Data * Front-End Data) / Restore Rate)

Restore Rate: The rate at which clients can restore data from the server back to their local computer or storage device.

3. Complete test procedures for disaster recovery to ensure that container-copy storage pools can be used to restore your environment in a time frame that meets your requirements.


Copying directory-container storage pools to offsite tape volumes for disaster recovery protection

You can protect data in a directory-container storage pool by copying the data to container-copy storage pools that are stored in offsite tape volumes.

Before you begin
Define at least one tape library to the server by using the DEFINE LIBRARY command. Provision enough tape drives and scratch volumes to meet your storage requirements. For more information about managing backup media and configuring disaster recovery manager (DRM), see Disaster recovery manager (V7.1.1).
Restriction: Virtual tape libraries are not supported, regardless of which library type is defined. Only physical tape is supported.

About this task

A container-copy storage pool protects data in a directory-container storage pool by storing a copy of the data on tape volumes. The tape copy is used to repair damage to a directory-container storage pool.

To copy the data in directory-container storage pools to onsite tape volumes, use the Operations Center. See Copying directory-container storage pools to tape.

To copy the data in directory-container storage pools to offsite tape volumes, use the command-line interface. Using the command-line interface, you can create a maximum of two container-copy storage pools. One copy can be taken to an offsite disaster recovery location. The other copy can be kept onsite to expedite recovery from less-critical failures.

Restriction: You cannot create an onsite container-copy storage pool if you are using replication. If replication is enabled, you can create one offsite container-copy pool. The offsite copy can be used to provide extra protection in a replicated environment. If replication is not enabled, you can create one onsite and one offsite pool.
Procedure

Protect a directory-container storage pool by completing the following steps:

1. Create a container-copy storage pool by issuing the DEFINE STGPOOL command.
2. Assign the container-copy storage pool to the directory-container storage pool by issuing the UPDATE STGPOOL command for the directory-container pool.
3. Schedule protection to offsite and onsite tape copies by issuing the UPDATE SCHEDULE command. When the protection schedule runs, the PROTECT STGPOOL command is issued and the following operations take place:

  • Data extents in the container-copy storage pools are copied to tape volumes without the associated metadata. This metadata is required to restore the tape copies. To protect the metadata, you must separately back up the server database along with its volume history, server options, and device configuration files.
  • Volume reclamation occurs when the reclamation threshold for the container-copy storage pool is less than 100%. However, onsite volumes are not a candidate for reclamation until they are 75% full. Be careful when you use reclamation with container-copy storage pools that have offsite volumes. When an offsite volume becomes eligible for reclamation, in effect the server moves the extents on the volume back to the onsite location. If a disaster occurs onsite, the server can obtain extents from the offsite volume if the restored database refers to extents on the offsite volume. To prevent volumes from being rewritten immediately after all extents are deleted, use the REUSEDELAY parameter to specify a value that is greater than 0.
Results
After you complete the configuration, data in the directory-container storage pool is copied to one or two container-copy storage pools based on the defined protection schedule.

What to do next
  • If you use reclamation with container-copy storage pools that have offsite tape volumes, ensure that the following requirements are met to provide disaster recovery protection:
  • Database backup operations run after storage pool protection schedules and DRM move schedules finish.
  • All database backup volumes and DRM volumes are taken offsite together.
For instructions about backing up the server database and related files, see Defining schedules for server maintenance activities.
  • Offsite container-copy storage pools must be enabled for DRM operations, so the tape volumes are included in offsite tape rotation schedules. Issue the SET DRMCOPYCONTAINERSTGPOOL command to enable the storage pool for DRM operations. If DRM is not configured, you must do so or use an alternate method to rotate tapes offsite. To verify that offsite container-copy storage pools are enabled for DRM, use the QUERY DRMSTATUS command.
    For instructions about configuring DRM, see Disaster recovery manager (V7.1.1).


Repairing and recovering data in directory-container storage pools

You can repair damaged data extents in directory-container storage pools and recover lost data after a disaster.


Repairing storage pools from a target replication server

If files, directories, or storage pools on a source replication server are damaged, you can repair deduplicated data extents in a directory-container storage pool on the source replication server from a target replication server. For instructions, see Repairing storage pools from a target replication server.


Repairing storage pools from container-copy storage pool volumes

If files, directories, or storage pools on a source server are damaged, you can repair data extents in a directory-container storage pool on the source server by retrieving the deduplicated data extents from onsite or offsite container-copy storage pool tape volumes.

Before you begin
Evaluate your storage environment to determine whether outages, network issues, or hardware failures are causing damage to data or causing the data to appear damaged. If issues in your environment are causing damage to data, identify and resolve the issues.
About this task

Use the procedure to repair the following types of damage:

  • Minor damage that is caused by accidental deletion of files or directories, overwritten files, accidental changes in file permissions, or disk errors caused by hardware issues.
  • Moderate damage that is caused by disk errors or disk mount errors. This type of damage results in the loss of one or more directories, but not a loss of the entire storage pool.
Damaged deduplicated extents are repaired with extents that were protected to container-copy storage pools.
Restriction: You can issue the REPAIR STGPOOL command for a specified storage pool only if you already copied the data to container-copy storage pools by using the PROTECT STGPOOL command.
When you repair a directory-container storage pool from container-copy pools, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The container-copy storage pool is unavailable.
  • The container-copy storage pool is damaged.
  • The container-copy storage pool volumes are unavailable or damaged.
Procedure
1. If you suspect minor damage, issue the AUDIT CONTAINER command for the container storage pool at the directory level to identify inconsistencies between the database and the directory-container storage pool. By identifying the damaged data extents in the directory-container storage pool, you can determine which data extents to repair. To conserve time and resources, audit only containers that you suspect are damaged. If you suspect that your container storage pool has more serious damage, issue the AUDIT CONTAINER command at the storage pool level. For example, to audit a directory, n:\pooldir, in a storage pool that is named STGPOOL1, issue the following command:
audit container stgpool=stgpool1 stgpooldirectory=n:\pooldir

To audit a storage pool that is named STGPOOL1, issue the following command:
audit container stgpool=stgpool1

The audit process might run for several hours.

During the repair operation, the server prompts you for the volumes that it requires. In step 3, you will bring the volumes onsite and check them into the library. The required volumes must be brought onsite and checked into the library.
2. To preview the repair operation and generate the list of tape volumes that are needed for the repair operation, issue the REPAIR STGPOOL command and specify the SRCLOCATION=LOCAL and PREVIEW=YES parameters.
For example, to preview the repair operation for a storage pool that is named STGPOOL1 from container-copy storage pools, issue the following command:
repair stgpool stgpool1 srclocation=local preview=yes

The preview process might take some time to finish.
3. If some of the required volumes are offsite, complete the following steps:

a. Use the list from the preview operation to determine which volumes need to be brought onsite.
b. When the volumes are back onsite, check them into the library by issuing the CHECKIN LIBVOLUME command and specifying the STATUS=PRIVATE parameter.
c. Update the status of the volumes by issuing the UPDATE STGPOOL command and specifying the ACCESS=READWRITE parameter.
For detailed instructions about the disaster recovery manager (DRM) function, see Using disaster recovery manager for tape environments (V7.1.1).
4. Based on the information that you obtained during the preview operation, ensure that the storage pool contains enough space for the recovered data. If there is not enough space, use the DEFINE STGPOOLDIRECTORY command to provision space.
5. To repair the directory-container storage pool, issue the REPAIR STGPOOL command and specify the SRCLOCATION=LOCAL parameter.
For example, to repair a storage pool that is named STGPOOL1 from a container-copy storage pool, issue the following command:
repair stgpool stgpool1 srclocation=local

When you issue the REPAIR STGPOOL command, the damaged extents are deleted from the volume immediately after they are repaired. The damaged extents are not retained according to the value specified by the REUSEDELAY parameter.
6. Identify any additional damaged extents by issuing the QUERY DAMAGED command.
7. If damage is detected and deduplicated extents cannot be repaired from the container-copy storage pools, it is still possible that they will be repaired. In some cases, the client node resends data during a backup operation and the damaged extents are repaired. Wait two backup cycles to allow client backup operations to occur. After two backup cycles, complete the following steps:

a. To confirm that the damage is repaired, reissue the QUERY DAMAGED command.
b. If an entire storage pool directory is damaged, create a new replacement storage pool directory using the DEFINE STGPOOLDIRECTORY command.
c. To remove objects that refer to damaged data, issue the AUDIT CONTAINER command and specify the ACTION=REMOVEDAMAGED parameter.
For example, to audit a directory-container storage pool that is named STGPOOL1 and remove damaged objects, issue the following command:
audit container stgpool=stgpool1 action=removedamaged

d. Optionally, issue the DELETE STGPOOLDIRECTORY command to delete the empty storage pool directory that you replaced with a new directory in step 7.b.
8. If you repaired an entire storage pool directory, delete the original directory, which is empty and was replaced by a new directory. Delete the original directory by issuing the DELETE STGPOOLDIRECTORY command.
What to do next
If you continue to detect damaged data over time, issue the AUDIT CONTAINER command for the directory-container storage pool to determine whether there is more widespread damage. For example, to audit a storage pool that is named STGPOOL1, issue the following command:
audit container stgpool=stgpool1




Repairing storage pools in an environment with both a replication server and container-copy storage pool volumes

If files, directories, or storage pools on a source server are damaged, you can repair data extents in a directory-container storage pool on the source replication server by retrieving the deduplicated data extents from either the target replication server or from container-copy storage pool tape volumes.

Before you begin
Evaluate your storage environment to determine whether outages, network issues, or hardware failures are causing damage to data or causing the data to appear damaged. If issues in your environment are causing damage to data, identify and resolve the issues.

Ensure that there is enough available space in the directory-container storage pool for the recovered data. The PREVIEW=YES parameter in the REPAIR STGPOOL command specifies how much data will be repaired. If there is not enough space, use the DEFINE STGPOOLDIRECTORY command to provision space.

About this task
Use the procedure to repair the following types of damage:

  • Minor damage that is caused by accidental deletion of files or directories, overwritten files, accidental changes in file permissions, or disk errors caused by hardware issues.
  • Moderate damage that is caused by disk errors or disk mount errors. This type of damage results in the loss of one or more directories, but not a loss of the entire storage pool.
Damaged deduplicated extents are repaired with extents that were protected to the target replication server or to container-copy storage pools on a source server.
Restriction: You can issue the REPAIR STGPOOL command for a specified storage pool only if you already copied the data to another storage pool on a target replication server or to container-copy storage pools by using the PROTECT STGPOOL command.
When you repair a directory-container storage pool from a target replication server, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The target replication server is unavailable.
  • The target storage pool is damaged.
  • A network outage occurs.
When you repair a directory-container storage pool from container-copy pools, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The container-copy storage pool is unavailable.
  • The container-copy storage pool is damaged.
  • The container-copy storage pool volumes are unavailable or damaged.
Procedure
1. Attempt to repair the storage pool from the target replication server by completing the steps in Repairing storage pools from a target replication server.
2. If the damaged extents cannot be repaired from the target replication server, repair the damaged extents from container-copy storage pools by completing the steps in Repairing storage pools from container-copy storage pool volumes.
3. If you repaired damaged extents from container-copy storage pools, issue the PROTECT STGPOOL command and specify the TYPE=REPLSERVER parameter for the storage pools on the source replication server.
What to do next
If you continue to detect damaged data over time, issue the AUDIT CONTAINER command for the directory-container storage pool to determine whether there is more widespread damage. For example, to audit a storage pool that is named STGPOOL1, issue the following command:
audit container stgpool=stgpool1



Repairing storage pools after a disaster

You can repair directory-container storage pools and recover their lost data after a disaster. If a disaster occurs and your primary site is no longer available, you can repair your directory-container storage pools by restoring them on a new target server at your recovery site.

Repairing storage pools from container-copy storage pool volumes after a disaster

If a disaster occurs on a source server, you can repair deduplicated data extents in a directory-container storage pool from offsite container-copy storage pool tape volumes. The directory-container storage pool is repaired on a target server at a recovery site.

About this task
Use the procedure to repair the following types of major damage:

  • Complete loss of all container storage pools on the source server
  • Complete loss of the primary site
The following assumptions are made for this disaster recovery scenario:
  • You were using the PROTECT STGPOOL command to back up data to offsite container-copy storage pools from a source server. You retrieved the offsite tape volumes and have them at your recovery site.
  • You were not using the PROTECT STGPOOL command to back up data to a target replication server.
  • You used the IBM Spectrum Protect Blueprints to configure the IBM Spectrum Protect source server, and you also used the Blueprint configuration scripts to restore the environment by setting up a new target server at a recovery site. The scripts copied backup versions of the IBM Spectrum Protect database, the server options file (dsmserv.opt), the volume history file (volhist.out), and device configuration file (devconfig.out) to their original locations on the recovery server. After the scripts run, you see the newly created, empty directories on the recovery server.
When you attempt to repair a directory-container storage pool from container-copy pools, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The container-copy storage pool is unavailable.
  • The container-copy storage pool is damaged.
  • The container-copy storage pool volumes are unavailable or damaged.
Procedure
1. Mark all data extents in the container storage pool as damaged by issuing the AUDIT CONTAINER command for the container storage pool at the storage pool level, and specifying the ACTION=MARKDAMAGED parameter.
For example, to audit a storage pool that is named STGPOOL1 and mark it as damaged, issue the following command:
audit container stgpool=stgpool1 action=markdamaged

2. If you protected the directory-container storage pool by using both onsite and offsite container-copy storage pools, issue the UPDATE STGPOOL command for the onsite copy of the container-copy storage pools, and specify the ACCESS=UNAVAILABLE parameter.
3. When the offsite container-copy storage pool volumes are back onsite, check them into the library by issuing the CHECKIN LIBVOLUME command and specifying the STATUS=PRIVATE parameter.
4. Update the status of the volumes by issuing the UPDATE STGPOOL command and specifying the ACCESS=READWRITE parameter.
5. Repair the storage pool by issuing the REPAIR STGPOOL command and specifying the SRCLOCATION=LOCAL parameter.
For example, to repair a storage pool that is named STGPOOL1 from offsite container-copy storage pools, issue the following command:
repair stgpool stgpool1 srclocation=local

When you issue the REPAIR STGPOOL command, the damaged extents are deleted from the volume immediately after they are repaired. The damaged extents are not retained according to the value specified by the REUSEDELAY parameter.
6. Confirm that there are no additional damaged extents by issuing the QUERY DAMAGED command.
7. Repeat this procedure to repair all of your storage pools.


Repairing storage pools from a target replication server after a disaster

If a disaster occurs on a source replication server, you can repair deduplicated data extents in a directory-container storage pool from a target replication server. The directory-container storage pool is repaired on a target server at a recovery site.

About this task
Use the procedure to repair the following types of major damage:

  • Complete loss of all container storage pools on the source replication server
  • Complete loss of the primary site
The following assumptions are made for this disaster recovery scenario:
  • You were using the PROTECT STGPOOL command to back up data from a source replication server to a target replication server. The target replication server is running at your recovery site.
  • You were not using the PROTECT STGPOOL command to back up data to offsite container-copy storage pools.
  • You used the IBM Spectrum Protect Blueprints to configure the IBM Spectrum Protect source server, and you also used the Blueprint configuration scripts to restore the environment by setting up a new target server at a recovery site. The scripts copied backup versions of the IBM Spectrum Protect database, the server options file (dsmserv.opt), the volume history file (volhist.out), and device configuration file (devconfig.out) to their original locations on the recovery server. After the scripts run, you see the newly created, empty directories on the recovery server.
When you attempt to repair a directory-container storage pool from a target replication server, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The target replication server is unavailable.
  • The target storage pool is damaged.
  • A network outage occurs.
Procedure
1. Mark all data extents in the container storage pool as damaged by issuing the AUDIT CONTAINER command for the container storage pool at the storage pool level, and specifying the ACTION=MARKDAMAGED parameter.
For example, to audit a storage pool that is named STGPOOL1 and mark it as damaged, issue the following command:
audit container stgpool=stgpool1 action=markdamaged

2. Repair the storage pool by issuing the REPAIR STGPOOL command and specifying the SRCLOCATION=REPLSERVER parameter.
For example, to repair a storage pool that is named STGPOOL1 from a target replication server, issue the following command:
repair stgpool stgpool1 srclocation=replserver

When you issue the REPAIR STGPOOL command, the damaged extents are deleted from the volume immediately after they are repaired. The damaged extents are not retained according to the value specified by the REUSEDELAY parameter.
3. If you did not use Blueprint configuration scripts to set up your target replication server, the file structure on the target replication server might not match the information that is stored in the database. Optionally, remove the storage pool directories that do not exist on the target replication server by issuing the DELETE STGPOOLDIRECTORY command.
4. Confirm that there are no additional damaged extents by issuing the QUERY DAMAGED command.
5. If damage is detected and deduplicated extents cannot be repaired from the replication server, it is still possible that they will be repaired. In some cases, the client node resends data during a backup operation and the damaged extents are repaired. Wait two backup cycles to allow client backup operations to occur. After two backup cycles, complete the following steps:

a. To confirm that the damage is repaired, reissue the QUERY DAMAGED command.
b. To remove objects that refer to damaged data, issue the AUDIT CONTAINER command and specify the ACTION=REMOVEDAMAGED parameter.
For example, to audit a directory-container storage pool that is named STGPOOL1 and remove damaged objects, issue the following command:
audit container stgpool=stgpool1 action=removedamaged

6. Repeat this procedure to repair all of your storage pools.


Repairing storage pools in an environment with both a replication server and container-copy storage pool volumes after a disaster

If a disaster occurs on a source server, you can repair deduplicated data extents in a directory-container storage pool from a replication target server or from offsite container-copy storage pool tape volumes. The directory-container storage pool is repaired on a target server at a recovery site.

About this task
Use the procedure to repair the following types of major damage:

  • Complete loss of all container storage pools on the source server
  • Complete loss of the primary site
The following assumptions are made for this disaster recovery scenario:
  • You were using the PROTECT STGPOOL command to back up data from a source replication server to a target replication server. The target replication server is running at your recovery site.
  • You were using the PROTECT STGPOOL command to back up data to offsite container-copy storage pools.
  • You used the IBM Spectrum Protect Blueprints to configure the IBM Spectrum Protect source server, and you also used the Blueprint configuration scripts to restore the environment by setting up a new target server at a recovery site. The scripts copied backup versions of the IBM Spectrum Protect database, the server options file (dsmserv.opt), the volume history file (volhist.out), and device configuration file (devconfig.out) to their original locations on the recovery server. After the scripts run, you see the newly created, empty directories on the recovery server.
When you attempt to repair a directory-container storage pool from a target replication server, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The target replication server is unavailable.
  • The target storage pool is damaged.
  • A network outage occurs.
When you repair a directory-container storage pool from container-copy pools, the REPAIR STGPOOL command fails if any of the following conditions occur:
  • The container-copy storage pool is unavailable.
  • The container-copy storage pool is damaged.
  • The container-copy storage pool volumes are unavailable or damaged.
Procedure
1. Mark all data extents in the container storage pool as damaged by issuing the AUDIT CONTAINER command for the container storage pool at the storage pool level, and specifying the ACTION=MARKDAMAGED parameter.
For example, to audit a storage pool that is named STGPOOL1 and mark it as damaged, issue the following command:
audit container stgpool=stgpool1 action=markdamaged

2. If you protected the directory-container storage pool by using both onsite and offsite container-copy storage pools, issue the UPDATE STGPOOL command for the onsite copy of the container-copy storage pools, and specify the ACCESS=UNAVAILABLE parameter.
3. When the offsite container-copy storage pool volumes are back onsite, check them into the library by issuing the CHECKIN LIBVOLUME command and specifying the STATUS=PRIVATE parameter. By moving the tape volumes onsite now, you are prepared to repair damaged extents from the container-copy tape volumes if the damaged extents cannot be repaired from the target replication server.
4. Update the status of the volumes by issuing the UPDATE STGPOOL command and specifying the ACCESS=READWRITE parameter.
5. Repair the storage pool by issuing the REPAIR STGPOOL command and specifying the SRCLOCATION=REPLSERVER parameter.
For example, to repair a storage pool that is named STGPOOL1 from a target replication server, issue the following command:
repair stgpool stgpool1 srclocation=replserver

When you issue the REPAIR STGPOOL command, the damaged extents are deleted from the volume immediately after they are repaired. The damaged extents are not retained according to the value specified by the REUSEDELAY parameter.
6. If you did not use Blueprint configuration scripts to set up your target replication server, the file structure on the target replication server might not match the information that is stored in the database. Optionally, remove the storage pool directories that do not exist on the target replication server. Issue the DELETE STGPOOLDIRECTORY command to delete directories that are not on the target replication server.
7. Confirm that there are no additional damaged extents by issuing the QUERY DAMAGED command.
8. If the damaged extents cannot be repaired from the target replication server, you can repair the damaged extents from offsite container-copy storage pools. For instructions, see Repairing storage pools from container-copy storage pool volumes after a disaster.
9. Confirm that there are no additional damaged extents by reissuing the QUERY DAMAGED command.
10. If damage is detected and deduplicated extents cannot be repaired from the replication server, it is still possible that they will be repaired. In some cases, the client node resends data during a backup operation and the damaged extents are repaired. Wait two backup cycles to allow client backups to occur. After two backup cycles, complete the following steps:

a. To confirm that the damage is repaired, reissue the QUERY DAMAGED command.
b. To remove objects that refer to damaged data, issue the AUDIT CONTAINER command and specify the ACTION=REMOVEDAMAGED parameter.
For example, to audit a directory-container storage pool that is named STGPOOL1 and remove damaged objects, issue the following command:
audit container stgpool=stgpool1 action=removedamaged

11. Repeat this procedure to repair all of your storage pools.

Command Reference: Commands for managing offsite container-copy storage pool tape volumes


Note: Only the updated syntax that is required to use container-copy storage pools for disaster protection is documented below. See the V7.1.7 documentation for the full command reference.


SET DRMCOPYCONTAINERSTGPOOL (Specify the container-copy storage pools to be processed by DRM commands)

Use this command to specify the container-copy storage pools to be processed by the MOVE DRMEDIA or QUERY DRMEDIA command when that command does not include the COPYCONTAINERSTGPOOL parameter.

By default, volumes in container-copy storage pools are not processed by the MOVE DRMEDIA and QUERY DRMEDIA commands. To process the volumes, you must issue the SET DRMCOPYCONTAINERSTGPOOL command, or you must use the COPYCONTAINERSTGPOOL parameter on the MOVE DRMEDIA or QUERY DRMEDIA command.

Tip: To display the current settings, use the QUERY DRMSTATUS command.
Privilege class

To issue this command, you must have system privilege.

Syntax

                              .-,---------.  
                              V           |  
>>-Set DRMCOPYCONtainerstgpool----
pool_name-+------------------><


Parameters

pool_name (Required)

Specifies the names of the container-copy storage pools. Separate multiple names with commas and no intervening spaces. You can use wildcard characters. The specified names replace any previous setting. If you enter a null string (""), all current names are removed.
Example: Specify storage pools to be processed by the MOVE DRMEDIA and QUERY DRMEDIA commands
Set CONTCOPY1 and CONTCOPY2 as the container-copy storage pools to be processed.
set drmcopycontainerstgpool contcopy1,contcopy2



QUERY DRMSTATUS (Query disaster recovery manager system parameters)

Note: One new field description, Container-Copy Storage Pools, was added. See QUERY DRMSTATUS for the full command reference.

Use this command to display information about the system parameters defined for disaster recovery manager (DRM).

Syntax

>>-Query DRMSTatus---------------------------------------------><


Parameters

None.

Example: Display DRM system parameter information
Display information about the DRM system parameters:
query drmstatus
             Recovery Plan Prefix:
        Plan Instructions Prefix:
      Replacement Volume Postfix: @
           Primary Storage Pools: PRIM1 PRIM2
              Copy Storage Pools: COPY*
       Active-Data Storage Pools: TSMACTIVEPOOL
    Container-Copy Storage Pools: COPYCNTRPOOL
     Not Mountable Location name: Local
                    Courier Name: Fedex
                 Vault Site Name: Ironmnt
DB Backup Series expiration days: 30 Day(s)
Recovery Plan File Expiration Days: 30 Days(s)
                    Check Label?: No
       Process FILE Device Type?: No
               Command file name:
             Recovery Plan Prefix:
        Plan Instructions Prefix:
      Replacement Volume Postfix: @
           Primary Storage Pools: PRIM1 PRIM2
              Copy Storage Pools: COPY*
       Active-Data Storage Pools: TSMACTIVEPOOL
       Container-Copy Storage Pools: COPYCNTRPOOL
     Not Mountable Location name: Local
                    Courier Name: Fedex
                 Vault Site Name: Ironmnt
DB Backup Series expiration days: 30 Day(s)
Recovery Plan File Expiration Days: 30 Days(s)
       Process FILE Device Type?: No
               Command file name:

Field descriptions


Container-Copy Storage Pools

The container-copy storage pools that are eligible for processing by the MOVE DRMEDIA, PREPARE, and QUERY DRMEDIA commands. If this field is blank, container-copy storage pools are not eligible.


MOVE DRMEDIA (Move disaster recovery media offsite and back onsite)

Note: One new parameter, COPYCONTAINERSTGPOOL, was added. See MOVE DRMEDIA for the full command reference.

Use this command to track volumes that are to be moved offsite and to identify the expired or empty volumes that are to be moved onsite. You can track database backup volumes, and volumes in copy storage pools, container-copy storage pools, and active-data storage pools.

The processing of volumes by this command depends on what the volumes are used for:

Container-copy storage pools

By default, volumes in container-copy storage pools are not eligible for processing by the MOVE DRMEDIA command. To process container-copy storage pool volumes, you must issue the SET DRMCOPYCONTAINERSTGPOOL command first, or specify the COPYCONTAINERSTGPOOL parameter on the MOVE DRMEDIA command.
Syntax

>>-MOVe DRMedia--
volume_name ------------------------------------>

>--+------------------------------------+----------------------->
 '-WHERESTate--=--+-MOuntable-------+-'  
                  +-NOTMOuntable----+    
                  +-COUrier---------+    
                  +-VAULTRetrieve---+    
                  '-COURIERRetrieve-'    

>--+--------------------+--+------------------+----------------->
 '-BEGINDate--=--
date -'  '-ENDDate--=-- date -'  

>--+--------------------+--+------------------+----------------->
 '-BEGINTime--=--
time -'  '-ENDTime--=-- time -'  

>--+------------------------------------+----------------------->
 '-COPYCONtainerstgpool--=--
pool_name -'  

>--+---------------------------+-------------------------------->
 '-COPYstgpool--=--
pool_name -'  

>--+---------------------------------+-------------------------->
 '-ACTIVEDatastgpool--=--
pool_name -'  

 .-Source--=--DBBackup-------.  
>--+---------------------------+-------------------------------->
 '-Source--=--+-DBBackup---+-'  
              +-DBSnapshot-+    
              '-DBNOne-----'    

 .-REMove--=--Bulk------------.  
>--+----------------------------+------------------------------->
 '-REMove--=--+-No----------+-'  
              +-Yes---------+    
              +-Bulk--------+    
              '-Untileefull-'    

>--+---------------------------------+-------------------------->
 '-TOSTate--=--+-NOTMOuntable----+-'  
               +-COUrier---------+    
               +-VAult-----------+    
               +-COURIERRetrieve-+    
               '-ONSITERetrieve--'    

>--+----------------------------+------------------------------->
 '-WHERELOcation--=--
location -'  

>--+-------------------------+--+-------------------+----------->
 '-TOLOcation--=--
location -'  '-CMd--=-- "command" -'  

                                .-APPend--=--No------.  
>--+---------------------------+--+--------------------+-------->
 '-CMDFilename--=--
file_name -'  '-APPend--=--+-No--+-'  
                                             '-Yes-'    

 .-Wait--=--No------.                      
>--+------------------+--+---------------+---------------------><
 '-Wait--=--+-No--+-'  '-CAP--=--
x,y,z -'  
            '-Yes-'                        


Parameters

volume_name (Required)
Specifies the name of the volume to be processed. You can use wildcard characters. If you use wildcard characters to specify this name, you must also specify the WHERESTATE parameter. The server looks for matching names among the following eligible volumes:

  • Database backup volumes, as specified by the SOURCE parameter of this command.
  • Copy storage pool volumes from the storage pools named in the COPYSTGPOOL parameter. If you do not use the COPYSTGPOOL parameter, the server processes volumes from copy storage pools that were previously specified in the SET DRMCOPYSTGPOOL command.
  • Container-copy storage pool volumes from the storage pools named in the COPYCONTAINERSTGPOOL parameter. If you do not use the COPYCONTAINERSTGPOOL parameter, the server processes volumes from container-copy storage pools that were previously specified in the SET DRMCOPYCONTAINERSTGPOOL command.
  • Active-data storage pool volumes from the storage pools named in the ACTIVEDATASTGPOOL parameter. If you do not use the ACTIVEDATASTGPOOL parameter, the server processes volumes from active-data storage pools that were previously specified in the SET DRMACTIVEDATASTGPOOL command.
Other parameters can also limit the results of the command.

COPYCONtainerstgpool
Specifies the name of the container-copy storage pool whose volumes are to be processed. This parameter is optional. You can use wildcard characters to specify this name. If you use wildcard characters to specify this name, you must also specify the WHERESTATE parameter.

The container-copy storage pools that are specified with this parameter override storage pools that are specified with the SET DRMCOPYCONTAINERSTGPOOL command. If this parameter is not specified, the server selects the storage pools as follows:
  • If the SET DRMCOPYCONTAINERSTGPOOL command was previously issued with valid container-copy storage pool names, the server processes only those storage pools.
  • If the SET DRMCOPYCONTAINERSTGPOOL command was not issued, or if all of the container-copy storage pools were removed by using the SET DRMCOPYCONTAINERSTGPOOL command, the server processes all container-copy storage pool volumes based on the setting of the WHERESTATE parameter. If the parameter is set to a value of NOTMOUNTABLE, COURIER, VAULTRETRIEVE, or COURIERRETRIEVE, the volumes are processed. If the value is MOUNTABLE, the volumes are not processed.


QUERY DRMEDIA (Query disaster recovery media)

Note: One new parameter, COPYCONTAINERSTGPOOL, and one new field description, Container-Copy Storage Pool Name, were added. See QUERY DRMEDIA for the full command reference.

Use this command to display information about database backup volumes, and volumes in copy storage pools, container-copy storage pools, and active-data storage pools. You can also use the command to create a file of executable commands to process the volumes.

The processing of volumes by this command depends on what the volumes are used for:

Container-copy storage pools

By default, volumes in container-copy storage pools are not eligible for processing by the QUERY DRMEDIA command. To process container-copy storage pool volumes, you must issue the SET DRMCOPYCONTAINERSTGPOOL command first, or specify the COPYCONTAINERSTGPOOL parameter on the QUERY DRMEDIA command.
Syntax
 
                .-*-----------.  
>>-Query DRMedia--+-------------+------------------------------->
                '-
volume_name -'  

 .-WHERESTate--=--All-----------------.  
>--+------------------------------------+----------------------->
 '-WHERESTate--=--+-----------------+-'  
                  +-All-------------+    
                  +-MOuntable-------+    
                  +-NOTMOuntable----+    
                  +-COUrier---------+    
                  +-VAult-----------+    
                  +-VAULTRetrieve---+    
                  +-COURIERRetrieve-+    
                  '-REmote----------'    

>--+--------------------+--+------------------+----------------->
 '-BEGINDate--=--
date -'  '-ENDDate--=-- date -'  

>--+--------------------+--+------------------+----------------->
 '-BEGINTime--=--
time -'  '-ENDTime--=-- time -'  

>--+---------------------------+-------------------------------->
 '-COPYstgpool--=--
pool_name -'  

>--+---------------------------------+-------------------------->
 '-ACTIVEDatastgpool--=--
pool_name -'  

>--+------------------------------------+----------------------->
 '-COPYCONtainerstgpool--=--
pool_name -'  

 .-Source--=--DBBackup-------.  .-Format--=--Standard-----.  
>--+---------------------------+--+-------------------------+--->
 '-Source--=--+-DBBackup---+-'  '-Format--=--+-Standard-+-'  
              +-DBSnapshot-+                 +-Detailed-+    
              '-DBNone-----'                 '-Cmd------'    

>--+----------------------------+--+-----------------------+---->
 '-WHERELOCation--=--
location -'  |         .-----------. |  
                                 |         V           | |  
                                 '-CMd--=----
"command" -+-'  

                                .-APPend--=--No------.  
>--+---------------------------+--+--------------------+-------->
 '-CMDFilename--=--
file_name -'  '-APPend--=--+-No--+-'  
                                             '-Yes-'    

>--+-----------------+-----------------------------------------><
 '-LRecl--=--
lrecl -'  


Parameters

volume_name
Specifies the names of the volumes to be queried. You can use wildcard characters to specify multiple names. This parameter is optional. The server looks for matching names among the following eligible volumes:

  • Database backup volumes, as selected by the SOURCE parameter of this command.
  • Copy storage pool volumes from copy storage pools specified by the COPYSTGPOOL parameter. If you do not use the COPYSTGPOOL parameter, the server queries volumes from copy storage pools previously specified by the SET DRMCOPYSTGPOOL command.
  • Active-data storage pool volumes from active-data storage pools specified by the ACTIVEDATASTGPOOL parameter. If you do not use the ACTIVEDATASTGPOOL parameter, the server queries volumes from active-data storage pools that were previously specified by the SET DRMACTIVEDATASTGPOOL command.
  • Container-copy storage pool volumes from container-copy storage pools specified by the COPYCONTAINERSTGPOOL parameter. If you do not use the COPYCONTAINERSTGPOOL parameter, the server queries volumes from container-copy storage pools that were previously specified by the SET DRMCOPYCONTAINERSTGPOOL command.
Other parameters can also limit the results of the query.

COPYCONtainerstgpool
Specifies the name of the container-copy storage pool whose volumes are to be processed. This parameter is optional. You can use wildcard characters to specify this name. The container-copy storage pools that are specified using this parameter override those that are specified using the SET DRMCOPYCONTAINERSTGPOOL command.

If this parameter is not specified, the server selects the storage pools as follows:
  • If the SET DRMCOPYCONTAINERSTGPOOL command was previously issued with names of valid container-copy storage pools, the server processes only those storage pools.
  • If the SET DRMCOPYCONTAINERSTGPOOL command has not been issued, or if all container-copy storage pools were removed using the SET DRMCOPYCONTAINERSTGPOOL command, the server processes all container-copy pool volumes based on the value that is specified by the WHERESTATE parameter. If the parameter is set to a value of ALL, NOTMOUNTABLE, COURIER, VAULT, VAULTRETRIEVE, COURIERRETRIEVE, or REMOTE, the volumes are processed. If the value is set to MOUNTABLE, the volumes are not processed.

Field descriptions


Volume Type
The type of volume. Possible values are:
DBBackup
A full or incremental database backup volume.
DBSnapshot
A database snapshot backup volume.
CopyStgPool
A copy storage pool volume.
ContcopyStgPool
A container-copy storage pool volume.

Container-Copy Storage Pool Name
For a container-copy storage pool volume, the name of the container-copy storage pool.

Document information

More support for: IBM Spectrum Protect
Server

Software version: 7.1.7

Operating system(s): AIX, Linux, Solaris, Windows

Reference #: 7048653

Modified date: 06 October 2016