Acronis VSS fails because C:\Device\snapman\Windows\NTDS is missing?
Hi All,
A fresh install of AB&R 11 Windows Server on Server 2008 resulted in failing backups from the beginning. The initial advice of a technician on chat was to switch VSS to Windows VSS provider.
This allowed backups to work.
I kept digging and saw one of the errors, in Event Viewer, that seemed to pinpoint a cause of the Acronis VSS-based backup's failure: lsass (784) An attempt to open the file "C:\Device\snapman\Windows\NTDS\ntds.dit" for read only access failed with system error 3 (0x00000003): "The system cannot find the path specified. ". The open file operation will fail with error -1023 (0xfffffc01). Acronis VSS provider always fails with the same error.
This is of course a server with active directory running. With this error message in hand, I decided to try something: I manually created the full directory structure C:\Device\snapman\Windows\NTDS. Sure enough, the backups started succeeding afterwards. Files placed into this directory during backups were edb.chk, edb.log, (and the first backup only, edbres00001.jrs and edbres00002.jrs). These files remain there after backups complete.
I've looked everywhere for references to these directories. Nothing useful on google, nothing in the registry, even did a binary grep of Acronis directories. Snapman.sys is obviously a component of AB&R. I spent 30 minutes on the phone demonstrating and discussing this issue. Still no answer.
The VSS writer, per 'vssadmin list writers', shows a 'Non-retryable' error message after the backups fail. Nothing useful in the output though.
Here's what AB&R shows in its log (abridged):
Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.
Error code: 0x70021
$module = "C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll"
Tag: 0xDF81DA2C74EC5084
Failed to unlock the volume snapshot.
Error code: 0x10C443
Tag: 0x14181C22EF45AFC7
The device is not ready
Error code: 0xFFF0
code = 2,147,942,421 (0x80070015)
Tag: 0xBD28FDBD64EDB8BC
Please note that this only happens on the C:\ drive, where AD is running. Using Acronis VSS on another drive succeeds, no problems. No \Device\snapman\ structure was necessary on the other attached drive.
Even though I've got backups running, it seems that something isn't quite right with the setup. I'd like to know if this directory should be created automatically, and if so, why it's failing. Or if I can configure it to use another standard directory. This machine had a Kaseya-managed True Image Echo install at one point. There are also a few security-related GPO's in place. Thanks for any insight into this.
-Matt
Hello Matt,
Thank you for your detailed post. I understand your concern, and would like to assist you with the problem.
I have contacted our Development team with the information you've provided (thank you for it). They've reported that they'd managed to reproduce the issue, and currently working on the fix. Unfortunately we have no time-frames available regarding when the fix will be ready. At the moment all we can do is recommend to use the workaround suggested by the support team.
I'm sorry for the inconvenience you've faced with support. I have found your case and forwarded the information about it to the Management team, rest assured they will investigate the cause.
Please also note that you can share your feedback with us directly via website feedback form. All comments are taken under consideration, your opinion is important for us.
Let us know if you have any questions or something is confusing you, I will be glad to clarify.
I look forward to it. Good to know my system isn't somehow hosed ;)
Thanks,
-Matt
Exact same thing has happened to our server. My question is how do we switch VSS to Windows provider until the fix arrives?
Hi Douglas
You can change this setting by following these steps:
- Edit your backups job
- Edit your Backup Options (near the bottom of the page)
- Select “Volume Shadow Copy Service” and set the snapshot provider to: “Software- System Provider”
- Select Ok, then Save the job
Just tested this with R0. The problem was NOT fixed. Still getting the exact same error. Looks like this one has been pushed back another several months, until R1?
-Matt
Does it still appear with "Software- System Provider” for VSS setting?
Nope, it never appeared with that in the first place. Just the 'Acronis VSS' causes the issue.
I updated to R0.5 last night (On Server 2008 32-bit). I am still getting the identical error with either Auto or Acronis VSS selected:
lsass (748) An attempt to open the file "C:\Device\snapman\Windows\NTDS\ntds.dit" for read only access failed with system error 3 (0x00000003): "The system cannot find the path specified. ". The open file operation will fail with error -1023 (0xfffffc01).
The R17437 changelog states:
The Acronis VSS provider is not properly installed on Windows Server 2008.
Is this supposed to fix the problem? I did an update from 17217.
Thanks,
-Matt
Hello Everyone,
Thank you for your posts.
The problem and the solution are described here: KB 23359
The only correct fix for the problem would be switching fully to MS VSS Provider in the backup options (Volume Shadow Copy Service section). Enable the option "Use Volume Shadow Copy Service (VSS)" => in Snapshot provider menu select the option Software - System provider.
Using workarounds with creating additional paths in the system is not safe and may lead to issues with Active Directory integrity inside of the backup.
Please let us know if you have additional questions.
Alexander