While awaiting guidance, he was experimenting with the processes, avoiding the loss of information.
This test is important for when the physical server is failing and / or the boot disk.
The pool hds remained intact.
Follow the image of the facts.
This test is important for when the physical server is failing and / or the boot disk.
The pool hds remained intact.
Follow the image of the facts.
Attachments
Another question.
I have the vm discs.
Where are the vms?
At this point, I still need help.
the pool is the same as it used, the discs are here, where the vms are stored and how to recover?
I have the vm discs.
Where are the vms?
At this point, I still need help.
the pool is the same as it used, the discs are here, where the vms are stored and how to recover?
Last edited:
Hey WagnerUrquiza!
nice you joined the conversation!
sorry - was away from forum and a subject for a while... seems like you found the way how to get to your VM disks - it is discussed in early posts!
NOW - I have the same question: HOW TO RESTORE VMs on a new PVE server without .conf files and not having at least a bkp screenshot of list of servers? I do use self-explanatory naming for VMs but in this case it is also lost w .conf files, right?
As I understand VM machines basically are .conf files as I can copy-paste-rename em and it will be new VMs, also regarding PVE 4 user "udo" was saying "Normaly it's enough to save config-data (like below /etc, /etc/pve, /root). An new install is done in 5 minutes and then you can copy back all used files, reboot and fine! This should be faster than recover some GB of data..."
https://forum.proxmox.com/threads/¿...ternal-disk-and-update-buckup-later-on.38694/
- plz correct if wrong for v5/6. So, I'm afraid, if you did not back it up, then there is no way to know what is what except with trying em... but I would do it only on a copies... Also there is a way to convert those raw images to real disks and check on real machines, but seems like a lot of work, what probably I will have to do now one way or another...
best
t
.
Hello.
VMs are
.conf files
and .raw data disks.
# pvesm path location: 100 / vm-100-disk10.raw
/var/lib/vz/images/100/vm-100-disk10.raw
https://pve.proxmox.com/wiki/Storage:_Directory
The .conf are VM details.
The .raws are the mass of data.
See image of post number # 26 and 27.
How to recover the data?
Preserves the hard drive or RAID of the old server;
Create / Install a new PROXMOX server on a different hard drive;
In this new server puts the HD or RAID of the old server;
The hard drives of the VMs will be listed.
See image of post number # 26 and 27.
To know what is in the hard drives of VMs?
Creates a VM with UBUNTU;
Attaches to this UBUNTU VM the hard drives that are listed from the old server;
Then you can see what system you have on that hard drive.
Was the information clear?
Comunidade
Hello.
VMs are
.conf files
and .raw data disks.
# pvesm path location: 100 / vm-100-disk10.raw
/var/lib/vz/images/100/vm-100-disk10.raw
https://pve.proxmox.com/wiki/Storage:_Directory
The .conf are VM details.
The .raws are the mass of data.
See image of post number # 26 and 27.
How to recover the data?
Preserves the hard drive or RAID of the old server;
Create / Install a new PROXMOX server on a different hard drive;
In this new server puts the HD or RAID of the old server;
The hard drives of the VMs will be listed.
See image of post number # 26 and 27.
To know what is in the hard drives of VMs?
Creates a VM with UBUNTU;
Attaches to this UBUNTU VM the hard drives that are listed from the old server;
Then you can see what system you have on that hard drive.
Was the information clear?
Comunidade