Hi
As part of testing out Proxmox for our new virtualization infrastructure, we have configured an offsite server with the same Proxmox VE 4.4-13/7ea56165 as our internal 5 node cluster.
The cluster runs a daily backup to a RAID6 NFS-share on our storage server. This server then does an rsync to a folder on the remote proxmox server. This folder is then created as a backup storage location in the proxmox webGUI on the remote proxmox server.
The purpose of this configuration is to provide fast disaster recovery from backups on the internal network if a node or VM dies and then use the remote server to restore mission critical VM's if our entire location goes down due to fx. fire, loss of power, long term outage on the internet connection etc.
However our test did not succeed as expected. We did perform the local scheduled backup of all test VM's on our internal PVE cluster to the internal backup server and this was also sent to the remote server using rsync, but upon restore of the VM on the remote PVE server it was unable to boot from the harddisk. The VM restores without errors and we then correct the network configuration to match the remote environment, while keeping everything else as it was when restored. We boot the VM, but it keeps stuck with a blinking cursor when trying to boot from the hard disk.
We then downloaded the backup from the remote server, onto the same node it was normally running on, using SCP and restored it here. It then booted fine.
Our local cluster is a mix of different servers, where most of them are using Intel Xeon E5620 processors and one server has 4 Intel Xeon X7550. The remote server uses a newer Intel Xeon E3-1240Lv3 and our test VM that was running a fresh and fully updated installation of CentOS 7.3 with nothing else installed.
How do I debug the issue on the remote server when no error or warning output is shown on screen or in the task log of the web GUI?
As part of testing out Proxmox for our new virtualization infrastructure, we have configured an offsite server with the same Proxmox VE 4.4-13/7ea56165 as our internal 5 node cluster.
The cluster runs a daily backup to a RAID6 NFS-share on our storage server. This server then does an rsync to a folder on the remote proxmox server. This folder is then created as a backup storage location in the proxmox webGUI on the remote proxmox server.
The purpose of this configuration is to provide fast disaster recovery from backups on the internal network if a node or VM dies and then use the remote server to restore mission critical VM's if our entire location goes down due to fx. fire, loss of power, long term outage on the internet connection etc.
However our test did not succeed as expected. We did perform the local scheduled backup of all test VM's on our internal PVE cluster to the internal backup server and this was also sent to the remote server using rsync, but upon restore of the VM on the remote PVE server it was unable to boot from the harddisk. The VM restores without errors and we then correct the network configuration to match the remote environment, while keeping everything else as it was when restored. We boot the VM, but it keeps stuck with a blinking cursor when trying to boot from the hard disk.
We then downloaded the backup from the remote server, onto the same node it was normally running on, using SCP and restored it here. It then booted fine.
Our local cluster is a mix of different servers, where most of them are using Intel Xeon E5620 processors and one server has 4 Intel Xeon X7550. The remote server uses a newer Intel Xeon E3-1240Lv3 and our test VM that was running a fresh and fully updated installation of CentOS 7.3 with nothing else installed.
How do I debug the issue on the remote server when no error or warning output is shown on screen or in the task log of the web GUI?
Last edited: