Newbie issue with broken hardware and Proxmox VM

[matt.]

Hi proxmox folks,

I'm new at my company, they use Proxmox 1.5, what is quite new to me, too. Last night one physical server died forever with all data lost.
On that server there has been running one proxmox cluster node, that node is not working any more of course, in the GUI I get the error message "Unable to get data for Cluster Node 52".

Since I have hundreds of virtual machines on different nodes to maintaine but no good documentation at all, I can't determine which virtual machine(s) ran on that node. How can I get the informations which virtual machine ran on that server? I already had a look at the master server /var/log/ directory but did not find any informations regarding which vm is on which node.

Thank you for your help in advance!

Matt.

 

[udo]

Hi proxmox folks,

I'm new at my company, they use Proxmox 1.5, what is quite new to me, too. Last night one physical server died forever with all data lost.
On that server there has been running one proxmox cluster node, that node is not working any more of course, in the GUI I get the error message "Unable to get data for Cluster Node 52".

Since I have hundreds of virtual machines on different nodes to maintaine but no good documentation at all, I can't determine which virtual machine(s) ran on that node. How can I get the informations which virtual machine ran on that server? I already had a look at the master server /var/log/ directory but did not find any informations regarding which vm is on which node.

Thank you for your help in advance!

Matt.

Hi,
unfortunality the infos do you need are on the broken node!
Normaly it's a good practice to backup the content to a backup-directory on another system.
And/or, if use shared storage to save the configs to other nodes.

Can you boot the broken system with an rescue-cd? Or connect the harddisk to another linux box?
The configs, do you needs are below /etc/qemu-server for kvm-vms or /etc/vz/conf for openvz.
For the place of the vm-data you must look in the config and in /etc/pve/storages.cfg (the storage.cfg file is on all cluster-nodes the same).

Udo

 

[matt.]

Hi Udo,

thanks for your answers.

unfortunality the infos do you need are on the broken node!

Yeah, to bad there is no backup. Nearly more bad that Promox does not save some informations like the hostname of the vm's, that would be a great help because then I'd know if the vm's were important or not and maybe could save time. But I don't want to distract from my previous collegues bad habits (not to have a backup e.g.).

Normaly it's a good practice to backup the content to a backup-directory on another system.
And/or, if use shared storage to save the configs to other nodes.

Unfortunatly (in this case) the system is using a local disk and it is a disk error (no RAID), it boots in an EFI BIOS at startup.

Can you boot the broken system with an rescue-cd? Or connect the harddisk to another linux box?

I'll check on that in the next 2 days and get back to you / to here.

The configs, do you needs are below /etc/qemu-server for kvm-vms or /etc/vz/conf for openvz.
For the place of the vm-data you must look in the config and in /etc/pve/storages.cfg (the storage.cfg file is on all cluster-nodes the same).

Thanks, that helped a lot so far!

Bye

Matt.

 

[dietmar]

Maybe there is still some info in '/var/lib/pve-manager/vzlist'?

 

[matt.]

Thanks to you all, the issue has been *solved*.

I was able to restore some data on the hdd and get the informaitions regarding the vm's on that machine.

Matt.