How do I correct the following issue below.

A week ago I started receiving this error message. The Windows Server Essentials Computer Backup service is not running. You cannot back up client computers until you start the service.

Suggested Resolution is before you start the service, resolve all alerts that are related to Server Storage. There were no issues with server storage.

To start the service:

In Health Monitoring tab, click Try to repair. If the problem persists, make sure the Client Computer Backups folder exists and can be accessed.

When I start the service this is what happens.

The windows server essentials computer backup service on local computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.

I have found fixes for Server 2008 and 2008 R2 but have yet to find a resolution 
for Server 2012 R2.  I have worked with EMC to try a resolve with no
luck.  The issue is the e:\ volume is on the other node in the cluster but
is looking at this path due to a SAP service that installed to this
cluster volume location on this node "e:\usr\sap\trn\ascs01\exe\sapstartsrv.exe".  
Below is the VSS event id, vssadmin list writers, and diskshadow output for
further information.

________________________________________

Event Id 8193, VSS -- I am receiving at every backup attempt:

Volume Shadow Copy Service error: Unexpected error calling
routine GetVolumePathName is fail on the path e:\usr\sap\trn\ascs01\exe,
winerror 0x00000002.. hr = 0x80070002, The system cannot find the file
specified.

Operation:

PrepareForSnapshot Event

Context:

Execution Context: Writer

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}<o:p></o:p>

Writer Name: System Writer

Writer Instance ID:
{b37cf597-c4a9-46ec-a4f1-f834daf9295c}

______________________________________________

Output for vssadmin list writers

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>vssadmin list writers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'

   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}

   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}

   State: [1] Stable

   Last error: No error

Writer name: 'VSS Metadata Store Writer'

   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}

   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}

   State: [1] Stable

   Last error: No error

Writer name: 'Performance Counters Writer'

   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}

   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}

   State: [1] Stable

   Last error: No error

Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}

   Writer Instance Id: {51014fc6-79fc-4719-a47e-890c12eae4af}

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'

   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}

   Writer Instance Id: {ca77048d-6a55-429d-8156-cd20cd480286}

   State: [1] Stable

   Last error: No error

Writer name: 'SqlServerWriter'

   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   Writer Instance Id: {02ce344c-fee1-471e-add1-80fc0f0eab1c}

   State: [1] Stable

   Last error: No error

Writer name: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Writer Instance Id: {7470832b-d895-43e1-bb24-4ba2411fa7bf}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {0591d297-755a-426e-83de-20dbc24d4a8a}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Writer Instance Id: {a163cc77-d300-4089-a5fb-2a45c33deb14}

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Database'

   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

   Writer Instance Id: {a717560f-50db-4771-99bc-03a68aa01f5d}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {6a4a6d8b-4b54-4904-8bf9-9433120b1aad}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {2ff1dddd-8586-43f0-a824-e4025d538a3f}

   State: [1] Stable

   Last error: No error

______________________________________________

Output for diskshadow

C:\Windows\system32>diskshadow

Microsoft DiskShadow version 1.0

Copyright (C) 2013 Microsoft Corporation

On computer:  AOTRNCL01,  9/11/2015 8:08:51 AM

DISKSHADOW> add volume c:

DISKSHADOW> create

COM call
"lvssObject4->GetRootAndLogicalPrefixPaths" failed.

Alias VSS_SHADOW_1 for shadow ID {a817c807-f00b-496b-b799-06a15a6f9e0f} set as
e

nvironment variable.

Alias VSS_SHADOW_SET for shadow set ID {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}
se

t as environment variable.

Querying all shadow copies with the shadow copy set ID
{e9ce9d2b-97d0-4415-ae49-

2ec7b5b3c87d}

        * Shadow copy
ID = {a817c807-f00b-496b-b799-06a15a6f9e0f}

%VSS_SHADOW_1%

               
- Shadow copy set: {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}

%VSS_SHADOW_SET%

               
- Original count of shadow copies = 1

               
- Original volume name: \\?\Volume{bcb4e1e6-f8a3-11e4-80bf-806e6

f6e6963}\ [C:\]

               
- Creation time: 9/11/2015 8:09:38 AM

               
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeS

hadowCopy1

               
- Originating machine: AOTRNCL01.waterone.org

               
- Service machine: AOTRNCL01.waterone.org

               
- Not exposed

               
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

               
- Attributes:  Auto_Release Differential

Number of shadow copies listed: 1

I need to know the maximum volume size Server 2012 can handle with its backup utility.

Anyone know?

Thanks.

This is a new installation and configuring the backup for the first time. We have two local volumes C and E and a Hyper-V guest located on E. We are trying to backup everything every night and by default windows offers to backup it all including system state, hyperv, and the volumes.

After configuring the backup completes on System state and C: just fine and then moves to E:. Before it even displays a total drive size it calls an error and fails the backup with 'The mounted backup volume is inaccessible." The error in event log is 0x807800C5 which in all my searches of forums seems to be related to others doing backups to network drives. I'm using the dedicated local drive option and have added the drives as valid backup destinations.

Upon further looking if I examine C:\Windows\Logs\WindowsServerBackup\Backup_error-xxxxx.log I find the following:

Backup of volume E: has failed. The mounted backup volume is inaccessible. Please retry the operation.

Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 5C9E0993-9FC4-494E-B6E7-28C7A2C22597
   Caption     : Backup Using Child Partition Snapshot\SERVERF-APPS-HV
   Logical Path:

Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: Host Component
   Caption     : Host Component
   Logical Path:

*-----------------------------*

E: has roughly 5.4TB free space and is using approximately 0.5TB total. My backup drives are empty 3TB drives.

I had Shadow Copy enabled for drive E so I tried changing the size limits to No Limit and when that didn't help I disabled Shadow Copy entirely on E:.

I'm at a loss of where to go next. It's difficult for me to make many changes because I have 6 backup destinations setup for the server and the infurating problem with needing to have all the destinations plugged in before you can successfully make changes to the backup settings is making it real difficult to try many things. I am remote to this server and had to make some serious changes to get the 6 drives all connected to begin with. (Yes, I read and tried all the command line suggestions which used to work on 2008 R2 just fine and now don't in 2012.)

Jeremy Regehr

Hello,

I need to perform a complete system recovery test on our UAT servers.

Current Configurations : NEC EXpress 5800 R120e-2M

Disk Drives  : 3 disks ( C:, D: and Y drive ) 

I tried yesterday but did not succeed.

Steps.

I made a full system backup image on drive Y: It was successful.

Boot the system using Windows 2008R2 bootable CD and select Recover System option.

Problems:

1. Windows could not recognize the disks firstly then I checked the NEC Express 5800 manual and found that I need to load the RAID drivers when Windows asks for the Load Drivers. Drivers were load successfully. It is hardware RAID implemented in the server.

Luckily, Windows detects the current installed operating system but the problem was that,

Windows detects the C: as H: when it displayed the list of installed operating.I tried next but Windows could not detect the backup image and finally gave up.

I saw  that all the disks volumes changed as follows

C : drive became H:

D : drive became N:

Y : drive became L:

I am not able to understand this behavior. Appreciate if someone can please provide some insight/information for above problem.

I am stuck at this point and can not test the Windows Full System Recovery on UAT before attempting it on our Production and DR environment.

Finally I booted the server as normal and I can see C,D and Y: drives.

Thanks,

Praveen

I'm testing 2008R2 SP1 Windows Image Backups. Two Servers alpha and omega each have an older backup stored on the other server, in shared folders. In Windows Server Backup - Recovery Wizard - Specify Remote Folder I get to specify the UNC path "to the remote shared folder that contains the backup." Easy, right? I have tried (from \\alpha)

\\omega\WindowsImagebackup    (which is the shared folder)

\\omega\WindowsImagebackup\alpha

\\omega\WindowsImagebackup\alpha\Backup 2011-03-22 133034

These all error with

"The specified remote shared folder does not contain any backup. Provide the path to a remote shared folder that contains backups."

Must be corrupted? But, vice-versa, trying from \\omega and looking at \\alpha i get the same error.

Tell me I'm missing something stupid..  Thanks!

my backups are failing with error VSS writer 'WIDWriter' with class ID '8D5194E1-E455-434A-B2E5-51296CCE67DF' has failed to process the snapshot

please help

each time i start a full backup to the server (windows 2012 R2 standard), i get the following error "the backup threw an exception".

the backup was working a while ago. is there any windows update that may have damaged the backup procedure ?

A sub company is using Windows Server 2003 and have their backup using windows Backup.  Is it possible to backup their data to remote NAS through Internet?  This task will achieve offsite backup solution.  If can, will buy a NAS and place it into other office.

They won't consider Cloud backup or expensive solution at this moment

Please suggests any NAS product or any solution. Many thanks!

I have arcserver backup software and it is failing on the system state so I ran a windows backup just for system state and it failed also with only 2 informational events as follows:

=============================event 1=====================================

Event ID 1001 / Source Windows Error Reporting / Log Name: Application

Fault bucket , type 0
Event Name: Windows Server Backup Error
Response: Not available
Cab Id: 0

Problem signature:
P1: 2
P2: 1
P3: 0x80780102
P4: 0x8078001d
P5: 0x00000000
P6: 0x8078001d
P7: 0x80780064
P8: 0x00000000
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_eb4095c0d039d80764d38dbbea8fdad2a78b745_00000000_2e4eb9ec <SEE FILE CONTENTS BELOW>

Analysis symbol:
Rechecking for solution: 0
Report Id: ade020c0-b5be-11e5-813a-fc15b421aaed
Report Status: 4100
Hashed bucket:

=================================event 2===============================

Event ID: 517 / Source: Backup / Log Name: Application

XML DATA

Hello All;

In windows 2008 R2 you can only schedule One Backup for the server...

Then after googling around I found a way to schedule an additional backup using this command:

wbadmin start backup -backupTarget:F: -include:C:,D: -systemState -allCritical -vssFull -quiet

where F: is the External HDD

and then use task scheduler to run the batch file

That did not work on windows 2012 R2

Any suggestions?

Thanks in advance

nabil@qg-jo.com

host vm's all have integration services enabled -- (tried disabling but still fails) 

has been working for months with no issue

suddenly 1st vm goes into offline state backing up -- and hangs -- backup never completes (fails - timeout of volumeshadowcopy creation) -- vm doesn't come back online stays offline - critical -- restart of server resolves state of vm --

in vm affected  event22, vss

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {3e02620c-e180-44f3-b154-2473646e4cb8} and Name SW_PROV is [0x80040154, Class not registered
]. 

list writers -

Writer name: 'Task Scheduler Writer'
   Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
   Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
   State: [1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
   Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
   State: [1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
   Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {e66639b5-a5f8-4f4b-b861-ae17b11be040}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {2481b3e5-2cde-4c10-8d55-24ffbe75d36c}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9b4e5832-5e68-435b-99c7-75f83cceb514}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {8f08e596-407b-4686-ba8e-7d9d943c2a7a}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {4283f4f9-76d1-42d7-ba10-0ad1265acfbc}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {b9d75626-6d41-40ac-ac82-de0a0fc786dc}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {93a4e0bc-85ea-40e2-a3ac-334b87fdef9f}
   State: [1] Stable
   Last error: No error

listproviders:

Provider name: 'Hyper-V IC Software Shadow Copy Provider'
   Provider type: Software
   Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Version: 1.0.0.0

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

on host

Provider name: 'Hyper-V IC Software Shadow Copy Provider'
   Provider type: Software
   Provider Id: {74600e39-7dc5-4567-a03b-f091d6c7b092}
   Version: 1.0.0.0

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

errors in host event logs -

backup: 

The backup operation that started at '‎2016‎-‎05‎-‎16T02:01:30.898000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x80780021'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.   (same error every time trying to run backup )

application logs:

Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.
. 




Error5/13/2016 7:32:10 PMMSSQL$MICROSOFT##WID18210Server
BackupVirtualDeviceFile::PrepareToFreeze:  failure on backup device '{D9AAED54-BA8D-4F3D-AEF7-45CB67E09BE3}2'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
. 
Error5/13/2016 7:37:21 PMMSSQL$MICROSOFT##WID5601Server
The service master key could not be force regenerated as requested by the -F startup option. The error number is 33094.

Error5/13/2016 7:37:26 PMVSS8193None
Volume Shadow Copy Service error: Unexpected error calling routine RegOpenKeyExW(-2147483646,SYSTEM\CurrentControlSet\Services\VSS\Diag,...).  hr = 0x80070005, Access is denied.
. 

Operation:
   Initializing Writer

Context:
   Writer Class Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Name: NPS VSS Writer
   Writer Instance ID: {4637a8c2-b018-43d3-b29e-9c59487cef91}

also seeing access denied on WID WRITER & SYSTEM WRITER

ideas of where i should begin?  is this related to vss writers needing to be reregistered or has to do with problems with windows internal database   (hyper-v host is also running remote access services/vpn only

Dear All,

I have installed Windows server backup and run scheduled backup on daily basis.

I have got below error every day and couldn't run recovery option in this module.

Writer Failures
Writer Id: {8D5194E1-E455-434A-B2E5-51296CCE67DF}
Instance Id: {70DAC225-B076-4428-AD69-EE41A62AB8EC}
Writer Name: WIDWriter
Writer State: 8
Failure Result: 800423F4
Application Result: 1
Application Message: (null)
   Component: master
   Logical Path: PARSRV\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\master.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\mastlog.ldf Recursive: 0
   Component: model
   Logical Path: PARSRV\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\model.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\modellog.ldf Recursive: 0
   Component: msdb
   Logical Path: PARSRV\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\MSDBData.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\MSDBLog.ldf Recursive: 0
   Component: SUSDB
   Logical Path: PARSRV\MICROSOFT##WID
   Component Result: 800423F4
   Component Message: (null)
       File Spec: C:\Windows\WID\Data\SUSDB.mdf Recursive: 0
       File Spec: C:\Windows\WID\Data\SUSDB_log.ldf Recursive: 0
*-----------------------------*


Backup of volume C: has failed. The operation failed due to a device error encountered with either the source or the destination. If the source or destination volume is on a disk, run CHKDSK /R on the source or destination volume, and then retry the operation.

 Could anyone help me to fix this issue.

Thanks,

Chandran Manikandan

Hi i am a relatively new to visualizations:

Just have a quick question with regards to virtual disks. each server has its own vhdx on the host, 

every night i take a copy on to a NAS drive: therefore ...if say one of the vhdx has a problem... would it be simply copying back the vhdx file back from the nas drive to restore the virtual server ?

Again apologies, if this comes across rather simplistic...i dont have too much experiance with Hyper V!

Thanks