Protection Manager can't manage SV Relationship within same filer

[JGPSHNTAP]

So, i'm testing something out, and i thought i read somewhere that PM can't manage SV relationship within same filer.  Even though relationship is in different aggregate.    I set one up, and did dfpm relationship list after dfm host discover and didn't see it in external relationship. 

This is just a lab scenerio, but i'm curious.

Please advise and if you have linkage that would be great.

thanks

[kryan]

Older versions of UM/DFM prevented creating relationships to the same controller due to an ONTAP limitation.  Once that limitation was removed UM still only allowed relationships to different aggregates on the same controller.  However, this changed in UM 5.2 using the dpAllowSameAggrRels option.

See this public report for details:

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=464200

Thanks,

Kevin

[JGPSHNTAP]

Kevin,

Hmm.. I was aware of the same aggr limitation, so I set this up in the different aggregates, aggr1, aggr0, but still no luck.    I'm running 5.2 in the lab. 

I also don't see that option available on our UM 5.2 server. 

dfm option list | ? {$_ -like "*dp*"}

clientStatThresholdPeriod             300

dpDynamicSecondarySizing              Enabled

dpMaxFanInRatio                       1

dpPriVolNameFormat                    %L

dpPriVolNameOption                    global-format

dpPriVolNameScriptPath

dpPriVolNameScriptRunAs

dpReaperCleanupMode                   Orphans

dpReaperInterval                      30 minutes

dpReBaselineMode                      Confirm

dpRestoreTransfersPerHost             8

dpSecQtreeNameFormat                  %Q

dpSecVolNameFormat                    %V

dpSecVolNameOption                    global-format

dpSecVolNameScriptPath

dpSecVolNameScriptRunAs

dpSnapNameFormat                      %T_%R_%L_%H_%N_%A

dpSnapNameOption                      global-format

dpSnapNameScriptPath

dpSnapNameScriptRunAs

[kryan]

From the PR:

....using the hidden option "dpAllowSameAggrRels".

For example:

# dfm option set dpAllowSameAggrRels=1

Changed allow a relationship within a single aggregate to 1.

Hidden options are not visible until set/changed.

Thanks,

Kevin

[JGPSHNTAP]

Kevin,

Ok, I see that, but to my above point, i'm going to different aggregates on same controller.  Do I still need that option

[kryan]

No, that option is for using the same aggr.

How long did you wait after refreshing the monitors?

Are there any error regarding that relationship int eh svmon.log?

Kevin

[JGPSHNTAP]

Hmm.. Kevin something is off.. I see we are on the same page now with the aggrs.

I forget to check the sv log - here is the error - Invalid primary path /vol/sv_test_m

Now that's bull.. what's wrong with that path?

[kryan]

Protection Manager has never been able to vault a volume - you will need the relationship to be in the following format for PM to use it:

/vol/sv_test_m/-

OR

/vol/sv_test_m/qtree1

You can read details in this PR:

DataFabric Backup Manager and Protection Manager do not support volume-to-qtree SnapVault

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=114665

Kevin

[JGPSHNTAP]

Kevin,

Yup, that did it.  Interesting read on the PR.