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

Show all

Help Center/ Volume Backup Service/ FAQs/ Why Does the Retention Rule Not Take Effect After Being Modified?

Why Does the Retention Rule Not Take Effect After Being Modified?

Updated on 2022-02-22 GMT+08:00

A retention rule does not take effect immediately after being modified in the following scenarios:

  • The retention rule remains to be by backup quantity, with only the configured quantity changed:

    The new retention rule takes effect when the backup policy is executed next time, and the new retention rule still takes effect for the backups generated by the original backup policy.

    For example: At 10:00 a.m. on Monday, a user sets the backup execution time of policy A to 02:00 a.m. every day, sets the rule to retaining three backups, and associates a disk. At 10:00 a.m. on Thursday, three backups are retained. Then the user modifies the retention rule to retaining one backup. However, this retention rule does not take effect immediately. Instead, it retains only the generated backup at 02:00 a.m. on Friday. At then, the three backups generated by the original policy have been deleted.

  • The retention rule is changed from by quantity to by time:

    The new retention rule does not take effect on the backups generated by the original backup policy. The backups generated by the original backup policy will not be automatically deleted.

    For example: At 10:00 a.m. on Monday, a user sets the backup execution time of policy A to 02:00 a.m. every day, sets the rule to retaining three backups, and associates a disk. At 10:00 a.m. on Thursday, three backups are retained. Then the user modifies the retention rule to deleting the backup generated one month ago. At 02:00 a.m. on Friday, the backup generated by the new backup policy is retained and the three backups generated by the original policy still exist.

  • The retention rule remains to be by time period, with only the configured time period changed:

    The new retention rule does not take effect on the backups generated by the original backup policy, but only on the new backups. The backups generated by the original backup policy still follow the original retention rule.

    For example: At 10:00 a.m. on August 5, a user sets the backup execution time of policy A to 02:00 a.m. every day, sets the retention rule to deleting the backup generated one month ago, and associates a disk. At 10:00 a.m. on August 8, three backups are retained. Then the user modifies the retention rule to deleting the backup generated three months ago. At 02:00 on September 6, the backup generated by the original backup policy on August 6 is deleted, and the backup generated on August 9 will be deleted two months later.

  • The retention rule is changed from by time to by quantity.

    The new retention rule does not take effect on the backups generated by the original backup policy, but only on the new backups. The backups generated by the original backup policy still follow the original retention rule.

    For example: At 10:00 a.m. on August 5, a user sets the backup execution time of policy A to 02:00 a.m. every day, sets the retention rule to deleting the backup generated one month ago, and associates a disk. At 10:00 a.m. on August 8, three backups are retained. Then the user modifies the retention rule to retaining one backup. At 10:00 on August 10, the backup generated on August 9 has been deleted and the backup generated on August 10 is retained. However, the backups generated on August 6, 7, and 8 still exist. At 02:00 on September 6, the backup generated on August 6 is 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