SnapCenter Issues
SnapCenter Issues
Highest rated
(rating)- CSNAPC-3727: SmCore logs are not getting auto truncated when configured max size is reached
- CSNAPC-8104: MySQL instance discovery fails on Linux when multiple instances are configured to run on the same port
- CSNAPC-10088: Resource group modification fails due to multiple entries for same file system in NSM Db
- CSNAPC-8350: Disk enumeration and backup fails when CSV disk owner is different from cluster owner
- CSNAPC-9735: Add support for ASMLibV3 in SCO
- CSNAPC-9769: SCO backup verification leaves stale export policies on ONTAP
- CSNAPC-9849: SnapCenter performance issue loading topology info when snaplock retention is enabled
- CXPLAT-1623: SCV 6.1 backup fails even if non-NetApp storage is not selected in Spanning disks
- CSNAPC-9889: Jobs scheduled to run after 10:38 on Sunday and Wednesday are delayed to run later in SnapCenter 6.1
- CSNAPC-9937: Oracle temp files are not consistently restored with SnapCenter.
- CSNAPC-9999: Implement a SC-SPL keep-alive mechanism during a long running SCC hana restore workflow
- CSNAPC-10032: SCO clone considers RMAN recovery output as failure instead of success
- CSNAPC-9444: SnapCenter Linux optional precheck script fails on RHEL
- CXPLAT-1678: [Doc Bug] Global permission as a requirement for vCenter RBAC is missing in SCV product document
- CSNAPC-9695: SC 6.x - All PostgreSQL instances have the same name (postgres_5432)
Recently updated
(date updated)- CXPLAT-1823: SCV 6.2 onwards Controlplane and WFE logs are flushed into syslog
- CSNAPC-11069: When there are multiple retention subjobs in the queue, SnapCenter only starts the first subjob in the queue
- CSNAPC-10255: SnapCenter DeleteBackup skips backup data removal from NSM for SCE resources, resulting in job entries piling up
- CSNAPC-9708: Edit a Resoruce Group in SnapCenter 6.1P1 can fail with "the transaction is aborted" and "An item with the same key has already been added"
- CSNAPC-4330: Event IDs are not purging as per the Purge retention settings
- CSNAPC-10116: SCE 6.2 - GetTargetLunInfo FAILED when using SVM FQDN
- CSNAPC-8304: Backup/clone/restore fails when SCW running under gMSA user account with Windows Failover cluster
- CSNAPC-7547: SnapCenter Dashboard showing "0 x" and "No data available" for Storage Savings after upgrading to 6.X
- CSNAPC-10673: ORASCPM (Oracle Applications) plug-in fails a backup when instance tablespaces are offline
- CSNAPC-11232: SC 6.1 SnapCenter_RefreshBackupSnapLock fails with FK constraint
- CXPLAT-1479: Unable to add datastore to Resource Group due to form size
- CSNAPC-11206: SC 6.2P1: Schedule Tab Does Not Display All Schedules Created for a resource group
- CSNAPC-11168: Snapcenter should retry 'Add-NcLunMap' when clone fails due to vserver reconfig locking
- CSNAPC-11099: For SC retention triggers even if the backup operation fails causing deletion of older backup when retention period is set by days.
- CXPLAT-1150: SnapLock Expiry Time differs from 24 hours depending on timezone of SCV
Recently added
(date created)- CSNAPC-11232: SC 6.1 SnapCenter_RefreshBackupSnapLock fails with FK constraint
- CXPLAT-1966: NFS based Datastore or VM SCV backups fail for few hours after service restart
- CSNAPC-11211: Delete clone / Get clone by ID via REST API deletes the oldest clone regardless of the specified ID
- CSNAPC-11076: RG edit/creation fails with Selected resources are combination of ASAR2 platform and non-ASAR2 platform types
- CSNAPC-11206: SC 6.2P1: Schedule Tab Does Not Display All Schedules Created for a resource group
- CSNAPC-11125: SnapCenter Host page "Search by name" function no longer works
- CSNAPC-11147: Sd* powershell cmdlets issue after ugprade to SnapCenter
- CSNAPC-11168: Snapcenter should retry 'Add-NcLunMap' when clone fails due to vserver reconfig locking
- CSNAPC-10961: Restore of a Failover Cluster Hyper-V VM fails if cluster owner node is not the same node as the Hyper-V VM registered node.
- CSNAPC-11099: For SC retention triggers even if the backup operation fails causing deletion of older backup when retention period is set by days.
- CSNAPC-11104: NFS storage discovery fails after restart of SMCore or reboot of SnapCenter Server
- CSNAPC-11069: When there are multiple retention subjobs in the queue, SnapCenter only starts the first subjob in the queue
- CSNAPC-10980: SnapCenter should report overall status as failed even if one of the sub-job fails
- CSNAPC-10964: Orphaned SVMs persist in SnapCenter cache even after Cluster is deleted from Storage Settings in SnapCenter
- CSNAPC-8320: SnapCenter report missing jobHost information using Resource Groups
