Search results

Isn't it possible for pbs to pause/stop backup if it is foreseeable that the disk will run out of space (or just a reserved space of a few gigs for system as in other backup programs)?

Ok. I moved some chunks und did gc twice like mentioned above. Can I set quota to a percentage (e.q. 99) or only to a fixed size like 14.3T? Is it possible to reduce the reserved space for root to less than 100G (!) ?

Nobody? :-(

Over the weekend my pbs datastore is running out of space and now I'm unable to run a garbage collection. This is the output of discus: and this is the output of zpool list: What is the meaning of FREE and second question: How could this help me out of my dilema? Is is possible to use the...

what is the cause if one card is in multiple immo groups and another only in one? proxmox / board bios/efi / driver ?

For the sake of completeness: I wasn't able to passthrough the hba mentioned above to 2 different vm's. I solved it by attaching another hba (HP) which was laying around to the host ;-)

one last (?) question: in this case i never have to run a prune job on the target because the pruned snapshots are "deleted" by the sync job (respectively the gc afterwards on target)....

thank you for clarification...

ok. this is what i thougt... but if I pruned snapshots on source (without gc) BEFORE sync is running they aren't synced to the target,right?

as i understand there's no 1:1 sync to a remote target (without processing the data afterwards) as known from "normal" backups (sync new files and delete old ones)? so a sync copies the content (chunks) of (new) snaphots und without a garbage collection on remote it runs out of memory at a...

EOM

But i have to take a deepdive into the logs to see this... it should be visible in the dashboard. ... Like in other backup programs... ups... did I say that out loud? :p

thank you for clarification.

Or did I miss something? :oops:

What I can't see (wether in pbs nor in the email reports) is detailed information which vm has backupped how many gigs per day / week / month... Is this planned for future versions?

Is it normal that there are huge time spans where no update seems to happen in logfile (last three lines): 2024-10-25T08:21:40+02:00: starting garbage collection on store remote_backupstorage_nas07 2024-10-25T08:21:40+02:00: Start GC phase1 (mark used chunks) 2024-10-25T08:23:12+02:00: marked...

I dit it... ;-)

Configuration of the sync job looks like this: https://forum.proxmox.com/threads/push-sync-job-from-pbs-to-nas-nfs.156464/

I've added an nfs share as sync target (so no direct backup). It's running well so far. Garbage Collection is slow of course. Just mount the share via fstab und go with it...

My backup plan syncs the backup on the local storage at the pbs server to a remote nfs share on a nas. If I set up a sync job for this I think this scenario isn't envisaged by pbs as I only can do this if I turn the remote storage (nas) to a local storage by mounting the nfs-share to pbs. So...