Reversed Incremental - .vbk filestamp unchanged

[cpurn]

Hi there,

We have a veeam job that does reverse incremental every night, all works well. We use Commvault to run incremental backup everynight ... my understanding is that the .vbk file is supposed to be updated after each successful reversed incremental job and then Commvault will pick this up as part of its incremental job.

The problem here is that I can't see any timestamp change on the .vbk file... the last change was when active full was done.

What have I overlooked here? thanks

[Gostev]

No idea, I too would expect it to change. Do you see any writes going into this file during backup job with Process Monitor?

[cpurn]

HI Gostev,

I have taken a screenshot - how would I be able to show this to you?

thanks

[cpurn]

Last active full was 30/11/2013, most recent reversed inc was 1/12/2013.
As you can see, the .vbk timestamp is showing behind.

[foggy]

Christian, what if you open the properties of this backup under the Backups > Disk node - what date do you see there for the latest restore point (VBK)?

[cpurn]

Hi Foggy,

The timestamp vbk timestamp has changed now.

Our backup job kicks in at 7pm every night and will run for about 6-7 hours. From below, it seems the .vbk only gets updated at the start of the job (last write 8:14pm) and .vrb last write time is 1:58am. Am I wrong to expect the .vbk file to be updated along together with .vrb?

thank you

[Gostev]

Could this behavior be due to your backup storage?
Looks like you are backing up to some share, what is behind it?

[cpurn]

Hi Gostev,

The target disk is a Netgear ReadyNAS with SATA disks (the current bottleneck with the backup operation). The device date & time is correct and is configured to use NTP for timesource.

If you think that we have done everything correctly with Veeam, I'm happy with this and I'll investigate our NAS. I thought I might check if I have overlooked anything with my veeam config.

thank you.

[Gostev]

Basically, you cannot control this in Veeam at all. Last modified is managed outside Veeam (by actual operating system), and it is updated by OS automatically when the file is closed. Both VBK and latest VRB are closed at the end of the backup job, and I expect them to be stamped by OS accordingly to this time.

[cpurn]

Hi Gostev

I was just curious that the VRB seems to be updated accordingly but not the VBK. They both live on the same remote filesystem volume on the Netgear Readynas.

thanks for your help and Foggy.

[Gostev]

Agree. If not storage, I see only one possible explanation, and that is VBK file not being closed at all... I would try backing up one VM to local disk, just a test to remove NAS from the picture.

[cpurn]

Don't you think the file handle was actually closed as of 8pm that this is reflected in the Access Time on the file object in the NAS?

[Gostev]

No, as the job is supposed to keep updating VBK as it runs.