[Feature] restore backup without creating a "current" backup #29843
Replies: 4 comments 1 reply
|
How long is the backup taking for you? The disk space used should be negligible. The reason it works this way is safety, so you can never accidentally lose a good database by restoring over it. |
|
in case of current backup corruption the backup creation process halts the restore. |
|
I get the same error when restoring an backup: |
|
command to restore the backup manually.
|
Uh oh!
There was an error while loading. Please reload this page.
I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.
The feature
Currently, if you restore a backup, it will first make a backup of the current state of the database.
That's really annoying because the main point of restoring a backup is that your current database is screwed up.
I don't need to waste time or disk space making a backup of a database which is screwed up due to my accidentally deleting something/running a job with settings that turned out bad/etc.
I understand the idea of making a backup first before restoring but it really should be optional.
Platform
All reactions