This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 83%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBF%3C/text%3E%3C/svg%3E)
Hi all,
I have a problem with a client server where backups are being broken. We use Unitrends for backup and everything was working fine until about August 18th. We run Server 2019 Standard and now we are getting backups failing pretty much every night. The logs say the the \EFI\Microsoft\boot\bcd file is locked and cannot be accessed. From some digging with Process Explorer it is being locked, along with bcd.log by the System process. Has anyone else had this happen and figured out a solution?
Thanks,
Brandon
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
May need to look for an option in Unitrends to skip locked or in use files. As a work-around you could use /export option to back it up.
https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/bcdedit-command-line-options
--please don't forget to Accept as answer if the reply is helpful--
Thanks for the response DS, but what I am trying to understand is why this is happening and how to fix it. If this was widespread among Server 2019 instances then Unitrends would be in major trouble. I am working with their support as well and they are not seeing this across many Server 2019 instances. Also to your point, if we exclude the Boot Configuration files recovering the entire system after a crash would not work, therefore kind of defeating the purpose. I have determined that the System process is locking these files but why did this start occurring on August 18th? I have numerous other Server 2012 machines not having this issue, but they do have different circumstances, such as they are VMs. But either way this was working and stopped working, did MS push an update that could have broke this?
Thanks for your thoughts.
Brandon
You might try confirming this by doing a system state backup.
--please don't forget to Accept as answer if the reply is helpful--
What we did to confirm, was exclude the System State from the backup. Once we did this the backup completed. As soon as we add the System State back in the backup fails with the same error that bcd and bcd.log are locked and can't be accessed. But here is the weird thing, if we run the backup manually every now and again, it will complete with the System State included. It is very weird.
Could be some timing thing to do with Unitrends. You might try confirming this by doing a system state backup from windows without the use of the third party tools.
--please don't forget to Accept as answer if the reply is helpful--
I will try that.
Thanks