I want Best Practices for Managing Large Backup Repositories?

Hey everyone,

I have been using Restic for a while now & I have to say; it is been an absolute lifesaver for handling backups. I am facing issu as my backup repositories are getting pretty large & I wanted to get advice from the community.

What are some best practices for managing large repositories? Are there any specific tips for keeping performance smooth and avoiding unnecessary bloat?? I do regular prunes & forget commands but I want to know if there are other optimizations I should consider. Also; is there a suggestion way to structure backups when dealing with multiple machines? Should I keep everything in one big repo or split them into separate ones?

I was looking at some python interview questions & it got me thinking about automation—are there any scripts or automated processes that could help manage Restic backups more efficiently?

Also i have check Best practice - single or multiple restic backup commands? & want to hear how you all handle large-scale backups and any lessons learned along the way. Any advice, scripts, or workflows you swear by?

Thank you… :blush:

1 Like

Honestly, at the end of the day… either split your repositories up, or buy more RAM lol

3 Likes

Quite an ecosystem has developed over the years to adapt, enhance and scale restic.

Some quick suggestions.

Resticprofile is a favourite of mine. You will find it with a google search pretty easily.

In terms of large repos, the trade off is between deduplication, and hardware capacity to maintain the index in RAM while performing operations.

For maintenance, and without knowing what backend you use, running the check command routinely is wise to ensure integrity of your backups. By default, it will just check the metadata of your repo so that it knows where everything is internally. With the --check-data option, you can verify the integrity of your actual data. You will have to consider the bandwidth costs against the confidence in the integrity of your backups. If local storage, then bandwidth cost is not a concern.

Finally, just scan the forums. This is a vibrant community with lots of existing information.

Damo.

1 Like