Suggestion: Check if requirements for backups are met before shutting down VMs...
-
Hi,
one of our VMs was in a stopped state this morning because our daily delta backup (with offline snapshot, 4 VMs in total in the backup job) had failed with error "NOT_SUPPORTED_DURING_UPGRADE()". The other 3 VMs were up and running.
I updated the pool master yesterday and rebooted, but I did not update the second server on which the stopped VM was running. The VM had this server assigned as a home server, too.
This happend:
- Snapshots failed for all 4 VMs, which is expected because of the update state.
- 3 VMs started up again on the pool master.
- 1 VM could not be started because it is not possible to start a VM when the host has not been updated. Is this correct?
Perhaps the update logic can be enhanced by checking some things before the backup job shuts down a VM. The key questions woud be:
- Is the backup target available?
- Can the VM be started again after the offline snapshot?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login