IBM Support

Db2 Database Requirements: IBM Storage Defender Copy Data Management 2.3.1

Detailed System Requirements


Abstract

This document details the backup and restores requirements for Db2 Database for IBM Storage Defender Copy Data Management 2.3.1.

Content

Important Brand Change Information

The product now known as IBM Storage Defender Copy Data Management was named IBM Storage Copy Data Management in levels earlier than 2.2.26. To learn more about the brand change, see IBM Storage CDM and Sentinel brand change to IBM Storage Defender CDM and Sentinel.
The product now known as IBM Storage Copy Data Management was named IBM Spectrum Copy Data Management in levels earlier than 2.2.20. To learn more about the brand change, see IBM Spectrum Protect brand change to IBM Storage Protect.

General

—
IBM Storage Defender Copy Data Management installs an agent on application servers when they are registered.
—

For AIX-based systems, the agent installation directory must be excluded for any anti-virus software scans. Add this path to the exclusion list for all anti-virus software that is installed on the application server.

/tmp/cdm_guestapps_<username>

Where <username> is the username of the account used to register the application server in IBM Storage Defender Copy Data Management.

—
IBM Storage Defender Copy Data Management support for third-party operating systems, applications, services, and hardware depend on the respective vendor. If a third-party product or version moves into extended support, self-service support, or end-of-life, IBM Storage Defender Copy Data Management supports the product or version at the same level as the vendor. See also IBM Support General Guidelines and Limitations — IBM support for software on unsupported operating systems.

Configuration

Db2 Configuration

Db2 12.1.4 (beginning with 2.3.1)

Storage Systems

IBM Storage Virtualize Software
Software Version: 8.7.0.x, 9.1.3
Server Types
Operating Systems
Storage Configuration
Physical
AIX 7.2 (beginning with 2.3.1)
AIX 7.3 (Version: 7300-04-00)
Fibre Channel

Notes

1.
With CDM 2.3.1 release, Db2 database standalone configurations are supported only.
2.
Cluster Db2 solutions are not supported.
3.
Virtual mode of configuration/registration is not supported for Db2.
4.
Only snapshots of the storage provider type 'IBM Storage Virtualize for Snapshot' are supported.
5.
Db2 archive log mode is not supported. It is recommended to configure Db2 in no archive log mode at present.
6.
Instant database restore for Db2 is not supported for this release.
7.
PIT restore is not supported.
8.
Database Revert is not supported for Db2.
9.
Replication mode is not supported. It includes policy-based replication.

Connectivity

—
The SSH service must be running on port 22 on the server and any firewalls must be configured to allow IBM Storage Defender Copy Data Management to connect to the server by using SSH. The SFTP subsystem for SSH must also be enabled.
—
The server can be registered by using a DNS name or IP address. DNS names must be resolvable by IBM Storage Defender Copy Data Management.
—

To mount clones or copies of data, IBM Storage Defender Copy Data Management automatically maps and un-maps LUNs to the servers. Each server must be preconfigured to connect to the relevant Storage Systems at that site.

—
For Fibre Channel, the appropriate zoning must be configured beforehand.

Prerequisites

On DB2 Server

1. DB2 Installation

—
DB2 must be installed and configured.
—
DB2 instance(s) must be created.
—
DB2 instance must be started before discovery/backup operations.
—
Start DB2 instance.
—
Verify instance is running:
sudo -u db2inst1 db2 get instance

2. Environment Variables

—
The DB2DIR environment variable must be set (e.g., /opt/ibm/db2/V12.1), where V12.1 is the DB2 version. Users can set it as per the DB2 version they have.
—
The DB2DIR environment variable should point to the DB2 installation directory. For DB2 12.1, set it as follows and add to the system-wide profile:
export DB2DIR=/opt/ibm/db2/V12.1
echo "export DB2DIR=/opt/ibm/db2/V12.1" >> /etc/profile.d/db2.sh
Verify DB2DIR is set correctly:
echo $DB2DIR
ls -la $DB2DIR/instance/db2ilist
—
Alternative: DB2 profile at $HOME/sqllib/db2profile for the current user. Supports both default and non-default installation paths via DB2DIR.

3. Python 3.x

—
Python 3.6 or higher required.
—
No additional Python packages needed (uses native DB2 CLI).

4. Sudo Configuration

—
The IBM Storage Defender Copy Data Management agent user needs privileges to run commands as root and other users by using Sudo. These privileges are required for various tasks such as discovering storage layouts and mounting and unmounting disks.
—
The sudoers configuration must allow the IBM Storage Defender Copy Data Management agent user to run commands without a password.
—
The !requiretty setting must be set.
—
Place the following lines at the end of your sudoers configuration file, typically /etc/sudoers:
cdmagent ALL=(ALL) NOPASSWD: ALL
Defaults:cdmagent !requiretty
Defaults:cdmagent env_keep+="DB2INSTANCE"
Defaults:cdmagent env_keep+="DB2_HOME"
Defaults:cdmagent env_keep+="INSTHOME"

5. DB2 CLI Access

—
db2 command must be in PATH or accessible via instance profile.
—
db2ilist command must be available for instance discovery.
—
Database manager must be started (see requirement 1 above).

6. File System Permissions

—
Read access to DB2 instance home directories (e.g., /home/db2inst1).
—
Read access to DB2 configuration files.
—
Read access to database storage paths.

Instant Disk Restore — Db2 Clone Runbook

Overview

This runbook describes the end-to-end automation steps required to clone a Db2 database from an instant disk snapshot mount point. This process isolates the clone so it can run alongside an existing live database on the same instance without causing conflicts or data corruption.

Architectural Rules & Assumptions

Rule
Detail
Database Instance User
db2inst1 (Modify according to your specific environment)
Db2 Naming Limit
The target database clone name must not exceed 8 characters (e.g., PRODCLN)
Transaction Log Isolation
Transaction logs are explicitly rerouted to an isolated local directory (/tmp/PRODCLN) to completely prevent overwriting or locking production log footprints
Catalog Protection
If the source database already exists on the target instance, the relocation utility will temporarily overwrite its registry entry. This runbook includes immediate safety steps to restore the original catalog pointer

Part 1: Provisioning & Initialization

Step 0: Verify Storage Mount Availability

Ensure the instant disk restore job has been successfully executed from your storage copy management software and that the snapshot is presented to the target server.

Example verified output:

df -h
/dev/TGFfslv00 360G 358G 2G 1% /data_1779858852006
Step 1: Prepare Physical Directories & Permissions

Log in to the server as root (or use sudo). We must establish the isolated transaction log landing path and physically align the data directories to match our new 8-character database name.

# 1. Create the isolated transaction log path and apply rigid instance ownership
mkdir -p /tmp/PRODCLN
chown -R db2inst1:db2iadm1 /tmp/PRODCLN
chmod -R 770 /tmp/PRODCLN
# 2. Rename the snapshot physical database folder to match the new target name
mv /data_1779858852006/db2inst1/NODE0000/PRODDB /data_1779858852006/db2inst1/NODE0000/PRODCLN
Step 2: Generate the Db2 Relocation Configuration File

Create the mapping configuration file used by the relocation engine to perform low-level binary data path alterations.

cat << EOF > /tmp/relocate_clone.cfg
DB_NAME=PRODDB,PRODCLN
NODENUM=0
INSTANCE=db2inst1
DB_PATH=/data,/data_1779858852006
STORAGE_PATH=/data,/data_1779858852006
LOG_DIR=/log,/tmp/PRODCLN
EOF

Part 2: Database Relocation & Core Alignment

Step 3: Run the Relocation Utility & Secure Production Catalog

As the db2inst1 user, flush out all active engine Command Line Processor (CLP) caches and initiate the data relocation.

# 1. Purge background connection caches to release file system handles
db2 connect reset
db2 terminate
# 2. Execute the binary relocation utility
db2relocatedb -f /tmp/relocate_clone.cfg
# 3. SAFETY MECHANISM: Immediately restore the original database catalog slot
Step 4: Perform Crash Recovery & Lift Write-Suspension

Because the storage clone was carved out of a live, running snapshot, it remains flagged in an unbuffered "crash" state. We must run crash recovery while simultaneously lifting the snapshot write-lock flag.

# 1. Flush the database backend registry one more time
db2 terminate
# 2. Re-initialize the engine internals, roll back uncommitted work, and resume writes
db2 "RESTART DATABASE PRODCLN WRITE RESUME"

Part 3: Validation & Cleanup

Step 5: Verification Routine

Run these standard queries to confirm that the clone is online, completely independent of production, and using the correct isolated paths.

# 1. Attempt connection to the clone
db2 connect to PRODCLN
# 2. Verify that the active transaction logs are running out of the isolated /tmp directory
db2 get db cfg for PRODCLN | grep -i "Path to log files"
# 3. Test catalog queries to confirm physical stability
db2 list tables

Part 4: Decommissioning & Cleanup Procedures

Step 1: Drop Database Registries (Instance Level)

As the db2inst1 user:

# 1. Terminate any stray or hanging connection handles to the clone
db2 "FORCE APPLICATION ALL"
db2 terminate
# 2. Deactivate the clone to purge active bufferpools from RAM
db2 "DEACTIVATE DATABASE PRODCLN"
# 3. Drop the database from the local instance filesystem and uncatalog it
Step 2: Clear Ephemeral Logs and Storage Mounts (OS Level)

Switch to the root account or use sudo to release the physical server footprints:

# 1. Purge the isolated log files from the /tmp directory structure
rm -rf /tmp/PRODCLN
# 2. Remove the empty directory mount point anchor
rmdir /data_1779858852006
Step 3: Storage UI Confirmation

Return to your Copy Data Management (CDM) user interface. Formally terminate the Instant Disk Restore session to tear down the virtual storage allocation and release SAN/NAS resources.

[{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSJHI7","label":"IBM Storage Defender Copy Data Management"},"ARM Category":[{"code":"a8m3p000000hBYdAAM","label":"HW\/SW Requirements"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.1"}]

Product Synonym

IBM Storage Defender CDM

Document Information

Modified date:
10 July 2026

UID

ibm17274979

Page Feedback