Best practices for Backup on SATA HDD

It died at times when backups ran, but this is at night and I can only roughly estimate when exactly the VM dies as it seems to lose last log info, too.
But, it died also when I moved the storage of another VM (which is I/O intense, of course). I realized that after a few seconds, it is likely that it died very shortly after initiating the storage move.

I did not change the settings, first attempt doing that ended in roasted VM (see some posts above), wanted to watch what happens after change in CPU provisioning (I try to avoid multiple changes at the same time to be able to sort out later). Also, I hoped to achieve some improvement using a SSD for the VM. Most probably this helps not that much, as long as the backup target is still SATA HDD.
 
if your VM dies when there is high load on the storage, it's because of VM locking. and VM locking happens if you did not change VM defaults to use qemu virtio dataplane.

go, monitor your VM with ping during backup/high i/o load and i'm sure you will see ping go crazy before your VM dies.

read https://bugzilla.kernel.org/show_bug.cgi?id=199727

>I did not change the settings, first attempt doing that ended in roasted VM (see some posts above),

that's weird and that should not happen.
 
  • Like
Reactions: _gabriel and sry

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!