Subscribe

Import of external SM relationship in Protection Manager

Hi,

As I understand, in dfm 4.0 you need to create a dataset with source in it and apply protection policy to dataset before you can run import wizard on external relationship. Problem I am facing is when you apply policy to dataset and chose destination it comes up with an error message and complains about size of destination. I suspect it’s because destination is restricted (SM destination) and PA not able to calculate size of it.

Do we need to break the SM relationship before importing or is there something I am missing?

Thanks.

Re: Import of external SM relationship in Protection Manager

What I have typically done... create the dataset without any source or destination resource (just give it a name and click next all the way thru the wizard).  Then apply the protection policy.  Then import the existing relationship.  You should not need to break SM.

Thanks,

Chris

Re: Import of external SM relationship in Protection Manager

Thank you for this. After import do you have to manually delete the SM relationship and schedule from destination filer or protection manager takes care of this?

Re: Import of external SM relationship in Protection Manager

I don't know for sure, because I think this behavior has changed recently... but I think it will leave the entry in the snapmirror.conf file.  In that case would need to manually remove it from the file (or comment it out).  However, I'd like for someone else to confirm this for you.

Thanks,

Chris

Re: Import of external SM relationship in Protection Manager

I am in the process of importing ~40 VSM relationships into Protection Manager 3.8.1 for monitoring only.  I created an empty dataset and a policy with no schedule.

For some reason many of the relationships are not importing and being removed from the "External Relationships" tab.

Is the reason for this logged somewhere?  I checked the dfpm.log and  didn't see anything.

I am also seeing the datasets are reporting an protection status of "Baseline Failure:  All baseline transfers failed because the dataset in non-conformant".  However, the dataset itself is reporting to be conformant and the transfers are working.  What causes this error and how can I clear it?

Re: Import of external SM relationship in Protection Manager

Hi Chris,

If you want to just monitor these relationships, then we don't have to import them to the dataset. You can just leave them at the "external relationship" page. You can monitor the lag of these relationships from the external relationship page. You can also set alerts for these relationships by using SnapMirror: Nearly out of date and SnapMirror: Out of date events. If you import them to a dataset, these realationships will not appear in the external relationship page and Protection Manager will be managing these relationships. Please check the attachment.

Thanks and regards

Shiva Raja

Re: Import of external SM relationship in Protection Manager

Hi Pasha,

     When you add your primary to your dataset and add the policy, PM will always try to create a destination volume based on the attached Resource Pool or if a volume was assigned on the destination will try to use it, after its conformance checks.

The procedure/method to import a external relationship is create an empty dataset with the policy attached and import or use an existing dataset with the policy attached.

Regards

adai

Re: Import of external SM relationship in Protection Manager

After import you dont have to do anything.

If the SM relationship had a snapmirror.conf entry you might have to remove them if you dont want both the protection policy and the snapmirror.conf to run the schedules.

Based on your needs you can disable either of them which you dont wish.

After importing a relationship PM doesn't remove the snapmirror.conf entry or snapvault snap sched for a Snapmirorr or Snapvault relationships.

Its up to the user to decide if he wants to go with filer scheduling or protection manger scheduling.

Also if you go with filer scheudling PM backup wont be registered.

Regards

adai

Re: Import of external SM relationship in Protection Manager

I am in the process of importing ~40 VSM relationships into Protection Manager 3.8.1 for monitoring only.  I created an empty dataset and a policy with no schedule.

For some reason many of the relationships are not importing and being removed from the "External Relationships" tab.

Didn't the conformance say anything ? Can you use the dfpm import cli with -D(dry run and post the output?)

Is the reason for this logged somewhere?  I checked the dfpm.log and  didn't see anything.

You may have to check in the conformance.log and dfmserver.log.

I am also seeing the datasets are reporting an protection status of "Baseline Failure:  All baseline transfers failed because the dataset in non-conformant".  However, the dataset itself is reporting to be conformant and the transfers are working.  What causes this error and how can I clear it?

Its a known issue, when a external relationship is imported to a dataset, and until a scheduled or on-demand backup is run, the protection status is shown as baseline failure.

To get rid of this just run one on-demand or one scheduled backup from PM.

Regards

adai

Re: Import of external SM relationship in Protection Manager

Pls note, the snapmirror nearly out of date  and out of date threshold have a value of 1.5 days and 2.0 days by default.

Regards

adai