Recent content by Rufus Ebonhawk

  1. R

    Windows 11 hard disk read-only

    Hi, our new one and only Windows 11 vm runs quite good. Today i wanted to add another hard disk, no thing. But - it is read-only in Windows! The hard disk 0 is writeable. Hard disk 1 not. Inside Windows hard disk 0 and 1 look similar in terms of settings. Hard disk 1 is not labeled as read...
  2. R

    proxmox-backup-client for other distributions

    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?
  3. R

    proxmox-backup-client for other distributions

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

    proxmox-backup-client for other distributions

    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...
  5. R

    [SOLVED] Recover encryption-key.json with master-private.pem

    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...
  6. R

    proxmox-backup-client killed /memory allocation of 27536946 bytes failed

    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...
  7. R

    proxmox-backup-client killed /memory allocation of 27536946 bytes failed

    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...
  8. R

    proxmox-backup-client killed /memory allocation of 27536946 bytes failed

    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?
  9. R

    proxmox-backup-client mount / umount does not stop process

    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?
  10. R

    [SOLVED] Huge number in size column

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

    proxmox-backup-client killed /memory allocation of 27536946 bytes failed

    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...
  12. R

    [SOLVED] Huge number in size column

    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...
  13. R

    [SOLVED] Huge number in size column

    Cool, this is precisely the case. Thx.