Hi 

my schedule backup for the server seems to hang on retrieving volume information. Previously it was working fine.

Please help.

Hi

I have recently added 2 SAS HDD on my server and extend the array and volume to the logical disk. But somehow when it not showing the correct volume size as what the array is showing.

Please help.

WSB issues with Hyper-V guests.

Host is Windows Server 2012 R2, with all current updates installed. Only Hyper-V role.

There are 2 guests, call them guest A and guest B, which both have up to date integration components. Guests are both running Windows Server.

WSB jobs always reports "Completed with warnings". Configured for full server backup.

Guest A backs up online with no issues.

Guest B goes into saved state because it contains dynamic disks. (Guest B runs DPM, therefore by design we have no choice re dynamic disks).

Q 1:

"Pass-through and iSCSI disks are not visible to the host operating system and therefore not backed up by the Hyper-V VSS writer. Backups of these volumes must be done entirely within the VM."

Guest B uses iSCSI to connect to a NAS and that is where the dynamic disks reside.Considering the above statement, I was hoping the VM could be backed up online, as the dynamic disks are apparently not visible to the host.

Is there any tweak to ignore the dynamic disks so that the guest can be backed up online? Note we’re not trying to include the iSCSI volumes in the guest backup. The point is if the dynamic disks are not visible to the host because they’re iSCSI-based then why should this prevent an online backup of the guest?

Q 2:

I am trying to understand if the saved state backup is the reason the backup job is 'completing with warnings', or if we have a separate problem.

When the backup runs it backs up the physical volume containing the guest B VHDX, and it test restores successfully.

But the item in WSB named "guestb(Offline)", reports status "Backup failed to complete". It acknowledges that it is trying to do an offline backup since it says "(Offline)", so the dynamic disks should not be an issue being on offline backup.

I have tried disabling "Backup (volume checkpoint)" integration service component in the guest settings but it still fails with the same error.

When the same guest was running on Windows Server 2012 (R1) with Hyper-V this was not an issue. But since moving the guest to a new server running R2 we get "Backup failed to complete" and "Completed with warnings".

I have observed a similar issue with another customer using R2. If guest is shutdown i.e. Off, WSB reports the same error messages as above. Turn the VM back on, and it completes an online backup with no issues reported. It seems silly that we cannot get a clean backup result just because a guest is shutdown. Is this correct?

On windows server 2012 R2 am able to create NFS share.

But when i look at the version i could see Mounted version 3 where i would like to use version 4.

can somebody help me to configure the NFS v4 on the windows server 2012 r2

Hi, I have some quesstions regarding WS2012 Backup

1)from http://technet.microsoft.com/en-us/library/cc732540.aspx 
"If you use a remote shared folder, make sure that the folder is available, that you have write access to the folder, and that you are a member of the Administrators group or Backup Operators group on the computer hosting the folder. Each time you create a backup, it will overwrite the older backups so that you will only have one backup at a time. The backup will inherit the access control list (ACL) permissions of the folder."

Is possible to store multiple backups (Bare metal recovery + SystemState + C:)  on a external harddrive using just the GUI? 

2)i run "wbadmin get versions" and got a list of around 30previous backups of same server (Bare metal recovery + SystemState + C:) and every backup should be around 30GB, but if I mount the external hard drive reserved for backups i can only find one .vhdx of 30GB. Is it normal?

Thank you

We recently implement a new Windows 2012 R2 domain controller but have been unable to take a system state backup using Windows Backup.  We get the following error?

There was a failure in updating the backup for deleted items.  Error code 0x8078014D

We have other Windows 2012 R2 domain controllers that we can backup the system state on using Windows Backup without any issues.

Hi,

Of 10 WS2012R2 backing up to either a NAS or a local USB drive, 6 generate the event ID 51 warning (An error was detected on device \Device\<var>DeviceName</var> during a paging operation) during the backup operation. All 6 servers are domain controllers.

The remaining 4 WS2012R2s do not log this warning, these 4 are not domain controllers.

What does this warning mean? Can we ignore this warning? The backup jobs run otherwise successfully.

Thanks

Ueli

Hello folks,

please can anybody give me advise?

I am running two Dell servers with Windows SRV 2012 STD, I am able to backup server on Synology RS 812 without any issue but I am unable to backup servers on WD MyCloud 2TB.

Errors are follow:

There was a failure in preparing the backup image of one of the volumes in the backup set.
 Detailed error: Incorrect function

The backup operation that started at '‎2014‎-‎11‎-‎30T17:39:53.657001600Z' 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.

I tried lot of resolution I found on the interent - SMB2 and 3 disabling, make shared folder public, run backup with and without NAS credentials and so on.

These settings doesnt help me also:

https://social.technet.microsoft.com/Forums/windows/en-US/c2032e37-ebe9-4221-9d37-5525fcdaae19/windows-8-backup-win7-file-recovery-system-image-creation-to-nas-device-fails-with-error?forum=w8itprogeneral

http://community.wd.com/t5/WD-My-Cloud/What-capabiliities-does-My-Cloud-offer-on-the-local-LAN/td-p/601011

Thank you for every help.

Regards,

Jan

Jendislav

Hey,

I'm using DPM 2012 backup system status for Windows Server 2008 R2, it failed with WSB Event ID: 521, WSB Error Code:  0x65C8C0). From Event log on protected computer, there is Event 512 and  error code 2155348249, the error appears to be caused by low disk space on the protected computer, however with my validation, the free disk still has about 40GB on the system volume(Note: protected computer just only one driver C:)

What should I next? Thanks.

Steve Xu

Hi,

Removable Storage Manager option is not available in Add/Remove Features of Server Manager.

I also tried Installing the "Windows6.1-KB974674-x64" but no luck, it prompts to turn on the Removable Storage Management.

Please help me to enable the RSm in Add/Remove features of Server Manager.

Thanks!

Hi Everyone,

I have single server domain environment with Server 2012 Std. and MS SQL 2012.

The problem is, I can’t perform backup. I’m fighting almost three weeks.

On two occasions, I have been successful. I used suggestions from Microsoft TechNet, however after several day performing backup, without any reasons, the problem appears back.

Now I can’t find solution about this error:

The error message is Event ID 8193:

Volume Shadow Copy Service error: Unexpected error calling routine CreateVssExamineWriterMetadata. hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.

Check the Application event log for more information.

Operation:

   Writer Exposing its Metadata

Context:

   Execution Context: Requestor

   Writer Instance ID: {2A478936-603E-4202-997C-458A46F0301F}

   Writer Class Id: {E8132975-6F93-4464-A53E-1050253AE220}

   Writer Name: System Writer

I did check VSS writers list:

C:\>vssadmin list writers

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

(C) Copyright 2001-2012 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: 'SqlServerWriter'

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

   Writer Instance Id: {d9b1eedd-23b7-4ed3-a012-2c6bdf5a01ca}

   State: [1] Stable

   Last error: No error

Writer name: 'ASR Writer'

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

   Writer Instance Id: {81b3c537-771b-4c3f-83e5-8e6e5471d229}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

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

   Writer Instance Id: {f291416a-f7c5-4b57-a3a1-5a03983efed8}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

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

   Writer Instance Id: {e671f460-7782-4043-b8cd-3c1dde2b80d9}

   State: [1] Stable

   Last error: No error

Writer name: 'IIS Config Writer'

   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}

   Writer Instance Id: {5248dd01-dc52-42f4-b7f7-62f79aaacbea}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

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

   Writer Instance Id: {54d5e97b-bc0d-4927-96e8-9e6db7bfc322}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

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

   Writer Instance Id: {ef0120aa-96b6-4bca-bf30-1fb8c17e023a}

   State: [1] Stable

   Last error: No error

Writer name: 'IIS Metabase Writer'

   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}

   Writer Instance Id: {2e906301-7e6e-4ce1-8417-78ef1556722b}

   State: [1] Stable

   Last error: No error

Writer name: 'DFS Replication service writer'

   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}

   Writer Instance Id: {0b2eef10-f971-421a-9f32-87e48aae01be}

   State: [1] Stable

   Last error: No error

Writer name: 'NTDS'

   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}

   Writer Instance Id: {2d579b36-ed89-41b9-a5ac-feb572d3514f}

   State: [1] Stable

   Last error: No error

I know, System Writer is missing.

There a lot suggestion on WEB, however nothing helps. Everything else, on the server, works fine.

The suggestion from Microsoft: http://technet.microsoft.com/en-us/library/ee264196(v=ws.10).aspx, is bizarre.

Of course, the Volume Shadow Copy is set to manual.

Also I did try several other sites, ex.: http://systemadministratorrecipes.blogspot.com/2012/08/event-id-8193-vss-error-server-2008-r2.html, but nothing helps.

Does anyone have any idea?

Best regards,

Aleksandar B. MCITP/MCSA

FreeLibrary Fails with Application verifier

I'm having trouble backing up one of our servers.

I've tried to take a manual shadow copy, but that fails too.

This is the output from the diskshadow:

DISKSHADOW> set context persistent

DISKSHADOW> set verbose on
istent
DISKSHADOW> add volume C:

istent
DISKSHADOW> add volume \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\

DISKSHADOW> create
me \\?\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}\Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.

* Including writer "Task Scheduler Writer":+ Adding component: \TasksStore

* Including writer "VSS Metadata Store Writer":+ Adding component: \WriterMetadataStore

* Including writer "Performance Counters Writer":+ Adding component: \PerformanceCounters

* Including writer "SqlServerWriter":+ Adding component: \ASTAREG-APP01\ASTAREG\master
--removed several lines to keep it readable. (approx 1400 lines)+ Adding component: \ASTAREG-APP01\ASTAREG\unit_450

* Including writer "System Writer":+ Adding component: \System Files

* Including writer "ASR Writer":+ Adding component: \ASR\ASR+ Adding component: \Volumes\Volume{21d0911e-a727-11e2-8124-806e6f6e6963}+ Adding component: \Volumes\Volume{21d0911f-a727-11e2-8124-806e6f6e6963}+ Adding component: \Disks\harddisk0+ Adding component: \BCD\BCD

* Including writer "Registry Writer":+ Adding component: \Registry

* Including writer "COM+ REGDB Writer":+ Adding component: \COM+ REGDB

* Including writer "WMI Writer":+ Adding component: \WMI

The last operation failed.
	- Returned HRESULT: 80042302
	- Error text: VSS_E_UNEXPECTED

Output from vssadmin list writers:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\administrator.LOCAL>vssadmin list writers
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: {1642a445-03f7-47aa-8c2a-026970ffe2a5}
   State: [11] Failed
   Last error: Retryable error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {c7f14ce1-862d-469c-a0f6-4d04f40a6154}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {8b7f6ee8-caec-426f-9bb8-a4604676be94}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {31e7e45c-a2d2-444a-9658-08f51e1223c5}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {03f58120-3f0f-4388-8d79-b18780dac432}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {33d15e4b-bf9e-4fd5-a85c-491b55cda09e}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {b048fc99-96a3-4c76-8077-a5e85f34c768}
   State: [1] Stable
   Last error: No error

I have a brand new 2008R2 SP1 server (Domain Controller) where I try to make SystemState backup. Backup seems to work fine, but I can not delete oldest.
I'm uncertain if I do have a valid SS backup.

I take backup with this command:

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

Starting to back up the system state [04-08-2011 08:45]...
Retrieving volume information...
This will back up the system state from volume(s) Local Disk(EFI System Partitio
n) (200.00 MB),C-OS(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...
Windows Server Backup is updating the backup for deleted items.
This might take a few minutes.
Found (96) files.
Found (13207) files.
Found (29482) files.
Found (39566) files.
Found (78588) files.
Found (79088) files.
The search for system state files is complete.
Starting to back up files...
The backup of files reported by 'Task Scheduler Writer' is complete.
The backup of files reported by 'VSS Metadata Store Writer' is complete.
The backup of files reported by 'Performance Counters Writer' is complete.
Overall progress: 1%.
Currently backing up files reported by 'System Writer'...
 - continuing to 100% -

Summary of the backup operation:
------------------

The backup of the system state successfully completed [04-08-2011 08:59].
Log of files successfully backed up:

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

If I check the backup with "Get Versions", I get this:

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

C:\>wbadmin get versions
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Backup time: 30-07-2011 21:00
Backup target: Fixed Disk labeled D:
Version identifier: 07/30/2011-19:00
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {6f4f38c8-3d3c-4e9f-87fb-d7cdb9c13c59}
 - several other backups-

Backup time: 04-08-2011 08:45
Backup target: Fixed Disk labeled D:
Version identifier: 08/04/2011-06:45
Can recover: Volume(s), File(s), Application(s), System State
Snapshot ID: {ae749899-447f-4c6d-b2d3-06c2f1816541}

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

So far everything seems ok.
But when I try to delete the oldest backup, things look weired:

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

C:\wbadmin delete systemstatebackup -deleteOldest
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

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

If I try with -keepversions, I get same result:

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

C:\>wbadmin delete systemstatebackup -keepversions:1
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

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

So do I have a valid Systemstate backup ?
And can I trust I can use it to recover if needed, since it says "No system state backups were found" ?
And why can't I delete the oldest backup ?

- Duelund

Hi all.

Why do we non-authoritative restore? Much easier to promote new server and replicate it.

Hi,

I have read through for forum to see any previous posts that can apply to the problem I have. There are a few but none of those are answered with solution. If anyone knows the answer for fixing my backup problem below, I will send a million thanks :)

I have a Windows server 2012 R2 standard running as a file server. It has drives as below:

C drive: O/S

D drive: DVD rom

E drive: data. Shared folder. Users map to shared folder in E drive

F drive: Backups drive. Use it to backup the "E\share" folder

E drive has a folder called "share". This folder has about 2TB

F drive has 4.5TB. It's a set of raided drives, Raid 5 using Dell Powervault MD 1000

I'm using the built-in Windows server backup utility(wbadmin) to backup E\share to F drive. The problem is that the backup utility can only keep 1(one) backup file. The properties of F drive shows it has plenty of space. However, if I run 5 backups within one day, it does NOT delete previous backups. The problem is it delete all backups when next day the backup runs. Question is:

Why doesn't it delete other backups ran within the same day?

Why does it delete all backups on the next day it runs the backup?

It appears that it's not the hardware or F drive issues in my case. It's something with configuration or setting under Windows registry and it flags to delete all backups on the next day the wbadmin backup runs. I already formatted and re-installed Windows server 2012 on this machine and it does the same. Did anyone in here ever have this weir situation like this before? I also replaced all the drives in MD1000 to make a new F drive but the backup still does the same.  It's weirder than weird. I have spent my time for last 3 weeks but could not find a solution to fix this issue. Please help...

Hi, 

I have a script running the below 

Wbadmin start backup -backupTarget:\\192.*.*.*\Jupitor\serverBackup\%dd%%mm%\CDrive -include:C: -vssFull -quiet > cDrive_log.txt
Wbadmin start backup -backupTarget:\\192.*.*.*\jupitor\serverBackup\%dd%%mm%\DDrive -include:D: -vssFull -quiet > dDrive_log.txt

I run this command wbadmin start recovery -version: ***********-** -itemtype:file -items:d:\bkup\monday\**.dbf  it shows me "invalid specific path"

Thanks and Regards Cityuser

Hi all,

we have two backup disks e: and f:

• e: is used for weekly backups, 40GB total size, 4.895.141.888 bytes free
• f: is used for daily backups, 100GB, 51.933.102.080 bytes free

Now in total we get only 5 backup versions /shadow copies. One located on drive e: and four located on drive f:

While I can understand the 1/8 rule for drive e:, I can not understand this for drive f:?

Maximum Shadow Copy Storage space: UNBOUNDED (100%) for both drives.

Why is WSB not using the  51.933.102.080 bytes free space on drive f: to create more shadow copies?

Shadow Copy Storage association
   For volume: (F:)\\?\Volume{502f9d83-eee4-11e2-a783-d89d671af684}\
   Shadow Copy Storage volume: (F:)\\?\Volume{502f9d83-eee4-11e2-a783-d89d671af684}\
   Used Shadow Copy Storage space: 10.984 GB (11%)
   Allocated Shadow Copy Storage space: 11.518 GB (11%)
   Maximum Shadow Copy Storage space: UNBOUNDED (100%)

Any hints?

Many thanks in advance.

Claus

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.