Start a Conversation

Unsolved

This post is more than 5 years old

10555

February 21st, 2014 10:00

Avamar - Total processed bytes inconsistent with original data size

Every so often I see a line like this in a log when investigating an Avamar backup exception:

00:25:13 avtar Error <16507>: Path "/var/log/resources": Total processed bytes 724 is inconsistent with original data size 731

Does this error indicate that the file size changed between the start of the backup and the time the agent attempted to back up that specific file? I'm not exactly understanding how/why a change in file size impacts the agent's ability to back up the file.

355 Posts

February 26th, 2014 06:00

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

223 Posts

March 5th, 2014 07:00

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.

2K Posts

March 5th, 2014 07:00

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?

223 Posts

March 10th, 2014 07:00

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

But thanks for your response.

November 27th, 2014 23:00

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.

2K Posts

November 28th, 2014 05:00

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

November 28th, 2014 20:00

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

38 Posts

December 10th, 2014 01:00

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 ?

355 Posts

December 10th, 2014 05:00

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

2K Posts

December 10th, 2014 06:00

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.

38 Posts

December 11th, 2014 23:00

yes, but this backup failed consistently for 3 days irrespective of schedule/on-demand with same error.

assuming this file is being changed every time after its chunk'ed and fails before the actual backup.

This case should throw an error only at the scheduled backups, but on-demand backup at a diff time interval has the same error.

finally if we consider these logs that are being changed all the time, avtar should probably throw code 32 error "process cannot use file already in use by another process"

2014-12-09 21:18:28 avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.72": Total processed bytes 10000139 is inconsistent with original data size 10000223 (Log #1)
2014-12-09 21:18:28
avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.54": Total processed bytes 10000062 is inconsistent with original data size 10000178 (Log #1)
2014-12-09 21:18:28
avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.97": Total processed bytes 10000004 is inconsistent with original data size 10000122 (Log #1)
2014-12-09 21:18:28
avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.98": Total processed bytes 10000122 is inconsistent with original data size 10000182 (Log #1)

38 Posts

December 11th, 2014 23:00

Pawan,

Thanks for your reply.

Backups here are however being completed with exceptions(excluding those files).

Not sure how chkdsk is related to this.

20 Posts

December 12th, 2014 05:00

I've never seen the "file already in use" error on a Linux backup - in my experience I've only seen those on Windows machines. I would expect busy log files on a Linux system to more or less consistently result in the 'bytes changed' exception.

2K Posts

December 12th, 2014 06:00

2014-12-09 21:18:28 avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.97": Total processed bytes 10000004 is inconsistent with original data size 10000122 (Log #1)
2014-12-09 21:18:28
avtar Error <16507>: Path "/opt/app/d1otm1m1/OTM632/OTMAPP/logs/glog.app.log.bak.98": Total processed bytes 10000122 is inconsistent with original data size 10000182 (Log #1)

If you look carefully at the file sizes, it seems likely that the .97 file rolled and became the .98 log file while avtar was attempting to back these files up.

These appear to be backup copies of human readable log files for Oracle OTM. Are they of any value? If not, you can exclude them to prevent the issue from occurring.

38 Posts

December 15th, 2014 02:00

Thank you Ian.

The major difference what i saw is

Backups failed totally before reboot and now completing with exceptions,both with same error.

Thank you, i will try if we can exclude those OTM logs

No Events found!

Top