If downtime is OK for you, STOP is the safest way to go. Expect your VMs unusable for some time, cause system/guest will shutdown and startup after backup.
Stop = VM will be shut down... so data in backup is 100% consistent under all circumstandes
Suspend = VM will be "freeze" for backup. So data can not change while backup is running..... but this can happen in the middle of a disk transaction.
Snapshot = Tell the Guest-OS via Agent to create a...
Replace your Supermicro SATA-DOM again.... we had several which report SMART-Error very soon after initially used... and some which are now years old.... SATA-DOM is a cool small SSD-Sata-Disk, but there are many which just fail very soon. So maybe you got 2 or 3 bad ones in a row..... Happens...
Don't compare Apples and Pines....
ZFS Raidz1 4x vdevs (24x500gb SSD samsung 860 evo) or anything else without real Power Loss Protection will NEVER perform well with ZFS....
When you use Windows or Ubuntu you have a normal FileSystem like NTFS or LVM with ext4.... these do know nothing about...
Völlig egal, das der 3te Server schwächer ist, er wäre immer das besser "Qourum" als ein Pi oder ein "reines" Qdevice. Er muss ja keine VMs tragen, er könnte aber und hat ein "funktionierendes" Web-Interface fürs Management....
Dann hat man doch eh schon 3 Nodes..... die kann man dann auch gleich als PVE installieren und einfach auf einem PBS zusätzlich installieren für die Sicherung...
Yes, something like that... experimented with the idea to have a guest share an RDX-Drive by SMB to have a target for 3 PVEs in a cluster.
Well turned out, this gets disconnected under heavy write load..... already installed a PBS onsite, but struggling with this "hanging" backup job.
Ok reboot...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.