Hi, I apparently shot myself in the foot. I wrote a puppet module to manage my syslogs. One step was to convert from rsyslog to syslog-ng. I was testing on a few select machines, including one of my Proxmox-VE HNs. Well, it did not go well on that machine. I noticed that the puppet run was taking an inordinate amount of time, and realized that was because the VMs on that host (including the puppetmaster) were gone.
Now all of the vms on that machine, while they show up in the web interface, do not show up on the filesystem in /var/lib/vz/private, and /var/lib/vz/root has directories for the containers, but they are all empty. In trying to reconstruct what happened, rsyslog was not uninstalled, syslog-ng was not installed, but I had to reinstall proxmox-ve-2.6.32, pve-manager, qemu-server, and vzctl. I don't understand why those were uninstalled. I figured, based on the experience with my other Debian boxes, that the Proxmox machines would handle the switch. I guess I thought wrong.
So at this point, I am trying to figure out my options. I have vzdumps, but those are from August 2013. I could restore them, but those are kind of old. I also have current backups of the hardware nodes, but exclude /var/lib/vz/private/*, /var/lib/vz/root/*, and /var/lib/vz/images/*, primarily because the backups of the individual hosts are sufficient for almost every situation...Except this one. :) The individual host backups are full backups except for:
Would my best option be to restore from the indivual host backup to a file then untar into /var/lib/vz/private/* or to restore my vzdumps and update everything to current?
Thanks,
--vr
Now all of the vms on that machine, while they show up in the web interface, do not show up on the filesystem in /var/lib/vz/private, and /var/lib/vz/root has directories for the containers, but they are all empty. In trying to reconstruct what happened, rsyslog was not uninstalled, syslog-ng was not installed, but I had to reinstall proxmox-ve-2.6.32, pve-manager, qemu-server, and vzctl. I don't understand why those were uninstalled. I figured, based on the experience with my other Debian boxes, that the Proxmox machines would handle the switch. I guess I thought wrong.
So at this point, I am trying to figure out my options. I have vzdumps, but those are from August 2013. I could restore them, but those are kind of old. I also have current backups of the hardware nodes, but exclude /var/lib/vz/private/*, /var/lib/vz/root/*, and /var/lib/vz/images/*, primarily because the backups of the individual hosts are sufficient for almost every situation...Except this one. :) The individual host backups are full backups except for:
Code:
'core.*',
'*.lock',
'/dev/*',
'/media/*',
'/mnt/*',
'/proc/*',
'/sys/*',
'/run/*',
'/tmp/*',
'/lib/init/rw/*',
'/var/cache/apt/archives/*',
'/var/lock/*',
'/var/run/*',
'/var/tmp/*'Thanks,
--vr
