Issue 6386 - backup/restore broken after db log rotation#6406
Merged
Conversation
progier389
force-pushed
the
i6386
branch
2 times, most recently
from
e1e96b9 to
d0334ed
Compare
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
progier389
added a commit
that referenced
this pull request
Jan 14, 2025
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database. Solution is to remove all existing log files before copying the backuped files. Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed. Issue: #6386 Reviewed by: @mreynolds389, @tbordaz (Thanks!) (cherry picked from commit a48be7b) (cherry picked from commit 0c8829b)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Restore does fail if the db log file have rotated since the backup. The reason is that the current log files are not removed mixing old and new log file which confuse the database.
Solution is to remove all existing log files before copying the backuped files.
Note: the number of db region should not change and having an extra db file should not be a problem so only the log files must be removed.
Issue: #6386
Reviewed by: @mreynolds389, @tbordaz (Thanks!)