Hello,
In my lab I'm testing a hyper-converged scenario on vmware using the vsan for vmware ovf template. Here are my hosts/guests:
- vmHost1 with guest starwind-vsan1
- vmHost2 with guest starwind-vsan2
- vmHost3 with guest starwind-vsan3
I created a 2TB volume with the "master" image on starwind-vsan1 and the "partner" image on starwind-vsan2. starwind-vsan3 is the witness.
During a power outage where all hosts go down the starwind-vsan guests come up but the storage is marked as unsynchronized. I have to manually force one of the images as synced (only used master to date, but I'm guessing I could use partner if I knew the master was down before the partner). A 5 hour full synchronization is then started :/ I'm 99% sure this is by design.
I thought I read that the storage wasn't supposed to be used used during a full sync? Is this true? If yes, that really stinks because waiting 5 hours to bring up the guests is going to be a problem.
I noticed the vmHosts will remount the storage while it is being synced. However, I/O actions like storage vMotioning a guest to the iSCSI target will cause the "master" starwind-vsa1 guest to crash. Maybe this is expected behavior during a full sync?
Thanks for the help - Jeff
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software