2011-07-08 08:59 AM
If I wanted to use SMVI to initiate my snapmirror updates does this mean the destination does not need an entry in the snapmirror.conf file?
Also, can SMVI be used to create a pure snapmirror schedule – Ie, not also create local backups / snapshots?
Solved! SEE THE SOLUTION
2011-07-11 10:52 AM
You need an entry in the snapmirror.conf file with no schedule (- - - -) but you can throttle it.
Start the baseline task and after that you can check to initiate a snapmirror update.
I hope it's help.
2011-07-12 05:07 AM
Your entry should look like this :
[srcfiler]:[srcvol] [dstfiler]:[dstvol] - - - - -
then do the snapmirror initialize. (baseline copy)
After that you only need to check the box "initiate snapmirror update" in SMVI.
2011-07-12 10:00 AM
Ok, that is the syntax I have but the snapmirror update isnot being performed (the backup is however).
I create the baseline with no issues, I can even run asnapmirror update on the dest without issues – Again, no error is logged in theVSC, snapmirror log or the system console ??
2011-07-12 11:10 AM
Did you add the destination filer into VSC?
From the backup.pdf (VSC 2.1) :
If you intend to initiate a SnapMirror update during a backup procedure, you must also add a
destination storage system at this time.
Be sure the check box "Initiate SnapMirror Update" is check on Job Properties.
2011-07-12 01:24 PM
I had used netbios name on filers but fqdn on SMVI (VSC) config – Changed both to the same (netbios) and all is well!
I notice that on the destination there are multiple snapshots – One with the smvi prefix and the other a normal snapmirror update. Is this because the backup is created first then a snapmirror update is performed (so we have two snaps on the src / dest with the same timestamp).
Lastly, do you know if it is possible to use flexclone to clone any snapshot (not the most recent) on the dest volume – For example, data is corrupt in the most recent replica so rather than break the relationship and end up with corrupt data, use flexclone to clone a previous snapshot to access “good” non corrupt data.
2011-07-13 10:01 AM
You can use "vol clone create" on the destination volume.
vol clone create <vol-name> [-s none | file | volume] [-f] -b <parent_flexvol> [<parent_snapshot>]
- create a new flexible volume that is a clone of <parent_flexvol>