Raising questions about my VIB/VBK's

[flavor4real]

Hello,

I think I have a issue here. I have several jobs setup, Three high priority Jobs are setup

Job 1 >> 6Hr; Retry 3/ wait 10min; Mon-Sat (24hrs) 14 Rollback points
Job 2 >> 6Hr; Retry 3/ wait 10min; Mon-Sat (24hrs) 14 Rollback points
Job 3 >> 2Hr; Retry 3/ wait 10min; Mon-Sat (0600-1800) 18 Rollback points

On Monday I've reviewed the VBK's and VIB's and recorded them.

Job 1 >> Earliest VBK (11/22/2010) VIB Count 8 Latest VBK (11/27/2010)
Job 2 >> Earliest VBK (11/22/2010) VIB Count 16 Latest VBK (11/27/2010)
Job 3 >> Earliest VBK (11/22/2010) VIB Count 23 Latest VBK (11/27/2010)

I thought that when the next Full Synthetic Job kicks in (which would be each saturday) the previous
VBK's or VIB's not needed will be removed/ deleted.
Now, Today is wednesday morning and files has been removed already.

Job 1 >> Earliest VBK (11/27/2010) VIB Count 8 Latest VBK (synthetic will run this weekend)
Job 2 >> Earliest VBK (11/27/2010) VIB Count 13 Latest VBK (synthetic will run this weekend)
Job 3 >> Earliest VBK (11/27/2010) VIB Count 19 Latest VBK (synthetic will run this weekend)

I thought, once the Synthetix job completes, it will look up and remove files (VIB's and VBK's) that it don't need. Why is this happening in the middle of the week, before the synthetic job is in place?

[rowdy]

Could you include a full filelisting of your backup directory of those two days (or next week if you don't have them)?
Also, what is the date included in the VBK filename?
I have also noticed that the 'touch' date (NTFS datestamp) isn't always updated properly as one would expect.
So, the VBK can be both older or newer than the NTFS datestamp indicates. I have seen both cases and confirmed that in fact, nothing was wrong with the VBK files.

[flavor4real]

Here is a screenshot ...
I put it on wikisend. cause i don't know how to get the image in here.
shot01.jpg

[Gostev]

I thought, once the Synthetix job completes, it will look up and remove files (VIB's and VBK's) that it don't need. Why is this happening in the middle of the week, before the synthetic job is in place?

This is absolutely normal and expected behavior for incremental backup.
Here is the existing topic about this > v5 Restore Point Bug?

[flavor4real]

I see what you saying. I think I'm making it more complicated than I should. looks like that everything is like it should be. Thanks for your help guys. All i need to implement is SureBackup to get good sleep thanks