[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[],[],null,["# Automatic backup creation and deletion\n\nAutopilot Standard\n\n*** ** * ** ***\n\nThis page provides an overview of automatic backup creation and deletion.\nIt details backup scheduling methods, [Recovery Point Objective (RPO)](https://en.wikipedia.org/wiki/Disaster_recovery)\nrisk levels, and backup deletion policies.\n\nAutomatic backup creation\n-------------------------\n\nBackup for GKE provides two backup scheduling methods to automatically\ncreate backups:\n\n- Smart scheduling\n- Cron scheduling\n\nWhen creating a backup plan, you can select either scheduling method.\n\n### Smart scheduling\n\nSmart scheduling automatically creates backups when needed to satisfy an\nRPO you set. Smart scheduling accommodates exclusion windows to prevent backups from running\nduring peak usage periods. Smart scheduling automatically retries failed backups.\n\nTo enable smart scheduling in your backup plan, follow these steps:\n\n1. Set a target RPO that defines the maximum permissible duration of data loss in the event of an incident. The minimum RPO is 60 minutes and the maximum is 60 days.\n2. Optional: Add exclusion windows. Specify time intervals when backups shouldn't run.\n\nFor instructions to create a backup plan with smart scheduling, see [Create a backup plan](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-plan#create).\n\n#### Backup exclusion window\n\nYou can configure exclusion windows to prevent backups from running during\nspecific time periods. Backup jobs are scheduled to start and finish outside\nthe window duration as much as possible, but ongoing jobs won't be canceled if\nan exclusion window begins when jobs are in progress. You can configure an\nexclusion window as a single occurrence, daily, or weekly. You can configure\nmultiple single occurrence windows but only one daily or weekly recurring window.\n\nFor example, if you don't want backups from 5:00 PM to 6:00 PM every day,\nyou can set a daily exclusion window with a start time of 5:00 PM and one hour duration.\n\nFor instructions to configure backup exclusion window to smart scheduling,\nsee [Create a backup plan](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-plan#create).\n\n### Cron scheduling\n\nCron scheduling automatically creates backups according to a time schedule you\ndefine using the standard [cron](https://en.wikipedia.org/wiki/Cron) syntax.\nFor example, `10 3 * * *` creates a backup at 3:10 AM every day. The minimum\ninterval between scheduled backups is 10 minutes. The cron scheduler doesn't\nautomatically retry backups in case of failure.\n\nFor instructions to create a backup plan with cron scheduling, see\n[Create a backup plan](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-plan#create).\n\n### Comparison between smart scheduling and cron scheduling\n\nThe following table summarizes the comparison between smart scheduling and\ncron scheduling methods.\n\nRPO risk level\n--------------\n\nEvery backup plan, regardless of its backup scheduling method, has a\ndynamically calculated RPO risk level after it has at least four successful backups.\nIf a backup plan violates RPO, or is at risk of violating it in the near future,\nthen the RPO is at risk for the plan.\n\nThe RPO risk level is calculated from the backup creation scheduling configuration\nand the backup history of the backup plan. There are five risk levels: `None`,\n`Low`, `Medium`, `High`, and `Critical`. Each backup plan also has an RPO risk\nmessage that explains why the backup plan is at a particular risk level and\nprovides advice for reducing risks.\n\nThe following table describes each RPO risk level.\n\nBackup plans with the same risk level may have different RPO risk messages\ndepending on the scheduling configuration and historical backup data points.\nFor example, the message for a medium risk level plan can be: Recent backups are\ntaking longer. If this trend continues, there is a risk the RPO will no longer be met.\n\nAutomatic backup deletion\n-------------------------\n\nYou can configure retention policy in a backup plan to automatically delete\nbackups after a period of time. The retention policy is required for backup plans\nthat include automatic backup creation. You can configure automatic backup deletion\nusing the parameter `backup_retain_days` in the backup plan retention policy.\nThe maximum retain time is 365 days.\n\nWhen configuring a retention policy for a backup plan that uses automatic backup\ncreation methods, consider the following limitations:\n\n- For backup plans using smart scheduling, the backup retention duration must be less than or equal to 360 times the target RPO.\n- For backup plans using cron scheduling, the backup retention duration must be less than or equal to 360 times the creation interval.\n\nFor instructions to create a backup plan with retention policy,\nsee [Create a backup plan](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-plan#create).\n\nWhat's next\n-----------\n\n- Learn more about [Plan a set of backups](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup-schedule).\n- Learn more about [Plan a set of restores](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/restore-plan).\n- Learn more about [Back up your workloads](/kubernetes-engine/docs/add-on/backup-for-gke/how-to/backup)."]]