Hello,
We are trying to deploy OnCommand Unified Manager (DFM/Operations Manager) on existing filers and vFilers.
We do not find a way to make it working.
Our environment
FilerP is the primary filer
vFilerS is the secondary vFiler hosted by Filer2
FilerT is the tertiary filer
There are existing cascaded Mirrors of volume /vol/testvol : FilerP ==> vFilerS ==> FilerT
We want to use OnCommand Unified Manager (DFM/Operations Manager) to manage this kind of policy.
Current SnapMirror relationships
SnapMirror.allow is set on all source (v)Filers
SnapMirror.conf on Filer2 (host of secondary vFiler)
nothing
SnapMirror.conf on vFilerS (secondary)
FilerP:testvol vFilerS:testvol - - - - -
SnapMirror.conf on FilerT (tertiary)
vFilerS:testvol FilerT:testvol - - - - -
SnapMirror status on Filers and vFiler is conform to SnapMirror.conf settings
Mirroring is working well
However:
- SnapMirror relationships are not visible in system manager on Filer2 (host of secondary vFiler) : this may be the expected behavior
- OnCommand Unified Manager does not detect data paths nor relationships to/from vFilerS
Therefore it looks like it is not possible to manage this configuration using OnCommand Unified Manager
In Operations Manager Administration Guide page 251 § “Prerequisites for monitoring vFiler units” it is written:
“Monitoring SnapMirror relationships
For hosting storage systems that are mirroring data to a secondary system, you must ensure that the secondary system is added to the vFiler group. The DataFabric Manager server collects details about vFiler unit SnapMirror relationships from the hosting storage system. The DataFabric Manager server displays the relationships if the destination vFiler unit is assigned to the vFiler group, even though the source vFiler unit is not assigned to the same group.”
Therefore, we performed several tests adding physical filers in accurate group in OnCommand Unified Manager ==> no change, relationships with vFilerS remain hidden.
In Multistore Management Guide page 51 § “Guidelines for using SnapMirror technology” it is written :
“When specifying a path name in the /etc/snapmirror.conf file, ensure that you use the storage system name, and not the vFiler unit name."
This means in our case, replace vFilerS with Filer2 (its hosting filer).
Therefore we tried change in snapmirror.conf of vFilerS after break on relationship.
Line changed
- from : FilerP:testvol vFilerS:testvol - - - - -
- to : FilerP:testvol Filer2:testvol - - - - -
snapmirror status still shows initial relationship
Source Destination State Lag Status
FilerP:testvol vFilerS:testvol Broken-off xxx:xx:xx Idle
Resync or update on the relationship results in error:
Source not set on command line or in /etc/snapmirror.conf file.
Then … we do not understand how to set SnapMirror relationships in mixed filer / vfiler environment to make OnCommand Unified Manager (DFM/Operations Manager) able to manage such configuration.
We will appreciate any help on following question:
- How to configure snapmirror relationship in vFiler : use vFiler name or hosting filer name ?
- How to configure snapmirror relationship in vFiler to make them manageable from OnCommand Unified Manager (DFM/Operations Manager) ?
Thanks a lot for your help.