Solved: How do you move a SV relationship between datasets in Protection Manager? - Page 2

reide · ‎2011-04-13

IHAC who needs to move a single OSSV relationship and secondary volume out of one dataset and into another dataset. Dataset "A" has 10 OSSV clients all using the same backup policy and schedule. Each OSSV relationship has its own dedicated secondary volume (1:1 relationship). The customer wants to move just one of these relationships to Dataset "B" so they can give it a different schedule. However, any attempt to remove the OSSV client or its secondary volume from Dataset "A" results in Protection Manager deleting the relationship. The customer wants to keep the relationship in-tact and avoid a re-baseline.

How can we accomplish this in Protection Manager? Because each OSSV client has its own secondary volume, this should be relatively easy but we can't seem to get it to work. I'm almost positive I've seen disucssions about how to do this, but I cannot find them.

Thanks.

adaikkap · ‎2011-04-13

Hi Earls,

Here is what you need to do in Protection Manager

Step 1:Prevents PM’s reaper cleaning up any relationship.

Set the following options as below before doing the following 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 or NMC UI Edit Dataset Wizard.

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 too.

· 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.)

2. After importing the dynamic referencing of the OSSV host is lost as we import each individual relationships.

3. So when a new dir/mnt path is added to the OSSSV host, admin has to manually add it to the dataset.

4. To restore from Old backup version the use must go back to the old dataset as they are not moved over.

Regards

adai

View solution in original post

How do you move a SV relationship between datasets in Protection Manager?

NetApp Support Site Wins Silver Stevie® Award

Sign-up for Software Release Notifications!