Hi there,
just a quick tip. We are using disk-based PBS-Servers where SSDs are not used.
If you are using mostly rotating hard disks with PBS and you get timeouts when listing Backups in PVE you can change Directory/File-Cache-Setting to keep the file and directory Metadata in RAM.
This is done just by adjusting "vm.vfs_cache_pressure" in sysconf or during runtime "sysctl vm.vfs_cache_pressure=10". You need to have enough ram to keep your directory/file inodes in RAM. (Example here about 5000 backups and 32GB RAM in Server with XFS is enough)
This setting will also boost Garbage Collection runtime a lot.
With "find /mnt/datastore/ -ls > /dev/null" in Shell/Terminal you can "preload" the structure or just wait until the Server has loaded it in Cache/RAM when selecting Backupstore in PVE....
This does not mean you should not use SSDs in your PBS, but not everyone has that value to spend. Often Backupservers are created from "old" Systems which are replaced by newer ones.... ;-)
just a quick tip. We are using disk-based PBS-Servers where SSDs are not used.
If you are using mostly rotating hard disks with PBS and you get timeouts when listing Backups in PVE you can change Directory/File-Cache-Setting to keep the file and directory Metadata in RAM.
This is done just by adjusting "vm.vfs_cache_pressure" in sysconf or during runtime "sysctl vm.vfs_cache_pressure=10". You need to have enough ram to keep your directory/file inodes in RAM. (Example here about 5000 backups and 32GB RAM in Server with XFS is enough)
This setting will also boost Garbage Collection runtime a lot.
With "find /mnt/datastore/ -ls > /dev/null" in Shell/Terminal you can "preload" the structure or just wait until the Server has loaded it in Cache/RAM when selecting Backupstore in PVE....
This does not mean you should not use SSDs in your PBS, but not everyone has that value to spend. Often Backupservers are created from "old" Systems which are replaced by newer ones.... ;-)
Last edited: