SBS 2011 backup failed

Dahoe
Dahoe used Ask the Experts™
on
HI there,
i just noticed on a SBS 2011 that the backups were failing with details "Volume shadow copy operation failed with error 0x80042306"

The eventlog shows volsnap Event ID 25
"The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."

This started 2 months ago & the last completed backup is 12 June.

The Server is set up for a daily full backup at 20.00, the office closes at 18.00

All help is much appreciated.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
That error indicates there are multiple VSS writers and they are conflicting with each other.  Apparently, Acronis is known to cause it as it saves the writers in the registry.
Read this:
https://www.backupassist.com/blog/support/how-to-resolve-a-ba910-volume-shadow-copy-error-0x80004230/

Author

Commented:
HI Davis & thanks for the info but i don't think it applies to this case as the only backup software ever used on this server is the built-in WIndows backup.
Is the backup to a dedicated disk ? If this is the case, how is the disk connected ? If the disk is USB connected, have any other USB devices been connected ? Have there been any errors on the disk ?
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
The backup is to an external USB hard drive & no other USB devices have been connected.
I havent't checked for errors on the backup drive but will run a scan on it now & then outside of office hours i'm going to scan the 2 internal drives.

Author

Commented:
The USB backup drive (WD Elements 2TB) passed SMART & the quick test with WD Lifeguard but the extended test will take 16 hours so going to stop it & run it overnight.
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
On the SBS server go to: C:\inetpub\Logs (IIRC).

Work your way through _all_ of the subfolders in the Logs folder and DELETE all but the most recent one(s) that are currently active. So, in Explorer set View to DETAILS, sort by date with newest on top, SHFT+END from the next oldest to the oldest, and finally SHFT+DEL to get rid of them.

Once that's done, space on the system drive should be freed up and VSS should be a lot happier.

Make sure any other partitions are not too full.

Commented:
What does

vssadmin show writers

show from cmd prompt run as admin?  Look for any not showing as stable and week probably just need the related service restarted.

Steve

Commented:
Also look at the space allocated for Shadow copies on each drive
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
I can't remember off the top if Windows Server Backup in Small Business Server 2011 (Server 2008 R2) supports Advanced Format (4Kn) drives? That may also be a problem.

Replace the drives. They are not expensive. Get them into WSB on SBS and run a backup.

Even better, use ShadowProtect for SBS, which is not expensive, and get a proper image based backup.

And one final note: Get a System State Backup STAT.
WD Elements 2TB?
That's the issue.
It's a 4k sector drive and the builtin requires a 512e sector disk.
Any WD Red drive < or = to 2tb size will work as they are 512e.
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
A good EE conversation on the subject here.

We bought a whole bunch of early WD Black 2TB WD2xx1FEX series drives because we knew they were 512n drives and they would be needed down the road (all of our clients were on SBS since the BackOffice days in some cases).

Author

Commented:
I decided to disable the Shadow Copies on both drives & run a manual backup & it worked. I then re-enabled the Shadow Copies & ran another scan & that worked also. I'll keep an eye on it this evening & make sure the schedueled scan works ok.

@Philip Elder - should i still do this? "Work your way through _all_ of the subfolders in the Logs folder and DELETE all but the most recent one(s) that are currently active. So, in Explorer set View to DETAILS, sort by date with newest on top, SHFT+END from the next oldest to the oldest, and finally SHFT+DEL to get rid of them."

@ pgm554 - some of the WD Elements are on the compatibility list & in system infornmation the Bytes/Sector is 512, would this mean it is one of them? It's been there for over 5 years & never had any problems with it before.


@ Steve Knight - think this all looks fine?

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(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: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b1f5fd2f-11d5-4196-b90a-51174cf37e5d}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {02156d27-1ebc-4168-b30a-49ea92cbb553}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {3cf5760c-7c3f-4f0d-9864-5e6627017b6b}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {1cd79954-8c42-4680-a11f-98d7bfea51ec}
   State: [1] Stable
   Last error: No error

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {66f89c34-43a8-483e-8b88-111b174c2ded}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {387b29f9-d205-48cd-bce7-7d760888c8ab}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {5a21951a-57c2-4545-a353-2fe871ab1702}
   State: [1] Stable
   Last error: No error

Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {e90b49a0-bf53-418a-8fbf-ff070fac299a}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {57d9520f-9b5b-4bd3-ae6d-15293d90fb69}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {fae0e2e8-c149-4da4-925f-a1acd7737c78}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {bb85d8ba-9cf4-4248-8acd-3fb4928687fb}
   State: [1] Stable
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {70959c34-165c-4a7e-ae04-8127c59b3cb1}
   State: [1] Stable
   Last error: No error

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {7d5d0e58-8851-46b2-934e-39aef9411929}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5dc8671c-bd6f-4520-a4c0-47c69f968998}
   State: [1] Stable
   Last error: No error

Writer name: 'Certificate Authority'
   Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86}
   Writer Instance Id: {6aade1ee-fadf-4eab-8cc5-f0f4d10468a9}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {3cdfcd5a-5582-4061-ba05-8fb82c3d613b}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {4f42f8db-9ffe-4dbd-a8b4-b50d6de467b4}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {981eb468-3e97-4cfd-98be-43115165b04d}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {b5b43f63-17b9-440b-a836-3a851ab2f673}
   State: [1] Stable
   Last error: No error
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
Yes. It's a part of a regular maintenance routine for SBS. Also, if still using WSUS check the size of the SUSDB and its accompanying log. They can be gargantuan.

The other thing to do is to delete the volume shadow copies stored which disabling and re-enabling may have done.
Commented:
"I decided to disable the Shadow Copies on both drives & run a manual backup & it worked. I then re-enabled the Shadow Copies & ran another scan & that worked also. I'll keep an eye on it this evening & make sure the schedueled scan works ok."

Well this seems to have done the trick, so far so good anyway.

Thanks for all the help guys as always it is much appreciated.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial