Can someone point me to instructions on how to resize a SnapMirror volume?
We have a 600Gb volume that we are mirroring from a FAS2020 in SiteA, to a FAS2020 in SiteB for backup.
Today I had to resize the primary volume in SiteA as it was running low on space. However, when I try to resize the mirror of this volume in SiteB it gives an error because the volume is "read only".
I've heard that the correct way of doing this is disabling the mirror, change the read-only state on the SiteB mirror via the command line, resize the volume, mark it read-only again and then restart SnapMirror - any ideas on how to actually achieve this would be great!
(and there I was thinking I'd quickly resize both volumes and "hey presto" everything would take care of itself! ).
When I run this command it tells me that the volume is already online. I can take it offline/online using the web GUI - but either way it won't let me change it's volume size because it's marked as "read-only".
So, if vol restrict [volname] restricts the volume (which I guess is the same as read-only), then what is the opposite command to unrestrict it?
This makes it seem like the mirror is not broken (?.. what does "snapmirror status" tell you) Just to be sure, you have done a "snapmirror break" (after a "snapmirror quiesce") on the destination system? Then did the vol online command. And still no luck?..
4) Grow the volume (command line: "vol size vol_name +size_to_grow")
5) resync the snapmirror (command line: "snapmirror resync vol_name")
Don't re-initialize (that'll re-baseline it!), and don't worry about A-SIS settings. Once a volume has been SnapMirrored, you shouldn't need to restrict it again, this is only for re-initializing (which you shouldn't need to do).
This whole thing can be a little tedious and quickly gets a bit annoying if you grow your volumes regularly. Can I recommend that you thin provision your SnapMirror destination volumes? Set the volume size to the maximum space you have in your aggregate, but set the space guarantee to "none". Then when you do a SnapMirror initialize (or indeed resync it if it already exists), this setting is over-written and the size is fixed (fs_size_fixed) using SnapMirror. As the source volume grows, the destination will also grow.
The only thing you have to watch out for here is if you have more space on your source than your destination, you could end up filling up the destination entirely, so just keep an eye on that.