Yes, it’s an excellent document!

We took his document & turned it into the runbook below. I would have attached the original doc, but yes – it’s nearly impossible to find on NOW. You’ll need to do some tweaking of the runbook information (snapmirror break original destination before creating the new destination etc) in order to fit your requirement since this design shows how to migrate a source qtree rather than destination volume, but the gist of what’s required should be contained within.

And, of course, I’d test it on the DR filer to make sure.

Happy reading!

Russell Zayas

Qualcomm Incorporated

Data Management Group

Pre Migration

Identify snapmirror sources & associated destinations
Copy the original source to the new source, using the following command:
- newsource> snapmirror initialize -S oldsource:/vol/oldsourcevol/qtree newsource:/vol/newsourcevol/qtree
Disable automatic snapmirror updates from destination filer's /etc/snapmirror.conf files
- original entry: oldsource:/vol/srcvol/qtree dest:/vol/dstvol/qtree restart=always 0 * * *
- new entry: oldsource:/vol/srcvol/qtree dest:/vol/dstvol/qtree restart=always - - - -

Migration Window

Take old source qtree offline (NFS & CIFS)
- oldsource> exportfs -u -v /vol/oldsourcevol/qtree
- oldsource> cifs shares -delete oldsharename
Get final snapmirror update
- newsource> snapmirror update -S oldsource:/vol/oldsourcevol/qtree newsource:/vol/newsourcevol/qtree

Update Mirrors With New Baseline (src to newsrc & src to dst)

Create common snapshot on oldsource for new baseline:
- oldsource> snap create oldsourcevol common_snap
Synchronize all mirrors with new baseline snapshot:
- newsource> snapmirror update -c common_snap -s common_snap -S oldsource:/vol/oldsourcevol/qtree newsource:/vol/newsourcevol/qtree
- destination> snapmirror update -c common_snap -s common_snap -S oldsource:/vol/oldsourcevol/qtree destination:/vol/destinationvol/qtree
Quiesce & Break relationships between oldsource/newsource & oldsource/destination(s)
- New Source
  - newsource> snapmirror quiesce /vol/volnewsourcevol/qtree
  - newsource> snapmirror break /vol/volnewsourcevol/qtree
- Destination(s)
  - destination> snapmirror quiesce /vol/destinationvol/qtree
  - destination> snapmirror break /vol/destinationvol/qtree

Establish New Relationships

Establish the new SnapMirror relationship using the following command:
- destination> snapmirror resync -S newsource:/vol/newsourcevol/qtree destination:/vol/destinationvol/qtree
- Note - snapmirror status will NOT update until resync is complete
Re-Enable automatic snapmirror updates in destination filer's /etc/snapmirror.conf files
- current entry: oldsource:/vol/srcvol/qtree dest:/vol/dstvol/qtree restart=always - - - -
- new entry: newsource:/vol/srcvol/qtree dest:/vol/dstvol/qtree restart=always 0 * * *
Update mirrors with standard "update -S":
- destination> snapmirror update -S newsource:/vol/newsourcevol/qtree destination:/vol/newsourcevol/qtree
Verify snapmirror relationship
- destination> snapmirror status
Export & Share New Source
- newsource> exportfs -v -a /vol/newsourcevol/qtree
- newsource> cifs shares -add newshare /vol/newsourcevol/qtree

Post Migration

Clean Up Old Common Snapshots
- destination> snap delete dstvol common_snap
- newsource> snap delete newsourcevol common_snap

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Kennedy, Jeffrey
Sent: Thursday, September 29, 2011 9:09 AM
To: Davies, Matt; toasters@teaparty.net
Subject: RE: Changing snapmirror destination to a new filer

There’s a way to do it and our SE actually wrote the tech doc I believe. I’ve done it a few times and it works, but after the change to NOW a few years ago the site has become nearly worthless; I can’t find the reference for it anymore by any obvious search string.

I also can’t recall the exact order of snapshots that need to be taken, but it’s really as simple as creating a common one across all 3 volumes and using that to resync after the migrate. But it is very important to not miss a step or it’s all for naught.

Support should be able to find the doc, or maybe even the guy who wrote it will see your post….

Jeff Kennedy

Qualcomm, Incorporated

QCT Engineering Compute

858-651-6592

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Davies, Matt
Sent: Thursday, September 29, 2011 8:38 AM
To: toasters@teaparty.net
Subject: Changing snapmirror destination to a new filer

Hi,

We currently 3 filers, and are looking to move a snap mirrored volume to another filer, we would like to do this without having to recreate a new snapmirror and all the traffic associated with with it.

The example is:

Filer1 has Vol1 witch is snap mirrored to drfiler1 Vol1

We would like to copy/move Vol1 on drfiler1 to drfiler2, and continue with it being a snap mirror of Vol1 on Filer1, without having to reinitialise the snap mirror

Drfiler1 and Drfiler2 are both on the same site so we have no bandwidth restrictions.

Is this possible and could someone point me in the right direction of how to do it.

Thanks

Matt

____________________________

Matt Davies

Director of International IT Operations

General Atlantic

23 Savile Row

London

W1S 2ET

Tel: +44 207 484 3203

Fax: +44 207 484 2803

Mobile: +44 777 559 4265

____________________________

_____________________________________________________________
This e-mail (including all attachments) is confidential and may be privileged.
It is for the exclusive use of the addressee only. If you are not the addressee,
you are hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, please erase all
copies of the message and its attachments and notify us immediately at
help@generalatlantic.com . Thank You.