Anything we need to consider here?
My server admin was doing some host work and put one into maintenance mode. Ended up with a lot of errors on VMs during the vmotion all with Appstacks and writable volumes attached.
http://kb.vmware.com/kb/2116782
I'm glad I check the VMware KB Digest regularly because this isn't listed in the known issues section of any of the release notes.
I'm guessing the proper route is put the host in maintenance then rebalance the pools in view and force the users to log off. We're working on a best practice for these scenarios
http://kb.vmware.com/kb/2116782
I'm glad I check the VMware KB Digest regularly because this isn't listed in the known issues section of any of the release notes.
Does this apply to Appstacks as well? I sure hope the fuck not.
The article states that "The above modification applies to Appstack volumes as well, however Appstack volumes opened in read-only mode makes it to support vMotion."
So I take that to mean that it will only be a problem for AppStacks during the provisioning mode when they are in a read/write state.
It also states that Storage vMotion will not work with either AppStacks or Writable Volumes: "App Volumes does not support Storage vMotion of virtual machines while AppStack volume or Writable Volume in use."
I can confirm it hasn't affected our App Stacks, just the writable volumes. Unfortunately this means writable volumes are out for us unless they can fix this, so the one group Writable volumes was needed for is now going to be on full clones now...