Preventive Service Planning
Abstract
This document details the known Issues and limitations for IBM Storage Defender Copy Data Management 2.x.x
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.
📋 Quick Navigation
Limitations
Catalog Backup Fails with FileNotFoundError for /host/backup Path
(Internal reference# ISCDM-29290)
Problem: While creating a catalog backup using the CLI command cdm catalog backup on IBM Storage Defender Copy Data Management 2.3.2 GA Build 931, the backup operation fails with a FileNotFoundError. Although the configured backup output directory is /tmp/scdm/catalog/backup, the backup process attempts to create the backup under /host/backup/, resulting in the following error:
FileNotFoundError: [Errno 2] No such file or directory: '/host/backup/defender-cdm-2.3.2-931-10-09-2026-15-40-backup'
As a result, the catalog backup operation is aborted and no backup is created.
Workaround: Restart the Catalog service pod and rerun the backup command.
kubectl delete pod scdm-service-catalog-5dd8bfd758-rqvpx -n scdm
Wait for the replacement Catalog pod to reach the Running state, then execute:
cdm catalog backup
The catalog backup completes successfully after the Catalog pod restart.
Limitation valid since: 2.3.2
Point-in-time restore not supported for physical SQL server across Dell storages
(Internal reference# ISCDM-28873)
Problem: Point-in-time not supported for physical SQL server across Dell storages.
Workaround: None
Limitation valid since: All Versions
Job-Level Snapshot Pre/Post Scripts are not executed for applications hosted on RDM volumes
(Internal reference# ISCDM-28514)
Problem: When Job-Level Snapshot Pre/Post Scripts are configured for applications hosted on RDM volumes, the scripts are not executed during the backup workflow. The backup job completes successfully, but the configured Pre/Post Scripts are not triggered for Oracle-RDM, IRIS-RDM, HANA-RDM, and SQL-RDM workloads. This functionality works as expected for Virtual and Physical deployments.
Workaround: None
Limitation valid since: All Versions
RRP (vMotion) Restore Failure After Initial Attempt with Powered-On VM
(Internal reference# ISCDM-26732)
Problem: When performing an Instant VM Restore using the RRP (vMotion) option while the original VM is still powered on, the job correctly fails with the expected error: "VM (vm_name) is powered on and therefore cannot be deleted. Power off the VM before retrying." However, after powering off the original VM and retrying the same restore job: The restore operation fails with a generic error: "A problem occurred while carrying out the requested operation" Additional observations: The cleanup restore action also fails with the same error. Re-running the restore using the same restore job continues to fail with the same message. The issue persists even after retries on the same job configuration. Recovery behavior: Creating a new restore job and performing the restore with the original VM powered off works successfully. This indicates that the restore job enters an inconsistent or unusable state after the first failed attempt when the VM is powered on.
Workaround: Do not reuse the same restore job after an initial failure caused by the VM being powered on. Instead: Power off the original VM. Create a new restore job. Execute the RRP (vMotion) restore again. This approach avoids the inconsistent job state and ensures successful restore execution.
Limitation valid since: 2.x
Sentinel Scanning is now supported for LVM based application servers
(Internal reference# ISCDM-26701)
Problem: Sentinel scanning jobs for Oracle, IRIS, and SAP HANA Physical LVM Database workloads may fail during the scan process when attempting to import cloned LVM volume groups. The failure is associated with vgimportclone command execution errors, causing the Sentinel scan job to terminate unsuccessfully.
Workaround: Update the global_filter configuration in /etc/lvm/lvm.conf to allow clone multipath and SCSI devices:
global_filter = [ "a|/dev/mapper/mpath.|", "a|/dev/sd.|" ]
After updating the configuration, refresh the LVM cache:
pvscan --cache
Verify that the cloned device is detected by LVM:
pvdisplay /dev/<clone_device>
After applying the configuration, the cloned devices should be detected successfully by LVM, allowing pvscan, pvdisplay, and vgimportclone commands to function as expected. Sentinel scanning jobs can then complete successfully for the affected LVM-based workloads.
Limitation valid since: 2.x
Restore to alternate server fails if both source and destination Oracle database hosts are ASM databases configured in virtual mode
(Internal reference# ISCDM-24940)
Problem: If oracle ASM database is configured using VMFS datastores and registered as virtual application in CDM, then during the restore to alternate host, it fails to restore the database.
Workaround: It is advised to use ASM configuration in physical mode only.
Limitation valid since: 2.3.1
The IBM Storage Defender Copy Data Management installation may fail on IBM Power with "provided IP is already allocated" error
(Internal reference# ISCDM-23996 & ISCDM-24731)
Problem: When the user installs IBM Storage Defender Copy Data Management installation on IBM Power, it may fail due to "provided IP is already allocated" error, leading to pod failures in installation. The installation logs may show below error message.
Workaround: Uninstall and then reinstall using the shell scripts provided with the IBM Storage Defender Copy Data Management installable to re-install. If the issue persists, contact IBM Support.
Limitation valid since: 2.3.0.0
Admin Console System Actions not triggering operations in IBM Storage Defender CDM
(Internal reference# ISCDM-25222)
Problem: While attempting to perform system actions from the CDM Admin Console, the UI reflects successful execution message, however no actual operations are triggered in the backend system.
Workaround: There are more ways to perform similar operation, e.g. SSH to CDM appliance and perform the required system operations like reboot or you may use hypervisor controls to reboot the CDM VM appliance.
Limitation valid since: 2.3.0.0; starting 2.3.2.0 Admin Console is deprecated.
Unable to login using created tenant account details
(Internal reference# ISCDM-25220)
Problem: Users are unable to login in with the newly created tenant account credentials, The login attempts failed despite correct user name and password being entered.
Workaround: Detailed steps are provided in the end-user documentation.
Limitation valid since: 2.3.0.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 upto 2.2.28.0; Virgo is removed starting 2.3.0.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: 1) Manually clean up the stale volume groups from the AIX proxy server. 2) 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.
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
Common Limitations (2.3.2)
After upgrade to 2.3.2, the next runtime displayed for Scheduled Jobs may show the Next RUNTIME in the past
Problem: After upgrading to version 2.3.2, the Next Runtime displayed for scheduled jobs may initially show an incorrect time in the past. This is a display-only issue and does not affect schedule execution. Scheduled jobs will continue to run as expected. After the job runs for the first time following the upgrade, the Next Runtime value is automatically updated and displayed correctly.
Workaround: None
Limitation valid since: 2.3.2
NetApp Mirror/Vault policies in SLA are ignored during backup, causing Snapshot+Mirror and Snapshot+Vault jobs to fail
Problem: When an SLA is configured using the NetApp provider with Snapshot and replication policies (Snapshot+Mirror or Snapshot+Vault), backup jobs do not honor the configured Mirror or Vault sub-policies. During execution, CDM creates only a local snapshot and disregards the associated replication policies defined in the SLA.
Workaround: None
Limitation valid since: 2.3.2
Copy Data Management catalog backup or restore job using cdm tool may fail with a time out error
Problem: In Copy Data Management appliance with large MongoDB database (several gigabytes in size), a catalog backup or restore job may report a timeout error even though the operation completes successfully. For catalog backup operations, you can verify successful completion by checking for the generated catalog backup file in the default location:
/tmp/scdm/catalog/backup. This issue is limited to the job status reporting and does not affect the actual backup or restore operation.Workaround: None
Limitation valid since: 2.3.2
IBM Storage Virtualize for Snapshot Limitations (2.3.2)
IBM Storage Virtualize for Snapshot Inventory job for grid systems displays In Progress status even after successful completion
Problem: In some environments, the IBM Storage Virtualize for Snapshot Inventory job completes successfully at the overall job level, but the grid systems task within the job logs displays In Progress status for the associated storage arrays, such as Gorgon and Kobold.
Workaround: Ignore the status if the job is completed successfully.
Limitation valid since: 2.3.2
InterSystems IRIS Limitations (2.3.2)
EPIC / InterSystems IRIS filesystem-level protection limitations
Problem: The following limitations apply to filesystem-level backup and restore for EPIC / InterSystems IRIS environments:
- Validated topology: Only the tested file system-to-LVM-to-storage topology is validated (IRIS Databases > Filesystem > Logical Volume > Volume Group > Physical Volume(s) > Storage Volume(s)). Deviations from the validated storage mapping may result in unknown behavior.
- Protection boundary: Protection is provided at the filesystem level. Namespace-level and database-level protection are not provided through filesystem-level workflows.
- Cross-filesystem dependencies: IBM Storage Defender Copy Data Management does not automatically analyze dependencies between databases or application components across multiple filesystems. Ensure that all dependent filesystems are included in backup and restore operations.
- Environment refresh: Environment refresh is not supported for file system-level protection.
- Storage array remote replication: Dell and IBM storage-array remote replication might not function as intended with granular filesystem-level EPIC / IRIS workflows.
- Post-restore IRIS application visibility: A restore operation creates and mounts the restored filesystem but does not automatically configure the restored databases to make them visible to the IRIS application. An IRIS database administrator must perform the required configuration, or you can automate the configuration by using a Post Restore Job Run Script.
- Non-standard filesystem-to-storage mappings: Configurations outside the supported filesystem/LVM/storage topology are not validated and might result in unknown behavior.
- Application-level dependencies: IBM Storage Defender Copy Data Management does not independently validate IRIS database relationships, application dependencies, or application-specific post-restore requirements.
Workaround: For cross-filesystem dependencies, ensure that all dependent filesystems are selected together for backup and restore operations. For post-restore IRIS configuration, an IRIS database administrator can perform the required configuration, or you can automate the configuration by using a Post Restore Job Run Script.
Limitation valid since: 2.3.2
Hyper-V SCVMM Limitations (2.3.2)
Backup job fails when a Cluster Shared Volume (CSV) is taken offline
(Internal reference# ISCDM-28580)
Problem: When a Cluster Shared Volume (CSV) is taken offline manually, a backup job that starts after a few minutes may fail. The following error is logged:
Storage disk not found for volume: C:\ClusterStorage\<VolumeName> in cluster <ClusterID> (checked <N> disks on VMHost: <hostname>) for VM ID: <VMID>Workaround: Ensure that all CSVs are online and in a healthy state before starting a backup job. Do not take a CSV offline while a backup job is in progress.
Limitation valid since: 2.3.2
Restore job intermittently fails with a "Mount CSV datastores: Failed" error for backups taken with a CSV offline
(Internal reference# ISCDM-28581)
Problem: When a restore job is created from a backup that was taken while a CSV was offline, the restore job may intermittently fail with the error:
Mount CSV datastores: Failed (0 objects). This failure occurs because SCVMM returns a SOAP fault error or reports that the disk number is not found in the available cluster disks.Workaround: Retry the restore job after a short interval to allow SCVMM to recover and report the correct disk state.
Limitation valid since: 2.3.2
VM-consistent and application-consistent backups are not supported for Hyper-V SCVMM
Problem: VM-consistent backups and application-consistent backups are not supported for Hyper-V SCVMM integration.
Workaround: None
Limitation valid since: 2.3.2
Restore to the original VM or cluster is not supported for Hyper-V SCVMM
Problem: Restore to the original VM or cluster is not supported. Only alternate-cluster restore is supported.
Workaround: None
Limitation valid since: 2.3.2
Revert and in-place restore operations are not supported for Hyper-V SCVMM
Problem: Revert and in-place restore operations are not supported for Hyper-V SCVMM integration.
Workaround: None
Limitation valid since: 2.3.2
Restore of VMs from a Hyper-V 2025 host to a Hyper-V 2022 host is not supported for ReFS-backed CSVs
Problem: Restore of VMs created by using ReFS-backed CSVs from a Hyper-V 2025 host to a Hyper-V 2022 host is not supported.
Workaround: None
Limitation valid since: 2.3.2
Network selection may not be retained when a restore job is edited (Hyper-V SCVMM)
Problem: When a non-default network is selected during restore job creation and the job is subsequently edited, the network selection may not be retained.
Workaround: None
Limitation valid since: 2.3.2
Static IP pool workflow is not supported for Hyper-V SCVMM
Problem: The static IP pool workflow is not supported. Only DHCP-based networking is available.
Workaround: None
Limitation valid since: 2.3.2
Only Fibre Channel storage environments are supported for Hyper-V SCVMM
Problem: Only Fibre Channel storage environments are supported. Other transport types, such as iSCSI, are not supported for Hyper-V SCVMM integration.
Workaround: None
Limitation valid since: 2.3.2
Each restore operation always creates a new dedicated CSV (Hyper-V SCVMM)
Problem: Each restore operation always creates a new dedicated Cluster Shared Volume (CSV). Placement onto an existing CSV is not supported.
Workaround: None
Limitation valid since: 2.3.2
Restore of VMs that use multiple CSVs is not supported (Hyper-V SCVMM)
(Internal reference# ISCDM-26999)
Problem: Restore of VMs that use multiple Cluster Shared Volumes (CSVs) is not supported.
Workaround: None
Limitation valid since: 2.3.2
Pre and post operation scripts are not supported for Hyper-V SCVMM
Problem: Pre and post operation scripts are not supported for Hyper-V SCVMM backup and restore operations.
Workaround: None
Limitation valid since: 2.3.2
PBR and PBHA configurations are not supported for Hyper-V SCVMM workloads
Problem: PBR and PBHA configurations cannot be used with Hyper-V SCVMM workloads.
Workaround: None
Limitation valid since: 2.3.2
Restore of Generation 1 (Gen1) virtual machines fails when the "Power on after recovery" option is enabled
(Internal reference# ISCDM-27051)
Problem: When you restore a Generation 1 (Gen1) virtual machine, the restore operation might fail with the error
Validate VM disks failed if the Power on after recovery option is enabled in the restore job's advanced settings.Workaround: Clear the Power on after recovery option and run the restore job again. After the restore operation completes successfully, manually power on the restored virtual machine.
Limitation valid since: 2.3.2
Multi-Disk VM restore fails from Windows Server 2022/SCVMM 2022 to Windows Server 2025/SCVMM 2025
(Internal reference# ISCDM-28263)
Problem: Restoring a multi-disk virtual machine fails when the backup is taken from a Windows Server 2022 / SCVMM 2022 environment and restored to a Windows Server 2025 / SCVMM 2025 environment. The reverse restore path (2025 to 2022) completes successfully. Single-disk virtual machines are not affected.
Workaround: None
Limitation valid since: 2.3.2
Recovery points are prematurely deleted for Hyper-V VMs sharing a CSV
(Internal reference# ISCDM-28318)
Problem: When multiple Hyper-V VMs that reside on the same CSV are protected in a single backup job using an Add Snapshot SLA policy with Snapshot Count set to 1, the maintenance job might delete a recovery point before its configured retention period expires. This occurs because the maintenance job tracks snapshots by LUN ID instead of using recovery point metadata, causing recovery points for VMs sharing the same CSV to be incorrectly identified and deleted.
Workaround: Create separate backup jobs for each VM that resides on a shared CSV. Separate backup jobs generate unique job and session IDs, preventing the maintenance job from incorrectly identifying and deleting recovery points associated with other VMs on the same CSV.
Limitation valid since: 2.3.2
Restoring Generation 1 Hyper-V virtual machine fails with "Create hardware profile: Failed (0 objects)" error
(Internal reference# ISCDM-27051)
Problem: When restoring a Generation 1 Hyper-V virtual machine that uses a VHD disk from a valid backup recovery point, the restore operation fails with the error:
Create hardware profile: Failed (0 objects).Workaround: Clear the Power on after recovery option and run the restore job again. After the restore operation completes successfully, manually power on the restored virtual machine.
Limitation valid since: 2.3.2
Sentinel Limitations (2.3.2)
Disabling the IBM Storage FlashSystem volume protection feature is a prerequisite for using Sentinel
Problem: The IBM Storage FlashSystem volume protection feature must be disabled before using Sentinel. If the volume protection feature is enabled, Sentinel operations that require snapshot creation or volume manipulation may fail because the protection feature prevents the necessary storage operations from being performed.
Workaround: Disable the volume protection feature on IBM Storage FlashSystem before configuring or running Sentinel backup and scan jobs.
Limitation valid since: 2.3.2
Datastore based VMware backup jobs do not trigger Sentinel scan
Problem: When Sentinel scanning is enabled in IBM Storage Defender Copy Data Management, Sentinel scans are not triggered when an entire VMware datastore is selected as the backup source. VMware consistent backup jobs with Sentinel scanning enabled are not supported for datastore-based backups.
Workaround: Configure the backup job by selecting individual virtual machines (VMs) instead of a datastore to ensure Sentinel scanning runs successfully.
Limitation valid since: 2.3.2
Permanent Restrictions
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: Since 2.2.10.0. Permanent restriction, see APAR IT42565.
Solved Limitations
Malware signature file upload fails with an RPM installation error
(Internal reference# ISCDMSEN-295)
Problem: When users download malware signature files and try to upload them through the UI, the upload operation fails with the following error message: "Something went wrong during upgrade: zypper reported error installing rpm. RPM package of software upgrade: ransomsigdb-20251128-01"
Workaround: None
Limitation valid since: 2.3.1
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 to 2.3.1.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
CDM LDAP Users connected to LDAP server using SSL endpoint are unable to execute Jobs created by self
(Internal reference# ISCDM-25656)
Problem: CDM LDAP Users connected to LDAP server using SSL endpoint are unable to execute Jobs created by self.
Workaround: Jobs created by local Admin Users can be executed by secure LDAP Users.
Limitation valid since: 2.3.0.1. Solved with 2.3.1.1
LDAP Authentication Failure in Fresh Deployments and Upgrades
(Internal reference# ISCDM-23037)
Problem: LDAP-based login fails in both fresh CDM deployments and upgraded environments. Users are unable to authenticate using LDAP credentials when the SSL checkbox is selected.
Workaround: None
Limitation valid since: 2.2.26 to 2.3.0. Solved with 2.3.1.1
Remote replication backup copies are displayed as Local during restore job creation for Pure based application
(Internal reference# ISCDM-26709)
Problem: When creating a restore job using a remote replication backup copy across all supported applications, the backup version selection interface incorrectly displays all copy locations as Local instead of Remote. This misrepresentation occurs in the "Copy" selection step when choosing the backup version, leading to potential confusion regarding the actual location of the backup copy.
Workaround: Restores can still be performed successfully by selecting the required backup copy, despite the incorrect location labeling.
Limitation valid since: 2.3.0. Solved with 2.3.1.1
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 valid since: 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 valid since: Since 2.2.7.4. Solved with 2.2.18
Related Information
[{"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":"a8m3p000000hBYSAA2","label":"Troubleshooting"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.26"},{"Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS57AN","label":"IBM Spectrum Copy Data Management"},"ARM Category":[{"code":"a8m3p000000hBYSAA2","label":"Troubleshooting"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Type":"MASTER"},{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCY00","label":"IBM Storage Copy Data Management"},"ARM Category":[{"code":"a8m3p000000hBYSAA2","label":"Troubleshooting"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.25"}]
Was this topic helpful?
Document Information
Modified date:
12 October 2026
UID
ibm16841453