DB restore #111

New Issue

OVERLORD · 2026-02-04T17:02:15+03:00

OVERLORD commented

2026-02-04 17:02:15 +03:00

Originally created by @Biepa on GitHub (Oct 15, 2018).

Hello together,
I am using the command in the documentation to backup the db.
sqlite3 /$DATA_FOLDER/db.sqlite3 ".backup '/$DATA_FOLDER/db-backup/backup.sq3'"

Unfortunately my knowledge about databases is very limited.
How do I restore a backup.sq3 file?

Tried it with...
sqlite3 db.sqlite3 < backup.sq3
but getting a "syntax error".

Is that because of the different endings?

Originally created by @Biepa on GitHub (Oct 15, 2018). Hello together, I am using the command in the documentation to backup the db. `sqlite3 /$DATA_FOLDER/db.sqlite3 ".backup '/$DATA_FOLDER/db-backup/backup.sq3'"` Unfortunately my knowledge about databases is very limited. How do I restore a backup.sq3 file? Tried it with... `sqlite3 db.sqlite3 < backup.sq3` but getting a "syntax error". Is that because of the different endings?

OVERLORD added the documentation question labels 2026-02-04 17:02:15 +03:00

OVERLORD closed this issue

2026-02-04 17:02:23 +03:00

OVERLORD commented

2026-02-04 17:02:26 +03:00

@dani-garcia commented on GitHub (Oct 15, 2018):

The backup should be a simple copy of the original database, I think. I'm not sure why we are using different extensions, that seems confusing.

Simply replace the db.sqlite3 file with the backup to restore it (This probably needs to be done when bitwarden_rs is stopped)

@dani-garcia commented on GitHub (Oct 15, 2018): The backup should be a simple copy of the original database, I think. I'm not sure why we are using different extensions, that seems confusing. Simply replace the `db.sqlite3` file with the backup to restore it (This probably needs to be done when bitwarden_rs is stopped)

OVERLORD commented

2026-02-04 17:02:35 +03:00

@Biepa commented on GitHub (Oct 15, 2018):

A simple copy with stopped container worked without problems. Thank you for the quick answer.

@Biepa commented on GitHub (Oct 15, 2018): A simple copy with stopped container worked without problems. Thank you for the quick answer.

OVERLORD commented

2026-02-04 17:02:46 +03:00

@mprasil commented on GitHub (Oct 15, 2018):

Agreed, I think we should also add restore information. I guess @Biepa was trying to approach this as restore from dump as it's more common with MySQL/Postgres? So maybe we need to be more specific that .backup command does consistent copy of the binary database and it's not the same as .dump which is probably what @Biepa was expecting.

@mprasil commented on GitHub (Oct 15, 2018): Agreed, I think we should also add restore information. I guess @Biepa was trying to approach this as restore from dump as it's more common with MySQL/Postgres? So maybe we need to be more specific that `.backup` command does consistent copy of the binary database and it's not the same as `.dump` which is probably what @Biepa was expecting.

OVERLORD commented

2026-02-04 17:02:53 +03:00

@Biepa commented on GitHub (Oct 15, 2018):

@mprasil You're right. That was, what I expected.
And if there isn't a need for the different endings, maybe that could also be changed in the documentation as it confused me a bit.

@Biepa commented on GitHub (Oct 15, 2018): @mprasil You're right. That was, what I expected. And if there isn't a need for the different endings, maybe that could also be changed in the documentation as it confused me a bit.

OVERLORD commented

2026-02-04 17:03:01 +03:00

@dani-garcia commented on GitHub (Oct 15, 2018):

The documentation is updated now with #224

@dani-garcia commented on GitHub (Oct 15, 2018): The documentation is updated now with #224

OVERLORD referenced this issue

2026-02-05 04:49:01 +03:00

[PR #111] [MERGED] Implemented PUT for single cipher sharing (#97) #2584

Sign in to join this conversation.