IBM Support

Oracle Requirements: IBM Storage Defender Copy Data Management 2.3.1

Detailed System Requirements


Abstract

This document details the backup and restore requirements for Oracle 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. Some anti-virus software might flag or attempt to remove the agent software. If you run anti-malware software application servers, exclude the installation path of the IBM Storage Defender Copy Data Management agent.

For Linux-based and 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. For Oracle, InterSystems Caché and IRIS, and SAP HANA:

/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

Oracle Configuration

Oracle 19c configured as: Standalone/RAC in ASM and non-ASM mode
Oracle 21c configured as: Standalone/RAC in ASM and non-ASM mode
Oracle 26ai configured as: Standalone

Storage Systems

IBM Storage Virtualize

Software Version: 8.7.0.x, 8.7.3.x, 9.1.0, 9.1.1, 9.1.2, 9.1.3
IBM SAN Volume Controller
IBM Storwize
IBM FlashSystem

Pure Storage

Pure/Everpure REST API version: 6.9.3

Dell PowerMax

Dell PowerMax 2000/8000
Dell PowerMax 2500/8500
Unisphere version: 10.2.x, 10.3.x, 10.4.x

Dell PowerFlex Manager

Version: 4.6.x, 4.8.x

Note: Due to a known limitation in PowerFlex Manager version 4.6.x and 4.8.x, the standard user account with storage admin privileges is insufficient for performing remote snapshot operations. As a workaround, user must be granted super-user privileges.

Dell PowerStore Manager

Version: 4.4.0

Note: Only Virtual Applications Supported

Server Types
Operating Systems
Storage Configuration
Physical
AIX 7.1
AIX 7.2
AIX 7.3 (Version: 7300-04-00)
Red Hat Enterprise Linux 8.x, 9.x
SUSE Linux Enterprise Server 15.x
Fibre Channel
iSCSI
NFS
Virtual
Red Hat Enterprise Linux 8.x and 9.x
SUSE Linux Enterprise Server 15.x
Physical RDM backed by Fibre Channel or iSCSI disks attached to ESXi
VMDK (dependent and independent disks) on VMFS datastores (Fibre Channel or iSCSI) or NFS datastores
iSCSI disks directly attached to guest operating system
NFS share mapped directly to the guest

Notes

  1. Standalone databases protected by IBM Storage Defender Copy Data Management can be recovered to the same or alternate standalone server installation. When you recover from standalone to RAC, if the source database uses Automatic Storage Management, then it is successfully recovered to all nodes in the destination cluster. If the source database uses non-ASM storage, the database is mounted only on the first node in the destination RAC.
  2. RAC databases protected by IBM Storage Defender Copy Data Management can be recovered to the same or another RAC installation or to a standalone ASM server. To recover a RAC database to a standalone server, the Grid Infrastructure must be installed on the destination server, and an ASM instance must be running.
  3. Oracle Flex ASM is not supported. Oracle ASM is not supported in virtual mode.
  4. RAC database recoveries are not server pool aware. IBM Storage Defender Copy Data Management can recover databases to a RAC, but not to a specific server pools.
  5. IBM Storage Defender Copy Data Management supports recovering databases from a source physical server to a destination-virtual server by provisioning disks as physical RDMs. Similarly, IBM Storage Defender Copy Data Management can recover databases from a source-virtual server that uses physical RDM to a destination physical server. However, source databases on VMDK virtual disks can be recovered only to another virtual server and not to a physical server.
  6. Oracle data must stay directly on one of the supported Storage Systems listed previously. VADP-based protection of virtual Oracle servers is not supported.
  7. On AIX LPAR/VIO servers, Oracle data must stay on disks attached to the server by using NPIV. Virtual SCSI disks are not supported.
  8. Masking and DevOps recoveries are not supported on virtual servers.
  9. For supported VMware vSphere versions, see in System Requirements: IBM Storage Defender Copy Data Management 2.3.1.
  10. Oracle servers registered as Virtual need VMware Tools installed and running.
  11. Data masking is not supported for Oracle in NetApp storage environments. Masking is not supported on source database on NFS (a copy of which cloned and masked) or source databases on replica copies. Instead of the default mirror copy, you must select a snapshot copy as a replication source.
  12. NetApp systems running in 7-Mode are not supported.

  13. Oracle 19c standalone is now supported for AIX 7.3. More requirements:

    Oracle database data and the flash recovery area (FRA) must stay on supported Storage Systems. IBM Storage Defender Copy Data Management can back up archived logs to a supported storage system if they are not already on one.
    During an Instant Database Restore, there might be failures if the new name specified for the restored database is similar to an existing database differing only by numerical suffix. For clustered instances of Oracle databases, the appliance always uses global database name in the UI.
  14. On all supported storage systems, snapshot condense is run during every maintenance jobs.
  15. Supported platforms: IBM Power Systems and Intel based Systems running supported AIX and Linux OS.

  16. For Dell PowerMax Storage:

    Use separate Storage Groups (SG) for different databases for improved performance.
    IBM Storage Defender Copy Data Management supports one parent SG, and it can contain different child SG for different databases.
    Keep datafiles and log files in separate SG.
    When using Parent SG with child SGs, use separate child SGs for data and log.
    For Instant Disk Restore, Host on Dell PowerMax array must have at least one Masking View created for itself, even if the host is a part of a hostgroup having active Masking View.
    Oracle 19c RAC configuration is now supported on the DELL PowerMax storage system.
    Oracle 21c RAC configuration is not supported on the DELL PowerMax storage system.
    For remote replication feature, please create and map the host to the remote array and have at least 1 masking created using it. The portgroup used in the masking view created by the user will be used by the CDM restore job while creating masking view to map the restored volumes to the host on the remote array.
  17. CDM does not support multiple DBs with same db_name (but different db_unique_name), as it relies on db_name to uniquely identify the Oracle home belonging to the database (instance).
  18. User should make sure that Oracle parameters (texts) do not exceed the recommended size by Oracle. e.g. CDM workflow may fail when the size of '_fix_control' parameter exceeds 255 characters.
  19. In Oracle RAC configuration, the cluster database restore will create only a single instance and the restored instance is not registered as a cluster resource.

  20. When the Prepare scripts option is chosen, the files will be copied to the CDM appliance under /data/log/ecxdeployer/<YYYY-MM-DD>/<random generated string> folder.

    Note: To run these scripts, they need to be copied from this folder of the CDM appliance to any preferred location on the Oracle Server.

    In order to execute the scripts, follow these steps as an Oracle user:

    a. Export the Oracle SID as the SID used during recovery.
    b. When executing an SQL script, login to SQLPlus using sqlplus / as sysdba. You can then run the script: @<location in oracle server>/Step-<number>_<operation>.sql
    c. When executing an RMAN script, login to RMAN using rman target=/. You can then run the script as: @<location in oracle server>/Step-<number>_<operation>.rman

  21. For Dell PowerFlex Storage:

    Ensure that the VMware ESXi hostnames registered in Dell PowerFlex Storage exactly match the hostnames configured on the VMware vSphere environment.
    Ensure that the Dell PowerFlex SDC component is installed and running on ESXi hosts where the application VMs are hosted.

  22. Applications that are registered as Physical for Dell PowerFlex need to follow the below steps. Since SDC setup is done as root user, binaries like drv_cfg are not accessible for non-root users which are used in Application registration.

    namei -l $(readlink -f /opt/emc/scaleio/sdc/bin/drv_cfg)
groups <username>
groupadd powerflex
usermod -aG powerflex <username>
groups <username>
chgrp -R powerflex /usr/bin/emc
chgrp -R powerflex /usr/bin/emc/scaleio/
chmod -R g+rx /usr/bin/emc/scaleio/
chgrp -R powerflex /opt/emc/scaleio
chmod -R g+rx /opt/emc/scaleio
chmod g+rx $(readlink -f /opt/emc/scaleio/sdc/bin/drv_cfg)
namei -l $(readlink -f /opt/emc/scaleio/sdc/bin/drv_cfg)

Oracle Support for VMware Virtual Machines

For Oracle servers running as VMware virtual machines, UUID must be enabled to run Oracle-based backup functions. To enable: power off the guest machine through the vSphere client, then select the guest and click Edit Settings. Select Options, then General under the Advanced section. Select Configuration Parameters..., then find the disk.EnableUUID parameter. If set to FALSE, change the value to TRUE. If the parameter is not available, add it by clicking Add Row, set the value to TRUE, then power on the guest.

Oracle support for VMware virtual machines requires Oracle data and logs to be stored on VMDK virtual disks or physical RDMs. Virtual RDM disks are not supported. The VMDKs must stay on a datastore created on LUNs from supported Storage Systems. Similarly, the physical RDMs must be backed by LUNs from supported Storage Systems.

Note: For Oracle RAC clustered nodes running vSphere 6.5 or later, if an existing shared SCSI controller is not found, IBM Storage Defender Copy Data Management automatically enables the "multi-writer" sharing option for each shared virtual disk.

Restore Jobs

If the xfsprogs package version on the destination server is between 3.2.0 and 4.1.9, the restore process might fail when you restore a database or file system from an XFS file system. To resolve the issue, upgrade xfsprogs to version 4.2.0 or later.

Revert Jobs

Restrictions:

Oracle revert jobs are only supported for backups using the IBM Storage Virtualize for snapshot provider, Dell PowerMax and Dell PowerFlex storage providers.

Note – With Dell PowerMax and Dell PowerFlex storage provider, revert with remote/replicated copy is not supported.
When you run revert jobs on Oracle, there are special considerations that must be met for jobs to successfully complete.
Oracle data, log and the operating system (OS) file system must be on separate datastores/LUNs. Make sure that the databases are on independent storage.
The underlying storage volume for the databases (data and log disks) being reverted should not contain data for other databases and should not contain a datastore that is shared by other VMs or by another database not being reverted.
Make sure that the production databases are not on VMDK disks that are part of a VMware VM snapshot.
All VM snapshots need to be removed from the Oracle server before you run the revert function.
Production databases are automatically shut down during the revert.
Revert is available only after a restore is completed.
Oracle ASM/RAC backups can only be restored on the same host.

When you create a job, you need to set the default revert action for the job. This behavior is controlled through the Revert Database option during the job creation process:

Enabled – Always revert the database.
Disabled – Never reverts the database.
User Selection – Allows the user to make the determination to revert the database when the job session is pending.

Note – 'Make Permanent' option will be disabled when Revert is enabled.

Restrictions:

The Revert function is not supported for AIX based Oracle deployments.
The Revert function is not supported for LVM based Oracle deployments.

Software

The bash and sudo packages must be installed. Sudo must be version 1.8.29 or later. Run sudo -V to check the version.

Python version 3.x must be installed. It might be necessary to add your python3 binary file location to the system PATH or to create a symbolic link. For example, if your python3 is installed at /opt/freeware/bin, you need to create a link as follows:

ln -s /opt/freeware/bin/python3 /usr/bin/python3

On AIX systems, it might be necessary to rerun any AIX inventory jobs.

RHEL 8.x or later: Ensure that the util-linux package is up to date by running:

yum update util-linux

Depending on your version or distribution, the package might be named util-linux.

RHEL 8.x or later: A required Perl module, Digest:MD5, is not installed by default. Install the module by running:

yum install perl-Digest-MD5

Linux only: If data stays on LVM volumes, ensure that the LVM version is 2.03.02 or later. To check the LVM version and if necessary to update the package, run:

lvm version
yum update lvm2

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.
When you register Oracle RAC nodes, register each node by using its physical IP or name. Do not use a virtual name or Single Client Access Name (SCAN).

To mount clones or copies of Oracle data, IBM Storage Defender Copy Data Management automatically maps and unmaps LUNs to the Oracle 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.
For iSCSI, the Oracle servers must be configured beforehand to discover and log in to the targets on the storage servers.

Authentication and Privileges

Authentication

The Oracle server must be registered in IBM Storage Defender Copy Data Management by using an operating system user that exists on the Oracle server (referred to as "IBM Storage Defender Copy Data Management agent user" for the rest of this topic).
During registration, you must provide either a password or a private SSH key that IBM Storage Defender Copy Data Management uses to log in to the server.
For password-based authentication, ensure that the password is correctly configured and that the user can log in without facing any other prompts, such as prompts to reset the password.

For key-based authentication, ensure that the public SSH key is placed in the appropriate authorized_keys file for the IBM Storage Defender Copy Data Management agent user.

Typically, the file is at /home/<username>/.ssh/authorized_keys
Typically, the .ssh directory and all files under it need their permissions set to 600.

Privileges

The IBM Storage Defender Copy Data Management agent user needs the following privileges:

Privileges to run commands as root and other users by using sudo. IBM Storage Defender Copy Data Management requires these privileges 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.
The ENV_KEEP setting must allow the ORACLE_HOME and ORACLE_SID environment variables to be retained.
Privileges to read the Oracle inventory. IBM Storage Defender Copy Data Management requires those privileges to discover and collect information about Oracle homes and databases. To achieve discovery and collection of information, the IBM Storage Defender Copy Data Management agent user must belong to the Oracle inventory group, typically named oinstall.

SYSDBA privileges for database instances. IBM Storage Defender Copy Data Management needs to run database tasks like querying instance details, hot backup, RMAN cataloging, and starting and stopping instances during recovery.

To achieve database tasks, the IBM Storage Defender Copy Data Management agent user must belong to the OSDBA operating system group, typically named dba.
If multiple Oracle homes each with a different OSDBA group, the IBM Storage Defender Copy Data Management agent user must belong to each group.

SYSASM privileges, if Automatic Storage Management (ASM) is installed. IBM Storage Defender Copy Data Management needs to run storage tasks like querying ASM disk information, and renaming, mounting, and unmounting diskgroups.

To achieve storage tasks, the IBM Storage Defender Copy Data Management agent user must belong to the OSASM operating system group, typically named asmadmin.
Shell user limits for the IBM Storage Defender Copy Data Management agent user must be the same as those limits for the user that owns the Oracle home, typically named oracle. Refer to Oracle documentation for requirements and instructions on setting shell limits. Run ulimit -a as both the oracle user and the IBM Storage Defender Copy Data Management agent user and ensure that their settings are identical.

For examples on creating a new user with the necessary privileges, see Sample Configuration in Oracle requirements.

Discovery

Oracle Home Discovery for Symbolic Links

IBM Storage Defender Copy Data Management discovers Oracle installations and databases by looking through the files /etc/oraInst.loc and /etc/oratab, as well as the list of running Oracle processes. When you connect to a database instance to discover its properties, IBM Storage Defender Copy Data Management connects by setting the ORACLE_HOME environment variable based on the path that was auto discovered.

In some cases, when Oracle databases are used in combination with SAP software for instance, a symbolic link to the Oracle Home path might be created. This link path can then be used by the database administrator to connect to the database.

Consider the following example where the real Oracle Home path can be /u01/app/oracle/product/19c/dbhome_1, while the symbolic link that points to it is /oracle/PRODDB/19c.

$ ls -l /oracle/PRODB
lrwxrwxrwx. 1 oracle oinstall 19c -> /u01/app/oracle/product/19c/dbhome_1

When IBM Storage Defender Copy Data Management connects to the instance by using the real, auto-discovered path, queries against the database can fail due to the ORACLE_HOME environment variable being incorrectly set. To override the auto-discovered path and force IBM Storage Defender Copy Data Management to use the correct symbolic link path, a configuration file must be defined on each Oracle server where symbolic links are in use.
Create or edit if it exists a file named /etc/guestapps_oraHomes.conf. Insert into this file these entries:

# Define one entry per line.
# Each entry must be in the form: <instanceName> = <oraHomePath>
# Lines beginning with the '#' character are ignored.
PRODDB = /oracle/PRODDB/19c
TESTDB = /oracle/TESTDB/19c

To ensure that the configuration file is readable by the agent user, run the following command:

chmod 644 /etc/guestapps_oraHomes.conf

Database Discovery

IBM Storage Defender Copy Data Management discovers Oracle installations and databases by looking through the files /etc/oraInst.loc and /etc/oratab, and the list of running Oracle processes. If the files are not present in their default location, the "locate" utility must be installed on the system so that IBM Storage Defender Copy Data Management can search for alternative locations of these files.

IBM Storage Defender Copy Data Management discovers databases and their storage layouts by connecting to running instances and querying the locations of their data files, log files, and other files. In order for IBM Storage Defender Copy Data Management to correctly discover databases during cataloging and copy operations, databases must be in "MOUNTED," "READ ONLY," or "READ/WRITE" mode. IBM Storage Defender Copy Data Management cannot discover or protect database instances that are shut down.

Databases must use a server parameter file (spfile). IBM Storage Defender Copy Data Management does not support copy operations for databases that use a text-based parameter file (pfile).

ASM Disk Discovery

When IBM Storage Defender Copy Data Management mounts snapshots or clones of ASM disks, it configures the disks to set the appropriate permissions required to make them discoverable by ASM:

The disk owner and group are set to the owner of the Grid installation and the OSASM group, which are typically grid and asmadmin. IBM Storage Defender Copy Data Management automatically discovers the appropriate owner and group information on each server.
The disk permissions are set to 660.

IBM Storage Defender Copy Data Management creates aliases or symbolic links with names that follow a consistent pattern. Ensure that ASM is able to discover the disks mapped by IBM Storage Defender Copy Data Management and update the ASM_DISKSTRING parameter to add this pattern.

Linux: IBM Storage Defender Copy Data Management creates udev rules for each disk to set the appropriate ownership and permissions. The udev rules also create symbolic links of the form /dev/ecx-asmdisk/<diskId> that point to the appropriate device under /dev.
To ensure that the disks are discoverable by ASM, add the following pattern to your existing ASM_DISKSTRING: /dev/ecx-asmdisk/*

AIX: IBM Storage Defender Copy Data Management creates a device node (by using mknod) of the form /dev/ecx_asm<diskId> that points to the appropriate hdisk under /dev. IBM Storage Defender Copy Data Management also sets the appropriate ownership and permissions for this new device.
To ensure that the disks are discoverable by ASM, add the following pattern to your existing ASM_DISKSTRING: /dev/ecx_asm*

Notes:

If the existing value of the ASM_DISKSTRING is empty, you might have to first set it to an appropriate value that matches all existing disks, then append the previous value.
If the existing value of the ASM_DISKSTRING is broad enough to discover all disks (for example: /dev/*), you might not need to update it.
Refer to Oracle documentation for details about retrieving and modifying the ASM_DISKSTRING parameter.

Sample Configuration

The following commands are examples for creating and configuring an operating system user that IBM Storage Defender Copy Data Management uses to log in to the Oracle server. The command syntax might vary depending on your operating system type and version.

Create the user that is designated as the IBM Storage Defender Copy Data Management agent user:

useradd -m cdmagent

If you use password-based authentication, set a password:

passwd cdmagent

If you use key-based authentication, place the public key in /home/cdmagent/.ssh/authorized_keys, or the appropriate file depending on your sshd configuration, and ensure that the correct ownership and permissions are set:

chown -R cdmagent:cdmagent /home/cdmagent/.ssh
chmod 700 /home/cdmagent/.ssh
chmod 600 /home/cdmagent/.ssh/authorized_keys

Add the user to the Oracle installation and OSDBA group:

usermod -a -G oinstall,dba cdmagent

If ASM is in use, also add the user to the OSASM group:

usermod -a -G asmadmin cdmagent
Note: If on AIX, the append argument (-a) needs to be omitted when you use the usermod command.

Place the following lines at the end of your sudoers configuration file, typically /etc/sudoers. If the existing sudoers file is configured to import configuration from another directory (for example, /etc/sudoers.d), you can also place the lines in a new file in that directory:

Defaults:cdmagent !requiretty
Defaults:cdmagent env_keep+="ORACLE_HOME"
Defaults:cdmagent env_keep+="ORACLE_SID"
cdmagent ALL=(ALL) NOPASSWD:ALL

[{"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

BM Storage Defender CDM

Document Information

Modified date:
05 July 2026

UID

ibm17275580

Page Feedback