SnapCenter Issues
SnapCenter Issues
Highest rated
(rating)- CSNAPC-3727: SmCore logs are not getting auto truncated when configured max size is reached
- CSNAPC-5599: No limitation about SnapMirror cascade relationships described in Release Notes
- CSNAPC-3790: SnapCenter if RestMode is enabled and for a resource partial secondary replication policy selected, then secondary restore is failing.
- CSNAPC-4263: Expanding LUNs from SnapCenter Plug-in for Microsoft Windows 5.0 fails with "Failed to resize the LUN. Force parameter specified, which is not supported for REST call"
- CSNAPC-5507: Clone/restore opertation fails for SQL/Oracle/SCW on a VMDK layout over NVMe TCP/IP when we have multiple NVMe subsystems with same ESx host NQN in a SVM and only one NVMe subsystem controller is added from the ESx host.
- CSNAPC-3779: Even though backup is finished, logging to SMCore_JobID.log never finishes
- CSNAPC-3314: Unable to add SVM using IPV6 IP
- CSNAPC-4330: Event IDs are not purging as per the Purge retention settings
- CSNAPC-4027: Oracle Database discovery fails with incorrect Oracle home details in inventory.xml
- CSNAPC-4427: Get-SmBackup cmdlet output format is changed
- CSNAPC-4147: Validation of each archive log using sc_command_executor adds overhead to total backup time
- CSNAPC-5476: Clone fails intermittently when junction Path for the newly created clone is not present.
- CSNAPC-4909: Specify an instance when attempting to create a new credential with SQL Authentication
- CSNAPC-3782: Email notification is not triggered for backup failing with error: "An error occurred while adding job to jobQ: Message Queue service is not available." and scheduled backups continue to fail even after MSMQ service comes up on plugin host
- CSNAPC-3920: SnapCenter Plug-in for SAP HANA Database (SCHANA) 5.0 script usage stops working in 5.0 with backups with more than one SVM name
Recently updated
(date updated)- SnapCenter 5.0: MySQL service does not start on SnapCenter server
- CSNAPC-4147: Validation of each archive log using sc_command_executor adds overhead to total backup time
- CSNAPC-5476: Clone fails intermittently when junction Path for the newly created clone is not present.
- CSNAPC-4909: Specify an instance when attempting to create a new credential with SQL Authentication
- CSNAPC-4427: Get-SmBackup cmdlet output format is changed
- CSNAPC-4956: Unable to upgrade SnapCenter to 5.0 release - when internet connectivity exists
- CSNAPC-4027: Oracle Database discovery fails with incorrect Oracle home details in inventory.xml
- CSNAPC-4330: Event IDs are not purging as per the Purge retention settings
- CSNAPC-5507: Clone/restore opertation fails for SQL/Oracle/SCW on a VMDK layout over NVMe TCP/IP when we have multiple NVMe subsystems with same ESx host NQN in a SVM and only one NVMe subsystem controller is added from the ESx host.
- CSNAPC-4589: SCSQL doesn't use gMSA during a backup job or cloning job
- CSNAPC-4858: Scheduled SCSQL verification jobs fails
- CSNAPC-3082: In-place restore fails while performing pre-restore operations of other nodes in Oracle ASMLib RAC setup having partition on LUNs.
- CSNAPC-3618: SCW generates duplicate entries during file system clone operation
- CSNAPC-3727: SmCore logs are not getting auto truncated when configured max size is reached
- CSNAPC-3782: Email notification is not triggered for backup failing with error: "An error occurred while adding job to jobQ: Message Queue service is not available." and scheduled backups continue to fail even after MSMQ service comes up on plugin host
Recently added
(date created)- CSNAPC-4147: Validation of each archive log using sc_command_executor adds overhead to total backup time
- CSNAPC-5476: Clone fails intermittently when junction Path for the newly created clone is not present.
- CSNAPC-4909: Specify an instance when attempting to create a new credential with SQL Authentication
- CSNAPC-4427: Get-SmBackup cmdlet output format is changed
- CSNAPC-4956: Unable to upgrade SnapCenter to 5.0 release - when internet connectivity exists
- CSNAPC-3782: Email notification is not triggered for backup failing with error: "An error occurred while adding job to jobQ: Message Queue service is not available." and scheduled backups continue to fail even after MSMQ service comes up on plugin host
- CSNAPC-3790: SnapCenter if RestMode is enabled and for a resource partial secondary replication policy selected, then secondary restore is failing.
- CSNAPC-3961: Size textbox in resize wizard is not editable after upgrading to SC5.0
- CSNAPC-4027: Oracle Database discovery fails with incorrect Oracle home details in inventory.xml
- CSNAPC-4330: Event IDs are not purging as per the Purge retention settings
- CSNAPC-3314: Unable to add SVM using IPV6 IP
- CSNAPC-3779: Even though backup is finished, logging to SMCore_JobID.log never finishes
- CSNAPC-5507: Clone/restore opertation fails for SQL/Oracle/SCW on a VMDK layout over NVMe TCP/IP when we have multiple NVMe subsystems with same ESx host NQN in a SVM and only one NVMe subsystem controller is added from the ESx host.
- CSNAPC-4263: Expanding LUNs from SnapCenter Plug-in for Microsoft Windows 5.0 fails with "Failed to resize the LUN. Force parameter specified, which is not supported for REST call"
- CSNAPC-5599: No limitation about SnapMirror cascade relationships described in Release Notes