We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As Ashton I want to be able to backup SonarQube safely so that I can restore it easily in the event of a disaster.
We should identify and select solutions that are able to backup the SonarQube database, and then follows the recommendations for restoration:
https://docs.sonarsource.com/sonarqube/9.6/instance-administration/backup-and-restore/
These should be written in a simple ADR to capture why the final solution was chosen and a follow on implementation issue should be created.
We currently don't have set SLAs but should target a baseline to have something while we continue to experiment.
The text was updated successfully, but these errors were encountered:
https://docs.sonarsource.com/sonarqube/latest/instance-administration/backup-and-restore/
In the absence of more specific guidance, use normal rds backup/restore practices
Sorry, something went wrong.
No branches or pull requests
Is your feature request related to a problem? Please describe.
As Ashton I want to be able to backup SonarQube safely so that I can restore it easily in the event of a disaster.
Describe the solution you'd like
We should identify and select solutions that are able to backup the SonarQube database, and then follows the recommendations for restoration:
https://docs.sonarsource.com/sonarqube/9.6/instance-administration/backup-and-restore/
These should be written in a simple ADR to capture why the final solution was chosen and a follow on implementation issue should be created.
Additional context
We currently don't have set SLAs but should target a baseline to have something while we continue to experiment.
The text was updated successfully, but these errors were encountered: