What I'm trying to do. Simulate a catastrophic failure where you have to restore from backup on new hardware.
What I've done. Install version 2.1. Download the Debian 5.0 template. Create an openvz container using Debian. Create a couple of backups. Copy the backup (.tar.lzo and .tar.gz) to a usb thumb drive. Reinstall Proxmox. Copy the backup off the thumb drive to /var/lib/vz/dump/dump.
Here's where it gets sticky for me. How to properly restore. What I did, from the Proxmox server, I ran vzrestore backup.tar.lzo 120 from the command line. (I am reading the doc's on the Wiki). The restore was successful in that the vz container shows up in the GUI but it's not using any disk space, memory, or cpu. I can't start it. So I'm doing something wrong I need a hint. I've taken a couple of shots at this and failed. Education by experimentation
Do you need to create a new container and try to restore to it?
Should you be able to start that new container after running vzrestore?
(Question. The default backup path is /var/lib/vz/dump. When I create a backup another /dump directory was created. So I wind up with /var/lib/vz/dump/dump/. Why is another /dump directory created? Why don't it just write the backup file to /var/lib/vz/dump?)
Thanks
What I've done. Install version 2.1. Download the Debian 5.0 template. Create an openvz container using Debian. Create a couple of backups. Copy the backup (.tar.lzo and .tar.gz) to a usb thumb drive. Reinstall Proxmox. Copy the backup off the thumb drive to /var/lib/vz/dump/dump.
Here's where it gets sticky for me. How to properly restore. What I did, from the Proxmox server, I ran vzrestore backup.tar.lzo 120 from the command line. (I am reading the doc's on the Wiki). The restore was successful in that the vz container shows up in the GUI but it's not using any disk space, memory, or cpu. I can't start it. So I'm doing something wrong I need a hint. I've taken a couple of shots at this and failed. Education by experimentation
Do you need to create a new container and try to restore to it?
Should you be able to start that new container after running vzrestore?
(Question. The default backup path is /var/lib/vz/dump. When I create a backup another /dump directory was created. So I wind up with /var/lib/vz/dump/dump/. Why is another /dump directory created? Why don't it just write the backup file to /var/lib/vz/dump?)
Thanks