Subscribe

How to restitute (or reconstruct or resume) a snapvault relationship after a qtree migration

Hi,

One of our customer that uses snapvault, whats to migrate its primary filer to a new one (viler actually).

We want to keep the history on the secondary.

The migration of the whole contain has been made with snapmirror, then the snapvault sched has been recreated on the new primary (that has been renammed with the name of the old one that was physically stopped).

The problem is that the relationships don't exist anymore.

What commend do we have to run on the primary, secondary to rebuild the relationship?

snapvault update, runs on the scondary seems to rebuild the relationship? Is there a better command for that?

what about "snapvault create -r"?

thanks for your help.

jm

How to restitute (or reconstruct or resume) a snapvault relationship after a qtree migration

I hope you moved it with volume snapmirror and not with qtree snapmirror.

check if you can see on both volumes the "snapvault"-snapshot that is used for the baseline and snapvault updates.

If they are both there with the same time then you can do:

snapvault modify -S source:volume destination:volume

after that

snapvault update -S source:volume destination:volume

snapvault is pulling like snapmirror so the command needs to be done on the secondary filer.

How to restitute (or reconstruct or resume) a snapvault relationship after a qtree migration

If you used qtree snapmirror and you still have all the "snapmirror" snapshots, then you might still be able to get the secondary working again without starting new baseline sv transfers. See the following KB for instructions: https://kb.netapp.com/support/index?page=content&id=1011499