docs: db data must be deleted before restoring backup #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nvdk
reviewed
Nov 26, 2024
| Backups can be restored either in the running container, or through an environment variable. The existing database data must be removed before restoring a backup. You can do this using the following command: | ||
|
|
||
| ```sh | ||
| rm data/db/virtuoso.{db,trx,pxa} data/db/virtuoso-temp.db data/db/.data_loaded data/db/.dba_pwd_set data/db/.backup_restored |
There was a problem hiding this comment.
I'm not sure about removing .data_loaded. By removing it, we will try loading it again after restoring the database.
This may or may not be what you want. It will result in loading any file in toLoad that does not have an entry with status 2 (loaded) in select * from DB.DBA.load_list;
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Otherwise, Virtuoso logs:
Although the message should be clear to the user as to what they are required to do, mentioning it specifically in the README might be useful for anyone restoring a backup for the first time (perhaps in a more stressful setting where seeing unexpected logs is the last thing they want to see).