Calculating digests Error: Cannot find shadow copy of volume

[JardaCZ]

Dear community,

I installed Veeam Agent for Windows on Small Business Server 2011 (SBS2011). It's a package of Server 2008 R2, Exchange, SharePoint.

When I run backup of system volume, it fails with error:
Calculating digests Error: Cannot find shadow copy of volume System Reserved.

case #02075241

Veeam tech support told me:
[18.02.2017 13:36:11] <32> Warning Key container is corrupt, deleting...
[18.02.2017 13:36:11] <32> Error Keyset does not exist. Error code: -2146893802
[18.02.2017 13:36:11] <32> Error Failed to delete corrupted container
[18.02.2017 13:36:11] <32> Error An exception was thrown from thread [11532].

Could you please perform the following test?

diskshadow
>set verbose on
>set context volatile
>add volume {cbda5276-b84e-11e4-a536-xxxxxxxxxxxxx}
>add volume c:
>begin backup
>create
>end backup


I'm afraid because it's production environment and I don't want to try it.
Someone with same experience?

You can see screenshot of my disk management, shadow copies and Veeam LOG. With my comments...


Regards,
Jarda

[JardaCZ]

I can find this errors in event LOGs:

ID: 190
source: Veeam Agent
type: Error
description:
Veeam Agent 'Backup Job ServerName' finished with Failed.
Job details: Calculating digests Error: Cannot find shadow copy of volume System Reserved
Error: Cannot find shadow copy of volume System Reserved

ID: 2007
source: ESE
type: Error
description:
Information Store (2192) Shadow copy instance 3 aborted.

ID: 9782
source: MSExchangeIS
type: Error
description 1:
Exchange VSS Writer (instance f6ea6f9e-5c4a-4fee-b340-xxxxxxxxxxxx:3) has completed the backup of database 'Mailbox Database' with errors. The backup did not complete successfully, and no log files were truncated for this database.

description 2:
Exchange VSS Writer (instance f6ea6f9e-5c4a-4fee-xxxxxxxxxxxx:3) has completed the backup of database 'Public Folder Database 0968366386' with errors. The backup did not complete successfully, and no log files were truncated for this database.

ID: 8230
source: VSS
type: Warning
description:
Volume Shadow Copy Service error: Failed resolving account spsearch with status 1376. Check connection to domain controller and VssAccessControl registry key.
Error: NetLocalGroupGetMemebers(spsearch), 0x80070560, The specified local group does not exist.

[JardaCZ]

I just googled around this errors.

resolution for ID: 8230 source: VSS
https://social.technet.microsoft.com/Fo ... nessserver
https://support.microsoft.com/en-us/hel ... 1-standard
http://www.eventid.net/display.asp?even ... SS&phase=1

It's strange, because Windows Server Backup runs fine.

I did this
•open registry editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl
•backup this key, just in case you need to restore it later
•CHANGE the value to 0 for all accounts except the NetworkService account which I left at 1
•close registry editor
•open services.msc and restart Volume Shadow Service
•retry Windows Server Backup (Veeam Backup)

The error ID: 8230 source: VSS disappeared, but Veeam Backup still doesn't work.

remaining errors:
ID: 2007, source: ESE
ID: 9782, source: MSExchangeIS

[JardaCZ]

I also tried with no luck:

vssadmin list writers
all stable, no errors

increase timeout
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SPP
DWORD 32bit: CreateTimeout
VALUE: 1200000


!!! it looks like Exchange VSS provider cannot create snapshot because of heavy I/O load !!!

remaining errors:
ID: 2007, source: ESE
ID: 9782, source: MSExchangeIS

[Dima P.]

Hi JardaCZ,

Thanks for the sharing the investigation details. Sharing this info with QA folks. Will update this thread once I hear anything.

[JardaCZ]

Hi community,

Veeam support told me:
We have found a bug which is a root cause of the issue the bug will be fixed in the final release.

So I think it's success, thanks to Veeam support.
We all expect final release in the end of March.


Regards,
Jarda

[Dima P.]

Hi Jarda,

Thanks for the heads up! Indeed, after checking with QA team we realized this is a known issue and it’s going to be fixed in 2.0 GA.

P.S. GA is planned for the end of Q1, so most likely end of March