adding backup procedure #67
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mmorency2021 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
needs-ok-to-test
|
Hi @mmorency2021. Thanks for your PR. I'm waiting for a openshift-kni member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
|
||
| ### Purpose | ||
|
|
||
| The purpose of this procedure is to show how to backup the Hub cluster CRs and Recover in case of failure. It can either be in an active-passive Architecture or just a simple hub. |
There was a problem hiding this comment.
| The purpose of this procedure is to show how to backup the Hub cluster CRs and Recover in case of failure. It can either be in an active-passive Architecture or just a simple hub. | |
| The purpose of this procedure is to show how to backup the Hub cluster CRs and Recover in case of failure. It can either be in an active-passive Architecture or just a simple hub. |
|
|
||
| ### Backup Process | ||
|
|
||
| #### 1- Create OBC and get the secret Information |
There was a problem hiding this comment.
| #### 1- Create OBC and get the secret Information | |
| #### 1- Create OBC and get the secret Information |
| name: default | ||
| namespace: namespace: open-cluster-management-backup |
|
|
||
| ### Before creating the backup ensure that all BMH are labeled correctly to avoid issue when restoration is done | ||
|
|
||
| ```yaml |
There was a problem hiding this comment.
This policy is also included as a yaml file below. Rather than duplicating the content can you just point to/reference the included yaml. This helps ensure that we don't have content that is out of sync as we make updates/fixes.
Same comment for other CRs in this readme.
| name: schedule-drtest | ||
| namespace: open-cluster-management-backup | ||
| spec: | ||
| veleroSchedule: "0 */2 * * *" #backup set every 5 mns |
There was a problem hiding this comment.
Isn't this every 30 minutes?
There was a problem hiding this comment.
my mistake , it is every 2 hours indeed.
|
@mmorency2021: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
backup procedure
All CRs needed for the backup procedure have been added.