No space used by DPM shadow copy volume

Hi,
Please help me to understand more DPM shadow copies.
Actually when exactly the shadow copies are getting created? Whether it is during synchronization backup or express full back up or both?
Please see the below snap. It is disk utilization report of one week for exchange backup. I have configured protection group as every 30 min synchronization backup & every day express full backup for 2 days of retention range.
So here I want to understand that why there is no any space used for shadow copies though my both backups (synchronization & express full) are running successful.

Hi,
If you are using DPM 2012 R2, this is a known issue that will be fixed in the next update. As an alternate, run "vssadmin list shadowstorage" from administrative command prompt.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Similar Messages

Used and allocated Shadow Copy Storage space is showing values in GB .

Hi All ,
This is an production issue and i need an urgent help on this case.
In my environment i am having exchange server 2013 in DAG extended with three sites.On that i am having two mailbox servers in the production site and one mailbox server in remaining two sites.
we have mounted all the mailbox databases in one production mailbox server.Those databases are present in LUN mapped to the production mailbox servers from SAN storage.
Issue :
Few of the mailbox databases are occupying too much of size on the LUN than it's original size.
Say for instance i have kept the mailbox database called "test" which is present on the LUN with the size of 190 GB.On that whole space the mailbox database is occupying only 100GB but on the diskmgmt and also on the explorer it is showing
only the free space as 17 GB.
Finally we have run the below mentioned command and found that the used and allocated shadow storage is occupying the size around 34 GB.
Attached snap for your reference :
Question : How to reclaim the space occupied by the shadow copy storage to the LUN ? If possible someone tell me why this issue is happening ?
Thanks & Regards S.Nithyanandham

Hi,
According to my research and technology, it’s caused by Volume Shadow Copy Service which is used to backup infrastructure for the Microsoft operation systems, as well as a mechanism for creating consistent point-in-time copies of data known as shadow copies.
We can use VssAdmin to create, delete, and list information about shadow copies. More details about Volume Shadow Copy Service, for your reference:
https://technet.microsoft.com/en-us/library/ee923636(v=ws.10).aspx
Besides, this issue may be related to Windows server. I recommend you to contact to Windows Server Team so that you can get more professional suggestions, please refer to:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Recovering from Old Shadow Copy Cache System Files

Hello,
We have a client who had data corruption on a large scale (virus) and did not have an active backup. Shadow Copy was enabled, but failed when attempting to restore using built-in Shadow Copy recovery. Folder and File level recovery failed.
We were able to use a tool called Z-VSSCopy to restore file-by-file, but as that was underway (days) the shadow copy service continued to run and eventually ran out of space, overwriting the shadow copies we were restoring from.
I know, I should have modified the schedule or at least increased the available size for shadow copies, but that is a lesson learned too late.
In viewing the shadow copy data in the \System File Information folder, I saw that the copies were in fact deleted, but I noticed two files that were from a month ago.
Z-VSSCopy and built-in are not recognizing them (or vssadmin) but I can see the data is still there. One is 300+ MB and the other 100+ MB.
Is there a way I can force recovery using data contained in these files, or are they lost?
I'm currently running a Data Recovery program in hopes I can recovery anything, but since there has been significant writing on this disk since the incidence, I have little hope.
Any help is GREATLY appreciated. Thanks.

Hi,
Generally if a previous version is not recognized by system, we may not able to recover the data inside.
If you can still see some VSS files, please test if they could be recognized by command line:
vss list shadows
If one of them could be recognized, it will be listed like this:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Contents of shadow copy set ID: {3020fef8-e11b-4b45-b26f-8fec24a2bd27}
Contained 1 shadow copies at creation time: 2013/10/28 21:09:33
Shadow Copy ID: {b340c998-6ae5-459a-8e15-7a81188242c7}
Original Volume: (G:)\\?\Volume{d35a24f1-3f7a-11e3-be86-f01faf2a379a}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Originating Machine: LAP-SHAN.fareast.corp.microsoft.com
Service Machine: LAP-SHAN.fareast.corp.microsoft.com
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: DataVolumeRollback
Attributes: Persistent, No auto release, No writers, Differential
Please check the timestamp to make sure it is the snapshot you are looking for.
If it is listed, try to create a symbolic link:
mklink /d c:\shadow123 \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\
*Note:add a back-slash in the end of this command line.
If this will work, you can access c:\shadow123 to get the files.
If you have any feedback on our support, please send to [email protected]

"DPM uses the Volume Shadow Copy Service (VSS)"

"DPM uses the Volume Shadow Copy Service (VSS) to create a snapshot of the protected data."
According to MS (http://technet.microsoft.com/en-us/library/bb808827.aspx)
Does that mean I have to set asides space on the protected server (a file server), so it can store shadow copies, and the DPM server taps into those shadow copies to create its recovery points etc?
Thanks

Hi Joe,
when you are protecting a file server. DPM will implement a change journal to record all the blocks that have been changed.
Then once the sync starts. The journal is interrogated and will tell DPM which file have been changed.
Then the VSS writer makes a copy of these data and send them to DPM.
You don't need additionnal space or to create a new folder on your server.

[2008R2] Prevent event : The shadow copies of volume D: were deleted because the shadow copy storage could not grow in time

During the restore of data using VSS Snapshots it deleted all the snapshots, this event was written in the system log :
The shadow copies of volume D: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
It only restored 20 GB of data and there should be plenty of space in the Shadow copy storage
Used Shadow Copy Storage space: 2.692 GB (0%)
Allocated Shadow Copy Storage space: 5.397 GB (0%)
Maximum Shadow Copy Storage space: 694.752 GB (18%)
When there isn't enough space it should start to delete the oldest snapshots to free up additional space, but it deleted
all the snapshots. The problem is the IO but how to prevent this from happening again?

Hi,
Since the shadow copy storage space doesn’t run out, the issue could be due to the Volsnap.sys driver has encountered excessive I/O activity.
You could refet to the article below to resolve the issue. This article is for Windows 2003 but it will also help on Windows 2008 R2 system.
Error message when a Windows Server 2003-based computer has a high level of I/O activity: "The shadow copies of volume Volume_Name were aborted because the diff area file could not grow in time"
http://support.microsoft.com/kb/925799
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

The shadow copy of volume E: were aborted because the shadow copy storage failed to grow

Hello there,
I am facing an issue regarding DPM 2010 backup.
Every time my tape backup is being failed and the error is "The shadow copy of volume E: were aborted because the shadow copy storage failed to grow" .
My protected server is an win 2008R2 File server which is getting backed up from DPM 2010 server.
The total space of E: is 700 GB out of which 750 MB space is free.
So i am quite confused how much space should be free in protected server drive for successful backup.
It would be great if someone could help me regarding this matter.
Thanks in advance.
Regards, Ishuv

Hello,
Though it is written that minimum space required is 300 MB but i still do have 700 MB free out of 759 GB in my protected server drive (E:).
The error detail is ;
Source: Volsnap
Event ID: 35
Error General: "The Shadow copies of volume E: were aborted because the shadow copy storage failed to grow."
The backup server is DPM 2010 attached with IBM tape library which have LTO 5 cartridge.
Protected server is Win2k8R2 file server. 'E:' drive total space is 759 GB in which 700 MB is free.
So , as per my understanding from the error above is VSS is unable to grow because of limited free space in the specific E drive. In Drive (E:) there is only 700 MB space free. Now my question is how much free space should be there in the protected server
drive to complete the backup successfully by the DPM 2010 server which is storing the backups in IBM LTO5 tape library.
Is there someone who had faced this issue. Please help!!
Regards,
Ishuv
Regards, Ishuv

Not enough space to create shadow copy Windows 8.1

I receive "There is not enough disk space to create the volume shadow copy on storage location." error on Lenovo IdeaPad when trying to create System mage Backup. When I check "Disk mgmt." console all volumes shown to have 100% free space.
Does anyone have a remedy for this problem?

It's kind of impossible for all volumes to have 100% free space if you're running Windows from one of them, eh?
But to get more space on a volume to make shadow copies do this (excerpted from my book). Note that this assumes you're using a Start menu replacement tool, but the same concepts apply when using the Start just substitute "Press
the Win key" for "Click Start".
Here's how to increase the depth of your System Restore history:
Click Start, type protection into the search box, and click
SystemPropertiesProtection.exe when it comes up.
Click on your C: drive in the Protection Settings
box to highlight it.
Click the [ Configure ] button.
Choose the ( ) Turn on system protection setting if it is not on.
Assuming you have sufficient disk space, increase the Max Usage slider
until you have allocated at least 20 GB of storage for System Restore settings. This will give you a nice, deep multi-week System Restore history if ever you should need it.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Backup Fail with Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider, Event ID 12293, error returned while creating the volume shadow copy 0x8004230f,

We are using TINA backup solution and windows 2003 backup is failling with VSS error.
For testing purpose we initiate a system state backup (or any file backup) with the help of windows 2003 ntbackup.exe and found it is failing with below error.
Backup error report.
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Backup.bkf created 28/05/2014 at 06:34"
Volume shadow copy creation: Attempt 1.
Error returned while creating the volume shadow copy:0x8004230f.
Error returned while creating the volume shadow copy:8004230f
Aborting Backup.
The operation did not successfully complete.
We check event viewer and found below error event.
Event Type:
Error
Event Source:
VSS
Event Category:
None
Event ID:
12293
Date:
28/05/2014
Time:
05:48:10
User:
N/A
Computer:
CQ329TOS
Description:
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if
volume is supported. [0x8000ffff] [hr = 0x8000ffff].

Resolution:
After getting this error we check Shadow Copy provider and writer health and fond it is fine.
To get shadow copy providers details use below command.
Command: vssadmin list providers
Command output
C:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7
To get shadow copy writers health
Command: vssadmin list writers
Command Output.
C:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {333e02cd-d9ec-43c8-9b45-39691ad1b351}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {800877a5-e13d-47a3-8f99-ebd4d3b3fd12}
   State: [1] Stable
   Last error: No error
Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {63400aa0-a17f-4121-9483-1cd226f03238}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {e13cb72b-84fa-4c86-86d8-48f523aafc9a}
   State: [1] Stable
   Last error: No error
Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {ce63b3a0-e038-4e56-9d07-929f256639de}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {008e8714-ed6d-4288-81ce-4b0b1ec41294}
   State: [1] Stable
   Last error: No error
Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {e22a8953-a52c-4a76-bec0-8773122cbff8}
   State: [1] Stable
   Last error: No error
Next I check Shadow Copies details from volume properties (right click on C or other drive then select properties then click on Shadow Copies Tab) and found it is showing the same error code..
From this error it is clear that the issue is inside the registry hive and due to junk hive shadow copies services not able to working properly.
For me the server have two disk we check disk signature at MBR and found the disk signature was.
Signature disk 0 : 9351912b
Signature disk 0 : FDFBE035
But at registry we found lot of nonexistance signature. Which indicate lot of junk valu inside registry.
Now how can we resolve this issue?
It is very simple just delete the registry key “volume” (registry key “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\STORAGE\Volume”) and reboot the server it will “Volume” registry hive automatically.
Note:
When you remove registry key it is showing error unable to delete, then please right click on it select permission then take ownership and assign full permission to your login account.
Please be careful when you delete registry key because system can fully crashed if you delete or modify wrong registry key.
Your can take a backup of the registry key by exporting.

The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the error 0x80042316

When using Microsoft Backup on a Windows Server 2008 SP2 (not R2 - [Microsoft version 6.0.6002]) I get the error "The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the
error 0x80042316"
The odd thing is that when I start the backup manually, it works fine. When it runs automatically the error appears.
When doing a SFC /scannow I do get errors that can't be corrected.
Is there anything short of rebuilding this machine (It's a DC and the only one this office has) I can do to fix this?

Hi,
0x80042316 means "Another shadow copy creation is already in progress". This error could occur when another VSS instance is running.
Is there any third party backup application installed? Try to uninstall it to see the result. And please also check if there is another backup schedule which causes the conflict.
Meanwhile please provide the result of:
vssadmin list providers
vssadmin list writers
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi,
I do have Crashplan ProE running. It started at 1900 and the Windows Backup starts at 2000. I have modified Crashplan not to start until 2300 to see if that helps.
Also:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
AND:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f0c7ee55-5885-4894-8dd3-14fffbdd4d2e}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {017a0133-7577-4322-b513-04f72404b70a}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b17d670-9ea8-4ff1-a59e-b474f4b893db}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {56aad1bf-9bf1-4fde-b2f4-a706577c632d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e942d09d-276e-450a-9bf4-b1d5abe6af8a}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3737164b-61ac-454c-b1f7-42f2620f10db}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {39458257-aca4-481e-a302-994f3eb1e9a3}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {6a8ab4aa-760c-4102-a27f-58f570c9c572}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {53577013-8397-448e-9a25-c7cac08aa0a8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ee2c9173-92e7-455c-8f73-601647c0ddb2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b1f60392-9dfd-4e3a-bda6-3dc2cb622ba4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a328aede-78f0-448e-9c36-e8379e9fe2a8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c39fa334-5c9d-4906-a3b5-33c3444948e6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {3c9c5584-b5fd-48cf-8541-0c8bfa585ca0}
State: [1] Stable
Last error: No error

Shadow Copy feature on Servers with DPM

Hello There,
Is it a recommended configuration to have Shadow Copy enabled on the file servers which are also being backed up by DPM? Please suggest.
And what are the pros and cons of using this mixed configuration.
Regards,
maqsood
Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

Hi,
Adding Pros and Cons.
Local shadows enabled on the DPM protected computers.
PRO - Clients will get previous versions of files directly off of the protected server. May be faster copy depending on network topology and speeds.
PRO - Server owner has more control over the length of time previous versions are maintained based on shadowcopy storage limits.
CON - Uses local storage on file server, so may limit shadow copy storage size.
CON - Users will never see previous version on the DPM server, so that may limit self-recovery of file if they are maintained for a longer time on the DPM Server and not available in local shadow copy.
CON - Unless educated, clients (users) may not know that backups of files are available on the DPM server, so may settle for a previous version available to them only from the file server instead of asking for a restore for a more desirable version from
help desk.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Does deduplication and Volume Shadow Copy work together?

Hi!
I have a fileserver with five 2TB-disks on it on a 2012 R2 server. I want to enable dedup on it that according to DDPEval.exe would save ~40%. I would also like to enable Volume Shadow Copies on the volumes so the the end user easily could restore removed
files and folders.
I have not found anything from microsoft about use both these features on the same volume, is it supported?
I have done some searching and found that for some users the say that dedup would change so much on the snapshots that it have to delete older snapshots, even though not much data have changed, the dedup force VSC to delete old snapshots.
Any experience with these features co-located on the same volume? Do I need to choose just one of them to use on my volumes?
Thanks!

Hi,
Based on my research, the Shadow Copy and Deduplication could be used together in a Windows Server 2012 R2. The deletion of the old snapshots could be due to the Volume for which the shadow copy being created is more than 64 TB. Volume Shadow Copy Service supports
a volume size of up to 64 TB.
For more detailed information, you could refer to the article below:
Windows 2012 R2 Data Deduplication Leverages Shadow Copies: “LastOptimizationResultMessage : A volume shadow copy could not be created or was unexpectedly deleted”.
https://workinghardinit.wordpress.com/2014/07/01/windows-2012-r2-data-deduplication-leverages-shadow-copies-lastoptimizationresultmessage-a-volume-shadow-copy-could-not-be-created-or-was-unexpectedly-deleted/
Please Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please
make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'

Hi there,
Currently only partial backups are being completed.
I receive the following error:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {B8818795-2E27-44A3-85AB-D4C3DDBD288E}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 5
Failure Result: 80042336
Application Result: 80004005
Application Message: (null)
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Logical Path: (null)
Component Result: 800423F3
Component Message: Failed to create the volume shadow copy inside of virtual machine 'SBS-SVR'. (Virtual machine ID 9E70CA9C-B992-425D-B091-95B76763BE39)
File Spec: C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines\\9E70CA9C-B992-425D-B091-95B76763BE39.xml Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM_404D40C1-A532-4272-AE8B-251C4A03B4F3.avhdx Recursive: 0
File Spec: C:\Users\Public\Documents\Hyper-V\Virtual hard disks\\SBS-SVR-SYSTEM.vhdx Recursive: 0
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 9E70CA9C-B992-425D-B091-95B76763BE39
Caption : Backup Using Child Partition Snapshot\SBS-SVR
Logical Path:
Error : 80780175
Error Message : Component was skipped from volume shadow copy.
Detailed Error : 800423F3
Detailed Error Message : The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.
The success file is as follows:
Backup of volume \\?\Volume{72ec559c-60ca-11e2-93e8-806e6f6e6963}\ succeeded.
Backup of volume C: succeeded.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
In the event logs: application, i found this:
The backup operation that started at '‎2014‎-‎05‎-‎18T11:00:22.221374600Z' has failed to back up volume(s) ''. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
Some errors that are occuring that may be linked are:
Event Viewer, Application and Service Logs, Microsoft, Windows, Hyper-V-VMMS (the below is occuring every 2 minutes)
Failed to register the service principal name 'Hyper-V Replica Service'.
Failed to register the service principal name 'Microsoft Virtual System Migration Service'.
Failed to register the service principal name 'Microsoft Virtual Console Service'.
Upon some research I tried the following without much luck:
http://support.microsoft.com/kb/2761899
http://social.technet.microsoft.com/wiki/contents/articles/1340.hyper-v-troubleshooting-event-id-14050-vmms.aspx
Specs:
Microsoft Windows Server 2012 Standard x64
6.2.9200
ProLiant ML350e Gen8
VM: Microsoft® Windows Server® 2008 Standard FE x64
6.0.6002 Service Pack 2
Look forward to any help.
John

Hi John,
Please run “vssadmin list writers” command to check the VSS writer status. There is a similar thread, please go through it to help troubleshoot this issue:
Windows 2012 Backup for HyperV failed with error code '0x80780049'
http://social.technet.microsoft.com/Forums/windowsserver/en-US/f1a0c9c6-7b4c-409c-b4da-c145b8b59eb1/windows-2012-backup-for-hyperv-failed-with-error-code-0x80780049?forum=winserverhyperv
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

System State Backup - 2008R2 - Volume Shadow Copy Error

I am attempting to do system state backup in my Test environment. I am running Hyper-V on a standalone "sandbox" server. I have configured a semi-duplicate environment.
We are updating the schema soon, and I would like to do a System State restore for practice and I haven't actually had to do one in about 10 years.
I am running 2008R2 DC as a VM in my Hyper-V environment. It has a C: and E: volume, VSS is enabled on e: and set to Unlimited. I set my set "BackupLocation=e:\adbackups" and attempt to run wbadmin.exe start systemstatebackup -backupTarget:"E:"
(with quotes or without it still fails.
My error from command is Error - Volume Shadow Copy Service operation error (0x800423f4) which appears to be a generic error. In the Backup Event Viewer it shows as Event ID 9, another generic error.
I am running as Domain Admin, and I checked that I have Backup Operator rights. Volume Shadow Copy service is running.

Hello Chris,
This issue occurs if any of the virtual disks attached to the guest VM was created by using the option to copy the contents of a physical disk. Please refer the below mentioned MS KB..
Backup of a Hyper-V virtual machine fails with error 0x800423f4 if the disk signature on a virtual hard disk is the same as a physical disk on the Hyper-V host
http://support.microsoft.com/kb/975695
Sincerely, Asifkhan -- Please mark my post helpful if it was really helpful to you.

ERROR in creating Shadow Copy: VSS_E_HOLD_WRITES_TIMEOUT

Hi,
We have custom VSS HWProvider and I am trying to create a shadow copy on x64 windows 2k3 server,
using following command:
C:\> vshadow.exe -p -nw -t =test1.xml J:
VSHADOW.EXE 2.2 - Volume Shadow Copy sample client
Copyright (C) 2005 Microsoft Corporation. All rights reserved.
(Option: Persistent shadow copy)
(Option: No-writers option detected)
(Option: Transportable shadow set. Saving xml to file 'test1.xml')
(Option: Create shadow copy set)
- Setting the VSS context to: 0x00000039
Creating shadow set {6654de2c-5000-48e6-afb9-64e22565acbc} ...
- Adding volume \\?\Volume{f0afe5a5-4a2f-11dc-bb12-001143de30f2}\ [J:\] to the s
hadow set...
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
Error during the last asynchronous operation.
- Returned HRESULT = 0x80042314
- Error text: VSS_E_HOLD_WRITES_TIMEOUT
- Please re-run VSHADOW.EXE with the /tracing option to get more details
here J:\ is a 100 MB NTFS partition, protected by custom backup application.
Event viewer has following error in Application Log:
"Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{f0afe5a5-4a2f-11dc-bb12-001143de30f2}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000]"
(Note: It works for win32 server.)
Though there is some information regarding this bug on MSDN, I could not proceed.
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2.3790.1830&EvtID=12298&EvtSrc=VSS&LCID=1033
Kindly help me.
Thanks,
VNY.

If SnapDrive 6.4 or 6.4.1 is in use, consider upgrading to 6.4.2 due to a known issue in bug 631829, which results in unnecessary VSS_HOLD_WRITES_TIMEOUTS errors,
due to a new ZAPI call workflow during a wafl-sync multicreation snapshot. This issue is fixed in SnapDrive 6.4.2 and higher.
If issues persist after the upgrade, or the version of SnapDrive is earlier than 6.4 or later than 6.4.2, the error is generally related to either full volumes or a potential performance bottleneck on the storage controller, and there might be a considerable
delay in SME backup time.
If the volume is full, resize the volume to ensure it has enough space. For more information, see
2013016: SnapDrive fails to mount LUN because it tries to enable LUN space reservation
2014096: SnapManager for Exchange backup fails with error code: 0xc00402b5
The delays and timeouts can be related to SnapDrive for Windows (SDW) Transport Protocol Settings on HTTP/S protocol with a domain account rather than using a local privileged account on the storage system. Using a domain account for HTTP authentication
can result in significantly reduced performance. To avoid this issue, use a storage system account for authentication (for example, root (7-mode), vsroot (Clustered ONTAP), or another privileged account created on the storage system(s)), instead of a domain
account for the Transport Protocol Setting on all DAG nodes.
If the issue still persists, call the NetApp support hotline and be prepared to gather some storage system-side performance data using the Perfstat tool.
For information on how to use the perfstat tool, see article 1010551: How to collect Perfstat data over RSH or SSH. The perfstat MUST
be collected during a backup where this problem is encountered to be useful for troubleshooting.

Do I really need to Shadow Copy Backup Drive?

I am running SBS 2011 Standard. Every once in a while I get "volsnap event id 25 (The shadow copies of volume \\?\Volume{4bac8e93-04ed-11e2-814f-90b11c020377} were deleted because the shadow copy storage could not grow
in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.)".
The referenced volume is actually my backup drive which is a "simple, basic, NTFS primary partition" without an assigned drive letter which is entirely devoted to Windows backup destination drive.
VSSADMIN LIST SHADOWSTORAGE shows:
Shadow Copy Storage association
   For volume: (\\?\Volume{4bac8e93-04ed-11e2-814f-90b11c020377}\)\\?\Volume{4ba
c8e93-04ed-11e2-814f-90b11c020377}\
   Shadow Copy Storage volume: (\\?\Volume{4bac8e93-04ed-11e2-814f-90b11c020377}
\)\\?\Volume{4bac8e93-04ed-11e2-814f-90b11c020377}\
   Used Shadow Copy Storage space: 2.094 MB (0%)
   Allocated Shadow Copy Storage space: 2.93 GB (1%)
   Maximum Shadow Copy Storage space: UNBOUNDED (100%)
which I assume means VSS is actually keeping a shadow copy of the backup drive (or trying to).
My question is - do I really need to shadow copy this volume? If not would I stop this by the following command?
VSSADMIN DELETE SHADOWSTORAGE /FOR={4bac8e93-04ed-11e2-814f-90b11c020377}

Just did a quick bit of research on this and I think the error may be misleading.
If you go into Disk Management, right click Disk Management, All Tasks - Configure Shadow Copies
Do they show as Disabled on that volumeID?
If I go into Windows Server Backup and check out the Details, I see (on this system) 70.63gb of Backup Items, and 186gb of Copies. Which tallies up with what I see under List ShadowStorage.
So, what I suspect is happening (although happy to be proved wrong) is that the error above is VSC making space on your backup disk, or some other management process of the backups themselves.
I expect if you delete that Shadow Storage you will in fact, be deleting the backups.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

No space used by DPM shadow copy volume

Similar Messages

Maybe you are looking for