- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API Description
-
VBS Backups
- Creating a VBS Backup
- Deleting a VBS Backup (Deprecated)
- Restoring a Disk Using a VBS Backup
- Creating a VBS Backup (Native OpenStack API) (Deprecated)
- Querying Summary Information About VBS Backups (Native OpenStack API) (Deprecated)
- Querying Details About VBS Backups (Native OpenStack API) (Deprecated)
- Querying Details About a VBS Backup (Native OpenStack API) (Deprecated)
- Querying the Job Status
- Deleting a VBS Backup (Native OpenStack API) (Deprecated)
- Restoring a Disk Using a VBS Backup (Native OpenStack API) (Deprecated)
- Sharing a Backup
- Canceling Sharing of a Backup
- Querying Backup Sharings
- Counting Backup Sharings
- Querying Details About a Backup Sharing
-
Backup Policies
- Creating a Backup Policy
- Querying Backup Policies
- Modifying a Backup Policy
- Deleting a Backup Policy
- Associating Resources with a Backup Policy
- Disassociating Resources from a Backup Policy
- Executing a Backup Policy At Once
- Enabling or Disabling a Backup Policy
- Querying Backup Jobs Triggered by a Backup Policy
- Adding a Tag to a Backup Policy
- Removing a Tag from a Backup Policy
- Querying All Backup Policy Tags
- Querying Tags of a Backup Policy
- Batch Updating or Removing Tags of a Backup Policy
- Querying Backup Policies by Tag
-
VBS Backups
- Permissions Policies and Supported Actions
- Appendix
-
FAQs
- What Is Volume Backup Service?
- What Is a Backup Policy?
- What Are the Differences Between Backup and Disaster Recovery?
- How Do I Purchase and Renew VBS?
- What Are the Differences Between CSBS and VBS?
- Does VBS Support Simultaneous Backup of All EVS Disks on a Server?
- Do I Need to Stop the Server Before Backing Up EVS Disks on a Server Using VBS?
- How Long Does VBS Take to Back Up an EVS Disk?
- Does VBS Support Cross-Region Backup and Restoration?
- Do I Need to Stop the Server Before Restoring EVS Disk Data with a VBS Backup?
- What Is the Charging Mode of EVS Disks Created with a VBS Backup?
- Why Are CSBS Backups Displayed on the VBS Backup Page?
- Can a VBS Backup of a System Disk Be Used to Restore the System Disk of an ECS?
- Can I Use a VBS Backup to Restore an EVS Disk Whose Capacity Has Been Expanded?
- Is There a Quota Limit on the Number of Backups?
- What Can I Do In Case of Exceptions in VBS?
- Why Add Tags to a VBS Backup or Backup Policy?
- Does Backup Can Be Performed Several Times a Day?
- Can a Disk Only Be Associated With One Policy?
- What Are Full Backup and Incremental Backup?
- What Are the Differences Between Backups and Snapshots?
- Why Is the Remaining Space Not Changed After a Backup Is Deleted?
- Why Is the Disk Space Usage Displayed in the File System Different from the Backup Size?
- Why Does the Retention Rule Not Take Effect After Being Modified?
- How Do I Disable Automatic Backup?
- Videos
- Glossary
-
More Documents
-
User Guide (Paris)
- Service Overview
- Getting Started
- Operation Guide
-
FAQs
- Does VBS Support Simultaneous Backup of All EVS Disks on a Server?
- Do I Need to Stop the Server Before Backing Up EVS Disks on a Server Using VBS?
- Does VBS Support Cross-Region Backup and Restoration?
- Do I Need to Stop the Server Before Restoring EVS Disk Data with a VBS Backup?
- What Is the Charging Mode of EVS Disks Created with a VBS Backup?
- Why Are CSBS Backups Displayed on the VBS Backup Page?
- Can a VBS Backup of a System Disk Be Used to Restore the System Disk of an ECS?
- Can I Use a VBS Backup to Restore an EVS Disk Whose Capacity Has Been Expanded?
- Is There a Quota Limit on the Number of Backups?
- What Can I Do In Case of Exceptions in VBS?
- Can a Disk Only Be Associated With One Policy?
- What Are Full Backup and Incremental Backup?
- What Are the Differences Between Backups and Snapshots?
- Why Is the Remaining Space Not Changed After a Backup Is Deleted?
- Troubleshooting Cases
- Change History
-
API Reference (Paris)
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
API Description
-
VBS Backups
- Creating a VBS Backup
- Deleting a VBS Backup (Deprecated)
- Restoring a Disk Using a VBS Backup
- Creating a VBS Backup (Native OpenStack API)
- Querying Summary Information About VBS Backups (Native OpenStack API)
- Querying Details About VBS Backups (Native OpenStack API)
- Querying Details About a VBS Backup (Native OpenStack API)
- Querying the Job Status
- Deleting a VBS Backup (Native OpenStack API)
- Restoring a Disk Using a VBS Backup (Native OpenStack API)
-
Backup Policies
- Creating a Backup Policy
- Querying Backup Policies
- Modifying a Backup Policy
- Deleting a Backup Policy
- Associating Resources with a Backup Policy
- Disassociating Resources from a Backup Policy
- Executing a Backup Policy At Once
- Enabling or Disabling a Backup Policy
- Querying Backup Jobs Triggered by a Backup Policy
-
VBS Backups
- Appendix
- Change History
-
User Guide (Paris)
- General Reference
Show all
Copied.
Why Does the Retention Rule Not Take Effect After Being Modified?
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.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot