cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted

Why are avv*.dat files much smaller in ePO repository than in VSE "engine" folder ?

Hi all,

when I have a look at the repositories located on my ePO 4.0 and my SuperAgents, I notice that the  avv*.dat  files are much smaller than in the local VSE 8.7 instances.

For instance, for DAT 6055:

- if I extract the files from ..\Repository\Current\VSCANDAT1000\DAT\0000\avvdat-6055.zip , I get this:

avvclean.dat : 487,929 bytes
avvnames.dat : 388,497 bytes
avvscan.dat : 73,742,118 bytes

- when I check the local VSE 8.7 definition files in C:\Program Files\Common Files\McAfee\Engine\ , I get :

avvclean.dat : 5,039,589 bytes
avvnames.dat : 2,116,053 bytes
avvscan.dat : 102,408,493 bytes

Any idea where this size difference comes from ?

Michael

3 Replies
Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 2 of 4

Re: Why are avv*.dat files much smaller in ePO repository than in VSE "engine" folder ?

The DATs are compressed, and expanded by the engine when it starts.

HTH -

Joe

Highlighted
McAfee Employee
McAfee Employee
Report Inappropriate Content
Message 3 of 4

Re: Why are avv*.dat files much smaller in ePO repository than in VSE "engine" folder ?

Avv dats are stored on the McAfee source servers and in the repository in a proprietary compressed format to reduce space and save bandwidth.

The Engine can work either way and decompress the Avvdats on the fly if needed, but it is faster to initialise the engine if we have them decompressed in advance.

Once the Avvdats are on the local machine there is no longer much advantage in storing the Avvdats compressed, so the update task decompresses them automatically and the resulting files you see on the client are consequently bigger.

Hence the difference between client and repository.

Hth,

Rob.





Was my reply helpful?


If this information was helpful in any way or answered your question, will you please select Accept as Solution in my reply and together we can help other members?
Highlighted

Re: Why are avv*.dat files much smaller in ePO repository than in VSE "engine" folder ?

Ok, thus a given dat file (for instance avvscan.dat) can contain either compressed or uncompressed data, although the extension remains ".dat".

I though it could have been the local VirusScan instance that recreates new .dat files from "previous .dat files + latest .gem files" , without performing any pruning and inducing an increase of size.

Thanks for your answers !

Michael

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community