Catalogue is outgrowing the storage node

Hello - a new week a new oddity.

How big is a Catalogue on a Storage node supposed to be?

I'm asking because mine seems to try to outgrow the backup data. It's now 26GB large (6.2G DB3 file and 19.9G for the WAL file). Odd because the Node is just trying to delete some backups from the catalogue - but that only makes it grow by 6GB every 3 hours.

I read that when you use WAL on SQLite you're supposed to checkpoint from time to time. I'll go to bed now - let's see if there storage node is crashed again tomorrow morning because it'll certainly run out of space by then.

Is anybody using the storage node in production? With Deduplication even? How many Computers do you backup? How many backups can it handle and stay stable? I have 10 PCs on the node with 500GB of raw (deduped) data and my storage node needs babysitting every single day. (And another one has already gone FUBAR with all the data lost)