Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 243 results
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/What_logs_are_required_for_SnapCenter_retention_issues
      Job logs and Job ID which should have deleted the snapshot; to pin point it, also provide the job IDs of the jobs before and after for the same schedule type Job logs and Job ID of the original backup...Job logs and Job ID which should have deleted the snapshot; to pin point it, also provide the job IDs of the jobs before and after for the same schedule type Job logs and Job ID of the original backup job which created the snapshot which has not been deleted. Job logs and Job ID of the job which should have deleted it, to pin point it, can also provide the job IDs of the jobs before and after for the same schedule type
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SCE_schedules_not_triggered_post_upgrade_of_SnapCenter_server
      Applies to SnapCenter server SnapCenter Plug-in for Exchange (SCE) Issue After upgrade of SnapCenter server, schedules for SCE with older plug-in version not triggered anymore SnapManagerWeb will have...Applies to SnapCenter server SnapCenter Plug-in for Exchange (SCE) Issue After upgrade of SnapCenter server, schedules for SCE with older plug-in version not triggered anymore SnapManagerWeb will have the following error: ErrorCode (136), ErrorMessage (The user you are trying does not have permission to access the system. Please re-authenticate to continue or contact your administrator.)
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_plug_ins_installation_fails_with__The_RPC_server_is_too_busy_to_complete_this_operation
      As the SnapCenter plug-ins are being pushed to the corresponding host, it fails with the following error message: Error : The RPC server is too busy to complete this operation. 2021-01-14T15:09:31.895...As the SnapCenter plug-ins are being pushed to the corresponding host, it fails with the following error message: Error : The RPC server is too busy to complete this operation. 2021-01-14T15:09:31.8959171-04:00 ERROR SnapManagerWeb_### PID=[7512] TID=[125] ErrorCode (-1), ErrorMessage (The minimum .NET framework version required on the host is v4.5.2. 2021-01-14T15:09:31.9007044-04:00 ERROR SnapManagerWeb_### PID=[7512] TID=[52] The RPC server is too busy to complete this operation
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Unable_to_detect_SnapMirror_or_SnapVault_relationship_after_MetroCluster_switchover
      Applies to ONTAP 9 MetroCluster (MCC) SnapMirror Issue SnapMirror destination information is missing after Switchover or Switchback in the Metrocluster (i.e. on ONTAP Upgrades), for example: After Sit...Applies to ONTAP 9 MetroCluster (MCC) SnapMirror Issue SnapMirror destination information is missing after Switchover or Switchback in the Metrocluster (i.e. on ONTAP Upgrades), for example: After Site A does a 'switchover' of Site B the snapmirror list-destinations the command does not find any of its SnapMirror relationships.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Unable_to_create_backups_of_SQL_with_SnapCenter
      Applies to SnapCenter (SC) Microsoft SQL Server (SQL) Issue SQL databases not available for backup Warning message: Not available for backup. DB is not on NetApp storage, auto-close is enabled or in r...Applies to SnapCenter (SC) Microsoft SQL Server (SQL) Issue SQL databases not available for backup Warning message: Not available for backup. DB is not on NetApp storage, auto-close is enabled or in recovery mode
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_leaves_dead_paths_in_VMware_vCenter_after_unmapping_disks
      2023-06-10T05:31:26.601Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.add] Add path: vmhba3:C0:T0:L50 2023-06-10T05:31:26.602Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.add] Add path: vmhba3:C0...2023-06-10T05:31:26.601Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.add] Add path: vmhba3:C0:T0:L50 2023-06-10T05:31:26.602Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.add] Add path: vmhba3:C0:T1:L50 2023-06-10T05:31:26.605Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba3:C0:T1:L50 changed state from dead 2023-06-10T05:31:26.608Z: [scsiCorrelator] hostname: [vob.scsi.scsipath.pathstate.on] scsiPath vmhba3:C0:T0:L50 changed state from dead 2023-06-10T05:36:30…
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/How_to_protect_a_baseline_snapshot_to_keep_SnapCenter_from_attempting_to_delete_the_primary_snapshot
      Applies to Snapcenter Server Issue The user requires 1 snapshot retention on the production on 2-node cluster, and 30-day retention on the remote vault copy. Error log: This Snapshot copy is currently...Applies to Snapcenter Server Issue The user requires 1 snapshot retention on the production on 2-node cluster, and 30-day retention on the remote vault copy. Error log: This Snapshot copy is currently used as a reference Snapshot copy by one or more SnapMirror relationships. Deleting the Snapshot copy can cause future SnapMirror operations to fail. Error: Remove Snapshot 'fp-gen-c_1wv14plug01_03-20-2018_03.00.24.9348' failed on volume 'DSTR_1EP14LGENC_SATA_FC_FP_V02'.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_Windows_plugin_fails_with_Activity_Discovering_File_System_failed
      Applies to SnapCenter Plug-in for Microsoft Windows Server (SCW) 4.4 Issue SnapCenter Windows plugin fails taking snapshots with error: Activity 'Discovering File-System' failed. Activity 'Discovering...Applies to SnapCenter Plug-in for Microsoft Windows Server (SCW) 4.4 Issue SnapCenter Windows plugin fails taking snapshots with error: Activity 'Discovering File-System' failed. Activity 'Discovering File-System' failed with error: Discovery failed for some of the resources. Please remove any disconnected or deleted disks from the Resource Group.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_repository_is_not_accessible
      After a fresh new installation the SnapCenter Graphical user interface it is not accessible and the following Stack trace it is reported in the Snapmanagerweb.log 2021-12-14T14:20:34.3148274+01:00 DEB...After a fresh new installation the SnapCenter Graphical user interface it is not accessible and the following Stack trace it is reported in the Snapmanagerweb.log 2021-12-14T14:20:34.3148274+01:00 DEBUG SnapManagerWeb PID=[5260] TID=[1] SnapCenterId:Populating the SnapCenter ID. The SnapCenter UI displays the below error when attempting to login SnapCenter repository is not accessible.
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_for_SQL_Plug-In_is_unable_to_enumerate_SQL_Server_Availability_Group
      SnapCenter unable to enumerate SQL Availability Group. SnapCenter interface does not show a SQL Availability Group that exists, even though SnapCenter is able to enumerate disks on each node. DCOM was...SnapCenter unable to enumerate SQL Availability Group. SnapCenter interface does not show a SQL Availability Group that exists, even though SnapCenter is able to enumerate disks on each node. DCOM was unable to communicate with the computer <Windows cluster name> using any of the configured protocols; requested by PID <PID> (C:\Program Files\NetApp\SnapCenter\SnapCenter Plug-in for Microsoft SQL Server\SmSqlServiceHost.exe).
    • https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_Plug-In_installation_fails_due_to_stale_service
      SnapCenter Plug-In for Windows (SCW) SnapCenter Plug-In for Exchange (SCE) SnapCenter Plug-In for SQL (SCSQL) When attempting to install the SCW plug-in package (with or without SCE or SCSQL) you may ...SnapCenter Plug-In for Windows (SCW) SnapCenter Plug-In for Exchange (SCE) SnapCenter Plug-In for SQL (SCSQL) When attempting to install the SCW plug-in package (with or without SCE or SCSQL) you may see the below error message generated in the SnapCenter_Windows_Host_Plug-In_Install_#######.log file 1-1-2021[12:00:00 PM]: (CLR Action): SWInstallerHelper: CheckStaleServiceExist: SCWPluginService is exist, remove the service manually & re-try the installtion again