Proxmox Backup Server 4.0 released!

It's based on NFS on a Synology NAS.
That's not a good choice for a local cache... i would recommended to use local fast nvme ssds, best with some redundancy for error correction.
 
  • Like
Reactions: Johannes S
Allow me a follow up question regarding the local cache. What kind of data does the cache hold and how long does it cache these files? I see a significant amount of data still stored in that cache. Is there any documentation how the cache is used or for it is used for in detail?

Thanks again for your help.
 
Allow me a follow up question regarding the local cache. What kind of data does the cache hold and how long does it cache these files? I see a significant amount of data still stored in that cache. Is there any documentation how the cache is used or for it is used for in detail?

Thanks again for your help..
The cache stores snapshot metadata such as index file, owner files, ecc. as well as backup data chunks. Chunks are stored in a least recently used cache, evicting older ones if no more slots are available. The cache will use as much storage space as available, therefore the recommendation to use a dedicated disk, partition or dataset with quota. Some more considerations are also to be found in the docs https://pbs.proxmox.com/docs/storage.html#datastores-with-s3-backend
 
  • Like
Reactions: Johannes S
The cache stores snapshot metadata such as index file, owner files, ecc. as well as backup data chunks. Chunks are stored in a least recently used cache, evicting older ones if no more slots are available. The cache will use as much storage space as available, therefore the recommendation to use a dedicated disk, partition or dataset with quota. Some more considerations are also to be found in the docs https://pbs.proxmox.com/docs/storage.html#datastores-with-s3-backend
Thanks again!
 
Is there a recommended size ratio for the s3 cache disk for maximum performance/reduced api calls?

I plan to backup about 4-6TB of VM storage, I assume some de duplication will happen there

So far it seems to be using about 2% of the s3 size
 
the larger backups (600G) are failing still after updating to 4.0.15

Its interesting to note the network graph for the backup server vs smaller backups, only incoming traffic , none out to the s3 based storage

are there any logs I can view to try get a clue - checked the journal log and nothing stands out like the previous vpn network issue (we use wireguard)
 

Attachments

  • Screenshot_20250928_034702.png
    Screenshot_20250928_034702.png
    144.3 KB · Views: 3