-
Notifications
You must be signed in to change notification settings - Fork 3
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
[minor] Setup Db2 Backup job for Disaster recovery scenario and Compliance/SLA #234
Conversation
Issue: MASCORE-3421
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we have to guard some of these calls so that these only run when a) backup is setup i.e. there is a bucket set and b) that we allow external customers to still use this chart to setup db2 for MAS. These customers are unlikely to have ICD and I see a lot of the scripts are calling into ICD as an assumption that it will be present. We either change change scripts to do this as optional, or say this backup process is internal ibm only.
The other thing we need to check is how much of an outage that this would cause if the setup-db2 job is run again (i.e. a change in values or we have a v6 version). I see a number of db2stop calls that would mean an outage when SRE simply update the gitops version. The scripts should ideally only set when things need to be set, and only restart if it is the first time of setup.
Issue: MASCORE-4470
Description
Updates to in Post DB provisioning steps are done except compliance (https://collaborate.mro.com/pages/viewpage.action?spaceKey=MASMS&title=Backup+Configuration+for+AWS)
Details required
Testing
Tested in noble4 ajw0111 instance
Job Execution logs: