Stretching a vSAN Cluster, Backups, and Site Failure

[huoldrnag]

Hello wise ones,

I need some help with vSAN stretched Cluster and backups in the event of a site failure.

Most backup solutions rely on snapshots, which use the same SBPM as their vmdks. Site failures typically persist for several hours, days, or even weeks.
In the event of a site failure, any backup job for a VM protected by a "stretched" SBPM would fail because vSAN would not create the snapshot file with the default parameters.

So, how should VM backup jobs be handled in a stretched cluster environment, given that one site may be hit by a disaster that requires several weeks to recover from?

I hope this helps a little.

[yaroslav (staff)]

Hi,

Thanks for your question and welcome to StarWind Forum!
VSAN does not feature snapshots and LSFS is deprecated. Please migrate to the *img files. Make sure your system meets the system requirements https://www.starwindsoftware.com/system-requirements and best practices https://www.starwindsoftware.com/best-p ... practices/. More on Stretched clusters https://forums.starwindsoftware.com/vie ... ion#p33692
StarWind VSAN is not the backup software, so solid backups are a must. Back up your VMs well. See more on backup best practices in the context of StarWind https://www.starwindsoftware.com/best-p ... practices/
StarWind VSAN features active-active replication. This means that data is the same on all nodes when HA devices are synchronized. If synchronized in the moment of failure, the storage on another node will pick up a slack and your VMs can be moved to another site.