Protecting data in directory-container storage pools

Edit online

Protect data in directory-container storage pools to reduce node replication time and to enable repair of data in directory-container storage pools.

Before you begin

Ensure that at least one directory-container storage pool exists on the target replication server. When you enable replication in the Operations Center, you can schedule storage pool protection. To configure replication and enable storage pool protection, complete the following steps:

On the Operations Center menu bar, hover over Storage and click Replication.
On the Replication page, click Server Pair.
Complete the steps in the Add Server Pair wizard.

About this task

Protecting a directory-container storage pool backs up data extents to another storage pool, and can improve performance for node replication. When node replication is started, the data extents that are already backed up through storage pool protection are skipped, which reduces the replication processing time. You can schedule the protection of storage pools several times a day to keep up with changes to data.

By protecting a storage pool, you do not use resources that replicate existing data and metadata, which improves server performance. You must use directory-container storage pools if you want to protect and back up the storage pool only.

Alternative protection strategy: As an alternative to using replication, you can protect data in directory-container storage pools by copying the data to container-copy storage pools. Data in container-copy storage pools is stored on tape volumes. Tape copies that are stored offsite provide additional disaster recovery protection in a replicated environment.

Procedure

Alternatively, to enable storage pool protection, you can use the PROTECT STGPOOL command from the source replication server to back up data extents in a directory-container storage pool.
For example, to protect a directory-container storage pool that is named POOL1 issue the following command:
```
protect stgpool pool1
```
As part of the operation of the PROTECT STGPOOL command, damaged extents in the target storage pool are repaired. To be repaired, extents must already be marked as damaged on the target replication server. For example, an AUDIT CONTAINER command might identify damage in the target storage pool before the PROTECT STGPOOL command is issued.
Optional: If damaged extents were repaired in the target storage pool and you protect multiple source storage pools in one target storage pool, complete the following steps to ensure a complete repair:
1. Issue the PROTECT STGPOOL command for all source storage pools to repair as much of the damage as possible.
2. Issue the PROTECT STGPOOL command again for all source storage pools. For this second operation, use the FORCERECONCILE=YES parameter.
  This step ensures that any repairs from other source pools are properly recognized for all source storage pools.

Results

If a directory-container storage pool is protected, you can repair the storage pool if damage occurs, by using the REPAIR STGPOOL command.

Restriction: If you replicate client nodes but do not protect the directory-container storage pool, you cannot repair the storage pool.

What to do next

Optionally, complete the following actions:

To view replication workload status, follow the instructions in the Daily monitoring checklist.
If the IBM® Storage Protect server replicates nodes to a remote server, determine whether IBM Aspera® Fast Adaptive Secure Protocol (FASP®) technology can improve data throughput to the remote server. Follow the instructions in Determining whether Aspera FASP technology can optimize data transfer in your system environment.