After head swap you most likely had issues due to systemid change; this should not happen this time.

1. Should not be a problem for existing filers

2. See https://kb.netapp.com/support/index?page=content&id=1011285&locale=en_US&access=s for procedure to migrate SV secondary. There is also description how to move primary somewhere, just search for it J

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley
Sent: Wednesday, April 08, 2015 10:17 AM
To: <Toasters@teaparty.net>
Subject: Snapvault with system shutdown and rename

Greetings,

We're going to be splitting data from a 7-mode cluster (7.3.7).  Some data is being SM to an 8.0.2 7-mode cluster with a new name.  The remaining data and the original cluster will be moved to a new location and offline for a couple of days.

My questions revolve around the snapvault snapshots and relationships.  A couple of years ago we replaced the cluster heads and the backup relationships broke because schedule created a new snapshot which did not match the one the secondary was looking for.  We had to re-baseline a lot of data.

1.  Do I need to disable the SV schedules on both primary and secondary volumes for the cluster that will be offline for a couple of days, or will it be fine and pick up where it left off when it comes back up?

2.  I know I'll need to modify the existing SV relationship with the data migrating to the new cluster.  Since there are no SV schedules in place on the new cluster, there shouldn't be any issues with a new SV snapshot being created before I do a snapvault start -S with the new relationship to update it.

It's 1am so I'm sure I may be missing something and wanted to check.  

Thanks,

Jeff

--

Jeff Cleverley
IT Engineer

4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611