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

Show all

Configuring an Automated Snapshot Policy

Updated on 2022-08-16 GMT+08:00

You can select a snapshot type and set one or more automated snapshot policies for a cluster. After an automated snapshot policy is enabled, the system automatically creates snapshots based on the preset time, period, and snapshot type according to the policy.

Perform the following steps to configure an automated snapshot policy.

Procedure

  1. Log in to the GaussDB(DWS) management console.
  2. In the navigation pane on the left, choose Clusters.
  3. Click the name of a cluster.
  4. Click the Snapshots tab page and click Policy List. All the policies of the current cluster are displayed on the Policy List page. Toggle on Snapshot Policy.

    • indicates that the policy is enabled (default). The default retention period is three days.
    • indicates that the policy is disabled. If this policy is disabled, historical automated snapshots will be automatically deleted.
    Figure 1 Policy list

  5. After this function is enabled, you can set the retention mode for automated snapshots. For more information, see Table 1.

    Table 1 Automated snapshot parameters

    Parameter

    Description

    Retention Days

    Retention days of the snapshots that are automatically created. The value ranges from 1 to 31 days.

    NOTE:

    Snapshots that are automatically created cannot be deleted manually. The system automatically deletes these snapshots when their retention duration exceeds the threshold.

  6. After automated snapshot is enabled, you can configure its parameters. For more information, see Table 2.

    NOTE:

    The snapshot creation time is UTC, which may be different from your local time.

    • If the snapshot type is set to Full, you can choose either Periodic or One-time, as shown in the following figures.
      • Periodic: Specify the days for every week/month and the exact time on the days.

      • One-time: Specify a day and the exact time on the day.

    • Incremental snapshots can be set only to Periodic, as shown in the first figure below.
      • When configuring a periodic incremental snapshot policy, you can specify the days for every week/month and the exact time on the days. You can also specify the start time and interval for the snapshots.

      WARNING:

      Choosing the days in red (29/30/31) may skip some monthly backups.

    Table 2 Parameter description

    Parameter

    Description

    Name

    The policy name must be unique, consist of 4 to 92 characters, and start with a letter. It is case-insensitive and can contain only letters, digits, hyphens (-), and underscores (_).

    Type

    You can choose either full or incremental snapshots.

    Policy

    You can choose either periodic or one-time snapshots.

    NOTE:

    You can select One-off Snapshot only when Snapshot Type is set to Full.

    One-time

    You can create a full snapshot at a specified time in the future. The UTC time is used.

    Periodic Policy Configurations

    You can create automated snapshots on a daily, weekly, or monthly basis:

    • Days: Specify days for every week or every month. Weekly and Monthly cannot be selected at the same time. For Monthly, the specified days are applicable only to months that contain the dates. For example, if you select 29, no automated snapshot will be created on February, 2022.
    • Time: Specify the exact time on the selected days. For incremental snapshots, you can specify the start time and interval. The interval can be 4 to 24 hours, indicating that a snapshot is created at an interval of 4 to 24 hours.
    NOTICE:

    If the incremental data is large and the execution period is long, the backup will be slow. In this case, increase the backup frequency.

  7. Click OK.

    NOTE:

    A maximum of three snapshot policies can be set for a cluster.

  8. (Optional) To modify an automated snapshot policy, click Modify in the Operation column.

  9. (Optional) To preview a policy, click Preview Policy. The next seven snapshots of the cluster will be displayed. If no full snapshot policy is configured for the cluster, the default policy is used, that is, a full snapshot is taken after every 14 incremental snapshots.

    NOTICE:

    Implementation of the same policy varies according to operations in the cluster. For example:

    • The policy preview time is for your reference only. The cluster triggers a snapshot within one hour before or after the preset time.
    • The next automated snapshots after cluster scale-out, upgrade, resize, and media modification are full snapshots by default.
    • If a periodic policy is used for a cluster, no automated backup is allowed within 4 hours after the last automated snapshot is complete.
    • If the snapshot start time of multiple policies conflicts, the priorities of the policies are as follows: one-time > periodic > full > incremental.
    • You can use any backup, full or incremental, to restore the full data of a resource.

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