ishenwei/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update nexus: fix conflicts and sync local changes

Browse Source
This commit is contained in:
Shen Wei
2026-04-26 12:06:50 +08:00
parent 191797c01b
commit f09834b5a5
2443 changed files with 254323 additions and 255154 deletions
Download Patch File Download Diff File Expand all files Collapse all files

102
knowledgebase/csd-wiki/ICSD/ITOM-Cloud-Service-Backup-Integrity-Testing-Plan_686074315.md
View File

@@ -1,51 +1,51 @@
# ITOM-Cloud-Service-Backup-Integrity-Testing-Plan_686074315
## Introduction
This document describes the general backup integrity testing plan to cover ITOM Cloud Deployed Products - ESM, OpsB, NOM, APM.
## Description
- We perform product backup integrity testing testing every 6 months to be compliant with ISO (May/June – localbackup; November/December – remote backup (DR account)
- This activity is business critical and mandatory and required by many regulations and audits.
- Some of our obligations for having the process in place and validated are:
- Ready to use and validated disaster recovery plan in place, which will help us to avoid catastrophic customer data loss (reduce damage or disruption and recover as possible in the
event of a disaster that leads to system failure or in case of customer account theft)
- Business continuity. All relevant teams, including CSD, RnD, other stakeholders will be notified one month before executing this drill
- The backup integrity testing report will be published regluarly basis to Cloud customers to prove DR resolution availbility
## Owner
- Assign an Owner in each Cloud Ops team to be responsible for
- Developing plans
- Updating DR resolution documents
- Overseeing the execution of backup integrity operations
- Publishing backup integrity testing result reports.
## Plan
- Notification to all internal stakeholders about backup integrity testing 1 month before the execution
- Backup integrity testing testing every 6 months to be compliant with ISO
- 1st backup integrity testing - **May/June** – localbackup
- 2nd backup integrity testing - **November/December** – remote backup
## General Procedures
- Data backup validation
- Select 1 non-prod farm/instance in a different region (AWS North Virginia, AWS Ireland,
AWS Sydney, AWS London, AWS Canada)
- There are some places where the customer data may be located:
- AWS RDS
- AWS EFS
- AWS EBS
- EKS K8S Configuration (Velero)
- EC2 Instances
- Need to be checked if there is back up data for all relevant components, if not please ensure
the backup mechanism is in place
- Perform Data Restore
- Select a specific set of backup data (with the same timestamp) for data recovery
- Record the approximate steps of the entire data recovery and how long it took
- Validate restored farm/instance
- We're leverage APM service availbility check and AWS Sythetics Check to validate success of data restore
- Confirm all major functionalities are working as expected
- Prepare backup integrity testing report
- Please refer to the attached document format to prepare the DR validation testing report. [ESM DR Validation Report - May 2023.docx](#)
# ITOM-Cloud-Service-Backup-Integrity-Testing-Plan_686074315
## Introduction
This document describes the general backup integrity testing plan to cover ITOM Cloud Deployed Products - ESM, OpsB, NOM, APM.
## Description
- We perform product backup integrity testing testing every 6 months to be compliant with ISO (May/June – localbackup; November/December – remote backup (DR account)
- This activity is business critical and mandatory and required by many regulations and audits.
- Some of our obligations for having the process in place and validated are:
- Ready to use and validated disaster recovery plan in place, which will help us to avoid catastrophic customer data loss (reduce damage or disruption and recover as possible in the
event of a disaster that leads to system failure or in case of customer account theft)
- Business continuity. All relevant teams, including CSD, RnD, other stakeholders will be notified one month before executing this drill
- The backup integrity testing report will be published regluarly basis to Cloud customers to prove DR resolution availbility
## Owner
- Assign an Owner in each Cloud Ops team to be responsible for
- Developing plans
- Updating DR resolution documents
- Overseeing the execution of backup integrity operations
- Publishing backup integrity testing result reports.
## Plan
- Notification to all internal stakeholders about backup integrity testing 1 month before the execution
- Backup integrity testing testing every 6 months to be compliant with ISO
- 1st backup integrity testing - **May/June** – localbackup
- 2nd backup integrity testing - **November/December** – remote backup
## General Procedures
- Data backup validation
- Select 1 non-prod farm/instance in a different region (AWS North Virginia, AWS Ireland,
AWS Sydney, AWS London, AWS Canada)
- There are some places where the customer data may be located:
- AWS RDS
- AWS EFS
- AWS EBS
- EKS K8S Configuration (Velero)
- EC2 Instances
- Need to be checked if there is back up data for all relevant components, if not please ensure
the backup mechanism is in place
- Perform Data Restore
- Select a specific set of backup data (with the same timestamp) for data recovery
- Record the approximate steps of the entire data recovery and how long it took
- Validate restored farm/instance
- We're leverage APM service availbility check and AWS Sythetics Check to validate success of data restore
- Confirm all major functionalities are working as expected
- Prepare backup integrity testing report
- Please refer to the attached document format to prepare the DR validation testing report. [ESM DR Validation Report - May 2023.docx](#)