V7 - Change tracking is disabled

[mikec20]

I am getting the following warning message in Veeam 7 while running an incremental backup job.

Failed to update unaccounted changes for disk xxxxxx.vhd. Change tracking is disabled.

Does anybody know why this is?

Further details:
- This is happening randomly to 13 differrent Hyper-V 2008 R2 servers during incremental backups
- All servers are using On-Host Backup to a repository on a local drive
- When I re-run the incremental job again on an affected server, it runs through fine.
- In the job settings, Use changed block tracking data is ticked

Tks

[veremin]

I’m wondering whether you have any error messages in the Windows Event log that might shed a light on what’s going on. Anyway, since we haven’t seen similar issues so far, I’d strongly recommend opening a ticket with our support team and letting them investigate it directly.

Thanks.

[rkovhaev]

Mike, please let me know your case number when you get it

[KennethJensen]

I have the same issue.

On my first incremental jon, 2 servers had the warning. One was a 32GB VHD on a W2003 server, and one was a 250GB VHD on s 2008 R2 SP1 server

Please advise

best regards
Kenneth

[rkovhaev]

Kenneth, please let me know your case number as well

[leo1]

same error here, too!
host 2012, v7, guest os 2003, only one machine gets this warning :/

so long

[foggy]

If nobody provides his case ID here, we will not be able to track the issue. Please kindly open a case and post ID here for reference.

[ChrisT]

I have the same issue and a windows log shows:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {bb7c26b2-01c7-40fc-a838-bbe321d143ae}

Case number is 00435632

[foggy]

Thanks for providing the case ID. Support is currently looking into it, we will update the thread once we have some information.

[Colin Reid]

Any updates on this problem? I got the same warning msg lastnight.

Colin

[foggy]

The case is still under investigation. If you could open your own case for that issue, it would probably provide some additional information to our support that could speed up the process.

[PeterWR]

I have just logged support case 00449743 for this issue.

[tombarnsley]

Hi all,

I am also getting this error on several servers.
Exchange 2013
Server 2012 as a DC
Server 2008 R2 running SQL

These warnings have only started occurring since we migrated from Vmware to Hyper V.

[Shralok]

I'd like to chime in... I am not sure if this is a related issue or not.

After upgrading to V7 I am getting the message that CBT is enabled when I run a job, but it is not using CBT when I look at the details.

"9/26/2013 9:33:37 AM :: Changed block tracking is enabled"
then I click on the VM name...
"9/26/2013 9:37:53 AM :: Hard disk 1 (49.0 GB)" (note, no [CBT] is listed)

Veeam Support - Case # 00451398

[foggy]

As an update to this thread, R&D is currently working on the fix for this issue, we will keep you posted on how it is going. Btw, it should be mentioned that the issue is specific to VHD disks only (VHDX are unaffected) and shows up on incremental job runs.

[kennocha]

As an update to this thread, R&D is currently working on the fix for this issue, we will keep you posted on how it is going. Btw, it should be mentioned that the issue is specific to VHD disks only (VHDX are unaffected) and shows up on incremental job runs.

I had this happen on a VHDX. However, I just reran a full and have yet to see it again so it could have just been some other kind of hiccup.

When I worked with Support on the phone and showed it to them they didn't seem overly concerned as I have only had it happen once.

[foggy]

Stephen, what is your support case ID?

[kennocha]

Stephen, what is your support case ID?

I was working on a separate issue when it happened. We didn't dive into it but: 00437248

I have yet to see it happen again as I said, so it could have been completely unrelated.

wds.domain.local Warning 3:02:59 PM 3:08:55 PM 1.2 TB 30.7 GB 3.1 GB 0:05:55 Failed to update unaccounted changes for disk wds.domain.local.vhdx. Change tracking is disabled.

[dsaunders]

Hello,

I have encountered exactly the same issue. The only strange thing is that it has only occurred on two VM's. These VM's are the only 2 VM's to be restarted since my upgrade to V7.
I hope that points someone in the right direction.
Thanks

[foggy]

According to the latest information from R&D, the fix was successfully tested in one of the customer's environment and should be included into the next patch.

[aeccles]

According to the latest information from R&D, the fix was successfully tested in one of the customer's environment and should be included into the next patch.

Foggy, can you provide us with the impact of this bug? Are our backups valid or should we consider the system unprotected? Also, do you have rough time frame on the next patch release?

Thank you

[foggy]

The only impact is that your backups could take longer than usual as CBT cannot be used and reading of the entire VM disks is required.

Please see this topic for the patch ETA estimation.

Thanks.

[aeccles]

thanks

[Lxk]

UPD: Fix is available.

[efrem.spataro]

Hi Lxk,

where could I find the "Fix".. Because Patch 2 isn't already available!
I have version 7.0.0.715 and I have this problem.

[Gostev]

Hi Efrem, please open a support case to get one. Thanks!

[milles08]

Just to add, I was experiencing this same error. Windows 8 host, Server 2012 VM, after converting from VHDX to VHD
Weird thing is I converted 9 Hyper-V VMs from VHDX to VHD, and the error only occured with one

Checking the Event Viewer, I saw this:
Windows cannot perform an online backup of this system because scoped snapshots are enabled. To resolve this, disable scoped snapshots by creating the following registry value on this computer:
PATH: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\
DWORD: ScopeSnapshots
Value: 0

I created the registry entry as suggested (had to create the 'SystemRestore' key also) and the problem went away immediately

Sam

[foggy]

Just to add, I was experiencing this same error. Windows 8 host, Server 2012 VM, after converting from VHDX to VHD
Weird thing is I converted 9 Hyper-V VMs from VHDX to VHD, and the error only occured with one

Sam, what Hyper-V version do you use? 2008R2?

[milles08]

That's right, Server 2008 R2 Host, and Server 2012 VM

Sam

[foggy]

Then this seems to be a known Microsoft issue.