Search results

Here you are. From http://download.proxmox.com/debian/pve/dists/trixie/pve-no-subscription/binary-amd64/ Particularly: http://download.proxmox.com/debian/pve/dists/trixie/pve-no-subscription/binary-amd64/pve-manager_9.1.1_all.deb...

I don't think I would be able to answer these questions better than the original documentation, so I'm just giving the link :): https://pbs.proxmox.com/docs/maintenance.html#pruning In case you can't discover the proper retension scheme after reading these docs (I admit it wasn't quite obvious...

A good method is creating a second PBS and "pull" the backups into it. It's documented at https://pbs.proxmox.com/docs/managing-remotes.html and there are quite many threads about it in the Forum :).

Welcome, @richhemmings . About problem number 2: retension settings are described at https://pbs.proxmox.com/docs/maintenance.html#pruning A nice prune simulator is at https://pbs.proxmox.com/docs/prune-simulator/index.html

Maybe this is a hint: https://forum.proxmox.com/threads/backup-job-error-no-space-left-on-device.160098/

Hi. This might be a blind shot, but I seem to remember a similar issue when the reason was the space in a temporary directory, not on the destination device. Maybe you'll be able to "google" for a similar thread... edit: Also fleecing rings some bell. My memories may be wrong of course.

I have little knowledge about PVE clusters, but I would say yes. Usually it's recommended to run newest PVE and PBs versions. From your screenshot "Add: Proxmox Backup Server" I understand that you add it as the root user. A safer method is NOT doing so. I recommend creating in the PBS a new...

It depends on various details. Prettier? Probably ;-). Safer? Maybe not. Again: it depends on how you want to access them from the Internet and how complicated you want to make your infrastructure. If you want to give them public addresses (NOT recommended!), giving them public domain names...

Making the hypervisor and the backup server accessible from the Internet is a bad idea. And they shouldn't have public IP addresses. So there's no need to give them public domain names :) . edit: For instance my PBS' FQDN is: pbs1:~# hostname --fqdn pbs1.local

When I was writing about unique ids, I meant VM ids. Names aren't so important. Just for "human" convenience I would give to backup servers some short and easy names like pbs1 and pbs2 :). Short and easy names give less clutter and occupy less space in GUIs, in command lines and in paths. P.S...

@Rytecbe, when you are configuring the PBS, I recommend using namespaces in the datastore. For instance you can create a separate namespace for each PVE node or each physical machine. Thanks to namespaces there is no conflicts from possible non-unique (*) ids in different PVE servers. Also...

"The only usecase for any backup server is to restore data when (not: if) the source system fails." Another usecase is restoring a file when the source system is OK and someone needs the file which has been deleted or modified in the meantime :).

Hi, @sebalinux . I know it would be a workaround, not a solution, but to locate the reason closer, you may try as well installing PVE 8 and then upgrading to PVE 9 and checking if it boots correctly.

@EggsLan , congrats on finding these variables :) . At the moment I've searched Google for PBS_RESTORE_FETCH_CONCURRENCY and it displayed miserable 5 (five) results only. I've checked again the official PDFs and they don't mention these variables at all. I'm surprised that Proxmox failed to...

Out of curiosity I've just tried to find the way how to do that. But I have failed to find it in the links from that post and in the official up-to-date documentation PDFs https://pbs.proxmox.com/docs/proxmox-backup.pdf and https://pve.proxmox.com/pve-docs/pve-admin-guide.pdf I've searched...

Sure! :)

The answers depend. I don't know. Maybe if you post what exactly you've done trying "to change the Proxmox host boot kernel" AND what were the outputs, someone will have any idea. If you post the commands and the results, please use "code tags" (the button marked as "</>" above).

Hello, virusbcn. Hard to give any hints because you have written no details about your PVE and what exactly you did and what were the outputs. Good that you have admitted you used "the Proxmox xshok script" some time. From what I managed to find, this is a collection of scripts which are able...

Depending on what that unofficial script spoiled, there may be less or more things to do - difficult to know in advance. Use a search engine for: proxmox forum web gui blank community script

As far as I can see, that's OK. E.g. at my PVE 8.4.14 the latest files in /var/cache/apt/archives/ have modification date Oct 23. At https://www.debian.org/security/ you can see recent Debian security advisories. There are some newer there, but mainly GUI stuff, so not for PVE. Besides, most...