Support
Contact
Sign In
Number of Successful Full Backups to Retain
- This article is for Windows only
Summary:
CSSB will track how many successful full backups have been performed for a given backup set. When a new full backup completes, any excess full backups and their dependents will be removed within 24 hours. The number of full backups to retain is configurable with no upper limit. Special retention values for retaining backups forever and delete after upload are also available. The cloud storage has courtesy buffer space for uploading new full backups that would temporarily put the account over quota.
For example, let's assume that a user has a full backup that is 100 GB, has chosen to retain 2 full backup cycles, and is backing up to local and cloud.
- When the first full backup completes, no backups are purged.
- When the second full backup completes, no backups are purged.
- After the third full backup completes, the first full backup and any of its dependent backups will be purged within 24 hours.
- Enough space must exist on the local disk for the third full backup to complete. If there is not enough local space to complete the full will fail to both disk and cloud
- In this scenario though the third full would put the account over-quota, it is allowed to complete since retention will remove the oldest cycle and return the account below quota.
Note: When buffer space is required for upload it is possible that you will get an email regarding being over-quota while the full is still in progress. This is most likely to occur when Safe Pro is being used in addition to CSSB.
Incremental and Differential backups are dependent upon a Full backup. When a Full backup is purged, any dependent Incremental or Differential backups will be purged at the same time.
Note: By default, backups are purged once every 24 hours. The retention policy is configurable in the CSSB Enhanced Interface by clicking the Advanced link and navigating to Retention Policy Enforcement within the Global Settings section.
Solution:
The sections below are collapsed. Please click the section title to open / close a particular section.
Backups will fail if they do not have enough space on disk and/or the cloud. You must ensure that there is enough space for your backups to complete. In all cases, you will need enough space for the total size of each backup cycle times the number of cycles retained. When backing up to disk and cloud, you will also need enough space on the local disk for the next full backup to complete, because the oldest backup cycle will not be deleted until the next full backup is complete.
We cannot predict exactly the amount of space you'll need for any given backup or backup cycle. It depends on the amount of data you have, the type of data you have, and the amount of data that changes between backups.
However, most users find that the size of one backup cycle is similar to the next. They can say things like "my full backups are around 100GB in size." If you have established backups, you can make an educated prediction for the amount of space you will need.
You can read more about storage and retention in the Knowledge Base article for Retention Policy Best Practices.
To set retention as forever, change the number of full backups to retain to 0 (zero). This action will have a significant effect on the total storage space used over time, since any backup with a retention of forever will not be removed.
Change the retention on the number of full backups to -1 to configure CSSB to purge the local backup after it successfully uploads to the cloud.
Feedback