The quickie rename won't work unless you hack the fsid of the new volume to match the fsid of the old volume. Even then, it is pretty high risk.
If it isn't updated often, and you have space, just do a new snapmirror, and change the mount point on the clients over time.
John
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of John Stoffel Sent: Monday, December 07, 2009 2:50 PM To: toasters@mathworks.com Subject: Redoing snapmirror to a destination
Guys,
Do to stupidity on my part, I managed to accidently delete a snapshot on the source side of a snapmirror pair, so that snapmirror can't continue. It's not critical, it's just our tools area, which isn't updated frequently.
So now I want to re-snapmirror, but I want to limit the downtime of the clients on the destination side as much as possible when I switch them to the new re-snapmirrored volume.
Currently, my clients mount east:/vol/tools, so what I'd like to do is:
west> snapmirror store tools rst0a,rst1a
east> vol create tools .... east> vol restrict tools east> snapmirror retrieve tools_new rst0a,rst1a
Now for the tricky part:
east> nfs off east> vol rename tools tools_old east> vol rename tools_new tools east> nfs on east> exportfs -a -v
so that all my clients see (on a read-only volume) is a quick outage or pause in NFS traffic, then they just continue on using tools and such as usual.
Or will I be forced to reboot all of my client machines one by one? Which will be truly truly truly painful...
The general snapmirror update and cleanup of the old volume is trivial. It's limiting the outage to my clients that I worry about.
Thanks, John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel@taec.toshiba.com - 508-486-1087