Hello all!
My M.2 just broke and i lost all my VM/config/etc...
I have a proxmox backup disk image (.qcow2) with a lot of snapshots from all of my VM in a Synology (shared with NFS)
I imported the disk to a VM with the following command
After attach the disk and power on the VM, all the time it stuck on "Booting from hard disk" (i tried all bios, proccesor type, disk configurations available)
Im now using the following command to maintan the original disk type, qcow2, because i saw that with the previus command the disk was migrated to raw (it may be the cause of the fail booting OS):
The command will take a lot, around 7-8 hours because it has 2 TB of information
My idea is the following:
1.- Import the disk with all VMs abckups, and start the machine
2.- Add proxmox backup server to my new proxmox server node
3.- Re-deploy my VMs with the backups stored in the disk of proxmox backup
Im doing something wrong?
Sorry for my bad english and ty all!
My M.2 just broke and i lost all my VM/config/etc...
I have a proxmox backup disk image (.qcow2) with a lot of snapshots from all of my VM in a Synology (shared with NFS)
I imported the disk to a VM with the following command
qm importdisk 100 vm-100-disk-0.qcow2 BackupsAfter attach the disk and power on the VM, all the time it stuck on "Booting from hard disk" (i tried all bios, proccesor type, disk configurations available)
Im now using the following command to maintan the original disk type, qcow2, because i saw that with the previus command the disk was migrated to raw (it may be the cause of the fail booting OS):
qm importdisk 100 vm-100-disk-0.qcow2 Backups --format qcow2The command will take a lot, around 7-8 hours because it has 2 TB of information
My idea is the following:
1.- Import the disk with all VMs abckups, and start the machine
2.- Add proxmox backup server to my new proxmox server node
3.- Re-deploy my VMs with the backups stored in the disk of proxmox backup
Im doing something wrong?
Sorry for my bad english and ty all!