Search results

  1. M

    Deactivate Sync Job

    Damn... I was too slow... ;-)
  2. M

    Two separated full meshs for cluster / corosync in a 3-node-cluster

    i used a simple network configuration for corosync then.
  3. M

    Two separated full meshs for cluster / corosync in a 3-node-cluster

    As EllerholdAG said, I didn't get it to work using frr for both meshes. You can configure it, but then nothing works anymore...
  4. M

    Resize ZFS pool after running out of space (PBS datastore full)

    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)?
  5. M

    Resize ZFS pool after running out of space (PBS datastore full)

    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 (!) ?
  6. M

    Resize ZFS pool after running out of space (PBS datastore full)

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

    Single SAS Port Passthrough (Dual Port HBA)

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

    Single SAS Port Passthrough (Dual Port HBA)

    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 ;-)
  9. M

    Garbage Collection on synced targets necessary if "remove vanished" is checked? (EOM)

    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)....
  10. M

    Garbage Collection on synced targets necessary if "remove vanished" is checked? (EOM)

    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?
  11. M

    Garbage Collection on synced targets necessary if "remove vanished" is checked? (EOM)

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

    Visibility! Feature request for backup reports (or more details in email reports)

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

    Visibility! Feature request for backup reports (or more details in email reports)

    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?
  14. M

    Long time span with no update in log while gc is running...

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