REPAIR STGPOOL not repairing all extents
The PROTECT STGPOOL command might not protect all data extents on the target replication server.
Who is affected: All IBM Spectrum Protect server users who use the PROTECT STGPOOL command with the REPLICATE NODE command by using IBM Spectrum Protect Version 7.1.7 or later.
In the following configuration:
SERVERA: The source server in a replication configuration to SERVERB
SERVERB: The target server in a replication configuration from SERVERA, and source server in a replication configuration to SERVERC
SERVERC: The target server in a replication configuration from SERVERB
If the PROTECT STGPOOL and REPLICATE NODE commands are used from SERVERA to SERVERB, non-deduplicated data extents are skipped during storage pool protection from SERVERB to SERVERC. No error message is displayed when the PROTECT STGPOOL command skips data extents.
In an alternative configuration:
SERVERA: The source server in a replication configuration to SERVERB.
SERVERB: The target server in a replication configuration from SERVERA, and in a storage pool protection configuration to a local container-copy storage pool.
The PROTECT STGPOOL command skips non-deduplicated data extents from SERVERB to the container-copy storage pool that is configured on SERVERB. No error message is displayed when the PROTECT STGPOOL command skips data extents.
In both configurations:
If you have non-deduplicated data extents that are damaged in the directory-container storage pool on SERVERB, attempts to repair that data with the REPAIR STGPOOL command fail. No error message is displayed by the REPAIR STGPOOL command.
If you have non-deduplicated data extents that are damaged in the directory-container storage pool on SERVERB, the following error messages are displayed when the data is retrieved:
Some of these steps use DB2 queries. Run the commands in the following way:
- On Windows, use the DB2 command line window to run the statements. Before you run the DB2 statements, issue the following DB2 command: "set db2instance=<name>" where <name> is the name of the server when it was installed. For example, SERVER1.
- On Linux, AIX and Solaris, these commands must be run by the instance ID that is used to run the server.
For all operating systems, issue these commands to initialize the DB2 environment:
1. db2 connect to tsmdb1
2. db2 set schema tsmdb1
To determine whether skipped data extents exist in your server environment, complete the following steps:
1. From the SERVERB, issue the following command to identify the pool ID that must be checked for skipped data extents:
db2 "select poolid from ss_pools where poolname=upper('Pool1')"
Replace Pool1 with the name of your storage pool.
2. Then, use the pool ID that is displayed in the output of step 1 and issue the following command:
db2 "select 1 from sd_non_dedup_locations where poolid=<poolID> and refcount>1 for read only with ur"
If the number 1 is displayed in the output of step 2, skipped data extents exist in your environment.
If you use the PROTECT STGPOOL and REPLICATE NODE commands in your configuration, and you use replication to protect your data to a second target server, issue both the PROTECT STGPOOL and REPLICATE NODE commands on the first target server until the fix for IT20527 is applied.
If you use the PROTECT STGPOOL and REPLICATE NODE commands in your configuration, and you use container-copy storage pools, avoid this configuration until the fix for IT20527 is applied.
This problem will be resolved in IBM Spectrum Protect levels 184.108.40.206, 7.1.8, and 8.1.2. This is subject to change at the sole discretion of IBM. The APAR fix is designed to prevent the problem, but the fix will not protect non-deduplicated data extents that are already skipped. After you apply the fix for IT20527 use the PROTECT STGPOOL command and specify the FORCERECONCILE=YES parameter to ensure that all data extents are protected.
|Storage Management||Tivoli Storage Manager||Server||AIX, Linux, Solaris, Windows||7.1.7||All Editions|
More support for:
IBM Spectrum Protect
Software version: 7.1.7, 8.1, 8.1.1
Operating system(s): AIX, Linux, Solaris, Windows
Software edition: All Editions
Reference #: 2003223
Modified date: 09 May 2017
Translate this page: