Does anybody know if your able to automate a BMR such as:

Upon reboot, perform a bare metal restore with NO user interaction, server reboots, and old image is online.

We are unable to attach any USB drives or anything to the server.

Ideas?

I'm trying to backup certain folder and files to a network share and I'm getting this error message. 

Windows Server backup failed to dismount the backup image. Detailed error: Element not found. 

I can't seem to find anything about this any help would be greatly appreciated.

We have Server 2008 R2 that runs our AD and 7 vss writers are currently in failed state which prevents Backup Exec 2010 R3 from successfully completing backup jobs. Server reboot does not make any difference. Any advice how to correct this problem and restart failing writers would be greatly appreciated, please see below:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

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: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {2d04dd9e-7f50-4d73-a209-80e9948d2460}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {18d13944-9659-4b05-a29f-254176b9b83f}
   State: [7] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {316433d1-184e-4b49-b119-531ad256f861}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {5a5e8043-d7b4-42e5-89dd-e039472b677a}
   State: [7] Failed
   Last error: Timed out

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {db6fab26-69d8-4906-b876-5ce442d03c8e}
   State: [7] Failed
   Last error: Timed out

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {5355b534-732a-4f2b-b8ba-73bf64063263}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {1bf8aaa9-a5f7-4fa7-bfca-dcbf3f2a880d}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a03128e5-ee5f-4291-9782-aefa7ef3ab9c}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {627bd54e-9888-443a-ae46-09c5913ae911}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {d180c79c-c74f-4f3f-bff6-7029c764d465}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {eeea94bc-4ecf-453b-83db-8ce7f080156e}
   State: [7] Failed
   Last error: Timed out

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {21ce4154-6e49-4a03-929d-8d6bad8a7080}
   State: [7] Failed
   Last error: Timed out

I have the exact same issue as here:

http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/cd02fdfd-a641-4a76-ba22-5c45fe16c845

Microsoft Windows [Version 6.0.6001]

Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\>wbadmin start systemstatebackup -backuptarget:D:

wbadmin 1.0 - Backup command-line tool

(C) Copyright 2004 Microsoft Corp.

Starting System State Backup [5/12/2011 1:28 PM]

Retrieving volume information...

This would backup the system state from volume(s) Local Disk(C:),New Volume(D:)

to D:.

Do you want to start the backup operation?

[Y] Yes [N] No y

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Creating the shadow copy of volumes requested for backup.

Identifying system state files to backup (This may take a few minutes)...

Found (2523) files

Summary of backup:

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

Backup of system state failed [5/12/2011 1:29 PM]

Log of files successfully backed up

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup 12-05-2011 13-28-35.log'

Log of files for which backup failed

'C:\Windows\Logs\WindowsServerBackup\SystemStateBackup_Error 12-05-2011 13-28-35

.log'

Enumeration of the files failed.

Access is denied.

From the log:

Error in backup of C:\documents and settings\all users\ during read: Error [0x80070005] Access is denied. 

In the linked post, Sandeep explains what the problem is, but not how to fix it.  Thank you in advance for any input you might have!

-Rock

I am running a Windows 2008 x64 R2 standard server.  This server has 2 x 1TB drives that are setup as Raid 1 (mirror) using Window's software raid via Disk Management. Both Disk 0 and Disk 1 are setup as dynamic disks. We are using Tivoli Storage Manager to backup the server.  Everytime we try to do a systemstate backup or backup the indivdual drives with open file support, VSS fails and spits out the following errors in TSM's dsmerror.log file:

06/14/2012 05:59:12 ANS5250E An unexpected error was encountered.
   TSM function name : StartSnapshotSet()
   TSM function      : 'StartSnapshotSet() failed with error VSS_E_SNAPSHOT_SET_IN_PROGRESS. -2147212522'
   TSM return code   : -2147212522
   TSM file          : asrutil.cpp (1918) 
06/14/2012 05:59:12 ANS1468E Backing up Automated System Recovery (ASR) files failed.  No files will be backed up.

06/14/2012 05:59:14 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 05:59:44 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 06:00:14 ANS5261W An attempt to create a snapshot has failed.
Another attempt will be made to create the snapshot in 30 seconds.
06/14/2012 06:00:44 ANS1327W The snapshot operation for 'D:' failed with error code: 653.
06/14/2012 06:00:44 Return code 653 unknown
06/14/2012 06:00:44 Unknown system error
Please check the TSM Error Log for any additional information
06/14/2012 06:00:44 Return code 653 unknown
06/14/2012 06:00:44 Unknown system error
Please check the TSM Error Log for any additional information
06/14/2012 06:00:44 ANS1377W The client was unable to obtain a snapshot of '\\u16247921\d$'. The operation will continue without snapshot support.

After going through IBM's support channels, it was discovered that this was a Microsoft issue, as even running a systemstate backup using the Windows Server Backup tool fails with the following errors showing up in the event log:

The backup operation that started at '‎2012‎-‎06‎-‎15T23:10:50.465000000Z' 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 '2155348075'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({e6ad9a3c-706a-4c97-9354-65be87f4e187}) [hr = 0x800706be, The remote procedure call failed.
]. 

Operation:
   Executing Asynchronous Operation

Context:
   Current State: DoSnapshotSet

When I run a "vssadmin list writers" command I get 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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {6c358ef9-c975-4fe6-96ba-a28710a1eaf6}
   State: [7] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {a7a3b9fe-3a1d-454e-95b5-076142d70a2c}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5e225f9c-af8e-4cb5-b04f-5630d4906057}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {ac277156-d435-490c-9c1b-1357dd7455b5}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {def41fc8-83f8-417f-af7f-ad80ca440dd4}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c2614332-716d-4734-8c36-bdfbb61748b2}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {bb2fd48c-967a-476d-a2ab-5fad1d238ece}
   State: [7] Failed
   Last error: Timed out

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {612a30b0-6d2c-4652-b933-10bf32635e70}
   State: [7] Failed
   Last error: Timed out

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {fee5672a-7b21-4da7-934a-84cc336c0605}
   State: [7] Failed
   Last error: Timed out

I've tried re-registering the writers as suggested in other posts, as well rebooting, but the problem persists. Any help would be most appreciated as I've exhausted most suggestions I've found in the forums.

Hello, we have recently added an oracle database to my server, my boss would prefer we keep 100% of the computers resources to the oracle database and has insisted me to build a new server and put all of my stuff on it. The problem is that I have spent hours and hours configuring that server with exchange server, VPN, file sharing services, etc., the list goes on and on. This is every Network Administrators nightmare.

Bottom line I have made a clone of the hard drive via Acronis, I thought I might get lucky and have similar hardware that the new server I built and it would boot up, I was not so lucky, as expected I got blue screened. I want this to be as simple as possible and after looking around I found there is no recovery/repair install for windows server 2008 that I could use which would just simply write over the system files and install to the new PC hardware while keeping my system settings and configuration in place.

Does anyone have some thoughts on the best way to do this? I have already done repairs to the boot sector via CMD in the recovery disk, no luck. Anyway to copy the registry over or something like that? I just want all of my system settings and configurations transferred to the new server I built.

Thanks

I have got the W2012 Backup running, saving to a volume which is my attached external USB hard drive. It does create its own folder and stores the backups there. But, I am still having some difficulty regarding configuring it. I would like to control its retention policy (ie only store the last 7 backups) so I can keep it from filling up my disk. According to this technet link:

Windows Server Backup Overview for Windows 2012 

this is supposed to be a feature of Windows backup on W2012. But, I cannot for the life of me figure out how to set these options. I can’t find any documentation on the Web that is relevant to this functionality in W2012. Could you please ask one of your Windows Server 2012 experts around there how this is done and share it with me?

Hello All,

I have a HP server that I have just installed Server 2012 standard, SQL Server 2012 and Sharepoint 2013.

When I try to take bare metal backup I get the error: "The system writer is missing", I have tried the backup as the local admin and domain admin.

The backup will only work if I decide to back up C:, once I select "Bare Metal" or "System State" the backup fails.

I have tried this solution: http://technet.microsoft.com/en-us/library/cc734021.aspx but have not had any luck yet.

When I run the command "vssadmin list writers" I can not see "System Writer" listed.

How can I add/turn on the System Writer?

Hello,

it looks like today is a day for problems with Windows Server Backup.

I have a strange problem with Windows Server backup (full backup, sistem state) of a server that has a Hyper-V role installed and hosts some VMs.

I'm doing full backup using Windows Server Backup on iSCSI disk (full backup, system state, but wuthoud VMs configuration files and VHDs). The backup fails to complete (it fails at the start, while doing VSS) with these errors:

2013‎-‎04‎-‎28T09:44:52.293000000Z' 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 '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

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

It is true that I use iSCSI in VMs but I don't know why this is a problem.

Any idea?

Thank you!

Best wishes,
Marko

Здравствуйте,

Не могу установить удаленно агента  Backup Exec 2010 R3 на Win Server 2008 R2 для бэкапа Exchange 2010. Учетка - доменная под кот. делаются бэкапы в системе.

Ошибка следующая:

Ошибка подключения к удаленному компьютеру. Убедитесь, что компьютер доступен, WMI включен и не заблокирован брандмауэром.14

брандмауэр выключен, антивирусник отсутствет, служба WMI включена. Сетевой доступ к серверу есть. Пробовал с учеткой локального админа, дал всевозможные права, но все безуспешно. На другие сервера агент встал замечательно.

We have a issue with our Server 2012 Standard server with Exchange 2010 running Windows Server Backup.  The backup is freezing the server to an extent that mouse and keyboard are frozen, the server does not ping and you are unable to send any sort of reboot command to the device.  It is a case we have to hard reset the server.

The configuration of the server is such: OS and Exchange installed on C drive, Exchange Data and Logs on D drive.  Full server backup configured to backup to dedicated disk in the server.  I am able to create and amend the backup schedule without issue and have checked I have the relevant VSS writers which are showing working status.  Upon the system freeze the event log stops, after reboot I have examined the logs which shows the VSS writers enabling and Shadow Copy status (there are no errors only informational).  The server is installed on the hardware so is not a virtual machine.

Upon first configuration of the windows backup it was working for several days but has then gone into the locking state.  I tried recreating the backup and reformatting the dedicated disk to no avail.  I am currently investigating dedicated backup applications for the server but still have a concern that if they are using any of the inbuilt backup technologies I may end up with the same issue.

Server is full patched with Windows Updates and Hardware is only 4 months old.

I have read several articles to ensure I have the backup correctly configured, eg. setting it to VSS Full Backup, rather than copy.

-------------------------- Many thanks for your time.

I use DPM2012 and was backing up our sharepoint servers.  The SQL data was backing up fine, but the BM/system states were failing.  So trying to see if it's a DPM issue, I went to the server itself and did a wbadmin -allcritial.  It gets between 40-60% before failing with, "The backup operation stopped before completing."  I checked the log in App->Microsoft->Windows->Backup and it has an error with:

Event ID 5

HResult 2147024894

I haven't been able to find any info with this particular error code.  At this point I'm not sure if I should be looking more for a general windows backup issue or if it's a sharepoint issue.  Here's some more of the log info in case that helps. 

Thanks,

-Danny

I have a Server 2008 R2 domain controller and mostly for restores of Active Directory, I want to create systemState backups. However, two problems:

1) since it uses so much space, I don't want to try to do daily backups. I figure that probably a problem will not be found immediately, but rather after a few days; so, I want to create a SystemState backup with wbadmin every 4 days and save maybe 2 or 3. That seems to be impossible as it will only create system state backups with a drive letter assignment, for example (F:) rather than a path (F:\SystemStateBackups\2013-04-29).

2) I've only been able to get it working by doing wbadmin start systemstatebackup -backupTarget:F:, but that only saves one backup. As soon as I run it again, it overwrites the previous one.

I'm not sure why Microsoft made this tool so complex and difficult to use, but I'm hoping that that is the problem rather than it actually being impossible to do.

Please, if someone knows how to at least get more than one system state backup by any means, let me know.

I HAVE WINDOWS 7,I HAVE TRIED MANY TIMES TO FIGURE OUT HOW TO RIP OR ADD A DVD IN THE WINDOWS MEDIA CENTER,SO I CAN MAKE A COPY.PLEASE TELL ME IF I CAN DO THIS AND IF SO HOW.

THANKS,

D.KEN-YATTA CARRINGTON

We have a backup requirement on the servers

• System States
• All data in C:\  

Backup destination D:\

I setup a schedule task to perform a daily backup on every night, however, i noticed that the size will keep growing in D drive, and I understand that the backup snapshot copies will be automatically rotated when the Disk is full by Windows Server backup technology.

But actually my company has a capacity requirement requirement said that every disk drive is not allow to over 90% capacity.

So, is there any way to configure the Maximum size of the rotation trigger level, or is there any way I can I keep the exactly copies (let say 7 copies only) on D drive?

I tried WBADMIN DELETE SYSTEMSTATEBACKUP -keepVersions:1 and WBADMIN DELETE SYSTEMSTATEBACKUP -deleteOldest, they are no use for me as it only make a system states backup. I need a whole system data and system states backup.

Thanks~

Hong Kong guy

Hi,

When we restore a 2008R2 vm on a Windows Server 2012 Hyper-V host as a Backup Using Child Partion Snapshot including the "Host Component" the network settings, i.e. virtual network switch, are not restored. Or are these settings considered part of the host? But then they should be restored with a system state restore, which they don't. Can someone shed some light on this?

Regards

Ueli

I'm receiving event ID 25 every hour with the following error:

The shadow copies of volume F: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.

Volume Shadow Copy is disabled on the drive properties, and the only fix for this (which only fixes it for about a week) is to reboot the server entirely.

2008 R2 with all of the latest updates.

Any ideas?

Hi guys,

I've got a weird issue with Windows Server Backup.

They are not currently scheduled but even though they start at the "supposed" scheduled time.

I checked the logs and found an Event ID 1 stating:

The backup operation has started.

and 10 mins later an Event ID 9 reporting:

The backup operation that started at '‎2013‎-‎04‎-‎30T13:02:09.237000000Z' 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 '2155348001'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

The sad thing is that my Backup solution (Backup Exec) is failing due to the same thing. My guess is that both backup jobs are colliding.

Any ideas why WB is still triggering even is not scheduled?

Thanks.

FRank