This document is the single authoritative backup and restore guide for a standalone Proxmox VE host. It is written to be usable during a real failure (NVMe disk read/write issues) but with the premise that the Proxmox VE host is still running and accessible (to try to create VM backups).
- Single Proxmox VE host (no cluster)
- Proxmox VE 8.x backups, restore onto Proxmox VE 9.1-1
- One failing NVMe (system + VM storage)
- One internal 500 GB SATA SSD used mainly for ISO images and auxiliary storage
- One external USB disk (NTFS) used for backups (already contains other data)
- VMs:
- Ubuntu-01 .. Ubuntu-04 (continuously running, some with Docker)
- Several Windows/macOS test VMs (mostly stopped)
- Virtual machines (primary priority)
- Proxmox host configuration (network, VM configs, mail, storage)
- Awareness of what is not backed up (packages, logs, caches)
/var/log/var/cache/usr,/bin,/lib(reinstalled by Proxmox installer)- System users/passwords
The USB disk already contains data and must not be wiped.
Example (adjust device name if needed):
lsblk
mkdir -p /mnt/usb-backup
mount -t ntfs-3g /dev/sdX1 /mnt/usb-backupIf an error occurs on mount, then most probably NTFS driver is not installed:
apt install ntfs-3gmkdir -p /mnt/usb-backup/proxmox-backups/dumpDatacenter → Storage → Add → Directory
- ID:
usb-backup - Directory:
/mnt/usb-backup/proxmox-backups - Content: ✔ Backup
Important: do not select ISO / Disk image here.
| Mode | When to use | Notes |
|---|---|---|
snapshot |
Running Linux VMs | Requires QEMU guest agent for consistency |
stop |
Docker-heavy VMs or Windows | VM is stopped automatically by vzdump |
You do not need to manually stop the VM when using --mode stop.
vzdump 201 --storage usb-backup --mode stop
vzdump 103 --storage usb-backup --mode stopvzdump 202 --storage usb-backup --mode snapshot
vzdump 100 --storage usb-backup --mode snapshotvzdump 101 --storage usb-backup --mode stopErrors like:
critical medium error, dev nvme0n1
job failed with err -61 - No data available
Mean:
- The source NVMe is failing
- The backup is aborted at the unreadable sector
This is not recoverable via vzdump.
- Do not retry endlessly (accelerates disk death)
- Accept partial VM loss
- Plan post-restore data recovery from raw disks
Critical directories/files:
/etc/pve/etc/network/etc/hostname/etc/hosts/etc/postfix/root
tar -czf /mnt/usb-backup/proxmox-backups/proxmox-host-config.tar.gz \
/etc/pve \
/etc/network \
/etc/postfix \
/etc/aliases \
/etc/aliases.db \
/etc/hostname \
/etc/hosts \
/etc/fstab \
/etc/vzdump.conf \
/etc/lvm \
/etc/ssh \
/rootWarnings about "Removing leading /" are normal and harmless.
ISO: https://enterprise.proxmox.com/iso/proxmox-ve_9.1-1.iso
Use Rufus:
- Partition scheme: GPT
- Target system: UEFI
- Boot selection: Proxmox ISO
- Write mode: ISO mode (default)
During installer:
- Hostname:
proxmoxorproxmox.local - IP address:
192.168.0.88 - Same gateway and DNS as before
Do not create extra storage yet.
- Install Proxmox
- Configure networking
- Mount USB backup disk
- Restore host config (selectively)
- Add storage
- Restore VMs
mkdir /root/restore
cd /root/restore
tar -xzf /mnt/usb-backup/proxmox-backups/proxmox-host-config.tar.gzcp -a etc/pve /etc/
cp -a etc/network /etc/
cp -a etc/postfix /etc/
cp -a etc/hostname /etc/hostname
cp -a etc/hosts /etc/hosts❌ Never extract directly to /.
Same as section 3.
- Identify disk:
lsblk - Mount (example):
mkdir -p /mnt/sata-iso
mount /dev/sdY1 /mnt/sata-isoDatacenter → Storage → Add → Directory
- ID:
sata-iso - Directory:
/mnt/sata-iso - Content: ✔ ISO
Yes – strongly recommended.
Reasons:
- Firewall rules
- Backup references
- Scripts
- Muscle memory
qmrestore /mnt/usb-backup/proxmox-backups/dump/vzdump-qemu-201-*.vma 201Repeat for all successfully backed-up VMs.
After Ubuntu VMs are restored and stable:
- Remove old NVMe
- Attach via USB/NVMe enclosure to another Linux system
- Identify LVM volumes
- Mount read-only
- Extract
.qcow2or raw disks
Windows disks can later be mounted in:
- Linux (
nbd,guestfish) - Windows (DiskInternals, FTK Imager)
If something goes wrong:
- Stop all restore operations
- Do not write to old NVMe
- Verify backups exist and are readable
- Restore only one VM at a time
- Keep USB backup mounted read-only if unsure
- Your successful Ubuntu VM backups are sufficient to recover services
- Windows VMs with failed backups may still yield data
- Proxmox VE 9.x is a safe upgrade target
End of document.