Loading...
Loading...
This article provides an overview of scenarios where out-of-schedule restorePoints are created and how to identify and remove them.
With Veeam Kasten for Kubernetes, there are multiple ways to take backups & exports. A manual backup/export from the application menu. A manual policy run with the `Run Once` button. A scheduled policy run. The outcome of all the above workflows is the same: a local and exported restorePoint is created inVeeam Kasten for Kubernetes, respectively. However, retention is different for each approach. Any restorePoints created as a part of scheduled policy runs follow retention configured in the policy. A manual backup/export run or a manual policy run is retained forever until it is deleted manually. Veeam Kasten provides an option to specify the expiration time when the manual backup/export is triggered. These are automatically retired when the expiration time has elapsed. It is recommended to set expiration time whenever a manual backup/export or policy run is triggered, as it avoids manual intervention. There might be situations where backup/exports are created before a change in the application or upgrade of infrastructure components. In such situations, these restorePoints would only be retired if manually deleted or the expiration time is elapsed. This needs handling as removing restorepoints over time is easily missed, which could cause capacity issues in the storage.
Labeling Explanation Consider the following regarding the methods used to label restorepoints: After a successful backup/export, Veeam Kasten creates the restorePoint with the label including the name of the policy that created it (e.g., k10.kasten.io/policyName). Since a manual backup/export is not policy-driven, no policy label is included. However, if an expiration time was set during the action, that expiration is set as a label (k10.kasten.io/expiresAt) in the restorepointcontent. For the restorepoints which are created using the run once button, Kasten adds the label: k10.kasten.io/isRunNow
Automating RestorePointContent Clean Up The example below can be used in a cronjob to regularly delete such manual restorepoints that are more than a month old.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.