Skip to main content

Incremental Backups - Deleting Strategy

Thread needs solution

I am testing how incremental backups work.
On the workstations the user's document and Outlook Pst files are backed up daily.
The backups are successful however on the workstations I now have over 60 incremental backups. Those backups are using disk space. From what I read I should not delete those incremental backups -that there is a method in the utility where I can change the backup routine - and those unnecessary older backups are removed.

What I want to do is trim those incremental backups down to at least five - keep the current five - and start another rotation. Ideally I would have always one full original backup and at least five recent backups.

I don't know how to do this....

0 Users found this helpful

Create a brand new task with your desired options, including a deletion threshold based on age, number of backups or total backup folder size.

A task for Incremental or Differential will always begin with a full backup. That is necessary, as that becomes the baseline.

For an Incremental task, after the first full backup, subsequent backups will be incremental, each one based on changes since the previous Incremental backup, all the way back to the second backup being incremental based on changes since the full backup. As such, you need all links in the chain, all incremental backups right back to and including the first full backup, in order to Restore.

For a Differential task, after the first full backup, subsequent backups will be differential, each one based on changes since the first full backup. To restore, you would need just any Differential and the Full backup on which it is based.

You should not allow an incremental chain to become too long. An incremental restore depends upon every incremental in the chain being valid, including the original full. It's better to limit each chain to just a few incrementals, followed by a fresh full backup to start a new chain.

You should validate backups periodically. That would have alerted you much sooner if the full backup were missing or unreadable.

This is very clear. Thanks!

With this comment 'You should not allow an incremental chain to become too long'.

If I do daily backups I would change the backup strategy to 'Create a full version after 11 incremental'.
That way I would have one complete chain -with a full backup -and 11 incremental backups - and then I would start another chain and another chain.
Thus I could eventually store those accumulated chains as an archive asset - and keeping for example the current two chains.