Direkt zum Inhalt

Deleting increments

Thread needs solution

If I have an incremental backup with the main (first file) and 20 incremental files, can I delete some of the incrementals and still be able to restore from it? I understand I would lose the parts I delete. I want to store some old backups but don't have enough space to store all of the files so deleting a number of them will still allow me to have access to some of that backup.

0 Users found this helpful

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 alert you much if the full backup were missing or unreadable.

Maybe now would be a good time to get a larger storage drive. Incremental pieces should not be deleted.
The only pieces which can be deleted and the remainder still work is the newest pieces added to the chain.
All the older pieces must be kept and the file numbers must be kept sequential.

GH12.

This is an example of how to set up a perpetual self deletion of old chains--if you get a larger storage disk.
Create Custom Incremental Backup Scheme. 6 Inc, Keep 4 chains. The 6-4 is an example only with user choice for whatever number of chains to be retained best fits the individual needs.

tuttle - Thank you for the explanation. That saved me a lot of time trying it.

GroverH - I need to store backups of my clients files for a year and I have a lot of clients. I have four external hard drives, the main one being a 1 TB drive. I let my backup run for a month on the main drive and then transfer it to one of the other drives and start a new backup. So, yes, I can keep adding more drives but that would just be more work and not permanently solve the problem since, hopefully, my client-base will continue to grow. I thought that if I could just save a few of the files (the main one and the last incremental) that it would save a lot if time and space. But I understand now that isn't possible. I appreciate your reply.

Tilden,
I believe if you were to change the backup type from incrementals to differentials, you could get by by just saving the base full and the most recent diff. The diff contains all changes since the last full and only those two files are needed to be current. Changes appear to have been made to 2015 that make the interim deletion older diff files less of an issue. In my testing, I have been able to delete the oldest dif files and the tib numbering would continue wiithout restore issues--but do your own testing.