Search results

  1. I

    Backup over 100%

    yes
  2. I

    Backup over 100%

    I am trying to do a backup of 4 VMs every 5 minutes. I see this in a log. INFO: starting new backup job: vzdump 149 150 139 158 --mode snapshot --fleecing 0 --quiet 1 --prune-backups 'keep-daily=14,keep-monthly=1' --notes-template '{{guestname}}' --mailnotification always --storage BACKUP...
  3. I

    [SOLVED] PBS 3.3.1: Backup tasks hang after concluding uploads

    We think the problem was the switch. We changed the switch and now it seems to work normally. We'll test it and I'll let you know if anything doesn't work. Thanks for your help. I have another question. We were using nfs v4. I read that nfs v3 will be better for our configuration.(HDD etc)...
  4. I

    Problem beim Erstellen eines Datastore

    Durch die Anpassung von Squash am Synology hat dann geklappt. Ich habe dazu in Synology den Eigentümer für Backup Ordner als admin Rekursiv verteilt und Squash "alle Benutzer zu admin."
  5. I

    [SOLVED] PBS 3.3.1: Backup tasks hang after concluding uploads

    Sorry the Swap is on PVE Hosts. PVE 1 -> RAM usage 58.96% (148.20 GiB of 251.35 GiB) SWAP usage 0.01% (512.00 KiB of 8.00 GiB) PVE 2 -> RAM usage 58.69% (147.51 GiB of 251.35 GiB) SWAP usage 10.98% (899.50 MiB of 8.00 GiB) PVE 4 -> RAM usage 70.50% (88.41 GiB...
  6. I

    [SOLVED] PBS 3.3.1: Backup tasks hang after concluding uploads

    previously started every 10 minutes and always was fine. Synchronisation will be started when the backups are completed. ( about 02:30) Logs are attached. We stopped the synchronisation because it takes too long. For 1 snapshot from 02:54 to 11:11. The synchronised backup was done on Sunday...
  7. I

    [SOLVED] PBS 3.3.1: Backup tasks hang after concluding uploads

    We have a problem with our current backup(PBS-3.3.3-1). We used to backup to two different Proxmox. This worked fine despite the dirty bitmap. After updating to 3.3 with the feature (backup: stat known chunks on backup finish) the problems started. Everything took so long that we could no...
  8. I

    [SOLVED] full backup after dirty-bitmap?

    Will a full backup be performed after a dirty bitmap? For example 60 GB VM First Backup take 3 Minutes INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared INFO: backup is sparse: 15.51 GiB (25%) total zero data INFO: backup was done incrementally, reused 15.71...
  9. I

    Backup taking a long time at "add blob" step.

    Will a downgrade or a new PBS with old version help?
  10. I

    Will there be a function in proxmox, analogous to the function in esxi VMware vSphere Fault Tolerance

    Do you have any plans in this regard? Is the project still going ahead?
  11. I

    [SOLVED] Unable to activate storage.......does not exist or is unreachable

    Konfiguration (sehe Bild ) Storage mit jeweils 2x 10 G/bit Ports. (Bond ist eingerichtet) Proxmox mit jeweils 2x 10 G/bit Ports. (Bond ist eingerichtet) Je Port geht zu einem eigenen Switch. Switch sind zwei Strecken (STP) verbunden. Proxmox zwischen 8:00 -08:30 CPU ca. 23 % zwischen 8:00...
  12. I

    [SOLVED] Unable to activate storage.......does not exist or is unreachable

    Wir bekommen in der letzten Zeit weitere Fehler. Die Storages sind nicht überlastet und man merkt keine Performance Problem. Das Problem ist, dass "directory '/mnt/pve/xxx-NAS' does not exist or is unreachable" Fehler passiert und ab und zu die VMs sich neu starten. (Windows Logs) Anbei ein...
  13. I

    Linux: root vulnerability (CVE-2024-1086)

    Thanks! could you tell me where you see that the bug is fixed? in the list I see Pending (6.8.0-7.7) and Released (6.8~rc2) but 6.8 rc2 is not installed on proxmox. @shanreich
  14. I

    Linux: root vulnerability (CVE-2024-1086)

    https://www.proxmox.com/en/proxmox-virtual-environment/features -> "Proxmox Virtual Environment is based on Debian GNU/Linux and uses a custom Linux Kernel"
  15. I

    Linux: root vulnerability (CVE-2024-1086)

    Proxmox (8.2) is based on Debian bookworm, according to the Debian documentation the bug has been fixed in the bookworm 6.1.76-1 kernel. bookworm (security) 6.1.90-1. (https://security-tracker.debian.org/tracker/CVE-2024-1086) I noticed that in our infrastructure Proxmox has kernel...
  16. I

    Import Disk VMDK-qcow2 Unsupported image type 'onolithicFlat

    I am trying to import a disk VMDK. qm importdisk 164 Disk4.vmdk NAS2 --format qcow2 but I get this error qemu-img: Could not open 'Disk4.vmdk': Unsupported image type 'onolithicFlat How can I solve it?
  17. I

    proxmox-file-restore with Command line

    Can I do a File-restore with the Command line?
  18. I

    [SOLVED] Different CPUs in a Cluster (AMD/CPU)

    Hier the Information So I used the check. Host AMD Everything is fine Host Intel Everything is fine VM on AMD Host with CPU Type "Host" Just one vulnerability (Photo1) VM on AMD Host with CPU Type "x86-64-v2-AES" Just one vulnerability (Photo1----if I set the recommend flag for the...
  19. I

    [SOLVED] Different CPUs in a Cluster (AMD/CPU)

    1) The Documentation say "If you care about live migration without security, or have mixed Intel/AMD cluster, choose the lowest compatible virtual QEMU CPU type." We have an AMD EPYC 7302 and an Intel(R) Xeon(R) Gold 6336Y. I tried the live migration with kvm64 and x86-64-v2-AES. An...
  20. I

    Cluster-redundanten Netzwerk

    Hallo, wir haben 6 Hosts jeweils mit 2 Netzwerkarten für Cluster-Netz reserviert. Die Verbindung ins Cluster läuft über 2 Uplink. Jede Karte hat ein eigene IP-Adresse im gleiche Subnetz. (192.168.2.x/24) Die Karte sind auf zwei unterschiedlichen Switch eingebunden und die Switchen sind mit 2...
Top Bottom
Back