Author Topic: Another question about VRDB  (Read 4311 times)

0 Members and 1 Guest are viewing this topic.

Offline MikeBCda

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2247
Another question about VRDB
« on: September 15, 2006, 08:01:25 PM »
This is probably already covered in previous posts and/or the Help file, but humor an old man ...

When generating a fresh VRDB, does it ensure that the latest data "version" it's saving for any given file is clean?  I'd assume so, since there would be no point in saving data from an infected file.
Intel Atom D2700, 2 gig RAM, Win 7 x64 SP1 & IE-11, Firefox 51.0
(default). 320 gig HD, 15Mb DSL, Win firewall, Avast 12.3.2280 free, SpywareBlaster, MBAM Prem., Crypto-Prevent

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89286
  • No support PMs thanks
Re: Another question about VRDB
« Reply #1 on: September 15, 2006, 08:12:20 PM »
Interestingly enough my VRDB generation duration (around 7 minutes) isn't much different to my local disks, standard scan without archives (8.5 minutes), so it could well also be scanning those files covered by the VRDB.

I would have though that they would have to be scanned otherwise there isn't much point in recovering to a possibly infected file. Since I do both on-demand scans and VRDB generation manually as part of my regular system maintenance, I usually do the on-demand scan first and then the VRDB generation.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.5.6116 (build 24.5.9153.762) UI 1.0.808/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Another question about VRDB
« Reply #2 on: September 15, 2006, 08:34:34 PM »
When generating a fresh VRDB, does it ensure that the latest data "version" it's saving for any given file is clean?  I'd assume so, since there would be no point in saving data from an infected file.
Files are not scanned.
The three 'last' versions are saved. So, if the VRDB period is too short, you can store three infected/damaged file info there...  ::) ???
The default period is 21 days.
The best things in life are free.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11863
    • AVAST Software
Re: Another question about VRDB
« Reply #3 on: September 17, 2006, 08:32:23 PM »
Actually, they are. I.e. yes, infected files are not inserted into VRDB.

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89286
  • No support PMs thanks
Re: Another question about VRDB
« Reply #4 on: September 17, 2006, 08:44:42 PM »
Thanks for the confirmation Igor.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.5.6116 (build 24.5.9153.762) UI 1.0.808/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Another question about VRDB
« Reply #5 on: September 17, 2006, 10:45:47 PM »
Actually, they are. I.e. yes, infected files are not inserted into VRDB.
Did this change lately?
I mean, I've read that the VRDB period couldn't be so short that you'll get all infected versions in it...
The best things in life are free.

Offline igor

  • Avast team
  • Serious Graphoman
  • *
  • Posts: 11863
    • AVAST Software
Re: Another question about VRDB
« Reply #6 on: September 18, 2006, 12:04:12 PM »
No, it's been always like this.
But of course, you can't guarantee that avast! detects this threat as soon as it appears (the VPS update might take a while).
« Last Edit: September 18, 2006, 02:17:36 PM by igor »

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: Another question about VRDB
« Reply #7 on: September 18, 2006, 01:13:26 PM »
No, it's been always like this.
But of course, you can't guarantee that avast! detects this threat as soon as appears (the VPS update might take a while).
Sure. Thanks Igor. I'll change a little the explanation of avast4.ini file thread with this 'new' explanation in mind.
The best things in life are free.