what is \?\volume \Boot\BCD

Question

I have a few windows servers that I am getting the following error on for backups (finished with exception)

2013-05-13 19:10:04 avtar Error <5139>: File access share error "\\?\volume{f1f1c4e9-9d3d-11e2-93e8-806e6f6e6963}\Boot\BCD" (code 32: The process cannot access the file because it is being used by another process). (Log #2)

I am unable to find out just what this is and if it is important or if it can be exclude (and if it can HOW to format the exclude)

So any windows admins out there know what this is?

ionthegeek · Accepted Answer

It looks like avtar is having difficulty accessing the boot partition. Does this happen during regular file system backups or during system state backups? Are the affected systems using EFI? System state backups do not currently support EFI. EFI support is scheduled for inclusion in the upcoming release (with the usual caveats that features and release dates are subject to change).

J_H_ · Answer

both the file backup and the VSS backup get the error.

windows 2008 servers and 2012

thank you for the info.

I will pass that along to the build group.

Any Idea how I can exclude this so I don't look at the exceptions every day?

J_H_ · Answer

All of the clients in question are at v6.1.101-87 thank you for the info

J_H_ · Answer

fyi - the bcdedit - does not show the EFT in the path

ionthegeek · Answer

For the filesystem backups, a similar error was reported to have been fixed in Avamar 6.1 so if the clients are running an older version, please try upgrading them to 6.1.1.

As far as system state restore goes, system state restore of EFI systems is not possible in current release versions of the software so your best bet is probably to skip Avamar system state backups for EFI clients. If you need to determine if a client is using EFI, the "bcdedit" command will show you this information.

EFI:

C:\Users\testuser>bcdedit

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\bootmgfw.efi

Windows Boot Loader

-------------------

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

Non-EFI:

C:\Users\testuser>bcdedit

Windows Boot Manager

--------------------

identifier {bootmgr}

device partition=C:

Windows Boot Loader

-------------------

identifier {current}

device partition=C:

path \Windows\system32\winload.exe

I wasn't able to find anything else interesting in the escalation database so if you continue to encounter this problem, I would recommend opening up an SR. I don't know if it's possible to exclude a volume in this way but if I were going to hazard a guess I would write:

--exclude=\\?\volume{f1f1c4e9-9d3d-11e2-93e8-806e6f6e6963}\Boot\BCD

I don't know the exact implications of doing this but since it's not being backed up anyway...

Avamar

what is \\?\volume \Boot\BCD

Was this post helpful?