Calculating digests error cannot find shadow copy of volume

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

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.

I also tried with no luck:

vssadmin list writers
all stable, no errors

increase timeout
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionSPP
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

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

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

Hello

I have been using Endpoint for about 1 month now and it worked wonderfully. One day I came home and saw that the backup stopped working. Have tried to reinstall the software but still having the same issue. The drive is accessible and seems nothing has changed since I installed it initially. Here is the error I’m getting

Has anyone seen this error?
Thanks

Yes I do see this in the logs:
The VSS service is shutting down due to idle timeout.

And this keeps starting:
The Software Protection service is starting.

Also get this:
The Software Protection service has completed licensing status check.

Will,

Unfortunately this means something is wrong… When your system writer is in Waiting for Completion or Non-retryable error, that VSS writer is the reason why no backups succeed anymore…

There could be many reasons why this happened… On older operating systems, you need to patch a lot, it could be another application that installed an additional VSS writer that doesn’t work happily with this one (not us, if that is what you are thinking now ) and in older versions of Windows Server we regularly saw a writer getting corrupt for no good reason at all…

— What OS are you using, and is it fully patched?
— Try restarting the device, and look if the writers are stable now before triggering a backup again
— Check services to see if the VSS services aren’t suddenly disabled
— Check in event log but specifically search for the words VSS, Shadow Copy or VolSnap (3 separate searches)

Let us know

Mike

Will,

Have you opened a support case?

Windows 7 Pro 64 bit with almost all patches installed.

Yes i have opened a case ticket

I am having the same issue. Windows 8.1 64-bit. Several successful backups have completed to external HDD. Now, same errors.

Did Veeam provide a solution?

My job activity:
9/8/2015 12:49:25 PM :: Preparing for backup
9/8/2015 12:49:36 PM :: Creating VSS snapshot
9/8/2015 12:50:05 PM :: Calculating digests Error: Cannot find shadow copy of volume WD My Book (E:)
9/8/2015 12:50:13 PM :: Finalizing
9/8/2015 12:50:31 PM :: Error: Cannot find shadow copy of volume WD My Book (E:)
:: Processing finished with errors at 9/8/2015 12:50:33 PM

Hello Brian,

Please open a support case thru Endpoint’s Control Panel > Support and post here the case ID. By the way is the device from the error a removable one (it looks like a USB drive)?

I had this issue and support asked me to change to use File level backup. I was able to get a successful backup.

But whats interesting is that in File level backup type mode you select Operating System from the list, it auto selects the volume with the OS from the list also ie C: and appends in italics that a volume backup will be performed. (Not what i was expecting! but neat.)

The realization of why this error appeared for me was now becoming obvious…

The Disk # in Disk Management of the OS had somehow changed for my select volumes in the Volume Backup.
The Volume Level backup configuration in VEB had the C: down as the disk to backup.
When the backup came along it was now not the same disk it was expecting and threw the error.
This was down to some shuffling of the Disk numbers in Disk Management. I had done some add/removal of disks (this endpoint is a server).
This is obvious even further as after taking a successful file level backup (as above) that when you review your backups in Restore Volumes you can see the Disk number has changed comparing the recent one taken to previous — its displayed at the top of the choose backup to restore dialog.
Further I was expected the VEB software to take a new full backup as part of a file level backup. NO it did do a volume backup and still only the changes as it continued to use CBT. Nice.

I thereafter re-configured the backup to do a Volume Backup and i rechose the specific volume again and now works.

Summary
Be careful adding/removing disks on endpoint as may re-shuffle volume/disk id’s and break VEB.

Thanks for the heads up Stuart!

But whats interesting is that in File level backup type mode you select Operating System from the list, it auto selects the volume with the OS from the list also ie C: and appends in italics that a volume backup will be performed. (Not what i was expecting! but neat.)

File backup mode is just a name — you can use volume level backup in conjunction with folder exlusion or folder backup only. Check Mike’s blog — a good explanation of all existing backup methods

This was down to some shuffling of the Disk numbers in Disk Management. I had done some add/removal of disks (this endpoint is a server).

So you just swapped the drives right while the Endpoint was set to perform an Entire PC backup or volume level backup?

So you just swapped the drives right while the Endpoint was set to perform an Entire PC backup or volume level backup?

Endpoint was set to Volume Level Backup and the C: volume was selected only. (This Endpoint is also a Veeam Proxy and Respository and Tape Server with SAN FC disks attached.)
I did some MPIO work on this Endpoint for new repository disks.
Thereafter the backups failed.
The MPIO work I believe was the root cause of getting errors as described, and must have done reassignment of Disk numbers, thereafter Disk number for C: was no longer valid or the same as before.

Присоединяйтесь к сообществу, чтобы узнавать новое и делиться знаниями

Зарегистрироваться

Merhabalar arkdaşlar,

Windows Server 2012″de Veem Backup ile sorunsuz backup alırken bir süre sonra backup alma hatası verdiğinin farkına vardım tüm google ve forum sayfalarında yazılan çözüm önerileni uyguladım fakat backup işlemlerini başlatamadım konu hakkında tecrübesi olan ve çözebilen arkadaşlar varmıdır acaba.

Gönderildi : 23/04/2018 15:04

(@hakanuzuner)

Gönderiler: 32135

Illustrious Member Yönetici

Merhaba,

Logları paylaşmanız mümkün mü? 

Danışman — ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 23/04/2018 16:12

(@ismaildilme)

Gönderiler: 43

Trusted Member

Merhaba Hakan Bey,

İlginiz için teşekkür ederim log kayıtalarını paylaşıyorum.

Log Name: Veeam Agent
Source: Veeam Agent
Date: 23.4.2018 10:53:42
Event ID: 190
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: GUNDUZSRV
Description:
Veeam Agent ‘Backup Job GUNDUZSRV’ finished with Failed.
Job details: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{ca4550bf-eb7b-4461-8746-0f553f26a6e7}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].
Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{ca4550bf-eb7b-4461-8746-0f553f26a6e7}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].
Event Xml:
<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
<System>
<Provider Name=»Veeam Agent» />
<EventID Qualifiers=»0″>190</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime=»2018-04-23T07:53:42.000000000Z» />
<EventRecordID>2120</EventRecordID>
<Channel>Veeam Agent</Channel>
<Computer>GUNDUZSRV</Computer>
<Security />
</System>
<EventData>
<Data>2deb68e7-20d1-4e59-aceb-4d42b9111024</Data>
<Data>637fcf28-9cb7-4488-a417-66d72730cccd</Data>
<Data>2</Data>
<Data>4000</Data>
<Data>6</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>1</Data>
<Data>Veeam Agent ‘Backup Job GUNDUZSRV’ finished with Failed.
Job details: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{ca4550bf-eb7b-4461-8746-0f553f26a6e7}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].
Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer’s data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{ca4550bf-eb7b-4461-8746-0f553f26a6e7}]. Writer’s state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f0].</Data>
</EventData>
</Event>

Gönderildi : 23/04/2018 17:54

(@turancoskun)

Gönderiler: 4111

Üye

merhaba,

kullandığınız veb versiyonu nedir ?

bir versiyonda benzer bir bug vardı diye hatırlıyorum, devamında versiyon update ile giderilmişti.

****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 24/04/2018 03:46

(@cahityolacan)

Gönderiler: 513

Super Admin

Bu Veeam Endpoint değil mi ? Sanal Değil Fiziki makine yedeği sanırım doğrumu ?

VSS servisinizi bir kontrol edin. VSS ile entegreli çalışıyor user pass değişimi yada servisin geç başlaması vb gibi sorunlardan dolayı yapabiliyor. 

Gönderildi : 24/04/2018 11:16

(@hakanuzuner)

Gönderiler: 32135

Illustrious Member Yönetici

Merhaba

VSS sorunu, bunun bir kaç nedeni olabilir, SQL yedeği aldığınızı görüyorum limite takılmış olabilir aşağıdaki yönergeleri takip eder misiniz?

https://www.veeam.com/kb1915

Danışman — ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 24/04/2018 17:19

(@ismaildilme)

Gönderiler: 43

Trusted Member

Veem Versiyon : VeeamAgentWindows_2.1.0.423

Sql dışında herahangi bir klasorü hedef gösterdiğimde farklı bir hatayı alıyorum.

24.4.2018 16:26:58 :: Calculating digests Error: Cannot find shadow copy of volume System Reserved
24.4.2018 16:27:00 :: Error: Cannot find shadow copy of volume System Reserved
24.4.2018 16:27:02 :: Processing finished with errors at 24.4.2018 16:27:02

Gönderildi : 24/04/2018 19:54

(@hakanuzuner)

Gönderiler: 32135

Illustrious Member Yönetici

VSS de sorun var bu durumda VSS debug açmanız gerekli.

Danışman — ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 24/04/2018 20:53

(@turancoskun)

Gönderiler: 4111

Üye

Veem Versiyon : VeeamAgentWindows_2.1.0.423

Sql dışında herahangi bir klasorü hedef gösterdiğimde farklı bir hatayı alıyorum.

24.4.2018 16:26:58 :: Calculating digests Error: Cannot find shadow copy of volume System Reserved
24.4.2018 16:27:00 :: Error: Cannot find shadow copy of volume System Reserved
24.4.2018 16:27:02 :: Processing finished with errors at 24.4.2018 16:27:02

backup job üzerinde, kaynak için system reserved partition seçmeden test etmeyi denediniz mi ?

****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 27/04/2018 03:17

(@ismaildilme)

Gönderiler: 43

Trusted Member

Evet denedim malesef sorun devam ediyor,

Gönderildi : 29/04/2018 02:28

(@turancoskun)

Gönderiler: 4111

Üye

Evet denedim malesef sorun devam ediyor,

Hakan hocanın belirttiği vss debug’la birlikte, farklı bir backup agent kullanarak test edin.

****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 29/04/2018 05:02

(@ismaildilme)

Gönderiler: 43

Trusted Member

vss debug tam olarak nasıl yapılıyor bilmiyorum bu konuda yardımcı olabilirmisiniz acaba.

Gönderildi : 03/05/2018 00:22

(@hakanuzuner)

Gönderiler: 32135

Illustrious Member Yönetici

Burada detaylı bir anlatım var.

https://kb.acronis.com/vsslog

Danışman — ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 03/05/2018 18:04

(@turancoskun)

Gönderiler: 4111

Üye

referans adreste 2. ve 3. adımıda inceleyebilirsiniz.

VSS Error Troubleshooting Guide Part 1 of 3

****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 06/05/2018 15:27

(@ismaildilme)

Gönderiler: 43

Trusted Member

Bilgilendirme için teşekkür ederim sorunu çözemeyince acronis backup sistemini kurdum ve sorunsuz yedekleme işlemini yapıyorum.

Başta Hakan bey olmakla beraber bilgisine esirgemen cevap veren tüm arkadaşlara teşekkür ederim.

Gönderildi : 10/05/2018 19:20

(@hakanuzuner)

Gönderiler: 32135

Illustrious Member Yönetici

Geçmiş olsun, bilgi ve geri dönüş için teşekkürler.

Danışman — ITSTACK Bilgi Sistemleri
****************************************************************
Probleminiz Çözüldüğünde Sonucu Burada Paylaşırsanız.
Sizde Aynı Problemi Yaşayanlar İçin Yardım Etmiş Olursunuz.
Eğer sorununuz çözüldü ise lütfen «çözüldü» olarak işaretlerseniz diğer üyeler için çok büyük kolaylık sağlayacaktır.
*****************************************************************

Gönderildi : 10/05/2018 23:42

Users found this page by searching for:

1. event id 36 49158

   ,

2. STORAGE#Volume# #000000001C300000#

   ,

3. the shadow copies of volume c: were aborted because the shadow copy storage could not grow due to a user imposed limit.

   ,

4. ID 36 The shadow copies of volume C:…MVolumesReplica1cd90fed-ff74-4d12-8145-2e8da7b5d67e were aborted because the shadow copy storage could not grow due to a user imposed limit.