Warning of size discrepancy during test phase

You can ask general questions, share opinions or advices about FBackup
Post Reply
davewilk
Posts: 15
Joined: Sat Aug 25, 2018 1:59 pm

Warning of size discrepancy during test phase

Post by davewilk »

I have been testing FBackup in Hyper-V Windows 8.1 virtual machine (machine name HV-Win81). I am doing a mirror backup with fast mirror, removal of excluded and deleted files, copying of NTFS security permissions, test after backup, backup empty folders, and smart file scanning mode.

My user name is David, and I am backing up the entire C:\Users folder to the destination C:\Backup\HV-Win81 (this is just a test, remember).

During the testing phase I get the warning:

"[8/25/2018 7:15:41 AM] Warning: Size of file "C:\Backup\HV-Win81\C\Users\David\AppData\Local\Microsoft\Internet Explorer\Indexed DB\Internet.edb" in destination (8454144) is different than the size stored in catalog (0)"

This always happens with just this one file, both on the initial backup and subsequent fast mirror backups. This file has not been changed since 8/18/2018 (probably the last time I used Internet Explorer), so I am sure it is not open during the backup.

The size of the file "Internet.edb" in both the source and the destination is indeed 8454144 bytes, so it seems that this file has been backed up correctly, but why does the catalog say it is 0 bytes?

Adrian (Softland)
Posts: 1953
Joined: Thu May 23, 2013 7:57 am

Re: Warning of size discrepancy during test phase

Post by Adrian (Softland) »

Hi,

The size in catalog is the size of the file read from Windows. If the size is different, it means FBackup was not able to read the correct size probably because of the Volume Shadow Copy service (it could be in use/locked even if IE is not running). Try to make a copy of that file and run again the backup. Does FBackup successfully copy the new file?

davewilk
Posts: 15
Joined: Sat Aug 25, 2018 1:59 pm

Re: Warning of size discrepancy during test phase

Post by davewilk »

Softland wrote:The size in catalog is the size of the file read from Windows. If the size is different, it means FBackup was not able to read the correct size probably because of the Volume Shadow Copy service (it could be in use/locked even if IE is not running). Try to make a copy of that file and run again the backup. Does FBackup successfully copy the new file?
Yes, I made a copy and the copy was backed up and tested correctly. The original was backed up correctly, but failed the size test (as before).

Actually I am just going to omit the whole of AppData\Local from the backup. It's only AppData\Roaming that contains any necessary information.

Thanks for the reply.

Post Reply