Beta state

[rolandf]

Hello,
I've seen that this project is in beta and not recommended for production yet.
I would like to know if someone already lost data with it or if you are over cautious but using it in prod is fine ?
Otherwise what are you using it for if not for backing up data ? You use it to test it and use something else for real backups waiting for rustic to stabilize ? If this is the case what would you recommend ?

Best regards,
Frederic

[aawsome]

Hi @rolandf

There are open points we want to fix before stating that we are production ready. This mainly a better unit test coverage (to ensure that future refactoring won't break things) and better error handling (to ensure that rustic doesn't abort in error cases but is able to report this to callers/schedulers allowing to handle the error situation).

I don't have knowledge about someone losing data due to a bug in rustic, but there has been problems with "wrong usage" (e.g. unsound usage of prune --instant-delete) , i.e. documentation is also something to work on.

I myself and others use it for (real) backups. If you use it, there are 2 recommendations (which basically hold for every backup tool you are using):

• Always and regularly do restore tests to ensure you really can restore in emergency cases!
• Don't rely just on a single tool, better to use multiple tools for multiple backups.

Additionally, rustic-specific:

• As the repo format is compatible with restic, you can use it to check your repository.

[rolandf]

Thank you