Hi Adrian,
Here is what you need to do in Protection Manager. I have answered for creator of this thread too.
For you directly use Step 2.
Step 1:Prevents PM’s reaper cleaning up any relationship.
Set the following options as below before doing and reset it back to orphans once done.
dfm options set dpReaperCleanupMode=Never
Step 2:Relinquish the Primary member and the secondary member.
Use the dfpm dataset relinquish
This will mark the relationship as external and PM will no longer manage(schedule jobs) the relationship.
Now remove the primary and secondary from the dataset.
Either using NMC UI Edit Dataset Wizard or using dfpm dataset remove cli.
First remove the primary member then remove the corresponding secondary member.
Step3:Discovering as External Relationships.
You must see this relationship as external in the External Relationship tab. If you don’t see it, close and re-login to NMC again,
Step4:Importing to a new dataset.
Create a new dataset with required policy and schedule. Or choose the dataset where you want to import this relationship to.
Use the Import wizard and import them.
Step 5:
dfm options set dpReaperCleanupMode=orphans.
Points to take care:
1. If an entire OSSV host was added as a primary member, and now moved to a new dataset.(the step 2, relinquishing the primary member needs to be done for each dir/mntpath of the OSSV host.).The same applies for a volume which is added as a primary member and now moved to a new dataset.
2. After importing the dynamic referencing of the OSSV host is lost as we import each individual relationships.The same applies for volumes too, now you will start seeing individual qtrees as primary members as opposed to volume.
3. So when a new dir/mnt path is added to the OSSSV host, admin has to manually add it to the dataset.The same applies for new qtrees too.
4. To restore from Old backup version the use must go back to the old dataset as they are not moved over.
Note:
- When you relinquish the relationship, it may not show-up in the "External Relationship Lag" box of the Dashboard view. However, if you go to Data -> External Relationships it will be listed there.
- When you import the relationship into a new dataset, it will show an error status of "Baseline error". Simply run an on-demand backup job and it will clear this error. Note: The backup job doesn't perform a re-baseline. It simply does a Snapvault update.
- Don't delete the old dataset if its empty. As adai stated, it has the backup history of the relationship before you moved it. So if you want to perform a restore from before the move, you need to restore from the old dataset. Once all the backups have expired from the old dataset, you can destroy it.
Regards
adai
