Hello,

What is the version of Avamar you are using and what is client OS ?

Does backup fails with this error or you are getting this error in logs with successful backup ?

Regards,

Pawan

Hello,

I have the same problem.

I am using version 7.0.1-61 and client OS is W2k3 R2 SP2.

Yes, the backup failes with errors.

avtar Error <16507>: Path "***": Total processed bytes 87972 is inconsistent with original data size 271360

After this error message I get a followong error:

avtar Error <5737>: I/O error: Unable to BackupRead(3)

Can someone explain this error. I had the same idea as in the first post, but normaly in my backup window nobody changes anything.

I've found a few possible causes for this issue while searching the escalation database.

This message can appear on UNIX / Linux systems if the file is overwritten after avtar has retrieved the file information but before it has actually backed up the file contents. This case is not fatal but will cause the backup to complete with exceptions. Silently backing up the metadata from one version of a file and the data from a different version would be bad.

This message can appear on Windows systems if the VSS snapshot being used for the backup is deleted by the OS. You would see a message like the following in the event logs:

The shadow copies of volume X: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

If a VSS snapshot is deleted out from under the backup software, it will likely cause a large number of errors and the backup may fail.

I also saw an issue reported for Windows dedupe volumes but this only applies to Windows 2012 and it is reported to be fixed in 7.0.0 so I don't believe it's relevant here.

If the backup is failing due to this issue (not just completing with exceptions), I would recommend opening a service request. Support will need debug logs plus the following information:

• Is the file being noted in the message special in some way (a symbolic link, junction point, stub file, etc.)?
• Is the backup being sent to the Avamar back-end or the Data Domain back-end?

Case is clear now, the application team did a reboot of the server while the backup was running.

But thanks for your response.

Hi All,

I am observing the same error message in the win 2008 server.

avtar Error <16507>: Path "c:\Users\C192761\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\D0OVPDTM\navigator[1].htm": Total processed bytes 98508 is inconsistent with original data size 124233

avtar Error <16507>: Path "c:\Users\v3x6633\AppData\Local\Microsoft\Internet Explorer\Recovery\High\Active\{5591090B-761F-11E4-9170-005056BE7241}.dat": Total processed bytes 31424 is inconsistent with original data size 31744

avtar Error <16507>: Path "C:\Users\v3x6633\AppData\Local\Microsoft\Internet Explorer\Recovery\High\Active\{5591090B-761F-11E4-9170-005056BE7241}.dat": Total processed bytes 31424 is inconsistent with original data size 31744

The Avamar has a client only upgrade and is at 7.1.101-61

Please advice.

Why are you backing up your IE browser cache and session restore data? That data is worthless.

yes, true Ian. But the complete file system is added with no exclusion thus, I guess it showed these paths too.

But the backups are working fine from today. No changes done, however it's fixed now.

Thanks

Thank you,

I had the same issue avtar Error <16507> Total processed bytes 10000125 is inconsistent with original data size 10000134

This got cleared after the reboot.

As per my understanding the avtar process, which locked the f_cache file earlier to reboot got killed and  a new avtar process spawn up and started taking the changed files after reboot.

Is this true, what i have assumed ?

Hello,

You can get this error message in two possible cases -

1. Avtar process is trying to scan a file which is locked by some other 3rd party product and preventing Avatar process.

2. Avtar process is trying to scan a file which is corrupted in some form.

You can try to exclude such file and re run the backup. If it is windows client, run chkdsk to correct any kind of corruption on disk.

Regards,

Pawan

As per my understanding the avtar process, which locked the f_cache file earlier to reboot got killed and  a new avtar process spawn up and started taking the changed files after reboot. Is this true, what i have assumed ?

No it's not.

There is a brief window between the time avtar begins working on a file and when it actually starts to chunk it to back it up. If the file is overwritten or changed during this time, this message will be reported. It has nothing to do with cache locking whatsoever.