mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #938] Backing up database #666
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#666
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @danielrlutz on GitHub (Mar 30, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/938
Hey there!
I'm really enjoying bitwarden_rs but I've come to my end of understanding. Which directory/file is necessary for saving the client's values? Is it possible to replace it and it is all going to work again?
Regards,
Daniel
@dani-garcia commented on GitHub (Mar 30, 2020):
There's a pretty good description in the wiki: https://github.com/dani-garcia/bitwarden_rs/wiki/Backing-up-your-vault
It mentions backing up the database with the sqlite command, but you can also copy the files like normal as long as the server is stopped before.
@danielrlutz commented on GitHub (Mar 30, 2020):
"The files"? Which one would that be? I tried to replace the db.sqlite3 from another database but the client data wasn't there.
@dennisgerding commented on GitHub (Mar 31, 2020):
I use a small script for backing up my vault. It could be easy for you.
@danielrlutz commented on GitHub (Mar 31, 2020):
Oh, this looks very useful, thanks!
May I ask why you remove the zip file in the end? Isn't that the final backup?
Also, why do you use a random variable? Is it common to use that for temporary directories?
@dennisgerding commented on GitHub (Mar 31, 2020):
I remove the zipfile because I mail it to myself (my vault is really small in size). I also had some issues in my mail client making a thread of all the mails, adding a random string in it stopped my mail client from making a thread of it all.
As side effect a random string also makes it possible to back up multiple times a day, however also the time could be used for that.
Edit: I also could figure out how to configure that folder in my mail client properly but I'm lazy.
@danielrlutz commented on GitHub (Mar 31, 2020):
Hmm.. so that's still secure because the database's content is encrypted with the master password by the individual users, right?
@dennisgerding commented on GitHub (Mar 31, 2020):
Yes I believe so.
@danielrlutz commented on GitHub (Mar 31, 2020):
Ok, thanks for your help :)
Oh, ehm.. how do you recover from a backup?
@dennisgerding commented on GitHub (Mar 31, 2020):
In my case I just untar the archive and run
docker-compose up -d. That is (for me) possible since it holds the config file, database, attachments and thedocker-compose.ymlfile. Docker will pull the images.