SBS 2008 Built-In Backup Fails

Our SBS 2008 built-in backup worked perfectly fine for the last five years until about a month ago. It was complaining that there is not enough disk space on the 1TB external backup hard drive.  So we upgraded to a known good working 2TB hard drive. Ever since we changed the hard drive the backup fails and we get the following errors:

The creation of the shadow copy on the backup destination failed because a time-out was reached.
Unknown error (0x80042313)

Backup started at '3/24/2015 12:18:08 AM' failed to backup volume(s) '' with following error code 2155348022 (Timed out before the shadow copy was created on the storage location.). Please rerun backup once issue is resolved.

Can it be the hard drive, although we know it works?

I searched the web with the given error codes, but had no luck finding a solution. Maybe I am searching for a wrong thing.
datzent83Asked:
Who is Participating?
 
noxchoGlobal Support CoordinatorCommented:
Does it work with old drive? I mean with 1TB drive.
Is the new drive 4K sector size drive?
0
 
datzent83Author Commented:
Below is what I get when I do vssadmin list writers

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: {8524a114-f10a-474c-bba7-0190d46342e1}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {70d6f96f-1051-413e-a67f-5f8448a8e58a}
   State: [1] Stable
   Last error: No error

Writer name: 'SPSearch VSS Writer'
   Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
   Writer Instance Id: {6a083456-2630-423f-8c7e-353688b71ba6}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {15e429da-6cd4-4f2f-8768-26b48c0fa6e4}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {e5873c42-395f-4878-95d0-473abdaf4110}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {57ccb66b-007e-4aaa-a16c-7f2f14ade7ea}
   State: [1] Stable
   Last error: No error

Writer name: 'SharePoint Services Writer'
   Writer Id: {c2f52614-5e53-4858-a589-38eeb25c6184}
   Writer Instance Id: {7034d0d5-6189-48ed-88c2-16df6fee9bc5}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {a3da5bed-5f4f-4380-9661-e4c539a6bc08}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {36636e57-d4a5-47e6-bcc0-0fd7fa43a526}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {dda6621f-855c-4ec2-865b-de202610e89c}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {703ba0e3-d8ea-480b-9664-1ea18960b4bc}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {bf4c7688-08b1-4238-8cc1-559ffa494437}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {9b89e086-615a-401e-9cd2-a831a78d3794}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {b4bf5376-e392-4ff8-a223-f4063d2f5855}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {edde4d7f-7665-44ae-a238-15a288476ec7}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {7ecd5d43-9b89-4ddb-8de7-c12983d297df}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {2e2761d2-7115-4f6d-a2d3-a3d27e89080b}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {91519a49-9278-4b76-bddf-d78a2beae902}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {1ea2db29-64d0-447e-8891-119d8224f03b}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {7f24afe5-e73d-48a3-9041-1c5b10636ca0}
   State: [1] Stable
   Last error: No error
0
 
Larry Struckmeyer MVPCommented:
AS noxcho requests,,, sector size and add the mfg and model of the drive.  Or compare it to this list:

http://social.technet.microsoft.com/wiki/contents/articles/1780.windows-small-business-server-external-backup-drives-compatibility-list.aspx

Be sure you run the wizard with that drive attached.

I have had excellent luck with WD Passport Ultra.  2.5", 2 TB, USB 2/3 and 3 year warranty.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
datzent83Author Commented:
I looked at the event viewer again and saw these errors prior the backup failing:

Event ID 9782
Exchange VSS Writer (instance 3fdd5810-2ee6-40bb-8ac7-cf1a22f5afb4:12) has unsuccessfully completed the backup of storage group 'First Storage Group'. No log files have been truncated for this storage group.

Event ID 9782
Exchange VSS Writer (instance 3fdd5810-2ee6-40bb-8ac7-cf1a22f5afb4:12) has unsuccessfully completed the backup of storage group 'Second Storage Group'. No log files have been truncated for this storage group.

Event ID 2005
Information Store (7764) Shadow copy instance 12 aborted.
0
 
noxchoGlobal Support CoordinatorCommented:
Well, VSS acts for Exchange as well, but you did not answer my questions.
0
 
datzent83Author Commented:
How can I check if the new hard drive is 4K sector?
0
 
Larry Struckmeyer MVPCommented:
One way would be to tell us the make and model or post a link to sales page.
0
 
datzent83Author Commented:
This is the hard drive I have: http://www.amazon.com/dp/B003187T98
0
 
datzent83Author Commented:
This seems to be very closely related: http://support.microsoft.com/en-us/kb/2616952
0
 
Larry Struckmeyer MVPCommented:
Turns out that drive has no information that I can find on the mfg web site.  I recommend the WD Passport Ultra 2 TB as a target.  

I have attached a picture of how you verify the sector size.  Right click the drive and select format.  Adjust the settings accordingly if they are not as shown.  If the drive has previous backups you will have to expose them by assigning a drive letter.
Format-Pic.JPG
0
 
datzent83Author Commented:
Wouldn't the wizard complain if the hard drive wasn't compatible? I will reformat it just in case.
0
 
noxchoGlobal Support CoordinatorCommented:
There is a way to check the sector size. Read this article: http://support.microsoft.com/en-us/kb/2510009
But does it work with old drive? Or if you select network storage?
0
 
datzent83Author Commented:
I fully formatted the hard drive with all the default settings. I had 1 successful backup. The second backup failed with an error:

The creation of the shadow copy on the backup destination failed because a time-out was reached.
Unknown error (0x80042313)
0
 
noxchoGlobal Support CoordinatorCommented:
Ok, one more time, does it work with old drive? Does it work when doing backup to network drive?
0
 
datzent83Author Commented:
It doesn't work with the old drive because it's 1TB. My full bankup is 1.2TB. Everytime it backs up to the old drive it complains that there is not enough disk space.
0
 
noxchoGlobal Support CoordinatorCommented:
Ah, ok. You do not have storage on network (NAS, SAN, file server) to try it with? This way you could definitely say that problem is in drive and not in Windows Server Backup.

Try as an alternative Paragon Hard Disk Manager 15 Server Basic: http://www.paragon-software.com/small-business/hdm-business/license.html
Does it complete the backups without problems?
0
 
datzent83Author Commented:
Installed a new WD Elements 2TB hard drive. The first backup was successful. I will see if the second backup is successful or not.
0
 
noxchoGlobal Support CoordinatorCommented:
Ok, report back when several backups run completed.
0
 
datzent83Author Commented:
I now have 3 successful backups using WD Elements 2TB hard drive. Thank you all for your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.