Hi Guys,

I'm having challenges with windows server 2012 essentials server with drive C:\ 250GB and E:\ 2TB backing up to 3TB USB (external) with error: 2155348326 on the dashboard

Event Viewer error ID: 517

The backup operation that started at '2014-07-07T13:37:46.850328500Z' has failed with the following error code: '0x80780166' () Windows backup encountered an error when writing data to the backup target.)

Best regards

yours affectionate Niyi Okunola

hi ........

when i take system state backup from command promt or windows backup utility then give me a error

systemstate backup failed .........check backup logs

Error in deletion of [\\?\Volume{15c46c92-2c8f-11e2-b15a-806e6f6e6963}\System Volume Information\EfaData\SYMEFA.DB] while pruning the target VHD: Error [0x80070020] The process cannot access the file because it is being used by another process.

shabrez khan

The Volume Shadow Copy service initially was running under the context of System, so we thought that ‘System’ doesn’t have permissions to access network shares. When the Volume Shadow Copy service was running under the context of System, this was the error logged:

“failed with following error code '0x8078014B' (There was a failure in creating a directory on the backup storage location.).”

Which is likely due to not having permissions to write to the network location.  This is a scheduled backup trying to write to a network location, so we changes the service to run under the context of an account that does have permissions to write to the network share.  Then the error changed to this:

“failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).”

HRESULT 0x8078006b
DetailedHRESULT 0x8004230f
ErrorMessage %%2155348075
BackupState 12
VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo>

We aren’t really seeing anything that gives any hint on what the issue is. Any ideas?  Thanks in advance!

I'm considering transitioning my server to RAID mirroring, in order to have one layer of continuous backup on an identical hard drive.  Are there any problems specific to RAID with Server 2012?

Do you have any alternative recommendations, which could provide piece of mind of continuous backup?

I considered this approach, because backup of one program will produce unusable data while the necessary service associated with it is running during the day.

Hello,

Our Shadow copies are getting deleted. I have no idea why. We use a limit of 381350MB and it runs every weekday at 6am. It is also stored on the same volume. I know it's not ideal, but we have no where else to put it.

Recent event log details.

Type:Error
Date:(17/06/2014 17:38:26)
Event ID: 35
Source: volsnap
Message: The shadow copies of volume F: were aborted because the shadow copy storage failed to grow.

Type:Error
Date:(17/06/2014 17:35:26)
Event ID: 13
Source: volsnap
Message: The shadow copy of volume F: could not grow its shadow copy storage on volume F:

The latest and only copy we have is on 18/06/2014 and is 2.9GB.
We have 1266.93 free storage left on the drive (F:)
Windows 2008r2

I tried vssadmin list writer - all stable and no errors.
vssadmin list providers -

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

Shouldn't it delete the oldest versions until it can save the new shadow copy?

Any help is appreciated. If you need more information, please let me know.

Cheers

Sam

Greetings,

I have Windows Server Backup running on Server 2012 STD R2 ( in a guest machine ) to a 1 TB USB drive. The backup runs successful no errors. However, it show only 1 Copies "Backups available: 1 copies".

-The backup size is: 611.62GB

-The backup type is: VSS Copy Backup

-The USB hard drive is dedicated for the Windows Backups

Any idea why this is happening?

wilson.molina@gmail.com

I have a fairly new 2012 R2 server with Essentials role installed. I just finished setting it up exactly as I like with clients connected and backing up to a storage space on the server. I bought a new eternal USB 3.0 HDD and just set up the server backup. I used the wizard in the Dashboard to create the backup job, excluding only the storage spaces drive. When I attempt to run the backup job, it always fails with error code 0x80780049 in the event log.  I have run chkdsk on C drive with no issues found.  During the backup wizard, I allowed it to format the new external drive.  If I watch the job run, it will get to 18%, and then jump to 100% and then say unsuccessful.  After looking at other posts on TechNet, I have tried to shrink the drive, recreate the job, and even uncheck all but drive C.  No change.  I also tried running the job via elevated command line, "wbadmin start backup".  When it reached 18%, it would repeat that output several times then fail.

Any ideas would be appreciated.

I have a good one here.  

On the same day, my server and a client it was backing up lost power unexpectedly and wont boot into Windows.  The server was no big deal to rebuild, but if I have to start over on the client I'm going to weep.  The rebuilt server has the old backups of the client intact on the Storage Spaces drive, but since the client wont currently boot it has not been attached to the new server so I dont know how to restore it from a backup.  

Is it possible to do a new install on the client, add it to the server, and then restore from an old backup?  

Any help or advice on this is appreciated!

Hi Tech Support team,

We are using Windows server 2008 std 32bit, in that server our ERP customized software is installed. we have created local user & group, all user are log on through RDP. Now we need to upgrading this server from Windows Server 2008 32bit to Windows Server 2008 64bit.  approximate 70 Locals users & groups has created.

my quotation is : can I backup & restore local users & groups from windows server 2008 std 32bit to Windows Server 2008 std 64 bit.

Thanks in advance.

Hello

I was trying to take a full back for my lync ME server , using windows backup , for a machine that is hosted on hyper v

but it keeps fails with the error :

Hi folks,

We are running into issues when attempting to configure a Windows Backup schedule through either running the Backup Schedule wizard or through using the wbadmin utility. While I have previously posted this issue on a separate forum (with no luck) I’ve restructured this description based on the responses received and am also hoping that this a more suitable forum for the problem we are experiencing.

On running the backup wizard the backup configuration screen shows the backup size to be 0KB for the Full Server option or if I choose ‘Custom’ and go to ‘select backup items’ the volume list is empty. However the later ‘select destination disk’ screen of the wizard lists all of the disks attached to the server along with the associated volume letters (via clicking the ‘Show All Available Disks’ option).

On the backup wizard reaching the summary stage it then proceeds to format the destination disk. On completion of this format the wizard status then changes to ‘Creating backup schedule’ at which point it then fails with the message “The specified number of volumes is invalid”.

Equally running the following wbadmin command:

wbadmin ENABLE BACKUP -addtarget:{81737a1c-0000-0000-0000-000000000000} -schedule:21:00 -include:c:

Results in the following error:

“ERROR - One of the source volumes specified cannot be included: c: Please specify source as a volume drive letter or access path (if volume is mounted in a folder). Only volumes on locally attached disks can be backed up.”

The server is a Dell PowerEdge R620 running Windows server 2008SP2 and is operating as expected other than for this windows back issue. Everything appears as normal when I view the disks within the Disk Management Console. Backups used to run on this server fine before it was migrated from old hardware to new hardware using Doubletake Move. Everything else is running fine since the migration apart from Windows backup so not why it would only be effecting Windows backup. I have also ran the wbadmin ‘delete catalog’ command to remove reference to the previous backups that were taken.

Is there any other tests that I can run to determine why Windows backup is having trouble seeing the available volumes at the 'Select Backup items' stage but not at the Select Destination' stage? Any help or pointers in the right direction would be very much appreciated.

Thanks,

Niall

Hi all,

I want easy steps to do harden windows server 2008 r2, i read http://technet.microsoft.com/en-us/library/gg236605.aspx. i understood that want to use SCM,MBSA,SCW tool complete the hardening process ? and I want to know how to take security group report from that? and also easy steps to do hardening, because am newbie ?

Hi Experts,

We are taking "system state backup" on our servers through scheduled task. We are making use of wbadmin.exe cmdlet for this. The back up target is the data drive on the local host.

This back up folder "windows system backup" is not inheriting permission from the root by default even though every setting regarding file permission and inheritance is correctly set at the root. Every time we have to force the ACL.

Is this the default feature of backup?

The back up folder by default consists only system,administrators and back up operators in its ACL but not other groups and users mentioned in the root.

We could confirm that every settings regarding file and permission and inheritance is correctly set and also tested by creating other folders manually.

Please advice???

Hi,

The system state is constantly failing on our Windows server 2012.
We get the error "Backup failed to complete. The system writer is not found in the backup." when trying to take the backup locally on our server.
The server contains 3 drives, Does not matter what drive I chose, The C: (Windows drive) has 96GB free out of 130 GB.

Information regarding the server:
OS: Windows Server 2012 Standard 64-bits (6.2 Build 9200)
Microsoft SharePoint Server 2013
Microsoft SQL Server 2012
Antivirus: System Center Endpoint Protection
It is a virtual machine with 16384 MB RAM and a page file with 18686 MB

We are using DPM 2012 Service pack 1.
It lists the following error when trying to take the backup/check inconsistency:

"Affected area: Computer\System Protection

Occurred since: 2014-07-11 08:14:29

Description: The replica of System Protection Computer\System Protection on SERVERNAME is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
 DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x1D34BA0). (ID 30229 Details: Internal error code: 0x80990ED0)
 More information
Recommended action: For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
 Synchronize with consistency check.
 Run a synchronization job with consistency check..."

EventIDs listed on the server:
Source: CAPI2, EventID 513
With the error message

Troubleshooting performed:

Performed backup locally using Windows Server Backup (It fails after a few seconds saying "Backup failed to complete. The system writer is not found in the backup." )
When using the vssadmin list writers, It lists the following:

Microsoft Windows [Version 6.2.9200]                                            (c) 2012 Microsoft Corporation. All rights reserved.   
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: {5f0a641e-7fb4-422b-bbc5-d60ecf688d75}                     
State: [1] Stable                                                              
Last error: No error
                                                                                                                                        
Writer name: 'ASR Writer'                                                         
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}                             
Writer Instance Id: {1bb12ddb-a7fd-424e-87fa-48e3f245a6c7}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                     
Writer name: 'Shadow Copy Optimization Writer'                                    
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}                              
Writer Instance Id: {c5bce6a4-2bbc-4df7-9938-580b2dbba292}                     
State: [1] Stable                                                              
Last error: No error  
                                                                                                                                     
Writer name: 'Registry Writer'                                                    
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}                              
Writer Instance Id: {bbcf0fd9-e505-4fa1-b83c-1734d4c249ac}                     
State: [1] Stable                                                              
Last error: No error    
                                                                                                                                   
Writer name: 'WMI Writer'                                                         
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}                              
Writer Instance Id: {a96beab3-2709-48c6-b48a-e730159c3a1a}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'IIS Metabase Writer'                                                
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}                              
Writer Instance Id: {cd1daf6a-79e8-411c-a1a7-1459fe2eb952}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'COM+ REGDB Writer'                                                  
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}                              
Writer Instance Id: {4527bf6a-c5b9-42dd-8320-21705ccd8dff}                     
State: [1] Stable                                                              
Last error: No error 
                                                                                                                                      
Writer name: 'BITS Writer'                                                        
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}                              
Writer Instance Id: {761ff855-d6cc-4e0d-a831-efa50e798192}                     
State: [1] Stable                                                              
Last error: No error
                                                                                                                                       
Writer name: 'IIS Config Writer'                                                  
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}                              
Writer Instance Id: {279dc9c7-5727-4ee1-bdfd-52f058b3e9b5}                     
State: [1] Stable                                                              
Last error: No error  "

- Tried the KB2009272 (http://support.microsoft.com/kb/2009272/sv)
- Shadow copies are NOT enabled on the server.
- There is enough space on the server itself and where we store the backup.
- Removed the server from the protection Group and all backed up system states of it that was stored (It has not successfully ran in a long while but somehow there was data being taken up) then added it again. It is OK until i run a inconsistency check.
- Backup of C:, D:, L: and SQL databases works fine.
- We have this occuring on several Windows server 2012 that has the same configuration as this one (SharePoint and SQL) so we have found the following article that describes that the SharePoint 2013 breaks the VSS writer and therefor the backup cannot be run.Article: http://blogs.technet.com/b/dpm/archive/2011/10/31/troubleshooting-data-protection-manager-system-state-and-bare-metal-backup.aspx

Best regards,
Sebastian