Veeam WAN Accelerator

[Elgringo]

Hi guys,

I just configured Veeam WAN Accelerator. It is used for VM replication.
My customer noticed something weird : Global Cache validation occur each time for a particular VM.

We run Veeam 9.5 and vSphere 6.5 U2


Thx

[wishr]

Hi Sebastien,

Welcome to Veeam community forums and thanks for posting.

Have you had a chance to look at that article? If so, please let us know what exactly you are concerned about.

Thanks!

[DGrinev]

Hey Sebastien,

On a side note vSphere version 6.5 U2 is unsupported.
Just wanted to make sure you aware of possible issues, here you can find a big thread about it. Thanks!

[foggy]

As for the cache validation, then what you're seeing means some sort of corruption occurs during data transfer each time. WAN accelerator performs data integrity checks upon transfer and is able to fix any inconsistencies, however, it then validates the cache to ensure it is ok (some sort of self-protection). I recommend contacting support to take a closer look at your log files. Thanks!

[obwielnls]

Some of my jobs that use wan acceleration give me this message on some of the machines, but only sometimes. 9.5 U3a but it's been going on for a while.

"Validating global cache for OSW2008x86" < the os varies with the machine type being backed up..

I"m trying to figure out the pattern but nothing seems obvious. It's not once per job, nor one per day as near as I can tell.

Does anyone know? Sometimes it takes a while and if I can avoid it I'd rather.

[Alex Uryumtsev]

Hello Bill,

In your case there might be corruption during data transfer. During transferring data WAN accelerator is doing integrity check and if the file is inconsistent, WAN can fix it. Finally WAN accelerator has to validate the cache files to make sure that the changed files are consistent.

For further information you should contact support so they can take a closer look at your log files.

If you still have questions left, let me know.

BR,
Alex

[Elgringo]

Hi

Thank you for your reply Alex. This is want I understand too after digging in the Veeam for vsphere guide.
So we will raise a support ticket so the support team might fing a workarround or will help point the root cause (In that way, we will be able to contact the network team with evidences).

Thanks again !