DCMCD Fixes

In my previous post I had outlined that I was going through a filer migration and I have just come across another small issue with regards to my VMware world! The Issue Via the NetApp VSC (Virtual Storage Console) I have a number of backups configured and I needed to take this into consideration when I was setting a volume to "Offline".  I needed to carry out a number of preparation tasks within the VMware world, mainly: Update the backup policies within VSC to remove any trace of a datastore hosted on said volumes Detach the datastore from all ESX hosts Now, being extremely excited and buzzing with anticipation of having the old filer completely unreferenced from my virtual world I inadvertently offlined a volume and deleted it a few weeks later as there had been no issues, alarms, alerts, fires, explosions etc. Noticed this week that one of the VSC backup policies still references one of the old datastores.  Thought I would try a...

Currently in the middle of cleanup tasks after a SAN migration and this one pain-in-the-a** datastore would not unmount from one particular ESX host.  Each attempt returned the following status: " Operation failed, diagnostics report: Sysinfo error on operation returned status : Busy. Please see the VMkernel log for detailed error information " Many posts/fixes where pointing towards a VM holding a connection to the datastore or HA being enabled on a cluster which accesses the particular datastore.  None of which gave me any joy or further progress towards a solution. Having tried many ESXCLI commands to see which virtual machine was keeping a connection to this datastore and checking HA settings, I stumbled upon another option.  SYSLOGS for the ESX hosts! In my scenario, this one ESX host (unlike the other 10+ hosts) was set up to push it's SYSLOGS to this particular datastore.  No idea who set it, why they set it, when they set it or fo...