Search results

Nicht nur bei den neuen Xeon, hier auch mit einem neuen i5-12500 (alder lake). Bei uns führt das im Übrigen dazu, dass nur noch Fragmente der Proxmox-GUI im Browser angezeigt werden und insbesondere die Graphen ab dem Zeitpunkt der Fehlermeldung gar nicht mehr dargestellt werden. Ein Zugriff...

Yes, we knew this was the case. However, the error message appears after the first call of "file restore", i.e. before a folder was selected. This is irritating. Then, where files can be restored from, they can actually be restored.

root@pbs:~# proxmox-backup-manager versions --verbose proxmox-backup 2.1-1 running kernel: 5.13.19-6-pve proxmox-backup-server 2.1.6-1 running version: 2.1.6 pve-kernel-helper 7.2-1 pve-kernel-5.13 7.1-9...

We set up a new PBS and now have the same problem. Has the patch now been incorporated into the repo or does it still have to be installed manually?

Thanks.

The direct start possibility of a VM in the console view is a nice novelty. Is it also based on Outcast or why is there a second query asking whether you want to start the VM? So like: forever, forever, forever-ever, forever-ever-ever ? Jokes aside: please abolish the second confirmation.

Wir haben aktuell das selbe Problem? Hat irgendwer eine Lösung gefunden?

Mit "NL" meinst Wasabi, richtig? Nutzen wir u.a. auch als cloud-storage, müssen aber die Daten per post-skript nach den Proxmox-backups mit rclone dorthin schaufeln. S3 bekommt man ja aber als backup-Ziel leider nicht "nativ" in Proxmox eingebunden, oder? Oder kann S3 der Proxmox Backup...

Gibt es bei 1&1. Sind dann aber auch "Deutsche Preise" ;) https://cloud.ionos.de/storage/object-storage?ar=1#pricing

how do you implement this technically? Do you need a local PBS that replicates to your PBS?

No, unfortunately not, as all of the above suggestions result in the GUI no longer showing any scheduled time at all. Actually, the integration into the GUI for the Proxmox developers shouldn't be a big problem, right?

I understand that the main focus of the PBS is not on deduplicating in the WAN but in the LAN. This is ONE approach to backups, but does not correspond to our current "philosophy" of it. For us, backups HAVE to be decentralized nowadays and transferred to one of the large cloud storage...

Unfortunately, I don't fully understand the suggestion: Are there several ways to save the backups in the PBS in a different location than each individual chunk in the sub-folders?

And what would be the suggestion for setting up a cloud backup with rclone for the PBS datastore? We have found out that with almost all cloud storage providers, uploading these tens of thousands of small files leads to running into the quota limit in a short time (and, yes, we use our own API...

We are in the process of testing PBS (great product: thanks for that!). It is important for us that we can then load the backup data from the storage to a cloud storage via rclone. It turned out that due to the relatively small chunk size, the upload to cloud storage providers is only loaded...

Does anyone have any idea how to do that?

Ist wohl leider tot, das Projekt. Schade.

One more small thing: after the backups have been renamed, Proxmox no longer automatically deletes them after the set number (Datacenter - Storage - "max backups"). Can that be changed in the script?

Strange. Suddenly the restore of a VM with a different name no longer worked. Happy too early.

Apparently Proxmox has made sure with a patch that the adapted format can now be used to restore directly. Thank you, Proxmox.