Data Protection - Page 126

Northman

We are planning to backup from a C800 cluster with FC storage (VMFS) to a FAS2720 (Unified storage). But in the demo lab I read: " Note: Secondary protection takes care of creating a replication relationship for the resources added in resource group. You need to create a consistency group-based SnapMirror relationship in the preferred cluster and SVM using a specified policy from the primary. The secondary protection is supported only for ASA r2 systems based datastore and virtual machines." So this mean backup to secondary storage is not supported for ASA systems? IF this is possible, I assume we also have to create a SVM with block storage? Can this block storage be iSCSi instead of FC? In the documentation for SCV 6.1 it also says: What’s new in SnapCenter Plug-in for VMware vSphere 6.1 Support for VMs and VMFS datastore on ASA r2 systems The SnapCenter plug-in for VMware vSphere 6.1 release now supports the provisioning of virtual machines (VMs) and VMFS datastore on ASA r2 systems. ASA r2 systems deliver a unified hardware and software solution that creates a simplified experience specific to the needs of SAN-only customers. SnapCenter Plug-in for VMware vSphere 6.1 supported features for VMs, datastores, and Virtual Machine Disk format (VMDK) on ASA r2 systems include: • Consistency group provisioning for primary protection • Consistency group-based backup • Clone workflows • Restore workflows • Secondary protection provisioning when you’re creating or modifying the resource group. The secondary protection is supported only on ONTAP 9.16.1 and later versions" But I am not sure if these statements only apply to ASA r2. Maybe ASA r1 is supported? I see nothing in IMT.

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.

Board Activity

Snapvault support for VMware snapcenter plug-in (SCV 6.1)

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