Hello,

Our system is composed of over 20 sites at geographically different locations, and two of the sites are the major server farms.
The two site are the primary and the secondary; the primary is to fail over to the secondary should the primary go down.

We are deploying AD CS for issuing certificates to users, and we need to back up AD CS so that it will also fail over to the secondary, along with other services (Exchange, Lync, etc.).

We would like to know whether it is possible to
1. Set up the AD CS server as a virtual machine.
2. Back up the AD CS server from the primary to the secondary using Hyper-V Replica.
3. Restore the replicated VM at the secondary site when a failover happens.

One more thing: our network bandwidth between the two major sites is *rather* limited.
Does anyone know if this would work or not?

Thanks,

Wanko

Hi,

We have enterprise vault 11 and Backup exec 2014 installed on Windows server 2008 R2 Enterprise edtion and Enterprise Vault on 2008 R2 Standard edition  respectively, from past few months the backup fails with the error access denied contacted Symantec for the case now Symantec has asked to look into the O.S level of Enterprise vault server.

The autoshare registry key path in the registry is  (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters) maintains its  value to 1 for three to four days and then it changes itself to 0.

The servers are in live production environment.

Please help and advice.

Thanks and Regards,

Ahmed

Hi,

My domainserver (Windows Server 2008 R2) is currently running on RAID 1 with 2 disks.
Iam going to replace my old RAID card and disk with a RAID card that can run RAID 5 and 3 new disks.

After this Iam also installing Exchange 2013 on the server.

My question is:
Is the easiest/smartest way to get the same domain settings and server settings to backup the whole serevr/domain on a external disk and restore it after I made the change of RAID/Disks?
When that is done just install the Exchange.

Thanks!

Hi everyone,

I am hoping that someone can help me out here.  I have a 2 node 2012 R2 Hyper-V Failover Cluster, and I am trying to get our Veeam backups to work on this Cluster.  On node 1 the backups work fine with no issues, but on node 2 the Veeam jobs constantly fail with the following error:

10/09/2015 14:39:23 :: Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Veeam application-aware processing with failover). Details: Failed to check whether provider '{400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}' supports shadow copies on the volume '\\?\Volume{d8496e1b-cf0c-4cf4-8554-0afd39f67e5d}\'.The volume shadow copy provider is not registered in the system.--tr:Failed to add volumes to the snapshot set.--tr:Failed to perform pre-backup tasks. 

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

Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
   Provider type: Software
   Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
   Version: 1.0.0.1

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

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

But for some reason on the working node, it lists the above providers along with the additional provider that Veeam is expecting:

Provider name: 'Microsoft CSV Shadow Copy Provider'
   Provider type: Software
   Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
   Version: 1.0.0.1

I could really do with knowing why node 2 is missing this provider, and how I can get it installed so that I can get the backups to work.  The Cluster Nodes were both built at the same time using the same configuration, so why this is missing is a mystery to me!

Any help anyone can give me is greatly appreciated.

Many thanks.

Robert Milner | MCITP: Virtualization Administrator | Website: http://www.remilner.co.uk | Twitter: @robm82

Dear,

We have a software that a few people is using but only on their local machine as it is not possible to use at the same time by several people. Is it possible to on the server create a script that backups the data from this software from the client machine? Either that I manually do it from the server or it does it automatically.

Sincerely,

Nitman

Hello everyone,

first of all, I've looked at lots of forums and lots of threads on this forum to find an answer that could help me but no luck so here I go.

My client has a Dell T310 sever with SBS 2011 Essentials (No sharepoint, No Exchange) as domain controller and file server.

Since the installation of a program called Zensoft (which basically is an ERP which uses a MySQL database), the Windows Server Backup doesn't run anymore.

In Windows Server backup it sais "A volume Shadow Copy Service operation failed. Detailed error: The volume shadow copy operation failed with error 0x800423F4. View the vent log for more information".

So that's what I did. I went to the eventviewer which showed me one VSS warning and one Backup error.

VSS Warning

Backup error

There is no solution in the event details...

VSSADMIN LIST WRITERS

C:\Users\administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative comm
(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: {c3fdd3ff-b919-4cfa-8c4e-5436fcf62d4d}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {007ff9de-983b-48a9-883f-ade2127496d8}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {84a5452d-e3ca-4170-99f1-2423b2951868}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Windows Server Storage VSS Writer'
   Writer Id: {e376ebb9-f0fe-4e1a-adaa-bfbdaf3ab488}
   Writer Instance Id: {4299009e-a50e-4d54-a9fb-cced15c40a9e}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0374fd5a-a6f4-4876-bf5a-be16520f2fb1}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {e9436ec6-76cc-4f74-b99f-78c8d4d9a132}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {37e00d01-cc07-47ef-b5f2-c85efdafdd89}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {cbaf3141-9918-4aac-a83d-02f518739fd1}
   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: {9101c190-4512-45bb-81ed-72f641e121d4}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {b7186baf-d6a4-4468-9fd3-d0d6adceef16}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {26bbfec7-e41d-426b-94ed-30bf2fe049d2}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {70874aa8-9b4a-43ac-b0de-24fdef92974a}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {fbb72699-4dcb-4635-9154-eb0f9f76919b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {a84a00da-e4b8-423e-ba95-6d91987e32c3}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {ecf4a9ee-0d7b-44ad-a392-f19afbcda937}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {cda58328-23af-4258-b5d1-f9357373096b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {d093c4e7-e0d1-4a4a-b0d9-62558f3fff67}
   State: [11] Failed
   Last error: Non-retryable error

VSSADMIN LIST PROVIDERS

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

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

To solve the non-retryable error, I've read that I need to reboot the server but I can't really reboot it every 5 minutes to do tests. And for the record, I've done that allready and didn't work.

The CMD line for the backup (found in task scheduler) is the following:

%windir%\system32\wbadmin.exe start backup -templateId:{f05558a1-e7ac-47e1-929e-df427ea5630f} -quiet

The backup is configured to to a full server backup on a dedicated external Western Digital hard disk of 1TB at 10:30PM.

I've read on a forum of Symantec that re-registering the VSS writers solves the issue but in my case, it didn't.

This is pretty much as far as I've gotten and I've run out of ideas and places to look on the internet. Either I find a thread that has the exact same issue but no solution, or a thread that is similar but not quite and doesn't help me.

Thanks in advance,

Steve

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

________________________________________

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

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

Operation:

PrepareForSnapshot Event

Context:

Execution Context: Writer

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

Writer Name: System Writer

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

______________________________________________

Output for vssadmin list writers

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>vssadmin list writers

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

(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'VSS Metadata Store Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'Performance Counters Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'System Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'SqlServerWriter'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'ASR Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Database'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

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

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

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

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

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

   State: [1] Stable

   Last error: No error

______________________________________________

Output for diskshadow

C:\Windows\system32>diskshadow

Microsoft DiskShadow version 1.0

Copyright (C) 2013 Microsoft Corporation

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

DISKSHADOW> add volume c:

DISKSHADOW> create

COM call
"lvssObject4->GetRootAndLogicalPrefixPaths" failed.

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

nvironment variable.

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

t as environment variable.

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

2ec7b5b3c87d}

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

%VSS_SHADOW_1%

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

%VSS_SHADOW_SET%

               
- Original count of shadow copies = 1

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

f6e6963}\ [C:\]

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

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

hadowCopy1

               
- Originating machine: AOTRNCL01.waterone.org

               
- Service machine: AOTRNCL01.waterone.org

               
- Not exposed

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

               
- Attributes:  Auto_Release Differential

Number of shadow copies listed: 1

On one of my AD 2008 domain controllers the NTDS writer is in failed state.

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {a0b40cc8-ded5-4497-b6dd-50f56de2dbe2}
   State: [11] Failed
   Last error: Non-retryable error

This is Windows server 2008 STD 64 bit

I'm trying to find out if there is a way to fix this WITHOUT rebooting my DC.  I tried restarting the VSS service.

The cause of the failure was this.

lsass (636) An attempt to write to the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\NTDS\edb.log" at offset 6029824 (0x00000000005c0200) for 512 (0x00000200) bytes failed after 0 seconds with system error 19 (0x00000013): "The media is write protected. ".  The write operation will fail with error -1032 (0xfffffbf8).  If this error persists then the file may be damaged and may need to be restored from a previous backup.

lsass (636) Unable to write to logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9\Windows\NTDS\edb.log. Error -1032 (0xfffffbf8).

Any help is greatly appreciated!

Using the WSB utility, I get the following error "The process cannot access the file because it is being used by another process."

I ran the utility through powershell and got the same error.  I checked the log files and get this error "Error in deletion of [C:\System Volume Information\001.dat] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process."

Looked at resource monitor and system constantly has access to the file.

Any help would be appreciated.

Thanks

Hi, 

Since some time now i have not been able to use the Windows server backup tool anymore.

I cant really tell since when this started, but for all i know the windows server backup service worked fine.

I even created a backup schedule and it made some backups. 

I am running this windows server 2012 Standard at home with just a couple of basic applications.

The server is used to host several websites with IIS, it manages my local DHCP and is used for locally shared storage.

There are no other security applications installed yet, because i am trieing to get rid of this error first. (so no symantec or whatever)

Since some time i am having trouble opening the windows backup snap-in. 

When ever i trie to open the Windows server backup snap-in i get the following error:

A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation.

Error details: The Windows Server Backup service has stopped. 

Close Wbadmin.msc and then restart it.

Whenever this error occures the folowing error is show in the windows logbook:

I tried to find simmilar cases over the internet but i cant seem to find a solution for the problem. 

I already tried to remove and reinstall the Windows server backup feature, this did not help. 

Is there anyone here that can help me find a solution for this problem ?

Thank you !

Best Regards Maikel

Hi, I am getting the following error when I start the Windows backup MMC:

A fatal error occurred during a Windows Server backup snap-in (wbadmin.msc) operation.

Error Details:

The server threw an exception.

Any suggestions appreciated.  I've tried uninstalling/reinstalling with no luck. Thank, Rick

Volume backups succeed with 1.13 GiB of data.

However, backups fail on the same volume when I increase the data to 50.2 GiB.

The target volume is a thinly provisioned 1 TiB iSCSI drive that WBAdmin formatted and dedicated entirely for backups. It takes WBAdmin an unusually long time (tens of minutes) to quickly format the drive. Yet data transfers fairly quickly: the 1.13 GiB backup completes in 1 minute.

During backup, WBAdmin snap-in reports transfer complete and compacting begin: compact stays 0% for a minute or so, jumps to 6%, stays for another couple of minutes, fails. I think it's timing out.

I've tried backups with and without deduplication, small (1.13 GiB) or large (96.86 GiB): large backups fail regardless of deduplication, small backups succeed regardless of deduplication. Only size seems to matter.

Backup Source

• Physical data: 50.2 GiB (deduplicated)
• Logical data: 96.86 GiB
• Volume: 256 GiB
• File system: NTFS
• Allocation unit size: 16 KiB
• Storage device: locally attached hard drive

Backup Target

• Volume: 1 TiB
• File system: NTFS
• Allocation unit size: 4 KiB (WBAdmin defaults)
• Storage device: thinly provisioned iSCSI

Event Log

Log Name:      Microsoft-Windows-Backup

Source:        Microsoft-Windows-Backup
Date:          8/29/2015 10:21:35 PM
Event ID:      5
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      ctu-testvm
Description:
The backup operation that started at '‎2015‎-‎08‎-‎30T01:00:04.242823700Z' has failed with following error code '0x80780049' (None of the items included in backup were backed up.). 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="2015-08-30T02:21:35.117902000Z" />
    <EventRecordID>144</EventRecordID>
    <Correlation />
    <Execution ProcessID="1784" ThreadID="3648" />
    <Channel>Microsoft-Windows-Backup</Channel>
    <Computer>ctu-testvm</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BackupTemplateID">{F17F4B95-4214-4706-8D56-0F1BB0F9288F}</Data>
    <Data Name="HRESULT">0x80780049</Data>
    <Data Name="DetailedHRESULT">0x0</Data>
    <Data Name="ErrorMessage">%%2155348041</Data>
    <Data Name="BackupState">12</Data>
    <Data Name="BackupTime">2015-08-30T01:00:04.242823700Z</Data>
    <Data Name="BackupTarget">ctu-tes 2015_08_29 18:25 DISK_01</Data>
    <Data Name="NumOfVolumes">1</Data>
    <Data Name="VolumesInfo">&lt;VolumeInfo&gt;&lt;VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="17" HResult="-2139618991" DetailedHResult="-2147024865" PreviousState="9" IsCritical="0" IsIncremental="0" BlockLevel="1" HasFiles="0" HasSystemState="0" IsCompacted="1" IsPruned="0" IsRecreateVhd="0" FullBackupReason="2" DataTransferred="104003403776" NumUnreadableBytes="0" TotalSize="104003403776" TotalNoOfFiles="0" Flags="8200" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /&gt;&lt;/VolumeInfo&gt;</Data>
    <Data Name="SourceSnapStartTime">2015-08-30T01:00:04.242823700Z</Data>
    <Data Name="SourceSnapEndTime">2015-08-30T01:00:09.712054300Z</Data>
    <Data Name="PrepareBackupStartTime">&lt;TimesList&gt;&lt;Time Time="2015-08-30T01:00:10.820Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="PrepareBackupEndTime">&lt;TimesList&gt;&lt;Time Time="2015-08-30T01:00:10.961Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteStartTime">&lt;TimesList&gt;&lt;Time Time="2015-08-30T01:00:10.961Z" /&gt;&lt;/TimesList&gt;</Data>
    <Data Name="BackupWriteEndTime">&lt;TimesList&gt;&lt;Time Time="2015-08-30T02:20:34.289Z" /&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">17</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="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="BMR">&lt;BMR IsPresent="0" HResult="0" DetailedHResult="0" /&gt;</Data>
    <Data Name="VssFullBackup">true</Data>
    <Data Name="UserInputBMR">false</Data>
    <Data Name="UserInputSSB">false</Data>
    <Data Name="BackupSuccessLogPath">C:\Windows\Logs\WindowsServerBackup\Backup-30-08-2015_01-00-04.log</Data>
    <Data Name="BackupFailureLogPath">C:\Windows\Logs\WindowsServerBackup\Backup_Error-30-08-2015_01-00-04.log</Data>
    <Data Name="EnumerateBackupStartTime">&lt;TimesList&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;/TimesList&gt;</Data>
    <Data Name="PruneBackupStartTime">&lt;TimesList&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;/TimesList&gt;</Data>
    <Data Name="BackupFlags">0x8</Data>
    <Data Name="ComponentInfoSummary">&lt;ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /&gt;</Data>
  </EventData>
</Event>

C:\Windows\Logs\WindowsServerBackup\Backup-30-08-2015_01-00-04.log

Backup of volume D: succeeded.

C:\Windows\Logs\WindowsServerBackup\Backup_Error-30-08-2015_01-00-04.log: blank

Anyone know what's going wrong and what to do?

Hi all,

Does anyone know what is this error i encountered? i configure the DFS feature of the server and i have no error encountered during my installation but this problem occurred once the scheduled is running.

Hi,

We are using Windows Back-up for creating backups.
But every time we reboot the server, the schedule is gone.
The event logs show no errors and the backups are done according to the schedule.

We also have Back-up Exec 2010 R3 installed on the server (but we don't use it anymore)

Does someone have encountered this problem?

Kind regards,
Francois

Hi

We have an afternoon windows backup taking place on SBS 2011. The users have experienced some disruption with their Outlooks when the backup is running consistency checks on exchange. Is there a way to limit the disruption that is being caused, or can we alter the backup schedule in any way to minimise the disruption.

Ashwin

We are looking for command to do OS backup for Win2012 (not R2), so that the backup can be used for bare metal restore in disaster recovery.

We found the command wbadmin, and some articles talking about the command's behavior on Win2008:

http://magiksys.blogspot.hk/2012/09/wbadmin-dont-do-incremental-backup.html

https://social.technet.microsoft.com/Forums/windowsserver/en-US/1932ee25-faf0-4d50-87b0-9540664c77bb/incremental-full-backup-with-wbadminexe-

http://blogs.technet.com/b/filecab/archive/2009/05/04/deciding-between-system-state-backup-and-allcritical-backup-in-windows-server-2008.aspx

Just want to know,

Is wbadmin's behavior still the same on Win2012?

If yes, does that mean there is no way to control whether a volume backup is full or incremental? wbadmin determines by itself?

And is wbadmin still commonly used in Win2012? Or is there a new command with more features?

Hi,

Does anyone know how to resolve this issue? once i run the excel using admin id i have no problem. but when user is using it the stdole2.tlb message box will occur.

TIA

Hi all,

I have confusing case regarding VSS on my Win 2008 Standard Server, since it is being used for backup i get to solve this one.

The previous issue was that i always get event SPP time out regarding VSS, i read on some forum that i need to set registry key CreateTimeout and set to 20 mins, and i did it. 

The thing is that the solution wasnt work for me, it works only 1 time after i restarted the server. So if i test using windows server backup it did success, but the next one will be fail. If i restart the server again, the backup will success again, and the next will be fail and always like that. It doesnt make sense if i have to restart the server everyday to make things work.

Vssadmin list writers returns No Error. 

I refer to event viewer again and this time the log given is as follow:

"Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{29877b54-c58d-11e3-8d4d-bc305bdf62e4} - 000000000000013C,0x0053c008,000000000022C000,0,000000000022D010,4096,[0]).  hr = 0x80070079, The semaphore timeout period has expired."

Anyone has idea on this?

Thanks.