Search results

  1. V

    Very Serious Backup/Restore Issue in PVE 5.0

    Unfortunately the original hosts were wiped, so all I have is the VZdump backup files
  2. V

    Very Serious Backup/Restore Issue in PVE 5.0

    All backups were stored to my FreeNAS machine. The ones which have worked correctly have been restored using this configuration as well. I have also tried copying the file to the Proxmox box to no avail. Am I just kind of out of luck for these VM's? It'd be really nice to be able to get them...
  3. V

    Very Serious Backup/Restore Issue in PVE 5.0

    root@proxmox1:/home# vma verify vzdump-qemu-101-2017_09_24-01_45_02.vma ** (process:29773): ERROR **: verify failed - wrong vma extent header chechsum Trace/breakpoint trap
  4. V

    Very Serious Backup/Restore Issue in PVE 5.0

    You're right and I should have done this originally. It just seems unfortunate that the backups I so diligently stored numerous copies of are now unusable.
  5. V

    Very Serious Backup/Restore Issue in PVE 5.0

    Unfortunately I was also using 5.0 (non-Beta).
  6. V

    Very Serious Backup/Restore Issue in PVE 5.0

    Yes however the version I used to make that was upgraded to 5.0 as well.
  7. V

    Very Serious Backup/Restore Issue in PVE 5.0

    I did not miss updating my hosts; I actually downloaded the latest ISO from the Proxmox site, burned it to a USB and installed it. I then immediately updated everything. proxmox-ve: 5.0-25 (running kernel: 4.13.4-1-pve) pve-manager: 5.0-33 (running version: 5.0-33/23132090)...
  8. V

    Very Serious Backup/Restore Issue in PVE 5.0

    Over the weekend I blew away two Proxmox hosts (clustered) and reinstalled the hypervisors from scratch (two single nodes). Because I had backups of everything, I thought I'd be fine to just restore the backup files and continue working. The hosts have multiple backups of most containers/VM's...