Preventive Service Planning
Abstract
This document details the known Issues and limitations for IBM Storage Copy Data Management 2.2.x
Content
Note: 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:
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.
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:
14 June 2024
UID
ibm16841453