RES02-01 Identifying and Backing Up Critical Data That Needs to Be Backed Up

The importance of different data varies. You need to specify the importance of all data in the application system and the corresponding recovery point objective (RPO) and recovery time objective (RTO) requirements. For example, for critical data, the allowed data loss time is short, so the data needs to be backed up more frequently. For general data, the allowed data loss time is relatively long, so the data can be backed up at a low frequency. For non-critical data, the data loss does not affect services, so the data does not need to be backed up.

• Risk level

  High

• Key strategies
  • Identify all data in the application system. Data can be stored in multiple resources, such as volumes of ECSs or BMSs, Relational Database Service (RDS) and Document Database Service (DDS) databases, Scalable File Service (SFS) file systems, and Object Storage Service (OBS).
  • Classify data by importance. In an application system, different types of data vary in importance and backup requirements. For example, critical data requires near-zero RPO, so it needs to be backed up in real time. Non-critical data can tolerate data loss, so backup is not required. Some important data can tolerate different levels of data loss, so it requires tailored backup policies.
  • Design backup solutions for the data to be backed up to meet the RPO and RTO requirements.