Data Protection - Page 126

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

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

georgewong2424

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?

limitless · ‎2025-02-12

> version NetApp Release 9.15.1P5 1. I have a snapmirror relationship and I manually mirrored a snapshot "test5" from source to destination using the below command. Dest > snapmirror -update -destination-path <> -snapshot test5 2. I created a flexclone at the destination using the snapshot test5 > vol clone show Parent Parent Parent Vserver FlexClone Vserver Volume Snapshot State Type ------- ------------- ------- ------------- -------------------- --------- ---- dest vol_dest_clone dest vol_dest test5 online RW 3. Now, I deleted(accidentally) the test5 snapshot at the source forcefully *> snap delete -vserver source -volume vola -snapshot test5 -ignore-owners true 4. The snapmirror relationship is not affected by this even after an update: >snapmirror update -destination-path dest:vol_dest > snapmirror show Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated - ---------- ---- ------------ ------- -------------- --------- ------- -------- SourceLocal:vola XDP dest:vol_dest Snapmirrored Idle - true - Question: - From the past experience I have noted that this type of action affects the snapmirror relationship. As mentioned in a 3rd party article: ~~~ If a FlexClone volume is created from a Snapshot copy that is not the most recent Snapshot copy, and that Snapshot copy no longer exists on the source volume, then every update will need to delete the Snapshot copy on the destination. In this case, all SnapMirror updates to the destination volume fail until the clone is destroyed or split. ~~ What has changed on a newer version of Netapp that deleting the source snapshot does not affect snapmirror? Or it only affects if snapshot deleted is a baseline snapshot?

Board Activity

Snapcenter 6.0, 6.1P1 upgrade error

default snapshot name case in SCS vs ONTAP

SnapMirror traffic is being routed through e0M instead

XCP exclusion

Does deleting a source snapshot that is mirrored and used at destination for flexclone impact snapm?