I'm having a hard time getting used to wbadmin, as I come from a NTbackup background.

I have this situation: One Windows 2008 R2 server, with roles Active Directory, file server, print server, DNS server and DHCP server. Operating system is on C: (total size 100 GB, 60 GB used) and file server's data is on E: (total size 380 GB, 300 GB used).

We have bought two external USB hard disks, each of 2 TB, labelled "USB-A" and "USB-B". Both "USB-A" and "USB-B" are never plugged at the same time to the server. Both "USB-A" and "USB-B" have been assigned the "K:" volume letter. All this works fine.

What we want: daily backups for week-1 to USB-A, daily backups for week-2 to USB-B, daily backups for week-3 to USB-A, daily backups for week-4 to USB-B, daily backups for week-5 to USB-A, and so on...

I run this command daily at 21:05 h. from the Windows server task scheduler:

wbadmin start backup -backupTarget:K: -include:C:,E: -exclude:"E:\$RECYCLE.BIN","E:\System Volume Information","E:\programs","E:\Users\TestUser","C:\TEMP" -vssfull -allCritical -systemState -quiet >> C:\TEMP\backuplog.txt

(Ok, I know it is redundant to say at the same time -allCritial with -include:C: and -systemstate, but lets put that aside for now.)

The problem: when on Monday, we want the backup to "start fresh", i.e. to make a full backup from scratch, discarding whatever old backups may be in the K: volume. What it happens on Monday is that the wbadmin program does an "incremental backup" over the last backup from the Friday nine days before. We do not want this (plus it takes almost 20 hours to finish, whereas a full backup from scratch only takes about 6 hours). Essentially, we want every Monday to make a full backup from scratch on K:, but we don't know how to force wbadmin to do so.

Any help, please?

Hi,

My laptop, running Windows 2008 x64, drained it's battery this weekend, while in standby. When trying to boot this morning, I got a 

Status: 0xc000000e

Info: The boot selection failed because a required device is inaccessible.

After restoring a bare metal backup from friday, I get that same message. Reinstalling the OS leaves me a workable system, but that's not really an option and makes the whole full system backups and bare metal restore obsolete.

Google takes me to a couple of posts, including one from Microsoft, that suggest using bcdedit to fix it. Since I'm posting here, y'all probably figured that that didn't work :/

The other posts say that bcdedit output says that there is a "device unknown" in the Windows Boot Loader configuration, like this

Windows Boot Loader
-------------------
identifier {default}
device unknown <===0xc000000e problem! 
path \Windows\system32\winload.exe
description Windows Server 2008 R2
locale en-US
inherit {bootloadersettings}
recoverysequence {e0025536-b36d-11de-aadd-ddc0b5870e2c}
recoveryenabled Yes
osdevice unknown <===0xc000000e problem! 
systemroot \Windows
resumeobject {e0025534-b36d-11de-aadd-ddc0b5870e2c}
nx OptOut
hypervisorlaunchtype Auto

In my case, it says "partition=D:". While this doesn't seem out of place, it's weird, since it should be C:.

When using diskpart, I can see that the System Reserved Partition is being mounted as C and that my C partition is now D. My guess is that this causes my problems. Or is it normal for that System Reserved Partition to be mounted in Recovery console?

Does anyone know how to fix this? Or at least why my restore also fails? Well, it doesn't actually fail, but leaves the system barely operable...

Hi. Now i testing Windows Backup on 2012. I have two virtual servers. One server is Domain Controller of domain "mydomain.localnet"

I made backup System State and now i want restore this backup on second virtual server. Backup file was copy to second server.
the first thing that I noticed: DSRM not available without installed AD DS and configure new domain. So, i have configured new domain "test-domain.localnet".

After my first try using command "wbadmin systemstaterecovery -start -version:12/04/2012-16:09 -backuptarget:C: -authsysvol" recovery system share folder not recovered. After second recovery - all forder in place. Test client with Windows 8 can authorize on new DC.  So, i think recovery AD have success. But...

On log i have same warning:

Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.test-domain.localnet.' failed.
These records are used by other computers to locate this server as a domain controller 
(if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). 

Possible causes of failure include: 
- TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers 
- Specified preferred and alternate DNS servers are not running 
- DNS server(s) primary for the records to be registered is not running 
- Preferred or alternate DNS servers are configured with wrong root hints 
- Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration 

USER ACTION 
Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' 
from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

Why i have message about my test-domain.localnet if i have restoring AD DS whith my domain? How i can fixed it?My first server is shootdown.

And why, after restoring backup the settings of network card - set to Dynamic ? I thoght network settings included on System State...

Thank you!

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.

Hi there,

I have an on-going issue with one of my clients servers and was wondering if anyone has had similar issues?

I run an NT Backup of the server every evening using Backup Assist. The job usually takes around 6 hours. Lately, the job has been over running and either taking 23 hours or timing out completely. This is obviously not acceptable.

I have spoken to Backup Assist tech dept and they say the problem lies with NT Backup. This makes sense as Backup Assist is only a wrap around for NT Backup.
I have run an NT Backup outside of Backup Assist and the problem still remains. Either the job times out or over runs.
This is now happening every night. However, if I reboot the server prior to the backup job starting, the backup completes successfully in the usual time of around 6 hrs.

There are no other jobs or scheduled tasks running at the same time as the backup itself.
I suspect the reason that the backup completes successfully after a reboot is due to the removing of temp files or unloading of cached data?

Please let me know if anyone has had a similar issue or has a possible resolution.

Many thanks.

Scott.

We're currently running into issues backing up our Windows Server 2012 VMs through the integrated Windows Server Backup utility. Each time the VM attempts to backup to the Shared Network Folder on our QNAP NAS, it generates the following event log on the VM:

Log Name:      Microsoft-Windows-Backup
Source:        Microsoft-Windows-Backup
Date:          2012-12-20 4:02:55 AM
Event ID:      5
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      TST12.dev.ad
Description:
The backup operation that started at '‎2012‎-‎12‎-‎20T11:00:25.289755100Z' 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.
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>5</EventID>    <Version>3</Version>    <Level>2</Level>    <Task>0</Task>    <Opcode>0</Opcode>    <Keywords>0x4000000000000000</Keywords>    <TimeCreated SystemTime="2012-12-20T11:02:55.974675700Z" />    <EventRecordID>29</EventRecordID>    <Correlation />    <Execution ProcessID="5312" ThreadID="3776" />    <Channel>Microsoft-Windows-Backup</Channel>    <Computer>TST12.dev.ad</Computer>    <Security UserID="S-1-5-18" />  </System>  <EventData>    <Data Name="BackupTemplateID">{929C5B37-29BF-46B2-B72B-C2819B13EB6D}</Data>    <Data Name="HRESULT">0x807800c5</Data>    <Data Name="DetailedHRESULT">0x8078004f</Data>    <Data Name="ErrorMessage">%%2155348165</Data>    <Data Name="BackupState">12</Data>    <Data Name="BackupTime">2012-12-20T11:00:25.289755100Z</Data>    <Data Name="BackupTarget">\\BMC-NAS1\Backups</Data>    <Data Name="NumOfVolumes">2</Data>    <Data Name="VolumesInfo">&lt;VolumeInfo&gt;&lt;VolumeInfoItem Name="System Reserved" OriginalAccessPath="" 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="554" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" 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" /&gt;&lt;/VolumeInfo&gt;</Data>    <Data Name="SourceSnapStartTime">2012-12-20T11:00:25.258548500Z</Data>    <Data Name="SourceSnapEndTime">2012-12-20T11:00:43.682705500Z</Data>    <Data Name="PrepareBackupStartTime">&lt;TimesList&gt;&lt;Time Time="2012-12-20T11:00:53.011Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="PrepareBackupEndTime">&lt;TimesList&gt;&lt;Time Time="2012-12-20T11:00:53.058Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="BackupWriteStartTime">&lt;TimesList&gt;&lt;Time Time="2012-12-20T11:00:53.074Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="BackupWriteEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data>    <Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data>    <Data Name="DVDFormatStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>    <Data Name="DVDFormatEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>    <Data Name="MediaVerifyStartTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>    <Data Name="MediaVerifyEndTime">&lt;TimesList&gt;&lt;/TimesList&gt;</Data>    <Data Name="BackupPreviousState">9</Data>    <Data Name="ComponentStatus">&lt;ComponentStatus&gt;&lt;/ComponentStatus&gt;</Data>    <Data Name="ComponentInfo">&lt;ComponentInfo&gt;&lt;/ComponentInfo&gt;</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">&lt;SystemState IsPresent="1" HResult="-2139619131" DetailedHResult="-2139619249" /&gt;</Data>    <Data Name="BMR">&lt;BMR IsPresent="1" HResult="-2139619249" DetailedHResult="0" /&gt;</Data>    <Data Name="VssFullBackup">true</Data>    <Data Name="UserInputBMR">true</Data>    <Data Name="UserInputSSB">true</Data>    <Data Name="BackupSuccessLogPath">C:\Windows\Logs\WindowsServerBackup\Backup-20-12-2012_11-00-25.log</Data>    <Data Name="BackupFailureLogPath">C:\Windows\Logs\WindowsServerBackup\Backup_Error-20-12-2012_11-00-25.log</Data>    <Data Name="EnumerateBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="EnumerateBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="PruneBackupStartTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="PruneBackupEndTime">&lt;TimesList&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;Time Time="1601-01-01T00:00:00.000Z" /&gt;&lt;/TimesList&gt;</Data>    <Data Name="BackupFlags">0x8</Data>    <Data Name="ComponentInfoSummary">&lt;ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /&gt;</Data>  </EventData></Event>

All our VMs running Windows Server 2008 R2 backup successfully to this network location using the same network and service credentials. This issue appears to only be happening on our VMs running Windows Server 2012. 

Hi,

I have a problem with backup on one our server Win2008 R2 Standard. Server is up-to-date.
I try to backup system state by command wbadmin start systemstatebackup -backuptarget:d: Each second backup fails with error:The Windows Backup engine could not be contacted. Retry the operation. The RPC server is unavailable.

Whole record:

wbadmin start systemstatebackup -backuptarget:D:
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Starting to back up the system state [3.8.2011 9:31]...
Retrieving volume information...
This will back up the system state from volume(s) Local Disk(EFI System Partition) (200.00 MB),SYSTEM(C:) to D:.
Do you want to start the backup operation?
[Y] Yes [N] No y

Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Please wait while system state files to back up are identified.
This might take several minutes...
Please wait while system state files to back up are identified.
This might take several minutes...
Please wait while system state files to back up are identified.
This might take several minutes...
Found (3) files.
Found (3) files.
Found (3) files.
Found (33) files.
The Windows Backup engine could not be contacted. Retry the operation.
The RPC server is unavailable.

vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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: {fe637c05-031b-4abb-a574-11efefd2c2c5}
  State: [1] Stable
  Last error: No error

Writer name: 'System Writer'
  Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
  Writer Instance Id: {41844ff0-2078-4315-a191-aa3c3fa5a656}
  State: [1] Stable
  Last error: No error

Writer name: 'Registry Writer'
  Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
  Writer Instance Id: {3442677d-5517-44e0-aba2-6cd8db34b904}
  State: [1] Stable
  Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
  Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
  Writer Instance Id: {d85e7e95-5e42-4589-979b-b720a4856236}
  State: [1] Stable
  Last error: No error

Writer name: 'COM+ REGDB Writer'
  Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
  Writer Instance Id: {e70a7c93-c37b-43e3-a95f-a12e21ec160e}
  State: [1] Stable
  Last error: No error

Writer name: 'WMI Writer'
  Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
  Writer Instance Id: {9c364129-6d2b-4a27-ac3b-f1d3d599f218}
  State: [1] Stable
  Last error: No error

Status of VSS writers after failed backup:

vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 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: {fe637c05-031b-4abb-a574-11efefd2c2c5}
  State: [1] Stable
  Last error: No error

Writer name: 'System Writer'
  Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
  Writer Instance Id: {41844ff0-2078-4315-a191-aa3c3fa5a656}
  State: [5] Waiting for completion
  Last error: No error

Writer name: 'COM+ REGDB Writer'
  Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
  Writer Instance Id: {e70a7c93-c37b-43e3-a95f-a12e21ec160e}
  State: [5] Waiting for completion
  Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
  Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
  Writer Instance Id: {d85e7e95-5e42-4589-979b-b720a4856236}
  State: [5] Waiting for completion
  Last error: No error

Writer name: 'Registry Writer'
  Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
  Writer Instance Id: {3442677d-5517-44e0-aba2-6cd8db34b904}
  State: [5] Waiting for completion
  Last error: No error

Writer name: 'WMI Writer'
  Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
  Writer Instance Id: {9c364129-6d2b-4a27-ac3b-f1d3d599f218}
  State: [5] Waiting for completion
  Last error: No error

When I start next backup it finnish OK and all writers are:

  State: [1] Stable
  Last error: No error

I already tried re-register VSS writers but without success.

There is one error in system event log after backup:

Log Name:   System
Source:    Service Control Manager
Date:     3.8.2011 11:32:02
Event ID:   7031
Task Category: None
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   server_name
Description:
The Block Level Backup Engine Service service terminated unexpectedly. It has done this 1 time(s). 
The following corrective action will be taken in 120000 milliseconds: Restart the service.

and one error in application event log:

Log Name:   Application
Source:    Application Error
Date:     3.8.2011 11:32:02
Event ID:   1000
Task Category: (100)
Level:     Error
Keywords:   Classic
User:     N/A
Computer:   server_name
Description:
Faulting application name: wbengine.exe, version: 6.1.7600.20687, time stamp: 0x4bbe9bee
Faulting module name: ntdll.dll, version: 6.1.7600.16695, time stamp: 0x4cc7b325
Exception code: 0xc0000005
Fault offset: 0x0000000000053874
Faulting process id: 0x13d4
Faulting application start time: 0x01cc51b420b404b2
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 0f6a224a-bdab-11e0-90c1-02215e9c3d33

Do you have any idea what can cause this problem?
Thanks for help.

Jakub

Hello

I have some Exchange 2007 databases on an old EMC Clariion SAN, and have created new ones on a new NetApp SAN.

Exchange is a CCR cluster.  On the currently passive node, Windows Backup of all volumes shows as 'Successful', but I get a bunch of these errors for each storage group:

... and the NetApp logs are not truncated.

Trying a backup of all volumes on the active node, this time it shows as 'Failed'.  The status is 'One of the backup files could not be created', and the NetApp logs partition has 0KB of 0KB Data Transferred.  The errors on the active node are slightly different for each storage group:

Exchange VSS Writer (instance e3091ad4-23b5-4d66-9abd-e6ed97ff6ade:1) has unsuccessfully completed the backup of storage group 'PublicFolderStorageGroup1'. No log files have been truncated for this storage group.

... followed by ...

I'm getting the following error:

Log Name:   Microsoft-Windows-Kernel-EventTracing/Admin
Source:    Microsoft-Windows-Kernel-EventTracing
Date:     5/17/2010 11:04:48 AM
Event ID:   2
Task Category: Session
Level:     Error
Keywords:   Session
User:     ****
Computer:   ****
Description:
Session "WbadminInBuiltTracing" failed to start with the following error: 0xC0000035
Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"><System><Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" /><EventID>2</EventID><Version>0</Version><Level>2</Level><Task>2</Task><Opcode>12</Opcode><Keywords>0x8000000000000010</Keywords><TimeCreated SystemTime="2010-05-17T18:04:48.898886000Z" /><EventRecordID>45</EventRecordID><Correlation /><Execution ProcessID="4816" ThreadID="2800" /><Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel><Computer>****</Computer><Security UserID="****" /></System><EventData><Data Name="SessionName">WbadminInBuiltTracing</Data><Data Name="FileName"></Data><Data Name="ErrorCode">3221225525</Data><Data Name="LoggingMode">2</Data></EventData></Event>

Does anyone know what this is or how to prevent it from occurring?

I'm running Windows Server 2008 R2.

Thanks much,
James

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>

im trying out powershell cmdlets for Windows server Backup tool (http://technet.microsoft.com/en-us/library/ee706683.aspx), and im able to do it perfectly. But there are no cmdlets specified for recovery of the same.

Im looking for an Powershell command that could perform what the below webadmin comand does

wbadmin start recovery

According to the below source, the recovery cmdlets are supported in powershell, but im unable to find them.

http://technet.microsoft.com/en-in/library/dd979562%28v=ws.10%29.aspx

plz help me guyz

I have Hyper-V installed on my Windows Server 2008 R2. I'm trying to create a backup of all system state. Using the Windows Server Backup utility whenever I try to "backup once", the backup fails with the following message

"The backup operation that started at '‎2011‎-‎11‎-‎17T22:31:05.700000000Z' 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 '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

I executed "vssadmin list writers" getting the following output:

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: 'Microsoft Hyper-V VSS Writer'

   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}   Writer Instance Id: {2926a618-af61-449d-b36d-cda547f22708}   State: [8] Failed   Last error: Inconsistent shadow copy



Writer name: 'System Writer'

   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}   Writer Instance Id: {c6a127d1-ff00-49e4-8b0e-20690fbb8f40}   State: [5] Waiting for completion   Last error: No error



Writer name: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}   Writer Instance Id: {b28b2e7a-2275-432f-9ce1-2f0fcc8c8621}   State: [1] Stable   Last error: No error



Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}   Writer Instance Id: {e6469584-321c-4a47-b141-cba16add6e6b}   State: [1] Stable   Last error: No error



Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}   Writer Instance Id: {f29ac3b4-b02d-486f-9ae4-be781f77768a}   State: [1] Stable   Last error: No error



Writer name: 'SqlServerWriter'

   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}   Writer Instance Id: {510585c1-bdf8-4280-9e88-1796934ecf58}   State: [1] Stable   Last error: No error



Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}   Writer Instance Id: {f710d31d-3afc-4ad9-8965-e9856a9ab349}   State: [5] Waiting for completion   Last error: No error



Writer name: 'COM+ REGDB Writer'   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}   Writer Instance Id: {3b8ee4d9-a032-4dcb-ac34-6552007b0da7}   State: [1] Stable   Last error: No error



Writer name: 'IIS Config Writer'

   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}   Writer Instance Id: {f0622c15-6b81-4545-8628-f35979666d64}   State: [5] Waiting for completion   Last error: No error



Writer name: 'BITS Writer'

   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}   Writer Instance Id: {39f712ed-d174-4e36-9c1b-2aabb819c0c7}   State: [1] Stable   Last error: No error



Writer name: 'NPS VSS Writer'

   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}   Writer Instance Id: {95fd9723-6ade-4adf-8100-dd473e98e06f}   State: [5] Waiting for completion   Last error: No error

Also, VSS errors can be seen of the following type

Volume Shadow Copy Service error: Writer with name Microsoft Hyper-V VSS Writer and ID {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} attempted to subscribe in safe mode. 



Operation:

   Initializing Writer



Context:

   Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}   Writer Name: Microsoft Hyper-V VSS Writer




Volume Shadow Copy Service error: Writer with name WMI Writer and ID {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} attempted to subscribe in safe mode. 



Operation:

   Initializing Writer



Context:

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

Hi all,

I've searched the forums and can't seem to find an answer to my question.

I'm attempting to put together a backup strategy using wbadmin. I want to have 1 full backup with 5 days incremental. I realize that wbadmin appends the incremental changes to the backup file which is OK. I plan to do a nightly zipping of the WindowsImageBackup folder and push it off to my backup server.

Upon testing the restoration of those backup files I only see the last backup if I choose "A backup stored on another location" option. If I restore the backup catalog using the following:

wbadmin restore catalog -backupTarget:{DRIVE LETTER OF BACKUPS}

I can then see the incremental backups if I use the "This server" option , but I can't restore them because they don't like being restored from a different volume.

My question is, is there any way around this? Can I restore a series of incremental backups to another machine using a different drive using wbadmin?

Thanks!

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!