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

Snapmirror reinstation after tech refresh

BALAJI_VENKATRAMAN

Hi Experts.

 

Right now we have an active snapmirror between Primary and Secondary site ie Singapore and HongKong.

 

SG is the primary and data is replicated every 5 mins to HK - which is a DR site i.e not active unless source goes donw due to some reason.

 

 

-old represents the existing filer and -new is the new filer for tech refreshing the old ones.

 

SG-old --> Snapmirrors --> HK-old

 

My plan for tech refreshing this filer is as below

 

Setup SM from SG-old to SG-new (in addition to current SG-old to HK-old).

 

During the downtime - failover services to HK-old and let all current IO's go there.

 

My question is - Will a resync work from HK-old to SG-new or not?

 

Please advice.

1 ACCEPTED SOLUTION

georgevj

If you are going to use separate shelf stacks for each of the new and old controllers, I think an easy way to do this would be by cascading the snapmirrors. Like, SG old -> HK old -> SG new -> HK new. That way you can avoid a resync. If you are planning to continue with HK old, after HK old -> SG new, you may have to do a snapmirror reverse resync. Please see "Data Protection Online Backup and Recovery Guide" at https://library.netapp.com/ecm/ecm_download_file/ECMP1196991 for supported configurations.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.

View solution in original post

1 REPLY 1

georgevj

If you are going to use separate shelf stacks for each of the new and old controllers, I think an easy way to do this would be by cascading the snapmirrors. Like, SG old -> HK old -> SG new -> HK new. That way you can avoid a resync. If you are planning to continue with HK old, after HK old -> SG new, you may have to do a snapmirror reverse resync. Please see "Data Protection Online Backup and Recovery Guide" at https://library.netapp.com/ecm/ecm_download_file/ECMP1196991 for supported configurations.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.

View solution in original post

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