i have a setup at hetzner with a pbs an 8 drive zfs raid10
Here every time when a vm is backed up to the backup server the vm will crash with io/errors and cpu stalls.
If you need an environment to repdroduce the errors i can provide access to the setup
Same here,
no Problems with fast backup server hardware and fast servers. But on a proxmox environment at a hoster i see the same.
It seems that during backups blocks are locked for write until they are completely written to the backup server. If this takes too long vm will crash.
On the vms i...
I have changed
} else {
$timeout = 3; # default
to
} else {
$timeout = 8; # default
in line 134 of /usr/share/perl5/PVE/QMPClient.pm , restarted the pve daemons
for service in pvedaemon.service pveproxy.service pvestatd.service ;do
echo "systemctl...
Same issue here, freshly installed backup server . all backups are working but i cannot backup one vm.
Debugged for hours without any success
INFO: started backup task 'f076c6d3-2cb2-4bca-bc7d-b87a765c3db6'
INFO: resuming VM again
ERROR: VM 103 qmp command 'cont' failed - got timeout
I had the same Problem. Solution was I added a mirror of small SSDs to the ZFS Datastore as "Special Device" , copied all backup data and deleted the original data. Afterwards the garbage collection was running in about 30 Minutes. Before I used the special Device it took about 20 hours.
We would like to regularly keep backups of Data outside of the Building. The full datastore including history of all Backups of all Machines does not fit on external disks and is too much for Internet syncing.
I would like to somehow export the latest image of each vm once a week to an external...
I was talking about this bug where data was backed up again although it did not change.
https://forum.proxmox.com/threads/proxmox-backup-client-to-backup-photos-strange-deduplication-factor-and-long-backup-backup-time-after-some-days.85703/#post-376286
Is it possible to change some apt packages...
We also hit this bug and i downgraded kvm and libproxmox-backup qemu some days ago, no problems since then.
Do you think I can update libproxmox-backup to a current version and just leave pve-qemu-kvm downgraded ?
I ask because there was another bug fixed a few days ago that makes incremental...
Wow, I added a zfs special device on 2 mirrored datacenter ssds and populated it by duplicating the data into a new zfs dataset.
Now my garbage collection on 8 TB backup data on a 9 spinning disk raid2z only took 20 Minutes instead of 18 hours before.
The special device with the metadata has 30...
Thanks for your help Fabian, the idea to duplicate the zfs data and later rename seems to be a really good way.
BTW: The lessons to always use Datacenter SSDs for Datacenter purposes we have learned many years ago.
I like proxmox backup server but budget only allows magnetic disks and raidz2.
So especially verify and garbage collect procedures need a hell of a lot of time.
For an 8 TB Backup space today verify needs 2 days and garbage collect needs 1 day.
I think with verify there is not much i can do...
I think the opposite.
If i run fstrim on an 80GB drive with only 20GB of data it will lead to 60GB changed data.
If I run fstri again it will lead to another 60GB of trimmed data.
Hmm, let's look at scsi0 80 GB Disk.
it constantly only has 20 GB in use and 60 GB free.
So it looks strange that 40GB change within a day
It is an ext3 filesystem.
I checked all cronjobs and logs an i have no idea what si happening ...
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.