Jump to content

[MERGE] Server 2012 R2 Backup and ESET File Security - Failure Compacting Virtual Hard Disk


Recommended Posts

Solution for Error:  There was a failure while compacting the virtual hard disk on the backup location. A device attached to the system is not functioning.

Windows Server 2012R2 Backup fails.

 

Solution:

 

You must change real time scan from all extensions to only scan infectable extensions.  This should resolve the issue.  Note:  Excluding the destination backup drive is not effective as a virtual drive is created during Backup.  

 

Since NOD32 does not allow exclusions without a specified drive letter, I had to change the following setting in NOD32:  Real Time File System Protection, Setup, Extensions.  Uncheck "Scan All Files".   

 

If Eset would allow blanket exclusions for certian file types, regardless of location, I could have excluded .vhd and .vhdx  extensions.  Unfortunately, this is not an option in NOD32.

 

 

Somewhat related Issue that may be of interest:
compacting the virtual hard disk(s) may take a long time
hxxp://support.microsoft.com/kb/2524602

Link to comment
Share on other sites

What version of ESET NOD32 are you using?

 

Since NOD32 does not allow exclusions without a specified drive letter, I had to change the following setting in NOD32:  Real Time File System Protection, Setup, Extensions.  Uncheck "Scan All Files".  

That's not true. You can exclude a whole drive if you want (although I really don't recommend you to do so).

 

If Eset would allow blanket exclusions for certian file types, regardless of location, I could have excluded .vhd and .vhdx  extensions.  Unfortunately, this is not an option in NOD32.

And that's wrong too. You can exclude a special file type from scanning - just exclude (for example) "*.vhd" and "*.vhdx".

 

More information about exclusions you can find here: How do I exclude files or folders from scanning in ESET Smart Security or ESET NOD32 Antivirus?

 

And because of your double post I'm not quite sure what ESET product you use. Do you use ESET NOD32 or ESET File or Mail Security?

 

 

But about you issue: I wouldn't recommend to exclude any files from scanning and also I would recommend to select the setting to "scan all file types".

 

Maybe someone with Windows Server 2012 can reproduce the issue and help you with troubleshooting it.

Edited by rugk
Link to comment
Share on other sites

Rugk makes good and correct points.

In addition, Nod32 should not be run on windows server.

File security is what you should be using, because it is preconfigured by ESET for a server, and to exclude important services servers use, right away by default.

Please let us know if you need assistance making the switch.

Link to comment
Share on other sites

Note:  This was posted in the home section here by mistake and again posted in the business section here https://forum.eset.com/topic/3861-server-2012-r2-backup-and-eset-nod32-failure-compacting-virtual-hard-disk/ , but the replies occurred here.

 

 

Note:  My original issue with Windows Backup had nothing to do with Eset after all. 

 

I am using ESET File Security for Microsoft Windows Server -  a product designed for servers:

hxxp://www.eset.com/us/business/products/file-windows/

 

In this product, if you select to exclude *.vhd  it automatically adds the drive letter when you click OK:

 

C:\*.vhd

D:\*.vhd

 

This strongly implies that if a new drive, say E, is added it will not exclude *.vhd on that new drive. 

I have not tested this by adding a new drive and going back to exclusions to check if it is added automatically.

 

This should be corrected by Eset, if not just the exclusion section which should technically be listed just as entered by the user:

 

*.vhd    --- Exclude any file with an extension of .vhd on any drive, anywhere, any time.

 

NOT:

 

C:\*.vhd

D:\*.vhd

Edited by MarcFL
Link to comment
Share on other sites

My mistake, you can exclude file extensions from any source in Advanced Settings -> Computer -> Antivirus and antispyware -> Real-time file system protection -> Threatsense engine parameter setup -> Setup -> Extensions. Please add desired extensions there that will not be scanned for threats.

 

An ESET Customer Care Representative has updated this case with the following information:

Our previous solution does not require that you disable the scan of all files. Please note the difference in wording when the "Scan all files" setting is checked/unchecked:

Enabled -> Files with the extensions listed below WILL NOT BE scanned for threats
Disabled -> Files with the extensions listed below WILL BE scanned for threats

Our recommendation is still add the extensions you want to exclude from scanning (e.g. VHD) to that list while the "Scan all files" setting is enabled.

Thank you for using ESET security products,
ESET Customer Care
North America
 

Edited by MarcFL
Link to comment
Share on other sites

The exclusion of file extensions can be placed in 2 locations.  In one location, mentioned above, it's easy to overlook the context change when "Scan all files" setting is checked/unchecked.

 

The rep's name was not in the email.

 

Thanks.

Link to comment
Share on other sites

  • 2 weeks later...
Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...