This is a problem which appears to have resurfaced after reportedly being fixed in Symantec. The Symantec support person asked that I post a question in Technet to see if we can get a quicker answer:
Error in deletion of [C:\System Volume Information\EfaData\SYMEFA.DB] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 1F883BB7-A6AA-4130-AB7D-0849DBBE2D8C
Caption : Backup Using Saved State\VM-Test
Logical Path:
*-----------------------------*
I've installed Windows Server 2012 Standard on the host, and am backing up a W2K12 Virtual Machine. I have deleted the previous scheduled backup and then recreated a new backup with just one virtual machine. If I delete the W:\WindowsImageBackup sub-folder (I renamed the "live" sub-folder temporarily) the VM is backed up OK the first time. If I try to back up a second time, I get the pruning error.
I have added the following exclusions:
VM locations:
C:\VHDs\*
T:\*
U:\*
V:\*
VM Extensions:
vfd
vhd
vhdx
WSB drive:
W:\*
DPM 2012 exclusions:
C:\Program Files\System Center 2012\DPM\DPM\bin\DPMRA.exe
C:\Program Files\System Center 2012\DPM\DPM\Temp\MTA\*
C:\Program Files\System Center 2012\DPM\DPM\XSD\*
C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe
The DPM Services were disabled and stopped.
AntiVirus: Symantec Endpoint Protection Small Business Edition Version 12.1.2100.2093
(12.1-RU2-MP1) This version was supposed to have a fix for all this.
Symantec re-installed this with me with only the "Virus and Spyware Protection" components included and double checked the exclusions list.
Disabling Symantec is not enough - it has to be uninstalled in order for the backup to work again.
The test virtual machine was stopped at the time of the backup and has one fixed size VHDx.
The Symantec Support person was hoping someone from Microsoft might be able to advise if there were any other exclusions that could be considered.
Strangely, this has been working fine for the past couple of weeks. It started acting up once I attempted backing up a VM with BitLocker encrypted VHDx's. (Not this test VM). Don't know if this was just a coincidence or if there is any connection. I have also been using Virtual Floppies, Differencing Disks, and Snapshots on other VMs.
When watching Resource Monitor, during the backup, it looks like ALL the virtual machine VHDs are opened and at least partially read, even though they are not running and not included in the backup.
Any suggestions would be helpful.
Thanks,
Bob.
Error in deletion of [C:\System Volume Information\EfaData\SYMEFA.DB] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 1F883BB7-A6AA-4130-AB7D-0849DBBE2D8C
Caption : Backup Using Saved State\VM-Test
Logical Path:
*-----------------------------*
I've installed Windows Server 2012 Standard on the host, and am backing up a W2K12 Virtual Machine. I have deleted the previous scheduled backup and then recreated a new backup with just one virtual machine. If I delete the W:\WindowsImageBackup sub-folder (I renamed the "live" sub-folder temporarily) the VM is backed up OK the first time. If I try to back up a second time, I get the pruning error.
I have added the following exclusions:
VM locations:
C:\VHDs\*
T:\*
U:\*
V:\*
VM Extensions:
vfd
vhd
vhdx
WSB drive:
W:\*
DPM 2012 exclusions:
C:\Program Files\System Center 2012\DPM\DPM\bin\DPMRA.exe
C:\Program Files\System Center 2012\DPM\DPM\Temp\MTA\*
C:\Program Files\System Center 2012\DPM\DPM\XSD\*
C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe
The DPM Services were disabled and stopped.
AntiVirus: Symantec Endpoint Protection Small Business Edition Version 12.1.2100.2093
(12.1-RU2-MP1) This version was supposed to have a fix for all this.
Symantec re-installed this with me with only the "Virus and Spyware Protection" components included and double checked the exclusions list.
Disabling Symantec is not enough - it has to be uninstalled in order for the backup to work again.
The test virtual machine was stopped at the time of the backup and has one fixed size VHDx.
The Symantec Support person was hoping someone from Microsoft might be able to advise if there were any other exclusions that could be considered.
Strangely, this has been working fine for the past couple of weeks. It started acting up once I attempted backing up a VM with BitLocker encrypted VHDx's. (Not this test VM). Don't know if this was just a coincidence or if there is any connection. I have also been using Virtual Floppies, Differencing Disks, and Snapshots on other VMs.
When watching Resource Monitor, during the backup, it looks like ALL the virtual machine VHDs are opened and at least partially read, even though they are not running and not included in the backup.
Any suggestions would be helpful.
Thanks,
Bob.
