I have been testing the vFiler DR plugin and noticed that when I do the following DFM and the NMC only shows the Stopped "DR backup" vFiler and not the running live vFiler.
1. Stop the running vFiler on the primary Filer using the Ontap CLI on the primary Filer
2. Resync the vFiler on the primary Filer to the DR vFiler on the secondary Filer
3. vFiler DR activate the secondary Filer DR vFiler from the CLI on the secondary Filer
4. Resync the now live vFiler on the secondary Filer back to the primary Filer to create the DR vFiler on the primary Filer (ready for the next flip)
When I view the vFiler from vFiler DR units in the NMC I only see the stopped DR backup vFiler on the primary Filer and not the running vFiler on the secondary system.
I've tried refreshing DFM for the vFiler and the primary Filer without any luck. This also means the volumes owned by the running vFiler are not monitored.
It seems the live vFiler isn't being discovered by DFM. Has anyone had similar issues? I'm using version="188.8.131.52" of the plugin.
We just use the CLI now and not a mixture of the CLI and the NMC plugin. I haven't had a chance to test this on the latests NMC plugin 184.108.40.206 though.
It would be good to use the NMC plugin as it makes the clean up after the failover a lot easier and less error prone.
All of our Filers including the one I was testing on were in DFM. When the issue occured I tried refreshing the host Filer in DFM, checking the "dfm diag host" didn't show errors.
It felt as though something was stuck which meant the vFiler couldn't be seen in the NMC plugin.
Time allowing I'll retest the process with the new plugin as it did make the whole failover process a lot less error prone and faster.
Did you create the original DR vFiler using command line? I use to notice that if I ever did anything command line on the dr vfilers the tool would not see it for a long while. Probably a bug.
This is what I would do.
First and foremost: Verify on the plugin that you do not have a volume mismatch. If you do let me know.
I'm going to re-rest with the new plugin this week but just noticed this Ontap bug:
vFiler missing after running 'vfiler dr resync' command
ran in the same problem with version 220.127.116.11
After stopping the primary, activating the DR and resyncing back only the DR (original primary) was visible in the NMC. Tried to stop/recreate/resync - from the CLI and NMC getting only to the point when BOTH vfilers were missing
Using "dfm vfiler list" I found there is no such (active) vfiler in the DFM, using "dfm vfiler list -a" there were several instances of this vfiler in "deleted=yes" state.
Added the primary using "dfm vfiler add -H <host> <vfiler>". Since then I can see both (primary and DR) again.
Anyone knows a way of purging the deleted vfilers from the DFM DB? Does it make sense (to try that)?
As James mentioned did you create the vFiler with the NMC vFiler DR plugin?
DFM doesn't actually delete objects from DFM it just marks them as deleted.
How to install and use the DFM Purge Tool
This can be done to clean up the DFM database if you have a lot of deleted objects.
You can also do this with:
(taken from here https://forums.netapp.com/thread/17829 but have used procedure previously)
both need DFM to be down while you do it so not ideal in a production enviroment.
thanks for the Purge tool and the pointers - it does not look I am going need this on daily basis but good to know there are ways of doing it.
I have created the vFilers using CLI - after installing the OnCommand Core they were successfully discovered and I moved the vFiler to DR and back several times using both NMC and CLI. This was the first problem I have encountered and to be honest - I do not see anything done differently than in previous cases
Good thing is I can get the missing vFiler back in the DFM, bad thing is no one seems to know what is causing it ....
I setup a vFiler and protected it using the NMC (as James suggested) and failed it back and forth but wasn't able to create the same issue. I imagine the NMC does some specific configuration that I missed when configuring it via the CLI?
Would be good to know if anyone else is able to reproduce the issue creating the vFiler with the NMC only?