Summary: We are trying to switch from using a SnapMirror Relationship to a SnapVault Relationship without having to rebaseline. We are doing this using a specific interface that is configured in the snapmirror.conf file; vif_lab-14. Snapvault Relationships do show up in the External Relationships tab in the NetApp Management Console, just not the one that was seeded with the SnapMirror Relationships destination volume. Is there any way to manually force the detection of the external relationships. I have used dfpm relationship list on the DFM server and it doesn't see the SMtoSV Relationship either.
i. Create a 100GB volume: vol create smvol_cifs_01 aggr_fas2_sata1 100g
ii. Set the Snap Reserve to 0% snap reserve smvol_cifs_01 0
iii. Disable the default Snapshot Schedule snap sched smvol_cifs_01 0 0 0
iv. Restrict the destination volume vol restrict smvol_cifs_01
b. Configure the SnapMirror Relationship for the FAS1 Primary Volume
i. Initialize the snapmirror relationship in the OnCommand System Manager
1. This will fail, stating it cannot connect to the source filer. We have previously set up the snapmirror.conf file with a multi definition so that the snapmirror flows to the source filer will use the VIF designated for the snapmirror traffic:
After I had run a refresh on the filers through Protection Manager, the SV's showed up under the External Relationships in the Management Console.
My question now is, if the root of the volume is a valid path using snapvault from the command line, as outlined in the Data OnTap Manual Page Reference Volume 1 for version 8.1, then why wouldn't DFM's modules accept the path?
"The primary_path can be a qtree, represented in a similar way; it can refer to the set of non-qtree data on a volume, represented by a path such as /vol/vol3/-; or it can refer to the contents of the entire volume, including all qtrees, by a path such as /vol/vol3."
You shouldn't have to reconfigure your existing SnapVault Relationships to fit them into a Management feature, the feature should allow for what is defined in the existing operating system. Addionally, having to define SnapVault relationships at the QTree level and separately for the Root Level, before importing them into the Management Console, adds managment overhead to what should be minimizing management overhead.