Data Protection - Page 10

JS75

Hello Does anyone know the reason for default snapshot names in SnapCenter begin uppercase like 'Daily', 'Weekly', while ONTAP defaults to all lower 'daily', 'weekly' etc. Since snapshot names are case sensitive it's causing confusion and complexity with protection policies. thanks, Jacek

Suhaib_Ali

Dear Community support. we are using ONTAP PowerShell ToolKit to automate the SnapMirror failover failback procedure. We are unable to find the reverse sync script for failback. The source SVM is SVM1 and the destination SVM is DR_SVM1. volume on source is App_Repo_32k and destination App_Repo_32k_des Also kindly provide the correct failover and failback procedure with PowerShell ToolKit. Thanks

Dave22

Good afternoon, we are trying to upgrade several instances of Snapcenter Server 5.0 to 6.1P1 and do a clean install of 6.1P1 on a new server. we keep running into the following error message: 'Package SMCoreError: Service 'Snapcenter SMCore Service" failed to start. Verify that you have sufficient privileges to start system services'. the server we are installing on is Windows Server 2022. we have installed the MS .net requirements and are in the administrators group so i know its not a privileges issue. Has anyone run into this and come up with a resolution? there is a kb i found but following this we are still getting the same msg during installation. https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_6.0_installation_fails_Unable_to_start_SMCore_service

georgewong2424 · ‎2025-03-25

While monitoring network port traffic, we observed that SnapMirror traffic is being routed through e0M instead of e0f and e3d (InterCluster LIF). Unified Manager indicates that e0M utilization has reached 100%, while e0f shows 0%. Since e0f and e3d have been configured as the SnapMirror InterCluster LIFs, we expected the traffic to be routed through e0f. I checked the Broadcast Domain, I found that only the e0f and e3d ports on both nodes are in the independent Broadcast Domain, no e0M in the Broadcast Domain group.

shirotan · ‎2022-01-25

For example, if snapshot is set for the share of \\ svm01 \ smb02, the \\ svm01 \ smb02 \ ~ snapshot folder will be displayed for FAS. (When show snapshot is set) -exclude path (‘* \ ~ snapshot \ *’) was able to exclude at scan time. I wanted to exclude the regular folder \\ svm01 \ smb02 \ test, but I didn't exclude it without -exclude path (‘* \\ test \\ *’).(Two \) It seems that some folders can be excluded with -exclude path (‘* \ <$ name> \ *’), but what is the condition for having to add two \s? Or is it better to always have two \s attached?

Board Activity

default snapshot name case in SCS vs ONTAP

NetApp Power Shell Tool Kit

Snapcenter 6.0, 6.1P1 upgrade error

SnapMirror traffic is being routed through e0M instead

XCP exclusion