41 backup and disaster recovery concept - #43
Open
hanswizzy wants to merge 8 commits into
Open
Conversation
hanswizzy
requested review from
Arielpetit,
Koufan-De-King,
NkwaTambe,
stephane-segning and
yvanhenang
January 15, 2025 07:40
stephane-segning
requested changes
Jan 27, 2025
stephane-segning
left a comment
stephane-segning
left a comment
Contributor
There was a problem hiding this comment.
Hmm I read it all, but I cannot see your Backup strategy. This looks like a very good Backup Strategy list. But which one are you people using?
…ackup-and-disaster-recovery-concept
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
4 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.
Description
Title:
Document Disaster Recovery & Backup Strategy Including RTO/RPO Metrics
Description:
As part of improving our resilience and compliance with banking service SLAs, we have created a comprehensive Disaster Recovery & Backup Strategy document that outlines:
Protection mechanisms for key components:
Clear RTO (≤ 2 hours) and RPO (≤ 15 minutes) targets for core banking services
Step-by-step recovery scenarios for:
Security controls including encryption, access management, and OIDC integration
Tools used and their configuration references
This document ensures that the team is aligned on how to restore services within defined SLAs and provides actionable steps for incident response.
Acceptance Criteria:
Related Files:
docs/disaster-recovery-strategy.mdterraform/charts/deploy/dev/webank.yamldocs/Provisioning_k8s_PostgreSQL.mddocs/argocd-deployment-guide.md