Solved

SBS 2008 backup Faliure

Posted on 2013-01-09
12
577 Views
Last Modified: 2013-03-12
Have a cleint using sbs 2008 backup & rectly the backup constanbly fails.

I have tried recreating teh job with a new external drive but teh backup alwatys fails.

Event log shows:

Log Name:      Microsoft-Windows-Backup
Source:        Microsoft-Windows-Backup
Date:          09/01/2013 14:38:35
Event ID:      9
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      GLINWELLSBS.glinwellmkt.local
Description:
Backup started at '{92d90531-36b9-47f6-8f67-8c5ffa651a5c}' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'.
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>9</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2013-01-09T14:38:35.004Z" />
    <EventRecordID>11080</EventRecordID>
    <Correlation />
    <Execution ProcessID="748" ThreadID="9028" />
    <Channel>Microsoft-Windows-Backup</Channel>
    <Computer>GLINWELLSBS.glinwellmkt.local</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="BackupSetId">{92D90531-36B9-47F6-8F67-8C5FFA651A5C}</Data>
    <Data Name="SppErrorCode">2155348129</Data>
  </EventData>
</Event>

Any ideas?
0
Comment
Question by:Daniel Bertolone
  • 6
  • 3
  • 3
12 Comments
 
LVL 10

Expert Comment

by:bigbigpig
ID: 38759067
From an elevated command prompt run:

vssadmin list writers

Open in new window


Do any show an error?
0
 

Author Comment

by:Daniel Bertolone
ID: 38759087
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

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

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {2e6b4463-58df-49d3-8bef-6a280703a045}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {d90c50f1-14f4-44f0-8973-4f8f02b2465d}
   State: [8] Failed
   Last error: Non-retryable error

Writer name: 'SharePoint Services Writer'
   Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
   Writer Instance Id: {e880d42a-48de-4d5e-b3f3-7917251fdd16}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {f937fa47-25f7-4c7a-b980-66eaa3d60687}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {d8d545f5-c2ee-46c9-80da-4659bc44f93f}
   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: {43a847d7-864b-4534-bd3c-e1fe157bfe30}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {f373ed10-cc0e-4bd7-9be9-ae513190abee}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {5af73c49-d021-46bd-aeb2-66af08532bc8}
   State: [5] Waiting for completion
   Last error: Retryable error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {c0df7d20-1a75-4507-ad44-4b175d18a050}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ab2a6fa7-a7e5-4022-bbab-969dc4fbf250}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {d76f2d9d-c836-4d46-ba16-fbefda55250a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {e6be9915-7218-4cce-a924-9751cf836cb9}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {fe714fc2-6df7-4029-ac81-29d0f315e7ca}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {90e07218-0eca-4d5e-a130-6bf2a5019700}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {aa09906a-cad4-4eed-bbb2-5937ee3fc56e}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {15416df3-78d7-459b-b2b5-45aa07e18bf8}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {b893ecd3-de8f-407b-80c9-44ce365907c5}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {bae67020-dc2a-4e7f-aef5-214a2a81bd5c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'SPSearch VSS Writer'
   Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
   Writer Instance Id: {de48d6b6-e1b8-431e-ad16-ff9cb18f417a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {e643d46a-4ab9-4b20-8452-9719a200c24b}
   State: [5] Waiting for completion
   Last error: No error


Few errors
0
 
LVL 10

Expert Comment

by:bigbigpig
ID: 38759150
Check the event logs (app and system) for source SQLWriter and see if you can find which database it's failing on, and the reason.

Did you recently do a Sharepoint update?
0
 
LVL 30

Expert Comment

by:pgm554
ID: 38760079
Has it ever worked?

Sounds like you have a non NTFS( OEM) partition ( FAT16).

Windows backup will not backup anything not NTFS.

What's the size of the USB drive?
0
 

Author Comment

by:Daniel Bertolone
ID: 38760408
It used to work fine, i would always get the alert stating that it could not backup the "oem" partition due to file format but it always allows me to continue with my selection and then attempt to start a backup.

The issue arose because the end user originally deleted the admin account that was used to setup the backup and has been failing ever since.

I recreated a new admin account along with a new backup job but it fails, could the new admin account be lacking anywhere in permissions?

How could you tell about the non NTFS partition?
0
 
LVL 10

Expert Comment

by:bigbigpig
ID: 38760740
I bet it's failing authentication to one or more SQL databases.  Check your SQL security and make sure the new account that's running the job has sysadmin role.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 

Author Comment

by:Daniel Bertolone
ID: 38760993
I thought it could be something along them lines as i am able to log in with widows authentication on all sql databases apart from SharePoint.

Now i don't know the sa login for SharePoint so how can i check that my new admin account has the sysadmin role?
0
 
LVL 30

Expert Comment

by:pgm554
ID: 38761206
You need to understand that the windows backup is based upon a .vhd format.
It cannot be larger than 2.2 tb and cannot back up a fat partition in case you need to do a dr recovery.

I ran into this my first time using the 2008 sbs backup.

You need to convert that partition to ntfs using the diskpart command or you will always get that error.

Also bear in mind that the newer usb disks(>2tb) use a different cluster size (4k)and will not work with the built in backup.

I would look at getting a good 3rd party like Acronis,Storagecraft or Symantec.

You could try rerunning the SBS backup wizard,but you'll still have to contend with that non ntfs error.
0
 

Author Comment

by:Daniel Bertolone
ID: 38762042
The backup alwAys worked previously with the same external hard drive & the same partitions on the system. The fat 32 partition was never included in the backup and never was an issue previously.

The issue has only surfaced since the user deleted the admin account that was running the backups.

I tried a job via backup exec and this is what I get :



V-79-57344-65233 - AOFO: Initialization failure on: "\\GLINWELLSBS\Microsoft Information Store\First Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).

The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Symantec Software VSS Provider (Version 1.0).

V-79-57344-65233 - AOFO: Initialization failure on: "\\GLINWELLSBS\Microsoft Information Store\Second Storage Group". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.

Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Waiting for backup complete notification (5).

The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Symantec Software VSS Provider (Version 1.0).
Network control connection is established between [::1]:30234 <--> [::1]:10000
Network data connection is established between    [::1]:55655 <--> [::1]:55654
0
 
LVL 30

Expert Comment

by:pgm554
ID: 38763297
Did you have Symantec backup installed?

The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Symantec Software VSS Provider (Version 1.0).

http://www.symantec.com/connect/forums/how-remove-provider-name-symantec-software-vss-provider
0
 

Accepted Solution

by:
Daniel Bertolone earned 0 total points
ID: 38965211
The issue seems to have resolved itself, i spoke with Symantec support who tried various tasks but the backup eventually worked without intervention.
0
 

Author Closing Comment

by:Daniel Bertolone
ID: 38976839
Issue resolved itself
0

Featured Post

Zoho SalesIQ

Hassle-free live chat software re-imagined for business growth. 2 users, always free.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You may have discovered the 'Compatibility View Settings' workaround for making your SBS 2008 Remote Web Workplace 'connect to a computer' section stops 'working around' after a Windows 10 client upgrade.  That can be fixed so it 'works around' agai…
Create your own, high-performance VM backup appliance by installing NAKIVO Backup & Replication directly onto a Synology NAS!
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now