Search results

commit id was what we wanted ;-)

Thank you, currently we can't dive deeper into the source code. We are willing to pay someone who can show us how to compile properly new versions of proxmox-backup-client for EL8.x (Rocky). Can you point someone out?

Thank you - you could you give us a pointer which commit of the proxmox repo fits to this commit of proxmox-backup?

We know that there is only an official client for Debian. We know that we can compile a client for EL8 from here, which we do: https://github.com/sg4r/proxmox-backup-client/releases We can see that more clients are planned in the roadmap: Backup clients for other operating systems There are...

Yes, thank you!

Currently we test our backup in a desaster mode. One scenario is the loss of encryption-key.json with which we encrypted a host backup with proxmox-backup-client: proxmox-backup-client key import-with-master-key encryption-key.json --encrypted-keyfile rsa-encrypted.key --master-keyfile...

I tried that on one machine (without --exclude /var/log/lastlog). Very long-running job, high cpu consumption, more RAM needed than usual. Sparse file /var/log/lastlog is the problem...

Thanks. I already contacted the maintainer. It seems he is not active currently. I understand that there is a need for a timeline. What I do not understand, is that a client for EL8 is not a top priority. We have only Rocky8 in production. We use Debian only for our Proxmox Server... From our...

We tried to update out EL8 client trying to adapt this script https://github.com/sg4r/proxmox-backup-client without luck. We cCanged commit ids but obviously we did not do it right. We do not have the time for now to dive deeper into it. Do you have an idea when official client for EL8 is coming?

Hi, starting a mount of a backup mounts the archive very well. umount of the mountpoint does unmount the mountpoint but the proxmox-backup-client process keeps running. How would we stop the proxmox-backup-client mount process besides the possibilty to kill -HUP the process?

This restart seemed to have solved the problem. No zfs error messages anymore.

Hi, just come from another thread which solved this one! :) https://forum.proxmox.com/threads/huge-number-in-size-column.105965/ We just added --exclude /var/log/lastlog as a parameter and - you know what - now the backup runs smoothly! RAM usage remains <= 1GiB and the backup is much faster...

We managed about around destroyed and created again zfs datasets with the same name... And removed and created them agaign as a datastore in PBS. Maybe we have to restart proxmox-backup-proxy to inform PBS about this changes ... :-? Currentlythere is a long running backup job active...

Cool, this is precisely the case. Thx.

root@io:~ # ls -lh /proc/spl/kstat/zfs/tank total 0 -rw-r--r-- 1 root root 0 Mar 4 16:02 dmu_tx_assign -rw-r--r-- 1 root root 0 Mar 4 16:02 iostats -rw-r--r-- 1 root root 0 Mar 4 16:02 multihost -rw-r--r-- 1 root root 0 Mar 4 16:02 objset-0x1a8b -rw-r--r-- 1 root root 0 Mar 4 16:02...

This is the output of the garbage collection. At the end: 2022-03-04T14:55:43+01:00: Original data usage: 972.506 GiB 2022-03-04T14:55:43+01:00: On-Disk usage: 7.048 GiB (0.72%) 2022-03-04T14:55:43+01:00: On-Disk chunks: 5710 2022-03-04T14:55:43+01:00: Deduplication factor: 137.98...

True. > the PVE side can already do that (if the PBS storage is configured with the matching key of course ;)) Just out of curiosity - where would you do that?

In the example above ist the vm with ~5GiB backup size a Debian 10 machine and the two other are Rocky 8.

We test proxmox-backup-client on some VM (Rocky 8, Debian 10/11) and experience a strange behaviour in the Size column of the GUI. All VM should have around 5GiB size but some have ~322GiB. In the respective snapshot folder the pxar-file of the VM with 322 GiB is ~1.7Mib and the...

dmesg -T: [Fri Mar 4 13:24:04 2022] [ 155799] 0 155799 648872 468354 4890624 0 0 proxmox-backup- [Fri Mar 4 13:24:04 2022]...