Backup Restic password store

Backup password stored in user profile. How restore data when server totaly broken ?

from documentation: Backup & Restore | Hestia Control Panel

::warning A new restic repository is initiated on the first time you run this command. An encryption key is generated at the same time in /usr/local/hestia/data/users/{users}/restic.conf. Please make sure to backup this file somewhere incase the server gets comprimised or the user gets deleted. Without this “secret” key we don’t provide any method to restore the user data. This is the reason why we alway advice to keep the orignal backup still working.

So technically if you do a complete re install and have the same configuration as before then just re-copy the old key to that file again. and go to the dashboard to pull the backup again. I didn’t test this but I think it should work

1 Like

umm I think you shouldn’t mark this as solution as I said I didn’t test this I would like to know what others know or have tried.

That is the currently the best solution.

Personally I suggest keep at least 1 backup active every week

restic repo can be used without encryption with --insecure-no-password param, so if we use at least 1 regular backup without any encryption there is no reason to use it on restic repo (it can be optional to use encryption while admin configuring backup)

The encryption feature is unnecessary for most of us. it should be an opt-in option in the incremental-update dashboard settings

Had a lot of issues to get it working without it…

possibly due to it requirement to add --insecure-no-password to each command when working with repo. If yes, maybe it will be better to hardcode this param to each command instead of key