Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Creating a Backup Policy

Updated on 2024-04-19 GMT+08:00

A backup policy allows CBR to automatically back up vaults at specified times or intervals. Periodic backups can be used to restore data quickly against data corruption or loss.

To implement periodic backups, you need a backup policy first. You can use the default backup policy or create one as needed.

Constraints

  • Backup policies can be applied to the following types of vaults: server backup vaults, disk backup vaults
  • A backup policy must be enabled before it can be used for periodic backups.
  • A maximum of 32 backup policies can be created in each account.
  • When expired backups are deleted, automatic backups will be deleted, but manual backups will not.
  • Only servers in the Running or Stopped state and disks in the Available or In-use state can be backed up.
  • CBR by default performs a full backup for a resource in the initial backup and incremental backups in all subsequent backups.
  • The minimum interval between two full backups is 1 day.

Procedure

  1. Log in to the CBR console.

    1. Log in to the management console.
    2. Click in the upper left corner and select a region.
    3. Click and choose Storage > Cloud Backup and Recovery.

  2. Choose Policies in the left navigation pane and click the Backup Policies tab. In the upper right corner, click Create Policy.

  3. Set the backup policy parameters. Table 1 describes the parameters.

    Table 1 Backup policy parameters

    Parameter

    Description

    Example Value

    Type

    Select a policy type. In this section, we select the backup policy.

    Backup policy

    Name

    Backup policy name

    A name must contain 1 to 64 characters including digits, letters, underscores (_), or hyphens (-).

    backup_policy

    Status

    Whether to enable the backup policy.

    Only after a backup policy is enabled and applied will CBR automatically backs up the vault resources and deletes expired backups.

    Execution Time

    Execution time

    Backups can be scheduled at the beginning of each hour, and you can select multiple hours.

    NOTICE:
    • There may be a time difference between the scheduled backup time and the actual backup time.
    • If a large amount of data needs to be backed up, you are advised to make backup less frequent to prevent the system from skipping any execution time.

      For example, a disk is scheduled to be backed up at 00:00, 01:00, and 02:00. A backup task starts at 00:00. Because a large amount of incremental data needs to be backed up or a heap of backup tasks are executed at the same time, this backup task takes 90 minutes and completes at 01:30. CBR performs the next backup at 02:00. In this case, only two backups are generated in total, one at 00:00, and the other at 02:00.

    • The execution times refer to the local times of clients, not the time zone and times of the region.

    00:00, 02:00

    • It is recommended that backups be performed during off-peak hours or when no services are running.
    • Peak hours of the backup service are from 00:00 to 06:00, during which there may be scheduling delays. So you are advised to evaluate your service types and schedule backups outside of the backup peak hours.

    Backup Cycle

    Select a backup cycle.

    • Week-based cycle

      Specifies on which days of each week the backup task will be executed. You can select multiple days.

    • Custom cycle

      Specifies the interval (every 1 to 30 days) for executing the backup task.

    Every day

    If you select day-based backup, the first backup is supposed to be executed on the day when the backup policy is created. If the execution time on the day you create the backup policy has passed, the first backup will be executed in the next backup cycle.

    It is recommended that backups be performed during off-peak hours or when no services are running.

    Retention Rule

    Rule that specifies how backups will be retained

    • Time period

      You can choose to retain backups for one month, three months, six months, one year, or for any desired number (2 to 99999) of days.

    • Backup quantity

      You can set the maximum number of backups to retain for each resource. The value ranges from 2 to 99999.

    • Permanent
      NOTE:
      • The system automatically deletes the earliest and expired backups every other day to avoid exceeding the maximum number of backups to retain or retaining any backup longer than the maximum retention period.
      • Expired backups are not deleted right after they are expired. They will be deleted from 12:00 to 00:00 in batches.
      • The retention rules apply only to auto-generated backups, but not manual backups. Manual backups need to be deleted manually.
      • If a backup is used to create an image, the backup will not be deleted by the retention rule.
      • A maximum of 10 backups are retained for failed periodic backup tasks. They are retained for one month and can be deleted manually.

    6 months

    NOTE:

    More frequent backups create more backups or retain backups for a longer time, protecting data to a greater extent but occupying more storage space. Set an appropriate backup frequency as needed.

  4. Click OK.

    NOTE:

    You can locate the desired vault and choose More > Apply Backup Policy to apply the policy to the vault. Then you can view the applied policy on the vault details page. After the policy is applied, data will be periodically backed up to the vault based on the policy.

Example

At 10:00 a.m. on Monday, a user sets a backup policy for their vault to instruct CBR to execute a backup task at 02:00 a.m. every day and retain a maximum of three backups. As of 11:00 a.m. on Saturday, three backups will be retained, which are generated on Thursday, Friday, and Saturday. The backups generated at 02:00 a.m. on Tuesday and Wednesday have been automatically deleted.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback