Creating Backup Policies Based on Service Tiering

Background

Resource backup policies define the backup frequency and retention rules. In practice, you need to configure different data backup policies based on the importance of data and the tiers of service systems deployed on the cloud.

Resource Planning and Costs

**Table 1** Resource planning and costs
Resource	Description	Quantity	Monthly Price
Backup vault	After a backup policy is created, you need to apply the policy to a vault to perform periodic backups.	1	For detailed billing modes and billing standards, see Billing.

Service Tiering

Based on the importance of service systems and the impact scope and degree of the service system interruption on the company's services, service systems can be classified into the following types:

Core system
1. Core systems that run a company's core business processes, such as purchase systems. If such systems are stopped, the company's operations will be severely affected or significant financial losses will be incurred.
2. Important infrastructure and office systems that support the company's critical applications. If such systems are interrupted, a large number of employees' work will be affected.
Important system
1. Important systems that run a company's crucial business processes. If such systems are stopped, the company's operations will be greatly affected or major financial losses will be incurred.
2. Infrastructure and office systems that support the company's important applications. If such systems are interrupted, employees' work will be severely affected.
General system
1. General systems that run a company's business processes, such as training systems. If such systems are stopped, the company's operations will be affected or financial losses will be incurred.
2. Infrastructure and office systems that support the company's general systems. If such systems are interrupted, employees' work will be affected.

Normally, data levels can be evaluated based on the impact of service systems. Core data corresponds to core systems, important data corresponds to important systems, and general data corresponds to general systems. If the data level and service system level do not match, determine the service system level based on the data level. For example, if a service system is evaluated as an important system, but its data is considered as the core data, then the service system should be considered as a core system.

Backup and DR Policies

You are advised to configure different data backup policies based on service system levels. The following table shows the commonly used backup policies for cloud resources. You can adjust the policies based on service requirements. For details, see Creating a Backup Policy.

System Level	Backup Object	RPO	Retained Duration	Full Backup	Incremental Backup	Remote Backup	Drill Frequency
Core system	Cloud server	4 hours	> 1 year	Weekly	6 times/day	Yes	Monthly
	Cloud database	4 hours	> 1 year	Weekly	6 times/day	Yes	Monthly
	SFS Turbo file system	4 hours	> 1 year	Weekly	6 times/day	Yes	Monthly
Important system	Cloud server	12 hours	1 year	Every two weeks	2 times/day	Yes	Quarterly
	Cloud database	12 hours	1 year	Every two weeks	2 times/day	Yes	Quarterly
	SFS Turbo file system	12 hours	1 year	Every two weeks	2 times/day	Yes	Quarterly
General system	Cloud server	24 hours	6 months	Monthly	1 time/day	No	Half a year
	Cloud database	24 hours	6 months	Monthly	1 time/day	No	Half a year
	SFS Turbo file system	24 hours	6 months	Monthly	1 time/day	No	Half a year