Backups not restoring to the correct snapshot

[ryandlich]

Hello,

I am trying to configure backups to backup a few servers. The backups restore to the original backup regardless of how many I take or how many time I make changes on the server. IE: one server is a game server and I take a snapshot backup, make a change, then take another snapshot backup and it shows both under backups. However when I stop the VM and restore it to the second snapshot it restore it to the first and the change is not there. This is pretty well out of the box, any ideas from the community?

backup storage is set to vmbackup(see below)

Gigabyte x570 with Ryzen 5900x, 64GB ram, one NVME for boot, one NVME for vmstorage, and one NVME for backups.







NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 1007K 0 part
├─nvme0n1p2 259:2 0 1G 0 part /boot/efi
└─nvme0n1p3 259:3 0 475.9G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:2 0 3.6G 0 lvm
│ └─pve-data 253:4 0 348.8G 0 lvm
└─pve-data_tdata 253:3 0 348.8G 0 lvm
└─pve-data 253:4 0 348.8G 0 lvm
nvme2n1 259:4 0 931.5G 0 disk
nvme1n1 259:5 0 953.9G 0 disk
└─nvme1n1p1 259:6 0 953.9G 0 part /mnt/nvme1

 

[ryandlich]

I believe that restoring to a backup is not working, because I can delete all backups, make the change and take a new one and the result is the same it restores to the non changed state.

 

[fiona]

Hi,
what kind of changes are you talking about? Are you really sure the new data in the VM has been synced to the disk and is not just living in guest RAM when you take the new backup? Please post the output of pveversion -v and qm config <ID> with the ID of your VM. What if you shutdown the VM before taking the new backup?

 

[ryandlich]

Hi,
what kind of changes are you talking about? Are you really sure the new data in the VM has been synced to the disk and is not just living in guest RAM when you take the new backup? Please post the output of pveversion -v and qm config <ID> with the ID of your VM. What if you shutdown the VM before taking the new backup?

That is a very good question, it could just be in RAM. I think I can test that. Here is the out put you asked for
root@vmhost:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.15.102-1-pve)
pve-manager: 7.4-3 (running version: 7.4-3/9002ab8a)
pve-kernel-5.15: 7.3-3
pve-kernel-5.15.102-1-pve: 5.15.102-1
ceph: 17.2.6-pve1
ceph-fuse: 17.2.6-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4-1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-3
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-1
libpve-rs-perl: 0.7.5
libpve-storage-perl: 7.4-2
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.3.3-1
proxmox-backup-file-restore: 2.3.3-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.6.3
pve-cluster: 7.3-3
pve-container: 4.4-3
pve-docs: 7.4-2
pve-edk2-firmware: 3.20221111-1
pve-firewall: 4.3-1
pve-firmware: 3.6-4
pve-ha-manager: 3.6.0
pve-i18n: 2.11-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-1
qemu-server: 7.4-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.9-pve1
root@vmhost:~# qm config 100
agent: 1,fstrim_cloned_disks=1
balloon: 0
boot: order=scsi0;ide2;net0
cores: 6
cpu: EPYC
ide2: cdrom,media=cdrom
memory: 8192
meta: creation-qemu=7.2.0,ctime=1685894152
name: Server1
net0: vmxnet3=D2:7E:79:701:1A,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: vmbackup:100/vm-100-disk-0.qcow2,discard=on,iothread=1,size=60G
scsihw: pvscsi
smbios1: uuid=753e4b04-f62f-4009-bf81-3bf5f7ff5eb9
sockets: 1
vmgenid: 2e5b1ced-4aec-4db2-b014-acc22912046c
root@vmhost:~#

 

[ryandlich]

You nailed it Fiona. The changes were existing in RAM. I’ve tested several times since and it is working as expected when i give it time to write to disk. Thank you!