New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore database and leave it in single user shutdown state [CORE5571] #5838
Comments
Commented by: @AlexPeshkoff In some cases (for example, when index participating in FK fails to activate) this is already done. I.e. I agree that leaving DB in maintenance mode is good idea, the question is - after what errors this does not happen? |
Commented by: @aafemt Without any error. A new option for the service: leave the database down even on success. |
Commented by: Sean Leyne (seanleyne) Why is a new option required? When user can restore to a different filename/location to perform any additional steps, then rename the file when ready for production use. |
Commented by: @aafemt You can restore database onto remote server. You cannot rename files on remote server using Firebird services. |
Commented by: @asfernandes A "single user maintenance mode" won't let others connect before you and leave you locked? |
Commented by: @aafemt IIRC, only SYSDBA and database owner can connect to a database in this mode. Exactly because of this this mode is set for the database during restore process. |
Submitted by: @aafemt
Database recovery isn't always complete after backup restore. In some cases it needs some additional steps. To prevent users from accessing database during these steps, it would be good to have a gbak/services option to leave the database in single user maintenance mode after restore.
The text was updated successfully, but these errors were encountered: