NOD32 and Veeam

[chimera]

Hey,
Got a problem with backing up VM's with ESET NOD32 antivirus installed and running on the VM. Its causing all Veeam backups to fail. When Veeam kicks off VSS, NOD32 CPU usage goes ballistic and Veeam eventually timesout with an error:

VSSFreezer: Failed to prepare guest, wait timeout 600 sec.

Some other VM's fail with the following:

Repairing backup from previous rollback
Repair of backup "**vm**" machine was unsuccessful
Failed to delete backup file. Some records are still having reference to this file

Im about to do some detailed investigation, but to save me the time if anyones encountered this before and knows what the problem is, let me know.

Cheers

[chimera]

The first issue was (temporarily) resolved by disabling NOD32 A/V while Veeam ran - this of course is simply a workaround for now. Need to find out what part of NOD32 actually causes this.

The second issue ('repairing from previous rollback' error) was resolved as per this post...
http://www.veeam.com/forums/viewtopic.php?f=2&t=1296

[chimera]

also, the failure of the 2 x VM's (with NOD32) are incidentally both domain controllers - whether that makes a difference or not?

also on one of the other VM's, I get the following error:

Repairing backup from previous rollback
Repair of backup "xxxxx" machine was unsuccessful
TextFromTar failed
Client error: The system cannot find the file specified

What does this mean???

[Vitaliy S.]

Hello,

Great effort in troubleshooting! Well done!
As for your 3rd issue could you please open a ticket with Veeam Support, and send us all the logs at Help->Support Information, it would help us to investigate the issue.

[chimera]

Hi,

I have determined the Veeam backup that generates the error:

Repairing backup from previous rollback
Repair of backup "xxxxx" machine was unsuccessful
TextFromTar failed
Client error: The system cannot find the file specified

...is also due to a previous backup failing at some stage. As a workaround, I've removed that VM from the job and added it to another job instead (which is probably better suited anyway) Its backing up fine now in the other job - so not an issue with the virtual machine but something to do with Veeam trying to repair the previous rollback and failing. Anyways... I'll create a support ticket with the domain controller backup with NOD32 issue as that is still not resolved.

Cheers