Preventive Service Planning
Abstract
This document details the known Issues and limitations for IBM Storage Defender Copy Data Management 2.2.x
Content
- 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.
This document is divided in to linked sections for ease of navigation. Use the following links to jump to the section of the document that you require:
Restore of oracle database fails on Dell PowerMax if selected restore with additional parameters like putting database in read-only or noarchivelog mode (internal reference# ISCDM-21767)
Problem: During the restore of oracle database deployed on Dell PowerMax or Dell PowerFlex storage, if user selects to configure database in read-only mode or configure it in noarchivelog mode using Advanced options, restore job fails to complete with error-that it failed to run additional parameters.
Workaround: None. User should avoid using these advanced options to restore Oracle DB on Dell Storage platform.
Limitation valid since: 2.2.27.0
Adding private key does not work in CDM UI, if ssh private and public keypair is generated using "ssh-keygen" command (internal reference# ISCDM-19507)
Problem: As per CDM documentation, 'ssh-keygen' is to be used for creating public and private key pairs, which later is to be used to register applications using these key pairs. But such keypairs generated using ssh-keygen fails to get registered in CDM. It however works if ssh-keygen command is supplemented with parameter -t rsa
Workaround: Use this command to generate private & public keypairs "ssh-keygen –t rsa –m PEM
Limitation valid since: 2.2.28.0
Virgo service may fail to start with timeout error after the appliance reboot (internal reference# ISCDM-21336)
Problem: User may get a screen with message "Error : 500 Internal Server Error" when trying to access the CDM UI portal after a usual reboot or after successful upgrade followed by reboot, due to the time taken by the Virgo service to start.
Workaround: In case the Virgo service fails to start, user can restart the Virgo service using one of the following methods:
- Login to the AdminConsole UI, navigate to 'Perform System Actions' tile and select the 'Restart' button on the 'Restart IBM Storage Defender CDM' tile.
OR
- SSH to the CDM appliance with root user and execute the following command:
"systemctl restart virgo"
Limitation valid since: 2.2.26.0
CDM UI generates an error "Identity can not be deleted as it is in use" when user try to delete both, the Key and the Credential for unregistered SAP HANA (internal reference# ISCDM-21350)
Problem: If SAP HANA registered using private key and database credentials, unregistering it successfully still does not allow you to remove the leftover private Key and database Credential and generates an error "Identity can not be deleted as it is in use".
Workaround: Create new private Key and Credential for SAP HANA registration.
Limitation valid since: 2.2.27.0
SCDM UI job log displays zero snapshot created for FC 2.0 volume snapshots if snapshots created with consistency group (internal reference# ISCDM-19428)
Problem: If volume snapshots (IBM FC 1.0 and FC 2.0) are taken with consistency group enabled, it shows in job log that it has created zero snapshots but internally on backend it does create snapshots and seen with IBM SVC storage CLI. Given this, functionality wise it is working fine, and issue is limited with CDM UI only where it incorrectly states it created zero snapshots.
Workaround: Use flash storage CLI to see the snapshot backup job created.
Limitation valid since: 2.2.26.0
Use of same SLA policy with multiple jobs could result in empty consistency groups on IBM Storage FlashSystem when the flash copies are condensed by SCDM maintenance job (internal reference#ISCDM-18841)
Problem: The maintenance job does not condense the flash copies when same SLA policy is used for multiple jobs.
Workaround: Remove the empty Flash copy mappings manually, remove respective jobs and SLA policy then re-create the SLA policy, create a new job and apply the policy keeping in mind 1 - 1 policy and job mapping.
Limitation valid since: 2.2.21.0
Upgrading to 2.2.25 may take more time than previous upgrades (internal reference# ISCDM-18424)
Problem: During upgrade from the previous versions to 2.2.25 takes longer.
Workaround: N/A. Estimated time increase ~ 50% than past upgrade experiences.
Limitation valid since: 2.2.25.0
Static IP to SCDM appliance not applied during deployment (internal reference# ISCDM-18591)
Problem: During the over deployment the properties entered for static IP address settings are not honoured.
Workaround: Use DHCP address (with MAC address binding) for the SCDM appliance.
Limitation valid since: 2.2.25.0
Cancelling the job before inventory completion can lead to inconsistent / hung job state (internal reference# ISCDM-16263)
Problem: When executing a job pressing the cancel button before the inventory completion can lead to an inconsistent and hung state of the job.
Workaround: Please reach out to the IBM support team.
Limitation valid since: 2.2.25.0
VMFS scanning jobs may exhibit an error with multiple SCSI stale disks (internal reference#ISCDM-17169)
Problem: VMware VMFS scanning job using different types of operating systems VMs for SGC 2.0 copies may exhibit the error "LAN indexing job failed", if it has multiple SCSI stale disks
Workaround: Reboot the Index Engine Host to remove the SCSI stale disks
Limitation valid since: 2.2.24.0
VM Replication is not support for Spectrum Virtualize for snapshot (internal reference#ISCDM-16261)
Problem: The VM replication function, which uses VADP for the backup for virtual machines does not work for the Spectrum Virtualize for snapshot SLA policy. If a VMware backup uses the Spectrum Virtualize for snapshot SLA policy with VM replication as a backup type, the backup job fails.
Workaround: When you create the Spectrum Virtualize for snapshot SLA policy, do not select the VM replication backup type.
Limitation valid since: 2.2.20.0
Oracle RAC is not supported for backup with Spectrum Virtualize for snapshot SLA policy (internal reference#ISCDM-16264)
Problem: Oracle RAC databases cannot be backed up with the Spectrum Virtualize for snapshot SLA policy. IBM Spectrum Copy Data Management does not create volume group snapshots for Oracle RAC volumes.
Workaround: Oracle RAC databases cannot have the Spectrum Virtualize for snapshot SLA policy selected.
Limitation valid since: 2.2.20.0
Volume Restore is not supported for volume group snapshots (internal reference#ISCDM-16259)
Problem: Volume restore is not available for storage controller restore when the backup is using a Spectrum Virtualize for snapshot SLA policy. The only restore type for Spectrum Virtualize for snapshot is Instant disk restore.
Workaround: When you create a restore job for Spectrum Virtualize for snapshot, instant disk restore is the only option that runs successfully.
Limitation valid since: 2.2.20.0
Oracle backup data masking is not supported for volume group snapshots (internal reference#ISCDM-16270)
Problem: Oracle backup jobs that are using the Spectrum Virtualize for snapshot SLA policy is not able to run data masking operations on the backups.
Workaround: The data masking option for Oracle backup jobs with the Spectrum Virtualize for snapshot SLA policy must be disabled.
Limitation valid since: 2.2.20.0
Orphaned volumes on AIX proxy server with Storage Sentinel (internal reference #ISCDM-16547)
Problem: During the unmounting operation of the filesystem on the AIX proxy server, the operation might fail to complete in a specified amount of time. As a result of this failure, the AIX proxy server is left with stale volume groups thus causing failure in the subsequent jobs.
Workaround:
- Manually clean up the stale volume groups from the AIX proxy server.
- Increase the unmount command timeout in the system property named "protection.application.AIX.proxy.unmount.timeout.seconds" which can be found in the "com.syncsort.dp.xsb.serviceprovider.properties" properties file.
Limitation valid since: 2.2.19.0
Incremental FlashCopy for Local and GlobalMirror backups is not supported for applications deployed virtually on VMs (internal reference#ISCDM-14024)
Problem: Using the Spectrum Virtualize incremental FlashCopy option within the Spectrum Virtualize snapshot SLA directs to an issue. If the application is deployed virtually and has its data and logs on virtual disks (VMDKs), the incremental option does not work properly.
Problem Verification: The incremental volume flash copies are not created on the Spectrum Virtualize (Flash System) storage and subsequent recovery jobs that try to use those backups fail. Further, the maintenance clean-up shows up log errors during trying to clean up those backups when their retention expires.
Workaround: Do not use FlashCopy Incremental for FlashCopy or Global Mirror in the SLA for backups of any Applications (Intersystems, SAP Hana, Oracle, or SQL) on Virtual Servers. Virtual servers are servers where the disks are VMDKs.
Limitation valid since: Since 2.2.10.
IBM Spectrum Copy Data Management does not support SAP HANA revert running on HyperSwap environments (internal reference #ISCDM-15708)
Problem: The revert function on SAP HANA is not supported for SAP HANA databases that are running on HyperSwap. The revert function requires disabling the HyperSwap relationship before it can run a revert on the SAP HANA database volumes.
Problem Verification: The revert job produces an error that is stating that the volumes that are being reverted is in an active-active relationship.
Workaround: User must break manually the HyperSwap relationship before you run the SAP HANA revert job in IBM Spectrum Copy Data Management.
Limitation area: IBM Spectrum Copy Data Management.
Limitation: Since 2.2.10.0. Permanent restriction, see APAR IT42565.
Restore to same host or alternate host for Oracle database fails if it is configured on LVM disks (internal reference# ISCDM-21253)
Problem: If Oracle database is configured on LVM partitions/disks, database backup succeeds but restore to the same host or alternate host fails.
Workaround: No workaround present at this time
Limitation valid since: 2.2.25.0 Solved with 2.2.28
SCDM UI job log displays zero snapshot created for FC 2.0 volume snapshots if snapshots created with consistency group (internal reference# ISCDM-19428)
Problem: If volume snapshots (IBM FC 1.0 and FC 2.0) are taken with consistency group enabled, it shows in job log that it has created zero snapshots but internally on backend it does create snapshots and seen with IBM SVC storage CLI. Given this, functionality wise it is working fine, and issue is limited with CDM UI only where it incorrectly states it created zero snapshots.
Workaround: Use flash storage CLI to see the snapshot backup job created.
Limitation valid since: 2.2.26.0 Solved with 2.2.27
Use of same SLA policy with multiple jobs could result in empty consistency groups on IBM Storage FlashSystem when the flash copies are condensed by SCDM maintenance job (internal reference#ISCDM-18841)
Problem: The maintenance job does not condense the flash copies when same SLA policy is used for multiple jobs.
Workaround: Remove the empty Flash copy mappings manually, remove respective jobs and SLA policy then re-create the SLA policy, create a new job and apply the policy keeping in mind 1 - 1 policy and job mapping.
Limitation valid since: 2.2.21.0 Solved with 2.2.26
Upgrading to 2.2.25 may take more time than previous upgrades (internal reference# ISCDM-18424)
Problem: During upgrade from the previous versions to 2.2.25 takes longer.
Workaround: N/A. Estimated time increase ~ 50% than past upgrade experiences.
Limitation valid since: 2.2.25.0 Solved with 2.2.26
IBM Spectrum Copy Data Management does not reject invalid values for the cleaning rate (internal reference #ISCDM-15794)
Problem: In the Global settings menu, you can enter a value for the cleaning rate for IBM Spectrum Virtualize storage. The value entered is not restricted to only valid values for the storage.
Workaround: Enter a valid value for the cleaning rate for IBM Spectrum Virtualize storage controllers. The supported range is 1 - 150, inclusive. For more information, see Background copy and cleaning rates - IBM Documentation.
Limitation area: IBM Spectrum Copy Data Management.
Limitation: Since 2.2.18.0. Solved with 2.2.19
IBM Spectrum Copy Data Management does not automatically restart after update (internal reference #ISCDM-14968)
Problem: After you upgrade, IBM Spectrum Copy Data Management appliance must be restarted manually. If IBM Spectrum Copy Data Management appliance is not restarted, there might be issues.
Workaround: Restart the IBM Spectrum Copy Data Management appliance manually through the administrator console.
Limitation area: IBM Spectrum Copy Data Management.
Limitation: Since 2.2.7.4. Solved with 2.2.18
Related Information
Was this topic helpful?
Document Information
Modified date:
12 December 2025
UID
ibm16841453