Differential backup, original full backup deleted and new full created, old differentials disconnected
I've now experienced this twice: I have a differential backup set to run daily, with no consolidation options. It runs for the first time, creates the full backup, and then for a number of days runs the differential.
After a time, however, it seems to delete the original full backup, and create a new one. All of the differentials prior to this are now lost, because the original full backup is no longer available.
Again, I've had this happen twice now with two different backups (the previous one turned off, of course). Any ideas?
Here's the screenshot. I was using the latest build that just preceded the one that installed this morning.
coppockm
Is there any chance that you made changes to the original task and what you see now is not the same settings that was on the orignal task
If the answer is no changes to original, then I have no explanation as there should not be any frequent deletes based on your current backup scheme. Editing a task into new configuration has proven results are often not what is expected. I make no task edits.
Going forward,
Cease using the existing task. Change to not scheduled and leave the task; or, you can use the task option to "REmove task from list"
Now, set up a new task as per this example.
If using differential type backups (which is full + X Diff), the 11-Diff illustration is my recommended method. Change the 6 or 4 to fit your available storage.
These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X number of chains" quota has been reached.
Note In this example, deletion of oldest backup chain will occur immediately following creation of backup #29. as 4 chains of 7 files each are being kept on a rotation basis so user always has the 28 most recent backup.
The number of dif per chain can be user selectable but it is not wise to have too many dif files based on the single full.
A more frequent full rather than too many dif would be my preference.
Instead of the keeping 4 chains, changing the 4 to a different number of chains, here are a few example. 1 chain=7 (1 full +6 diff).
Store no more than 2 recent version=14 most recent backup kept
Store no more than 3 recent version=21 most recent backup kept
Store no more than 5 recent version=35 most recent backup kept
Figure 11-Dif: -Example of custom/differential backup method settings
If using differential type backups (which is full + X Diff), the 11-Diff illustration is my recommended method. Change the 6 or 4 to fit your available storage.
These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X number of chains" quota has been reached.
In this example, deletion of oldest backup chain will occur immediately following creation of backup #29.
Allow space for 1 more full backup in addition to "Store no more than X number of chains" as the program will NOT delete the oldest full until its replacement has been successfully created.
In this example, one chain or one recent version chain =1 full plus 6 diff or 7 files per chain.
If keeping 4 recent version chains (4 chains of 7 each) retention would be 28 files. Deletion begins after backup 29.
When restoring, a single diff file is selected and that specific diff plus its full backup base will be restored (2 files restored).