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

Creating an Organizational Backup Policy

Updated on 2025-01-17 GMT+08:00

An enterprise can use an organization's management account to configure organizational backup policies for all the member accounts in the organization. All member accounts in the organization can use the created organizational backup policies.

This section describes how to create an organizational backup policy.

Constraints

  • Backup policies can be applied to the following types of vaults: server backup vaults, disk backup vaults, SFS Turbo 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 a backup time and a replication time are both configured, ensure that replication starts after backup is complete. Or, replication may fail.
  • 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 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. Select a backup type from the left navigation pane.

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

    Figure 1 Create Organizational Policy

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

    Table 1 Backup policy parameters

    Parameter

    Description

    Example Value

    Organizational Policy Name

    Organizational policy name

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

    org_policy

    Organizational Policy Description

    Description that can help the organization members to understand the usage of the policy.

    /

    Organizational Policy Type

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

    Backup policy

    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.

    Backup Frequency

    Select a backup frequency.

    • Weekly

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

    • Day based

      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 service off-peak hours or when no services are running.

    Execution Time

    Execution times of the backup policy in a day

    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 service 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.

    Full Backup

    Whether to perform periodic full backups.

    • Enable

      Enabling full backup improves your data reliability, but full backups will use more storage space.

      Configure a full backup frequency. The value ranges from 0 to 100. Value 0 means that a full backup will be performed in every backup task.

    • Do not enable

      Periodic full backup will not be performed. Instead, CBR will always perform incremental backups after the first backup.

      NOTICE:
      • A full backup usually takes a long period of time. If a full backup of a resource is in progress, other backups of this resource will not be performed. For example, any policy-based backups planned to be executed during a full backup will be skipped.
      • When backups are kept by quantity, full backups can be performed only when the full backup frequency configured is less than the number of retained backups.

    7

    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.

    • Advanced Options

      You can also set long-term retention rules with advanced options. Long-term retention rules and quantity-based retention rules will be both applied.

      • Day-based: 0–100
      • Weekly: 0–100
      • Monthly: 0–100
      • Yearly: 0–100

      A resource may be backed up multiple times in a day. If day-based backup is configured, only the most recent backup of that day is retained. If you set Day-based to 5, the most recent backup of each of the last five days that have backups generated will be retained and the earliest backups will be deleted automatically. If day-based, weekly, monthly, and yearly retention rules are all configured, all the rules will apply and the union set of backups will be retained. For example, if Day-based is set to 5 and Weekly to 1, five backups will be retained. The long-term retention rule and the quantity-based retention rule both apply.

    • 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 Create Now.

    NOTE:

    After the backup policy is created, it will automatically appear in each member account's policy list.

Follow-Up Operations

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