I just started testing the pbs backup client for some advanced backup scenarios. One question of course is how to get the maximum performance out of the server that creates backups.
In multiple larger infrastructures there are so called 'backupworkers' (VMs) who have plenty of CPU and RAM as well as 'read-only' access to certain filesystems/mounts. They create backups and handle snapshot schedules etc..
One setting allows specifying "Max number of entries loaded at once into memory".
Is this related to "Chunk size in KB. Must be a power of 2."?
What I am also trying to achieve is a someonewhat interactive UI where support staff is able to check on customer backups and restore certain backups. Is there something on the roadmap that will allow LDAP login to the PBS UI and configure "service desk" roles that can only restore, never delete files?
In multiple larger infrastructures there are so called 'backupworkers' (VMs) who have plenty of CPU and RAM as well as 'read-only' access to certain filesystems/mounts. They create backups and handle snapshot schedules etc..
One setting allows specifying "Max number of entries loaded at once into memory".
--entries-max <integer> (0 - 9223372036854775807) (default=1048576):Is this related to "Chunk size in KB. Must be a power of 2."?
--chunk-size <integer> (64 - 4096) (default=4096):- But how does one know how much the server can handle?
- How does one calculate the entries-max value?
- So available "RAM / chunk-size = entries-max" ? (Which wouldn't work with the default value on most systems)
- What is the meaning of "entry" (entries) here?
What I am also trying to achieve is a someonewhat interactive UI where support staff is able to check on customer backups and restore certain backups. Is there something on the roadmap that will allow LDAP login to the PBS UI and configure "service desk" roles that can only restore, never delete files?
