- Posts: 2
- Liked: never
- Joined: Aug 30, 2017 6:04 pm
- Full Name: K Berger
The "solution" amounts to: "Add more nodes or never put your servers into maintenance mode to end up with one active node for the vSAN, ever."
Our normal setup is One Witness Node in a Datacenter, and a Two Host Cluster in each satellite office. We sometimes require a server in maintenance mode for fairly a long duration, as we don't have any on-site IT for these small offices. During these times, we are unable to perform any backups that involve VM snapshots.
I would much rather prefer to see a Warning message for the VM backup instead of a Hard Failure. I can take a manual snapshot, and the VM is working just fine. The problem is, if we have a node in maintenance mode or is offline due to a fault or what-have-you (the situation we are in now) Veeam simply refuses to attempt a snapshot, even though it only needs it temporarily for the duration of the backup.
P.S. I searched for this issue on the forums here and didn't find anything closely related.
- Veeam Software
- Posts: 278
- Liked: 38 times
- Joined: Jan 14, 2016 6:48 am
- Full Name: Anthony Spiteri
- Location: Perth, Australia
1. Are all VM backups impacted during the maintenance periods? IE. Are any VMs backing up?
2. What's your fault domain config?
3. How many Veeam Proxies are you running and where?
Global Technologist, Product Strategy | VMware vExpert
Email: firstname.lastname@example.org | Mobile: +61488335699
Twitter: @anthonyspiteri | Skype: anthony_spiteri
Users browsing this forum: Baidu [Spider], Bing [Bot] and 55 guests