Background: VMware 6.0U2 on ESXi/vCenter - planning upgrade to 6.0 U3 or to 6.5 possibly in 3-6 months. HPE Proliant Blade Servers all reaching back to Dell Compellent SAN. My backup sol...
See more...
Background: VMware 6.0U2 on ESXi/vCenter - planning upgrade to 6.0 U3 or to 6.5 possibly in 3-6 months. HPE Proliant Blade Servers all reaching back to Dell Compellent SAN. My backup solution is HPE Data Protector which has a physical agent and can copy Physical RDM without issue. I am considering VEAAM or similar in the future but am concerned that they only leverage VM snapshots on VMDKs and won't be able to handle a Physical RDM that would be used for a WSFC with a Cluster Across Boxes that is the Approved Solution that allows vMotion. For VM level Operating System maintenance I'd like to setup WSFC to keep my file and SQL DB's up at all times and not have to deal with an outage for server patching for those services. The VM level backups are less disruptive to my file servers/SQL servers than the physical agent initiating a Volume Shadow Copy to pull a backup on a 1TB+ volume. I don't know everything and am open to suggestions/advice/best practices for getting a balance between service up-time/DR/ongoing maintenance My current environment has No Clustering with multiple SQL servers and file servers running independently as single points of failure and the VMs takes an outage when patching the OS. So the idea of going to a CIB setup and being able to use VM level backups exclusively and not take an outage for patching would be some nice incentives. However ESXi Host Maintenance looks like it could require an outage: WSFC points... No Clustering Cluster in a Box Cluster Across Boxes vMotion Yes No Yes Disk requirement None VMDK Only PRDM on shared Disks VM level backup and restoration ability Yes: if VMDK Yes No Outage: OS - Failure or Patching Yes No No Outage: ESXi Failure or Maintenance No Yes No My question: If running WSFC in a Cluster in a Box mode with 2 server nodes and wanting to do ESXi host maintenance, would it be possible to put 1 of the server nodes in the cluster in maintenance, shut down the VM in maintenance mode then vMotion both VMs of the cluster to a different host? I'm assuming the disk Timeout Value has been increased in the OS of the cluster VMs like in the CAB requirement. You are out of High Availability for a bit of time, but don't have to take an outage to do ESXi Host maintenance. TIA
