I have a new Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system state wasn't getting backed up.
 
Then I would run "vssadmin list writers" from CMD and system writer would be timing out....
 
Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6}
    State: [7] Failed
    Last error: Timed out
 
I would also get Event ID 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} - 0000000000000140,0x0053c020,00000000003BDFD0,0,00000000003BBFA0,4096,[0]).  hr = 0x80070057, The parameter is incorrect.
 
I would also get Event ID 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
 
Also event ID 22 for volsnap The shadow copy storage volume specified for shadow copies on volume\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} could not be added.
 
Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies.

PLEASE HELP!

Hello,

We use backup assist to run our backups, however, our hyper-v backup has stopped working.

I've checked to see what <g class="gr_ gr_88 gr-alert gr_spell gr_disable_anim_appear ContextualSpelling ins-del multiReplace" data-gr-id="88" id="88">vss</g> writers are missing and could see that the <g class="gr_ gr_117 gr-alert gr_spell gr_disable_anim_appear ContextualSpelling" data-gr-id="117" id="117">vss</g> hyper-v one is no longer there...

Here is what appears when I run the command.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>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: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {96dbac67-78eb-44d3-b977-c27dad7adc3f}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {5f024110-d766-4a0b-8412-11fb8964d71e}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {b0003ed1-ecc4-41f8-a171-276b3c5ba043}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {980194c2-060b-487a-b1ca-fb27c294ff56}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {59ee729d-7cdd-42b9-ae26-1495e76cedb1}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c02f9a00-b840-49c9-ae43-e0e59b83b535}
   State: [1] Stable
   Last error: No error

But when I run the same on our VTwo server there are a considerable amount more services.

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>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: {0fc7d32c-9a42-43d6-b0cc-dda636b64c92}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {f270c894-fd9d-4584-863f-d1d956697eb5}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {9a08626c-1a62-404a-8255-77aa633743b9}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {cea26534-9085-4089-b49d-39caea7d2893}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {11306641-af46-4c67-b313-48b010dd2139}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {6edb7baf-c91a-4b64-8a64-25e5f3eeef47}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {031ad868-c59c-4b8a-8db3-6139ac33384e}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fd00b398-ca39-4c73-8d40-2df3859b6043}
   State: [1] Stable
   Last error: No error


C:\Users\Administrator>

Hi,

Here I have a Windows Server 2012 R2 Standard server, using Netbackup software for the backup, which is a product of Symantec company.

The server roles as file server, problem now is the backup process always failed when processing on an EFI partition.

After consulted with the product vendor, they suggested to ask MS for help..

Here is the log:

- Type: VSS_CT_FILEGROUP [2]

- Is selectable: TRUE

- Is top level: TRUE

- Notify on backup complete: FALSE

- Paths affected by this component:

- \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot>

- Volumes affected by this component:

- \\?\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot<file:///\\%3f\GLOBALROOT\Device\HarddiskVolume2\EFI\Microsoft\Boot> [Does not exist]

Here is the BCD info:

Please let me know if any other information you need to know.

Really thanks for any help.

Regards

John

Hi all,

This is my environment :
Windows server 2003 R2 Standard Edition SP 2 (joined domain) as File server , local drive DATA F: with a shared folder MLC (sharing data for local users - about 230 GB).
NAS device (192.168.22.7) : Buffalo LinkStation LS-WXL4BD firmware 1.73 , on this NAS I created a shared folder Backup , File server can see this Backup share folder and mount it as network drive U: , from Fileserver I can access , read , write data on U: drive.
I created schedule tasks backup Full and Incremental (by backup wizard ) F:\MLC to U:\Backup\Fileserver , jobs ran successfully before (as domain administrator).
Recently, NAS has firmware issue, I have to reset and reconfigure it , after that , jobs don't work anymore.
The full backup job stops when it runs about 120 GB. Here are some events :

Event Type:	Information
Event Source:	Removable Storage Service
Event Category:	None
Event ID:	98
Date:		12/7/2017
Time:		2:59:34 PM
User:		N/A
Computer:	APPSVR01
Description:
RSM was stopped.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7036
Date:		12/7/2017
Time:		2:59:35 PM
User:		N/A
Computer:	APPSVR01
Description:
The Removable Storage service entered the stopped state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7035
Date:		12/7/2017
Time:		2:59:40 PM
User:		NT AUTHORITY\SYSTEM
Computer:	APPSVR01
Description:
The Removable Storage service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7036
Date:		12/7/2017
Time:		2:59:40 PM
User:		N/A
Computer:	APPSVR01
Description:
The Removable Storage service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7036
Date:		12/7/2017
Time:		3:02:03 PM
User:		N/A
Computer:	APPSVR01
Description:
The Volume Shadow Copy service entered the stopped state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Information
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7036
Date:		12/7/2017
Time:		3:05:03 PM
User:		N/A
Computer:	APPSVR01
Description:
The Microsoft Software Shadow Copy Provider service entered the stopped state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	NTBackup
Event Category:	None
Event ID:	8001
Date:		12/7/2017
Time:		2:59:02 PM
User:		N/A
Computer:	APPSVR01
Description:
End Backup of 'F:' 'Warnings or errors were encountered.'

 	Verify:  Off 
 	Mode:  Replace 
 	Type:  Normal 
 
Consult the backup report for more details.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	NTBackup
Event Category:	None
Event ID:	8019
Date:		12/7/2017
Time:		2:59:03 PM
User:		N/A
Computer:	APPSVR01
Description:
End Operation: Warnings or errors were encountered. 
Consult the backup report for more details.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	Application Hang
Event Category:	(101)
Event ID:	1002
Date:		12/7/2017
Time:		3:01:46 PM
User:		N/A
Computer:	APPSVR01
Description:
Hanging application ntbackup.exe, version 5.2.3790.3959, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 48 61 6e 67   ion Hang
0010: 20 20 6e 74 62 61 63 6b     ntback
0018: 75 70 2e 65 78 65 20 35   up.exe 5
0020: 2e 32 2e 33 37 39 30 2e   .2.3790.
0028: 33 39 35 39 20 69 6e 20   3959 in 
0030: 68 75 6e 67 61 70 70 20   hungapp 
0038: 30 2e 30 2e 30 2e 30 20   0.0.0.0 
0040: 61 74 20 6f 66 66 73 65   at offse
0048: 74 20 30 30 30 30 30 30   t 000000
0050: 30 30                     00      

Backup Status
Operation: Backup
Active backup destination: File
Media name: "Fileserver.bkf created 12/7/2017 at 8:54 AM"

Volume shadow copy creation: Attempt 1.
Backup (via shadow copy) of "F: DATA"
Backup set #1 on media #1
Backup description: "Set created 12/6/2017 at 3:18 PM"
Media name: "Fileserver.bkf created 12/7/2017 at 8:54 AM"

Backup Type: Normal

Backup started on 12/7/2017 at 9:01 AM.

Error: The device reported an error on a request to write data to media.
Error reported: Unknown error.
There may be a hardware or media problem.
Please check the system event log for relevant failures.
The operation was ended.
Backup completed on 12/7/2017 at 2:59 PM.
Directories: 13073
Files: 105953
Bytes: 118,284,467,242
Time:  5 hours,  57 minutes, and  54 seconds

Error: F: is not a valid drive, or you do not have access.

----------------------

The operation did not successfully complete.

----------------------

C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\Fileserver.bks" /n "Fileserver.bkf created 12/6/2017 at 3:18 PM" /d "Set created 12/6/2017 at 3:18 PM" /n "Fileserver.bkf created 12/6/2017 at 3:18 PM" /v:no /r:no /rs:no /hc:off /m normal /j "Fileserver-full" /l:s /f "U:\Fileserver\Fileserver.bkf"

I've seen and found similar post online and her but so far no one with an answer.

Windows Server Backup extremely slow while 'compacting the virtual hard disk(s)'
Compacting virtual hard disks

Running a Windows 2016 Server that has the hyper v role that I backup using the Windows Backup to backup the server to a local attached USB disk.

When I firstly create the backup job it takes quite some time because it needs to copy all the data, which is understandable. After that the incremental is done within a hour backing up 3 TB of data and 6 VMs, which is a great result.

Then after a while the backup disk is filling up and it will take for ever to finish a backup. Every day it will start to do a full and compacting the virtual hard which will take almost the whole day.

I'm doing a disaster recovery exercise where a full forest recovery is needed and was wondering: when you restore a DC using a full System State Windows Server Backup and a Windows Server DVD is it enough to restore the DC's state this way. Or do you also need to perform a system state restore in "Directory Services Restore Mode". I know in a complete forest recovery (which also has subdomains) it's neccesary to specify a restore which will be authtariave for sysvol. But doesn't it suffice to use the wbadmin and the -authsysvol switch. So the steps would look like this:

1) Boot server with DVD and attach HDD with system state backup on it

2) Open CMD

3a) If it's the first server in the root domain run following command: wbadmin start systemstaterecovery -authsysvol ...

3b) if it's a subdomain DC just run: wbadmin start systemstaterecovery ...

4) After it's finished invalidate RID, check fsmo, metadata cleanup, cleanup DNS, reset trusts, reset krbtgt password....

Does this seem alright or is using "Directory Services Restore Mode" absolutely necessary.

I'm the new IT guy here at work. Our Server O/S is Windows server 2008 R2. The old ext usb backup drives have died. I bought 4 WD passport 1TB drives. I can setup a drive to do a complete backup with no issue using windows server backup. When I put Passport 2 or Passport 3 or Passport 4 .. etc. it will not back up without me deleting the current backup job and creating one with the current weeks usb drive. My question is... how do I simply use or switch out all 4 WD 1TB Ext USB drives from week to week without deleting the current backup job. The old USB Ext drives where inter-changeable.

Kevin

Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          7/22/2009 10:47:53 AM
Event ID:      519
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      FCSERVER2.Fellowship.local
Description:
The description for Event ID 519 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

EV_RenderedValue_0.00
F:
2147942402
%%2147942402

The locale specific resource for the desired message is not present

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" /><EventID>519</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2009-07-22T14:47:53.948Z" /><EventRecordID>31560</EventRecordID><Correlation /><Execution ProcessID="1260" ThreadID="4248" /><Channel>Application</Channel><Computer>FCSERVER2.Fellowship.local</Computer><Security UserID="S-1-5-18" /></System><EventData><Data Name="BackupTime">2009-07-22T14:32:35.872Z</Data><Data Name="FailedVolumeNames">F:</Data><Data Name="ErrorCode">2147942402</Data><Data Name="ErrorMessage">%%2147942402</Data></EventData></Event>

Hi! 

I have a following error while doing scheduled backups: "Failure while compacting the virtual disk on the backup location"OS is Server 2012 R2 Essential 

I use a dedicated HDD for backups. Its a WD GREEN 3TB. 

Any suggestions? 

LOGS:

• EROOR: The backup operation that started at '‎2014‎-‎06‎-‎27T00:57:25.744931200Z' has failed with following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
• WARNING: The backup operation that started at '‎2014‎-‎06‎-‎26T16:30:31.944377600Z' has completed with errors. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Hi All,

We use a backup product called Datto which is currently failing to backup as the VSS writers just keep failing.

We reboot the server and it works for two or three days and then fails again.

These are the writers in their current state:

Even when i restart the services and bring the writers back online, the backups continue to fail, it's only when we restart the server they start working again.

The services are restarted as per the following KB:

https://kb.datto.com/hc/en-us/articles/200554775-How-to-resolve-VSS-writer-errors-without-rebooting-VShadow-

OS is Windows Server 2008 R2 SP1

Patching is up to date as of today (April 20th 2018)

This is the output from the Datto portal:

Wed 18/04/18 8:07:40 am - Writer "Microsoft Hyper-V VSS Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Instance ID: {d916171a-b1fb-449a-9040-fdc7126efeac} 
Wed 18/04/18 8:07:40 am - Writer "System Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {e8132975-6f93-4464-a53e-1050253ae220} Instance ID: {8a104ae3-52ba-4628-a7e0-cebc4b21f91b} 
Wed 18/04/18 8:07:40 am - Writer "SqlServerWriter" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Instance ID: {97a8f30c-57d9-4c48-8912-1d11fed93729} 
Wed 18/04/18 8:07:40 am - Writer "ASR Writer" Failed: False Status: 1 (VSS_WS_STABLE) Writer Failure code: 0x00000000 (S_OK) Writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4} Instance ID: {680e60a3-8da1-4753-a45b-8cb88b4b3268} 
Wed 18/04/18 8:07:40 am - Writer "Registry Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {afbab4a2-367d-4d15-a586-71dbb18f8485} Instance ID: {61200074-eb5d-4cdc-ba92-c064f504dbb1} 
Wed 18/04/18 8:07:40 am - Writer "IIS Config Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Instance ID: {ebd20780-2b14-4d5e-85ca-1998cab5cd95} 
Wed 18/04/18 8:07:40 am - Writer "COM+ REGDB Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {542da469-d3e1-473c-9f4f-7847f01fc64f} Instance ID: {ed72cee2-725e-4450-9135-9b7068965b1d} 
Wed 18/04/18 8:07:40 am - Writer "BITS Writer" Failed: False Status: 1 (VSS_WS_STABLE) Writer Failure code: 0x00000000 (S_OK) Writer ID: {4969d978-be47-48b0-b100-f328f07ac1e0} Instance ID: {a0ace692-3867-426d-8a50-cbdafef6fec8} 
Wed 18/04/18 8:07:41 am - Writer "WMI Writer" Failed: True Status: 9 (VSS_WS_FAILED_AT_FREEZE) Writer Failure code: 0x800423f2 (<Unknown error code>) Writer ID: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Instance ID: {2a7d3d06-f1fb-45a9-b23d-cfc29dc7c33f}

Please note there will be a difference in the state of the writers as some of the services have been restarted between the above output and the list at the top.

Unfortunately there is no phone support from Microsoft on Server 2008 R2 so they've requested i post here, so please let me know if there's any more information needed.

Any help would be much appreciated.

Thank you.

Hello,

I'm creating a script to automatize my Wsus offline. I created a backup from the source server and I want to restore it on the destination server using powershell Server backup cmdlets.

Here is what I've done so far:

on the source server:

wsus is on E:\Wsuscontent
I backup to a USB drive I:\

On the destination server:

Wsus is on e:\wsuscontent
Backup is on \\mynas\backup

To restore I use: 

$BackupLocation = New-WBBackupTarget -NetworkPath "\\mynas\backup"
$Backups = Get-WBBackupSet -BackupTarget $BackupLocation -MachineName SourceServer
Start-WBFileRecovery -BackupSet $Backups -NoRestoreAcl -Option SkipIfExists -SourcePath "E:\wsuscontent" -TargetPath "E:\" -Force

  And I get the following error: "Start-WBFileRecoverry: The specified backup storage location is invalid."

any idea ?

Regards,

Jon

MCITP Enterprise Administrator / Server Administrator

I have a standalone Windows 2016 server(not promoted as DC), not joined to any Active Directory domain. It's just a very basic setup with single C:\

My backups on network backup drives and other Windows 2012 share fail with errors:

wbadmin start backup -backuptarget:\\<IP>\<share-name> -allcritical -quiet -user:<user> -password:<pwd>
• There was a failure in preparing the backup image of one of the volumes in the backup set.
The specified backup disk cannot be found.
• There was a failure in preparing the backup image of one of the volumes in the backup set.
The mounted backup volume is inaccessible. Please retry the operation.

These errors are either seen either while copying 'System Reserve' or at other times, if 'System Reserve' completes backup, 'C:\' backup fails

Event viewer for error code 517

- <System><Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" /> <EventID>517</EventID> <Version>1</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2018-04-22T10:48:45.043974800Z" /> <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /> <Execution ProcessID="6632" ThreadID="9400" ProcessorID="0" KernelTime="7860" UserTime="10020" /> <Channel>Application</Channel> <Computer /> </System>
- <EventData><Data Name="BackupTime">‎2018‎-‎04‎-‎22T10:46:02.419799100Z</Data> <Data Name="ErrorCode">0x807800C5</Data> <Data Name="ErrorMessage">%%2155348165</Data> </EventData>
- <RenderingInfo Culture="en-US"><Level>Error</Level> <Opcode>Info</Opcode> <Message>The backup operation that started at '‎2018‎-‎04‎-‎22T10:46:02.419799100Z' has failed with following error code '0x807800C5' (%%2155348165). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.</Message> <Channel>Application</Channel> <Provider>Microsoft-Windows-Backup</Provider> </RenderingInfo></Event>

Event viewer for details error 5 when only C:\ fails

- <System><Provider Name="Microsoft-Windows-Backup" Guid="{1db28f2e-8f80-4027-8c5a-a11f7f10f62d}" /> <EventID>5</EventID> <Version>3</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2018-04-22T10:48:45.043949000Z" /> <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" /> <Execution ProcessID="6632" ThreadID="9400" ProcessorID="0" KernelTime="7860" UserTime="10020" /> <Channel>Microsoft-Windows-Backup</Channel> <Computer /> </System>
- <EventData><Data Name="BackupTemplateID">{be262c77-db7f-4796-b068-2977ff3bfd8c}</Data> <Data Name="HRESULT">0x807800C5</Data> <Data Name="DetailedHRESULT">0x8078004F</Data> <Data Name="ErrorMessage">%%2155348165</Data> <Data Name="BackupState">12</Data> <Data Name="BackupTime">‎2018‎-‎04‎-‎22T10:46:02.419799100Z</Data> <Data Name="BackupTarget">\\10.98.32.164\test1</Data> <Data Name="NumOfVolumes">2</Data> <Data Name="VolumesInfo"><VolumeInfo><VolumeInfoItem Name="System Reserved" OriginalAccessPath="" State="14" HResult="0" DetailedHResult="0" PreviousState="9" IsCritical="1" IsIncremental="0" BlockLevel="1" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="345636864" NumUnreadableBytes="0" TotalSize="345636864" TotalNoOfFiles="0" Flags="554" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="12" HResult="-2139619249" DetailedHResult="0" PreviousState="9" IsCritical="1" IsIncremental="0" BlockLevel="1" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1576" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo></Data> <Data Name="SourceSnapStartTime">‎2018‎-‎04‎-‎22T10:46:02.404154600Z</Data> <Data Name="SourceSnapEndTime">‎2018‎-‎04‎-‎22T10:46:18.170040100Z</Data> <Data Name="PrepareBackupStartTime"><TimesList><Time Time="2018-04-22T10:46:25.701Z" /><Time Time="2018-04-22T10:46:40.889Z" /></TimesList></Data> <Data Name="PrepareBackupEndTime"><TimesList><Time Time="2018-04-22T10:46:25.717Z" /><Time Time="2018-04-22T10:46:40.998Z" /></TimesList></Data> <Data Name="BackupWriteStartTime"><TimesList><Time Time="2018-04-22T10:46:25.732Z" /><Time Time="2018-04-22T10:46:41.045Z" /></TimesList></Data> <Data Name="BackupWriteEndTime"><TimesList><Time Time="2018-04-22T10:46:38.654Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="TargetSnapStartTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="TargetSnapEndTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="DVDFormatStartTime"><TimesList></TimesList></Data> <Data Name="DVDFormatEndTime"><TimesList></TimesList></Data> <Data Name="MediaVerifyStartTime"><TimesList></TimesList></Data> <Data Name="MediaVerifyEndTime"><TimesList></TimesList></Data> <Data Name="BackupPreviousState">9</Data> <Data Name="ComponentStatus"><ComponentStatus></ComponentStatus></Data> <Data Name="ComponentInfo"><ComponentInfo></ComponentInfo></Data> <Data Name="SSBEnumerateStartTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SSBEnumerateEndTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SSBVhdCreationStartTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SSBVhdCreationEndTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SSBBackupStartTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SSBBackupEndTime">‎1601‎-‎01‎-‎01T00:00:00.000000000Z</Data> <Data Name="SystemStateBackup"><SystemState IsPresent="0" HResult="0" DetailedHResult="0" /></Data> <Data Name="BMR"><BMR IsPresent="1" HResult="-2139619249" DetailedHResult="0" /></Data> <Data Name="VssFullBackup">false</Data> <Data Name="UserInputBMR">true</Data> <Data Name="UserInputSSB">false</Data> <Data Name="BackupSuccessLogPath">C:\Windows\Logs\WindowsServerBackup\Backup-22-04-2018_10-46-02.log</Data> <Data Name="BackupFailureLogPath">C:\Windows\Logs\WindowsServerBackup\Backup_Error-22-04-2018_10-46-02.log</Data> <Data Name="EnumerateBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="EnumerateBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="PruneBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="PruneBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="BackupFlags">0x1</Data> <Data Name="ComponentInfoSummary"><ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /></Data> </EventData>
- <RenderingInfo Culture="en-US"><Level>Error</Level> <Opcode>Info</Opcode> <Message>The backup operation that started at '‎2018‎-‎04‎-‎22T10:46:02.419799100Z' has failed with following error code '0x807800C5' (%%2155348165). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.</Message> <Channel>Microsoft-Windows-Backup/Operational</Channel> <Provider>Microsoft-Windows-Backup</Provider> </RenderingInfo></Event>

I have searching over the net and could not find any concrete fix.

My NAS drive supports only SMB2 and not SMB3

Some other interesting observations:

• I tried an alternate method of mapping network share, creating a VHDX out of it, then mapping that as local drive. The backup on that one seems to work. Both for my NAS box and any Windows 2012 Share
• I tried backing up the data on a Samba share and that seems to work for Windows 2016. For 2012 R2 it still fails with same error for all partitions
• Another backup box from the same vendor works fine with backups

This makes me wonder what difference could be between the 2 backup methods. If there is issue with Windows Configurations or the backup box. I am totally out of ideas

Any suggestions on how to debug this ? Apparently, the VHDX method(where backup works) doesn't seem to fit our infra, so that is not an option :(

System is non production, running server 2008 enterprise (localized in Dutch).

"Bare Metal Recovery" selected, backups scheduled daily using Windows server back-up.

Backup destination is a local disk, with plenty of disk space still free.

backups running fine up and until 6 june.

At that date we installed SQL server 2008 R2 and Advantage ADS (other database server).

I recently noticed that the backups have been failing since 6/6.

Investigation performed so far :

-> error message in backup wizard : "the system writer is not found in the backup"

-> confirmed that system writer is not in the writer list when doing vssadmin list writers in a cmd box.

-> found a gazillion articles on google indicating wrong permissions on %windir%\winsxs\Filemaps\*

reference article : http://support.microsoft.com/kb/2009272

most of these also mention problems with CAPI2 (cryptographic provider) but I see no evidence of that in my application log, only event ID 517 is present, indicating error 2155347997.

I follow the article instructions anyway and update file permissions but system writer is still not listed.

Then the article mentions that Event ID 8213, indicating permission issues, might be showing, but it's NOT.

registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl is already on 1

-> NO log is created under C:\Windows\Logs\WindowsServerBackup\ during the backup attempt.

-> I was able to restore the winsxs\filemaps folder from the last successfull backup without any problem.
log file was created during that restore.

-> using vsstrace.exe I get this output repeating over and over.
There are error messages in there but I have no idea what they mean and searching the net doesn't give me anything :

ERROR 1 CONTEXT (repeaded approx 300 times)

[10:14:23.075 P:150C T:1388 INCTYPEH(0256) GEN] ENTER[CVssAutomaticLock2::CVssAutomaticLock2]
[10:14:23.075 P:150C T:1388 INCTYPEH(0197) GEN] ENTER[CVssCriticalSection::Lock]
[10:14:23.075 P:150C T:1388 INCTYPEH(0197) GEN] EXIT[CVssCriticalSection::Lock] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.075 P:150C T:1388 INCTYPEH(0256) GEN] EXIT[CVssAutomaticLock2::CVssAutomaticLock2] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.075 P:150C T:1388 CORPRVMC(0363) COORD] ENTER[CVssProviderManager::GetProviderItfArrayInternal]
[10:14:23.075 P:150C T:1388 CORPRVMC(0363) COORD] EXIT[CVssProviderManager::GetProviderItfArrayInternal] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.075 P:150C T:1388 CORPRVMC(0468) COORD] ENTER[CVssProviderManager::GetProviderInterfaceInternal]
[10:14:23.075 P:150C T:1388 CORPRVMC(0470) COORD] CONTEXT[CVssProviderManager::GetProviderInterfaceInternal] Adding context: 'Aanroepbare interface voor deze provider verkrijgen' (0)
[10:14:23.075 P:150C T:1388 CORPRVMC(0471) COORD] CONTEXT[CVssProviderManager::GetProviderInterfaceInternal] Adding context: 'Provider-id' = '{b5946137-7b9f-4925-af80-51abd60b20d5}' (2)
[10:14:23.076 P:150C T:1388 CORPRVMC(0472) COORD] CONTEXT[CVssProviderManager::GetProviderInterfaceInternal] Adding context: 'Klasse-id' = '{00000000-0000-0000-0000-000000000000}' (2)
[10:14:23.076 P:150C T:1388 CORPRVMC(0473) COORD] CONTEXT[CVssProviderManager::GetProviderInterfaceInternal] Adding context: 'Context van snapshot' = '-1' (2)
[10:14:23.076 P:150C T:1388 CORSOFTC(0155) COORD] ENTER[CVssSoftwareProviderWrapper::AddRef]
[10:14:23.076 P:150C T:1388 CORSOFTC(0156) COORD] Provider Wrapper AddRef(00000000004006D0) 2 --> 3
[10:14:23.076 P:150C T:1388 CORSOFTC(0155) COORD] EXIT[CVssSoftwareProviderWrapper::AddRef] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.076 P:150C T:1388 CORSOFTC(0163) COORD] ENTER[CVssSoftwareProviderWrapper::Release]
[10:14:23.076 P:150C T:1388 CORSOFTC(0164) COORD] Provider Wrapper Release(00000000004006D0) 3 --> 2
[10:14:23.076 P:150C T:1388 CORSOFTC(0163) COORD] EXIT[CVssSoftwareProviderWrapper::Release] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.076 P:150C T:1388 CORSOFTC(0123) COORD] ENTER[CVssSoftwareProviderWrapper::QueryInternalInterface]
[10:14:23.076 P:150C T:1388 CORSOFTC(0128) COORD] Error while obtaining an interface interface 0x80004002
[10:14:23.076 P:150C T:1388 CORSOFTC(0123) COORD] EXIT[CVssSoftwareProviderWrapper::QueryInternalInterface] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002
[10:14:23.076 P:150C T:1388 CORSOFTC(0155) COORD] ENTER[CVssSoftwareProviderWrapper::AddRef]
[10:14:23.076 P:150C T:1388 CORSOFTC(0156) COORD] Provider Wrapper AddRef(00000000004006D0) 2 --> 3
[10:14:23.076 P:150C T:1388 CORSOFTC(0155) COORD] EXIT[CVssSoftwareProviderWrapper::AddRef] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:23.076 P:150C T:1388 CORPRVMC(0468) COORD] EXIT[CVssProviderManager::GetProviderInterfaceInternal] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002

Error message 1 :

[10:14:23.076 P:150C T:1388 CORSOFTC(0123) COORD] ENTER[CVssSoftwareProviderWrapper::QueryInternalInterface] 
[10:14:23.076 P:150C T:1388 CORSOFTC(0128) COORD] Error while obtaining an interface interface 0x80004002

ERROR 2 CONTEXT (repeaded 7 times) :

[10:14:33.503 P:04A0 T:14E4 WRTWRTIC(2274) WRITER] EXIT[CVssWriterImpl::RequestWriterInfoInternal] Time spent: 00:00:00-0015; total: 0xf; HRESULT: 0
[10:14:33.505 P:150C T:1388 WRTASRWC(0183) WRITER] EXIT[CVssAsrWriterBackup::_AddComponents] Time spent: 00:00:00-0015; total: 0xf; HRESULT: 0
[10:14:33.505 P:150C T:1388 WRTASRWC(0627) WRITER] ENTER[CVssAsrWriterBackup::TranslateWriterError] 
[10:14:33.505 P:150C T:1388 WRTASRWC(0628) WRITER] TranslateWriterError - 0x00000000
[10:14:33.505 P:150C T:1388 WRTASRWC(0633) WRITER] TranslateWriterError - 0x00000000
[10:14:33.505 P:150C T:1388 WRTASRWC(0627) WRITER] EXIT[CVssAsrWriterBackup::TranslateWriterError] Time spent: 00:00:00-0000; total: 0; HRESULT: 0
[10:14:33.505 P:150C T:1388 WRTASRWC(0146) WRITER] EXIT[CVssAsrWriterBackup::OnIdentify] Time spent: 00:00:00-0015; total: 0xf; HRESULT: 0

vssadmin 1.1 - Opdrachtregelbeheerprogramma voor Volume Shadow Copy-service
(C) Copyright 2001-2005 Microsoft Corp.

Naam schrijver: 'Task Scheduler Writer'
 Schrijver-id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
 Id van schrijverinstantie: {1bddd48e-5052-49db-9b07-b96f96727e6b}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'VSS Metadata Store Writer'
 Schrijver-id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
 Id van schrijverinstantie: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'Performance Counters Writer'
 Schrijver-id: {0bada1de-01a9-4625-8278-69e735f39dd2}
 Id van schrijverinstantie: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'ASR Writer'
 Schrijver-id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
 Id van schrijverinstantie: {7ddb5279-28d6-4f25-af34-535b05c33460}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'Shadow Copy Optimization Writer'
 Schrijver-id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
 Id van schrijverinstantie: {5c4742bd-a15c-4769-9e11-7422623c4f35}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'SqlServerWriter'
 Schrijver-id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
 Id van schrijverinstantie: {6b99c086-1f34-4cb8-bea5-887846f86a75}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'Registry Writer'
 Schrijver-id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
 Id van schrijverinstantie: {7a76da99-a6f1-4b4b-85f4-5040079f6487}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'COM+ REGDB Writer'
 Schrijver-id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
 Id van schrijverinstantie: {93839243-d67d-49d2-856e-49a1ec4dc87b}
 Status: [1] Stabiel
 Laatste fout: Geen fout

Naam schrijver: 'WMI Writer'
 Schrijver-id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
 Id van schrijverinstantie: {2ae99e39-7c2c-4fbb-809a-9d42b4aba1ff}
 Status: [1] Stabiel
 Laatste fout: Geen fout

notice that also the BITS writer is missing, but the others seem just fine ...

-> followed instructions in this article : http://briandrab.spaces.live.com/blog/cns!B69C8C4D664E3F01!252.entry?sa=609120164

moved all files under filemaps to a different folder but that didn't work either so i just restored them.

-> I probably could restore the backup from 6/6 completely and reinstall sql + ads, but I want to find out what is happening before I do that, I find not much info on the web over what mechanism makes the writers visible exactly.
This would be a lot of work with no guarantee that things don't break again.

At this point I welcome any suggestion, but i'd like to see some arguments as to why it would be a good idea, not just try this or try that, as I'm trying to understand the whole vss setup a little better.

UPDATE : BITS writer came back in stable state after reboot, so only system writer is still missing.

Hello,

I am working with a client and we are running into issues backing up the Windows Server 2008 System State.

We are running DPM 2007 SP1. We have Windows Server Backup installed on the Server 2008 system, and what we are seeing is that in DPM the System State Backup of the server, the status of the Protection State is "Replica is inconsistent".

The alert in DPM reads the following

Affected area: Computer\SystemState
Occurred since: 3/3/2009 5:31:19 PM
Description: The replica of System State Computer\SystemState on <servername> is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent (ID 3106)
 DPM failed to create the system state backup. If you are trying to create the system state of a Windows 2008 Server operating system, verify that the Windows Server Backup (WSB) is installed, and that there is enough free disk space on the protected server to store the system state. (ID 30214 Details: Internal error code: 0x809909FB)

WSB is installed on the protected system and it has plenty of space.

When I look at the logs on the Server 2008 system, I see the following errors:

Log Name:      Microsoft-Windows-Backup
Source:        Microsoft-Windows-Backup
Date:          3/3/2009 5:11:30 PM
Event ID:      5
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      <servername>
Description:
Backup started at '3/3/2009 4:11:26 PM' failed with following error code '2155348226'.

Log Name:      Application
Source:        Microsoft-Windows-CAPI2
Date:          3/3/2009 8:46:23 PM
Event ID:      513
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <servername>
Description:
Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Details:
AddCoreCsiFiles : BeginFileEnumeration() failed.
System Error:
Access is denied.

Log Name:      Application
Source:        Microsoft-Windows-Backup
Date:          3/3/2009 5:12:58 PM
Event ID:      517
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      <servername>
Description:
Backup started at '3/3/2009 4:12:55 PM' failed with following error code '2155348226' (System writer is not found in the backup.). Please rerun backup once issue is resolved.


I followed the instructions of the following article to make sure that the COM permissions are correct.
http://technet.microsoft.com/en-us/library/cc734021.aspx

Everything is correct, except that when I look at the List of Writers (vssadmin list writers), I do not see the "System Writer" which is what WSB/DPM 2007 is trying to use in the System State Backup.

My question then is, how do I add the System Writer into the subscriber list for VSS?

I have an issue with a server, I have tried doing a BMR restore that's passes but on reboot i get the following error. After a couple of restarts no luck.

Your PC needs to restart
Please Hold down the power button.
Error Code: 0x00000074
Parmamaters:
0x0000000000000001
0x0000000000000002
0xFFFFF8012DAF8260
0xFFFFF80130db3258

Daniel Wingfield

I would like to get a list of the last 20 or so backups, ideally with status, start time, end time, amount of data transferred. Basically the information in Last Backup/View Details window, but for the last 20 backups.

I thought perhaps this information might be available using powershell. Get-WBBackupSet gives me this

VersionId        : 05/31/2018-19:00
BackupTime       : 2018-05-31 21:00:06
BackupTarget     : \\?\Volume{1f595350-71c8-4029-8d46-03e18ed44607}
RecoverableItems : Volumes, SystemState, Applications, Files, BareMetalRecovery
Volume           : {System Reserved, Local disk (C:), Shares (E:)}
Application      : {FRS, AD, Registry}
VssBackupOption  : VssFullBackup
SnapshotId       : 61fb1bfa-bdbc-4ac8-8997-6d78b9de22fc
BackupSetId      : b36d31d3-f56b-4988-8534-4bdd3e88e839

The server is running Windows Server 2012 R2.

I'm trying to restore some files from server backup on different PC.

Is this possible?

Backup was done on Windows server 2016.

I'm trying to restore some files on different PC, with Windows 10 Ent 2018.

I typed this command: 

D:\>wbadmin start recovery -version:06/11/2018-20:00 -itemtype:File -items:'e:\stuff' -backuptarget:f: -recoverytarget:D:

Here is what I'm getting:

wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.

Warning:  The START RECOVERY command is not supported in this version of Windows.
The operation ended before completion.

Does it mean that recovery of single files or parts of backup can be done only on servers?

We have recently installed Window 2008 and are receiving the following message:

Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.

Details:

AddCoreCsiFiles : BeginFileEnumeration() failed.

System Error:

Access is denied.

I have followed all of the posting that are listed and have made sure the necessary rights have been assigned to the c:\windows\registration file but hte "System Writer" will not show when running vssadmin list writers. 

Please help.

Thank you.

I need to set up a scheduled backup, I know I need to use task scheduler and wbadmin to do that, but having trouble setting it up:(

I want to run a Full VSS server backup (System reserved partition, drives C,D,E, BMR, System State, Host Component and one VM). Run it weekly, keep last 4 weeks of backups.

I want to run a full one on Friday night, then incrementals from Saturday till Thursday.

Then run 4x times, but with 28 days retention, so it would always keep last 28 days of backups.

Could you please help me with setting this up?