I am backing up some vms that are residing on a Proxmox cluster. They all have been set up in HA.
If I remove a vm and restore it, all is restored, but it seems the HA part of the config does not get put back.
If I restore a vm that still is present I get a warning it will remove the VM prior to restoring it. In the end the restore fails with the message "Failed to perform restore. unable to remove VM-XXX - used in HA resources and purge parameter not set".
am I doing something wrong, or is HA not supported by Veeam?
-
oscarm
- Service Provider
- Posts: 79
- Liked: 7 times
- Joined: Sep 10, 2013 11:43 am
- Full Name: Oscar Muntenaar
- Contact:
-
tx.fz
- Influencer
- Posts: 12
- Liked: 1 time
- Joined: Jul 30, 2020 2:12 pm
- Contact:
Re: Proxmox HA settings are ignored?
Same issue here. Opened case #08131128.
-
oscarm
- Service Provider
- Posts: 79
- Liked: 7 times
- Joined: Sep 10, 2013 11:43 am
- Full Name: Oscar Muntenaar
- Contact:
Re: Proxmox HA settings are ignored?
my case: #08117044
what I have figured out so far:
https://pve.proxmox.com/wiki/High_Availability
The HA Manager’s primary management unit is called an HA resource (or “HA service”). Currently, an HA resource can be either a Virtual Machine (VM) or a Linux Container (CT).
Each HA resource is uniquely identified by a service ID (sid), which consists of the resource type and a type-specific ID, which is the VMID for VMs and containers. For example, for the VM with VMID 100, the service ID is vm:100.
An HA resource can only run on nodes where all of its dependencies are available. By default, the HA Manager treats every cluster node as eligible. To keep this default, a VM or container should:
use options that are compatible with all cluster nodes
use only shared storage that is accessible from all cluster nodes
use only network interfaces that exist on all cluster nodes
use only device passthroughs that are present on all cluster nodes
If any of these dependencies is only available on a subset of nodes, restrict the HA resource to that subset with a strict node affinity rule. The HA Manager then limits placement, recovery, and migration to the rule’s nodes.
it seems HA settings are not kept in the VM settings.
Still it would be nice if somehow if a VM is HA enabled this would be acknowledged and with restores put back, and if they purge HA settings of a VM that is present when you restore it. After all there's an API to talk to the HA manager so hopefully this will be possible in the near future.
what I have figured out so far:
https://pve.proxmox.com/wiki/High_Availability
The HA Manager’s primary management unit is called an HA resource (or “HA service”). Currently, an HA resource can be either a Virtual Machine (VM) or a Linux Container (CT).
Each HA resource is uniquely identified by a service ID (sid), which consists of the resource type and a type-specific ID, which is the VMID for VMs and containers. For example, for the VM with VMID 100, the service ID is vm:100.
An HA resource can only run on nodes where all of its dependencies are available. By default, the HA Manager treats every cluster node as eligible. To keep this default, a VM or container should:
use options that are compatible with all cluster nodes
use only shared storage that is accessible from all cluster nodes
use only network interfaces that exist on all cluster nodes
use only device passthroughs that are present on all cluster nodes
If any of these dependencies is only available on a subset of nodes, restrict the HA resource to that subset with a strict node affinity rule. The HA Manager then limits placement, recovery, and migration to the rule’s nodes.
it seems HA settings are not kept in the VM settings.
Still it would be nice if somehow if a VM is HA enabled this would be acknowledged and with restores put back, and if they purge HA settings of a VM that is present when you restore it. After all there's an API to talk to the HA manager so hopefully this will be possible in the near future.
-
Mildur
- Product Manager
- Posts: 11926
- Liked: 3388 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Proxmox HA settings are ignored?
Hi Oscar
I did ask our QA team last week. I will provide an update once I have it.
Best,
Fabian
I did ask our QA team last week. I will provide an update once I have it.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 56 guests