Jump to content
RESET Forums (homeservershow.com)

WHS 2011 client backups fail to start


dslabby
 Share

Recommended Posts

Hello and apologies in advance for the length of this post.
 

My WHS2011 has not been doing the normal client back-ups for the past 2 weeks.  It has been working fine for nearly 2 years
up to now.  All the client attempts immediately fail with the errors below in the event viewer on the WHS.  All the WHS services are started on both the server and the clients and set to automatic. The volume shadow copy service is also started and automatic on both.  All the clients can see and interact with the server through both the connector and RDP, all start a backup
which never goes past 1 - 4% and then fails with the attached errors being thrown.  It seems to fail somewhat quicker than the error messages appear as the sometimes take 15 - 20 minutes to pop up in the connector.  The server is using Stablebit Drivepool v 1.3 with a pool of 4 internal and 4 external (usb2.0 & 3.0) disks totaling 12TB. The network consists of 2 desktops, mine (wired through router to the server w/ cat 6) one in the kitchen (wireless, 5ghz) 2 laptops (one 5ghz and one 2.4ghz both N) all have been backing up fine until recently.  Changes to the network have been the addition of a new 3TB usb 3.0 drive to the server (partioned as GPT and formatted through the disk management console on the server, it's part of the storage pool)  The router firmware was updated from stock Linksys firmware to Tomato USB (have run this in the past with no issue) Toastman version latest edition. Had to tweak it with a fix for IPv6 but now all clients and devices show both IPv4 & IPv6 addresses, had to do this previously as well.  Changing back to the stock Linksys firmware did not change the back-up issue, so I went back to Tomato.  Router is a Linksys e4200v1.  I have a netgear repeater running on both N bands (2.4 & 5ghz) and a media bridge in our living room that are all working fine and can see all other devices in the network.  AV is Norton IS 2013.  Media server from the WHS 2011 box is working fine and feeds my TV/entertainment equipment flawlessly.  i don't think network connectivity is the problem.  Stablebit Scanner shows the message below for 2 -1.5 TB drives in the pool, 
as far as I can read the message, it refers to unreadable sectors (1) being over some internal S.M.A.R.T. limit but not "yet" in danger of drive failure.  I reinstalled WHS 2011 on the system drive fresh and re-added the pool drives to get all my data back.  Ran Stablebit’s WSStroubleshooter to reset all drive permissions to “Everyone” I can see and manipulate any drive on the network; I just can’t get WHS to back any of my clients up to the server. I have kind of run out of troubleshooting ideas, if anyone here has any ideas I'll gladly take them as this is starting to worry me. The majority of the files on the server are movies and music I would rather no lose or re-organize.  Sorry this got so long, but I wanted to put out all the info I had up front rather
than have to post back with additional info. Can anyone help me hunt this done? 


TIA


Dave

 



Log Name:      WSSG

Source:        Windows Server

Date:          4/1/2013 3:55:43 PM

Event ID:      258

Task Category: Backup

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

Backup job 2 for DAD started.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="WindowsServer" />

    <EventID
Qualifiers="20479">258</EventID>

    <Level>4</Level>

    <Task>1</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated
SystemTime="2013-04-01T19:55:43.000000000Z" /> 
<EventRecordID>23</EventRecordID>

    <Channel>WSSG</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>DAD</Data>

    <Data>2</Data>

  </EventData>

</Event>


 

 

Log Name:      WSSG

Source:        Windows Server

Date:          4/1/2013 3:56:14 PM

Event ID:      271

Task Category: Backup

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

The Windows Server Client Computer Backup Service
encountered the following error: Error code: 0x1 API name: WriteFile File:
K:\ServerFolders\Client Computer
Backups\S-1-5-21-3710693545-3704739162-2845261045-1016.E.VolumeCluster.4096.new
Error: Incorrect function.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="WindowsServer" />

    <EventID
Qualifiers="53247">271</EventID>

    <Level>2</Level>

    <Task>1</Task> 
<Keywords>0x80000000000000</Keywords>

    <TimeCreatedSystemTime="2013-04-01T19:56:14.000000000Z" />  
<EventRecordID>24</EventRecordID>

    <Channel>WSSG</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>0x1</Data>

    <Data>WriteFile</Data>

    <Data>K:\ServerFolders\Client
Computer
Backups\S-1-5-21-3710693545-3704739162-2845261045-1016.E.VolumeCluster.4096.new</Data>

    <Data>Incorrect function.</Data>

  </EventData>

</Event>



 

Log Name:      WSSG

Source:        Windows Server

Date:          4/1/2013 3:56:14 PM

Event ID:      267

Task Category: Backup

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

The Windows Server Client Computer Backup Service failed
at (567) of (d:\wssg_src\colorado_qfe\backup\pc\util\diskfile.cpp).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="WindowsServer" />

    <EventID
Qualifiers="53247">267</EventID>

    <Level>2</Level>

    <Task>1</Task>  
<Keywords>0x80000000000000</Keywords>

    <TimeCreatedSystemTime="2013-04-01T19:56:14.000000000Z" />  
<EventRecordID>25</EventRecordID>

    <Channel>WSSG</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>  
<Data>d:\wssg_src\colorado_qfe\backup\pc\util\diskfile.cpp</Data>

    <Data>567</Data>

  </EventData>

</Event>


 

 

Log Name:      System

Source:        Service Control Manager

Date:          4/1/2013 3:56:20 PM

Event ID:      7034

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

The Windows Server Client Computer Backup Service service
terminated unexpectedly.  It has done
this 3 time(s).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control
Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}"
EventSourceName="Service Control Manager" />

    <EventID
Qualifiers="49152">7034</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>  
<Keywords>0x8080000000000000</Keywords>

    <TimeCreated
SystemTime="2013-04-01T19:56:20.967737500Z" />

    <EventRecordID>3605</EventRecordID>

    <Correlation />

    <Execution ProcessID="804"
ThreadID="6528" />

    <Channel>System</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Windows
Server Client Computer Backup Service</Data>

    <DataName="param2">3</Data>

  </EventData>

</Event>


 

Log Name:      Application

Source:        Application Error

Date:          4/1/2013 3:56:17 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

Faulting application name: WSSBackup.exe, version:
6.1.8800.16400, time stamp: 0x50949597

Faulting module name: WSSBackup.exe, version:
6.1.8800.16400, time stamp: 0x50949597

Exception code:
0xc0000025

Fault offset:
0x000000000004f888

Faulting process id:
0x8e0

Faulting application
start time: 0x01ce2f08efbd2826

Faulting application
path: C:\Program Files\Windows Server\Bin\WSSBackup.exe

Faulting module path:
C:\Program Files\Windows Server\Bin\WSSBackup.exe

Report Id:
367f012f-9b06-11e2-b580-001b218b5ef3

Event Xml:

<Event
xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ApplicationError" />

    <EventID
Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>  
<Keywords>0x80000000000000</Keywords>

    <TimeCreated
SystemTime="2013-04-01T19:56:17.000000000Z" />  
<EventRecordID>1704</EventRecordID>

    <Channel>Application</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>

    <Data>WSSBackup.exe</Data>

    <Data>6.1.8800.16400</Data>

    <Data>50949597</Data>

    <Data>WSSBackup.exe</Data>

    <Data>6.1.8800.16400</Data>

    <Data>50949597</Data>

    <Data>c0000025</Data>

    <Data>000000000004f888</Data>

    <Data>8e0</Data>

    <Data>01ce2f08efbd2826</Data>

    <Data>C:\Program Files\Windows
Server\Bin\WSSBackup.exe</Data>

    <Data>C:\Program Files\Windows
Server\Bin\WSSBackup.exe</Data>

    <Data>367f012f-9b06-11e2-b580-001b218b5ef3</Data>

  </EventData>

</Event>


 

Log Name:      Application

Source:        VSS

Date:          3/31/2013 8:00:11 PM

Event ID:      12289

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Log Name:      Application

Source:        VSS

Date:          3/31/2013 8:00:11 PM

Event ID:      12289

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      SERVER

Description:

Volume Shadow Copy Service error: Unexpected error
DeviceIoControl(\\?\Volume{ba21fdb8-9a5a-11e2-8fbd-806e6f6e6963} -
00000000000000FC,0x00530024,0000000000000000,0,000000000044C720,4096,[0]).  hr = 0x80070001, Incorrect function.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="VSS" />

    <EventID Qualifiers="0">12289</EventID>

    <Level>2</Level>

    <Task>0</Task>  
<Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-01T00:00:11.000000000Z"/>  
<EventRecordID>1332</EventRecordID>

    <Channel>Application</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>  
<Data>DeviceIoControl(\\?\Volume{ba21fdb8-9a5a-11e2-8fbd-806e6f6e6963}-
00000000000000FC,0x00530024,0000000000000000,0,000000000044C720,4096,[0])</Data>

    <Data>0x80070001, Incorrect function.

</Data>

    <Data>

    </Data>  
<Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505       2444946464330303030303338322D205049443A202030303030333230302D205449443A2020303

03030353131322D20434D443A2020433A5C57696E646F77735C53797374656D33325C73766368

6F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F5

24954595C53595354454D2C205349443A532D312D352D313820</Binary>

  </EventData>

</Event>.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="VSS" />

    <EventID Qualifiers="0">12289</EventID>

    <Level>2</Level>

    <Task>0</Task>  
<Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-01T00:00:11.000000000Z"/>  
<EventRecordID>1332</EventRecordID>

    <Channel>Application</Channel>

    <Computer>SERVER</Computer>

    <Security />

  </System>

  <EventData>  
<Data>DeviceIoControl(\\?\Volume{ba21fdb8-9a5a-11e2-8fbd-806e6f6e6963}-
00000000000000FC,0x00530024,0000000000000000,0,000000000044C720,4096,[0])</Data>

    <Data>0x80070001, Incorrect function.

</Data>

    <Data>

    </Data>  
<Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505

2444946464330303030303338322D205049443A202030303030333230302D205449443A2020303

03030353131322D20434D443A2020433A5C57696E646F77735C53797374656D33325C7376636

86F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F

524954595C53595354454D2C205349443A532D312D352D313820</Binary>

  </EventData>

</Event>



 

Link to comment
Share on other sites

Tow obvious things to check....is the drive full or is it experiencing some sort of problem indicating it could be failing?  IF it were one client I'd say it was a client issue but with all of them failing at the same time, I'd be looking to exchange that drive.

Link to comment
Share on other sites

I would start by making sure I had a copy of all my WHS2011 data somewhere else before I did anything else.  I assume you have a bunch since you have 12TB of storage?  Do you have it backed up offsite or locally?

 

Then I would take my WHS back to base.  New install with no addins and no stablebit and no USB drives.  I might even pull those drives and check them with another PC to make sure they are good.  Then start adding things back in.  It's a ton of work, but it's a start.  I have never seen this issue before.  Did you check with the Stable bit guys?

Link to comment
Share on other sites

  1. as the others indicated, ensure you have additional copies of your data.

  2. see if you can remove the drives that Stablebit Scanner is complaining about, then test the drives.
Link to comment
Share on other sites

Thought I might have found an answer to this as I found an exclamation point in device manager for the new WD #TB My Book I added to the pool recently.  It was asking for a WD SES USB Device Driver, found it on the WD web site and installed, no cure as the backups still fail with dash board claiming the backup was canceled by the client.  At least I got rid of the exclamation point.  Could transfer all the folders off to other computers to save though it would take days even over gigabit, but I'd rather not if possible.  Still have the old client backups in a renamed folder just in case they would be useful. 

 

Client side error logs give two errors on failure:  (may help narrow this down)

 

Log Name:      WSSG
Source:        Windows Server
Date:          4/2/2013 9:32:23 PM
Event ID:      514
Task Category: Backup
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dad
Description:
Backup job 5 on SERVER did not succeed.  Reason: ServerFailure, System.String[]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Server" />
    <EventID Qualifiers="53247">514</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-04-03T01:32:23.000000000Z" />
    <EventRecordID>409</EventRecordID>
    <Channel>WSSG</Channel>
    <Computer>Dad</Computer>
    <Security />
  </System>
  <EventData>
    <Data>5</Data>
    <Data>SERVER</Data>
    <Data>ServerFailure, System.String[]</Data>
  </EventData>
</Event>

 

And:

 

Log Name:      WSSG
Source:        Windows Server
Date:          4/2/2013 9:32:23 PM
Event ID:      517
Task Category: Backup
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Dad
Description:
Backup of volume E: to SERVER did not succeed. Reason: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ProtocolException: ConnectionLost, Details: Reconnect attempt rejected by server
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.BackupProtocol.SendClusterHash(Int64 clusterIndex, Byte[] hash)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.DoClusterPass1()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.RunWithoutCatch()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.Run()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Server" />
    <EventID Qualifiers="53247">517</EventID>
    <Level>2</Level>
    <Task>2</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-04-03T01:32:23.000000000Z" />
    <EventRecordID>408</EventRecordID>
    <Channel>WSSG</Channel>
    <Computer>Dad</Computer>
    <Security />
  </System>
  <EventData>
    <Data>5</Data>
    <Data>E:</Data>
    <Data>SERVER</Data>
    <Data>Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ProtocolException: ConnectionLost, Details: Reconnect attempt rejected by server
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.TryReconnect(Int32 localGeneration)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.WriteWithReconnect(Int32 count)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.ReconnectableStream.Write(Byte[] buffer, Int32 offset, Int32 count)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Protocol.BackupProtocol.SendClusterHash(Int64 clusterIndex, Byte[] hash)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.DoClusterPass1()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.RunWithoutCatch()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupOperation.Run()</Data>
  </EventData>
</Event>

 

 

Don't know what they are telling me I am new at reading them.  The dashboard (through Home Server Status) claims the client is canceling the backup, does any of this explain why?  The guys at stablebit drivepool punted it back to microsoft say it did not seem to be a problem with the pool but with WHS 2011.  Kind of thought they would.  Could a flaky ethernet card be causing this, I had that happen on my old WHS v1 and the card swap cured the backup failures, been so long I can't remember the errors were then though.  Thanks for the help, I going to bed, morning comes too early in the morning.

 

Dave

Edited by dslabby
Link to comment
Share on other sites

Dumped everything but my client backups to my new 3TB usb drive and then took out the two drives giving "failing but not imminent failure" drives. Rebuilt the server from square one with 2 usb drives coming into the server case to replace the 2 WD 1.5TB Green drives that were failing.  Patitioned and formatted each drive one at a time as I added them, with the remaining 2.5 TB drives (USB) being added last.  Drivepool  installed, and pool created.  Set up the server pool and backup again and I am in the process of copying back all the media files.  My computer began a full automatic backup at midnight and is currently about 35% done, no reason to think it will stop.  Wish it hadn't taken this drastic a move to get it going again but glad it seems to work again. Server folder move to the pool went without a hitch and everything back on the server is being seen by the devices that need to.  Probably never figure out what made it go south, but it likely had to do with the failing drives.  Hope adding Stablebit Scanner didn't muck anything up, but I'm waiting until I done before I try adding it back in.  Now I have to work on replacing the drives I took out, I'm back to a mere 9.5TB, barely enough room to store all my stuff.  :P

 

Guess a good clean install, from time to time, is necessary to eliminate the chaff in any Windows install.  An educating way to spend the weekend.  Thanks for the help.

 

Dave

Link to comment
Share on other sites

Well, it all worked for a while.  The first backup for all computers on the network went without a hitch.  Then on Tuesday night, a wad of updates came down for the server and it restatred twice.  Since then, no backups.  All computers failing with the same errors as before. 567, 271 ect.  Clients display that the backups are being cancled by the client and the errors refer to the drive D: and E:.  Two of the computers being backed up don't have a drive D: or E:?  on the third they are DVD drives, the 4th computer has not yet been backed up.  I haven't gone through all th error logs yet, but this looks identical to the previous errors and backup failures.  Lights Out was installed at about this time as well, I will take it out and retry the backups, other than the ~20 updates it installed on 4/8 there have really been no changes from when it was working and did the original backups.  I'll try peeling those off one at a time and see if it helps at all, wouldn't be the first update to fix one thing and break another.  This is getting so old.  Oh I also added my 3tb usb 3.0 drive to the pool (Stablebit drivepool) after partitioning it and formating, all drives in the server show healthy by SMART and by Stablebit Scanner.  The 3tb is partioned as GPT, it would only use 2 tb if partioned as MBR, the remaining 754+ gb was not accessable.  Seems to be working fine as a storage drive.  I'm about ready to look at Linux for my home Server needs, I have a key for Server 2012 Standard/Datacenter and a copy of 2012 Esstentials as well as Standard/Datacenter.  Could try that route if it would be better and stable,  Heard there are ways to install Esstentials trial and once all set up and patched to upgrade to standard.  Did I mention this is all getting old?

 

Help?

Link to comment
Share on other sites

The one thing that strikes me is that you're changing too many things, too quickly.

 

When you're having issues with a system and get it working again, you really need to leave it alone for a while, like say a week, to be sure it really is OK. Don't even let updates get installed.

 

After it's been running OK for a while, then let the updates install. If there aren't too many updates, I would even do them one at a time. After each update, test the backup again. If there are a lot of updates I do 5 or 6 at a time and test.

 

If all the updates work OK, then start doing things like adding a USB drive. Again, do them one at a time and test afterward.

 

The whole point of the process is to identify the thing that's causing issues; it's not a process to be followed all the time - it would just be too time consuming.

 

Thankfully, most of the time, doing updates and adding software and hardware doesn't cause issues like you're having. When it does happen, though, it requires methodical troubleshooting to identify the cause.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...