Differential backup does not restart set number after a full restore
Hi... some weeks ago I had a trouble on my desktop and so I decided to do a restore of the full machine from last backup I had.
After this action I noticed that all following differential backups where so big, like the first set backup, maybe because all data restored are considered "a difference" from the first backup file.
That's ok. But at the end of the set, I expected that a new backup set were done, but not, the incremental counter is going beyond the max number configured.
In other words... I have a backup set configuered for a new backup after 8 differential backups. Last set is named XXXX_diff_b6_sYYY.tib. After the _b6_s3 backup I made the full restore. I expected a new backup set after last differential backup named _b6_s8 (as usual) but now the counter has reached the _b6_s11 ... Why a new backup set does not start yet? This is filling my destination backup...


- Log in to post comments

Hi Steve... The mean of the differential backup big size was clear, but I couldn't realize why a new set wasn't started yet. Well... I understand that next scheduled backup will be a new set backup, since the last was the 11th.
Thanks for your explanation.
- Log in to post comments