Effective December 3, NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources.
For accounts that did not pre-register (prior to Dec 3), access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Discussions

Snaplock Compliance SLC volumes being moved and volume snapmirror VSM relationships will break

Bart-Gaines

I am moving shelves containing 7-mode snaplock compliance volumes to another 7-mode ha pair that already has snaplock compliance configured.

I expect no issues with the move, and expect the volumes to show up as snaplock compliance volumes on the new filers.

The SLC volumes are sources for VSM relationships.

The source will move but the data and base snapshots will remain the same.

Can the relationship be modified to point to the new location of the source?

or will they need to be snapmirror break  and left as a SLC copy of the SLC source volume on the VSM destination?

 

 

1 REPLY 1

Sahana

Hi,

 

Breaking Volume SnapMirror relationship of a SnapLock Compliance(SLC) volume causes 
 the data in the destination volume to be locked for the duration of the 
 retention period. Hence reinitialization or resynchronization to the destination 
 volume is not allowed until the end of the retention period. 

Refer https://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=229202 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public