I was having the same issue described here with two different Proxmox servers. I updated /etc/network/interfaces as below, and it solved the problem. Thanks for the guidance!
iface vmbr0 inet manual
bridge-ports enp4s0f0
bridge-stp off
bridge-fd 0...
One additional note.
I'm using hardware pass through on a number of VMs. The "Data Center" functionality for "Resource Mapping" works to deal with address differences for hardware between PVE cold backup hosts as long as you are consistent with the resource name between the PVE hosts. Of course...
@fiona and @chudak,
Thanks for the feedback. I really appreciate it. The bit I was missing was restoring from the VM backup screen and selecting the Proxmox backup server as the source instead of local. Now that I do that it is working like a charm.
Test your backups... Document recovery...
I have two PVE servers that are not clustered because do not want to keep both machines on 24/7 and I don't need hot fail over, particularly considering the cost of keeping both machines turned on 24/7. I run VM backups to a Proxmox backup server that is available when I run backups. I'm trying...
Thanks!
I had done enough poking to understand that I could treat it like a standard Debian host and do backups that way. It is good to know everything is in /etc/pve. I'll do a little poking around in there and see if a simple backup of that folder is enough for my needs. I am mainly looking...
I've looked around and have not been able to find anything regarding backup of the server configuration. Is there a recommended way to backup the VE server itself (not backups of the VMs running on the VE server)?
Thanks!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.