i recently migrated (due to lack of space) some of my biggest datasets from one aggregate to another on the secondary storage. the dataset consist of 4 snapvault relationships which reside in one volume (non-qtree + 3 qtree)
everything went fine. also the dataset still back's up correctly and the retention ist correct.
nevertheless i now have a lag error because the dataset now belives that there are 8 relationships.
see the attached screenshot for details.
also on the filer's (primary and secondary) i only see the correct 4 relationships:
a) did you use the "magage space" wizard of the NetApp Managament Console (the Protection Manager GUI), or
b) did you move the volumes manually by using SnapMirror?
if a) everything should be OK as Protection manager itself takes care of migrating all the relationships alongside the volumes(s).
The Manage Space wizard:
In case of b) you definiteley have some work to do...
Protection Manager really does not like if one performs manual changes. The new destination volume you might have created is discovered as a new volume by Operations Manager. When you then subsequently SnapMirror the old volume to the new, along with its SnapVault Snapshots, Operations Manager then discovers a new SnapMirror relationship *and* a new SnapVault relationship, but from its point of view those have nothing to do with the dataset. If you then even subsequently delete the old volume(s), Protection Manager might even go along and create new volumes on its own, including a SV baseline as you just ripped away the volumes from under its feet.
So b) will now need some manual clean-up. Basically you need to remove the relationships from Protection Manager control. This will mark the relationship as "external". Afterwards you can import this relationship into the dataset. Unfortunately with this procedure you will most likely lose all existing backups. The Snapshots will still be there, but Protection Manager will not know about them anymore. Also the old ones would not be automatically deleted and you need to check manually.
For either case I suggest to call support. In case of a) for whatever reason the process might not have completed successfully, in case of b) you need help for the manual clean-up.
If this post resolved your issue, please help others by selecting ACCEPT AS SOLUTION or adding a KUDO