{"id":213,"date":"2021-07-23T12:25:15","date_gmt":"2021-07-23T12:25:15","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/backup-retention-behavior\/"},"modified":"2021-07-23T12:25:15","modified_gmt":"2021-07-23T12:25:15","slug":"backup-retention-behavior","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/backup-retention-behavior\/","title":{"rendered":"Backup Retention Behavior"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 82 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

82<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n

This document explains the retention behavior of cPanel & WHM\u2019s backup system. You can edit this behavior in WHM\u2019s Backup Configuration<\/em> interface (WHM >> Home >> Backup >> Backup Configuration<\/em>).<\/p>\n

How backup retention works<\/h2>\n

The system has two retention modes: the default backup retention behavior and strictly-enforced retention. Both behaviors ensure that the system saves the amount of successful backups that you set in WHM\u2019s Backup Configuration<\/em> interface (WHM >> Home >> Backup >> Backup Configuration<\/em>). However, the default backup retention behavior will retain that number of successful backups, along with failed backups, until the next successful backup completes. This means that the system could retain a number of backups larger than the amount that you set in WHM\u2019s Backup Configuration<\/em> interface (WHM >> Home >> Backup >> Backup Configuration<\/em>).<\/p>\n

When the strictly-enforced retention behavior encounters failed backups, it keeps at least one successful backup, but deletes any backups that surpass the retention limit that you set in WHM\u2019s Backup Configuration<\/em> interface (WHM >> Home >> Backup >> Backup Configuration<\/em>). Because the system will not surpass the retention limit, we recommend that you enable strictly-enforced retention if you have limited space on your server. To enable strictly-enforced retention, select the Strictly enforce retention, regardless of backup success<\/em> setting in WHM\u2019s Backup Configuration<\/em> interface (WHM >> Home >> Backup >> Backup Configuration<\/em>).<\/p>\n

You can customize whether the system will notify you when a backup succeeds or fails. For more information on how to set up your backup notifications, read our Contact Manager documentation.<\/p>\n

Default backup retention behavior<\/h3>\n

When cPanel & WHM completes a backup, the system deletes the oldest backup. When the system-generated backup fails, the system will keep the failed backup, it will not<\/strong> delete the oldest backup, and will continue to retain the oldest backups. This behavior ensures that the system keeps at least one successfully-completed backup.<\/p>\n

After the next backup successfully completes, the system will delete the oldest backups to return to the desired number of backups.<\/p>\n

Standard backup retention behavior<\/h3>\n

If you run daily backups and retain four of them, the system will retain the latest four backup files:<\/p>\n

\n
\n<\/figure>\n

After the system successfully completes the next backup (5), it deletes the oldest backup (1):<\/p>\n

\n
\n<\/figure>\n

After the next backup fails (6F), the system does not delete the oldest backup (2):<\/p>\n

\n
\n<\/figure>\n

If several more backups fail (7F, 8F, and 9F), the system will continue to retain the oldest backups:<\/p>\n

\n
\n<\/figure>\n

After the next complete backup succeeds (10), the system deletes the oldest backups so that it only retains four backups:<\/p>\n

\n
\n<\/figure>\n

Backup retention behavior with the Strictly enforce retention setting<\/h3>\n

With strictly-enforced retention, cPanel & WHM will delete the oldest backup when the system completes a backup. However, when the system-generated backup fails, the system will keep the failed backup and delete the oldest backup. Also, it will not<\/strong> continue to retain the oldest backup, except for the last successful backup. This behavior ensures that the system keeps at least one successful backup.<\/p>\n

After the next backup succeeds, the system will delete the oldest backups to return to the desired number of backups.<\/p>\n

If you run daily backups and retain four of them, the system will retain the latest four backup files:<\/p>\n

\n
\n<\/figure>\n

After the system successfully completes the next backup (5), it deletes the oldest backup (1):<\/p>\n

\n
\n<\/figure>\n

After the system generates a partial backup (6F), it deletes the oldest backup:<\/p>\n

\n
\n<\/figure>\n

After several more partial backups (7F and 8F), the system only retains partial backups:<\/p>\n

\n
\n<\/figure>\n

After the next partial backup (9F), the system must retain the last successful backup (5), so it deletes the oldest partial backup in order to retain only four backup files:<\/p>\n

\n
\n<\/figure>\n

After the next complete backup completes (10), the system can delete the oldest backup (5) so that it only retains four backups, with at least one successful backup.<\/p>\n

\n
\n<\/figure>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

Valid for versions 82 through the latest version Version: 82 Overview This document explains the retention behavior of cPanel & WHM\u2019s backup system. You can edit this behavior in WHM\u2019s Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration). How backup retention works The system has two retention modes: the default backup retention …<\/p>\n","protected":false},"author":1,"featured_media":214,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/213"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=213"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/213\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/214"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=213"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=213"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}