Quantcast
Channel: Spiceworks Community
Viewing all articles
Browse latest Browse all 5334

windows server backup fails after migrating from single disk to arrary

$
0
0

So I have a server running windows 2008 R2 and SQL server 2012.  I had windows backup on a schedule to do a full backup onto another remote server on our network and it was working fine for months, until I cloned the single disk on a RAID 1 mirror. I would have loved to have set the server up with RAID to begin with but cost/time restrictions etc. It's a true hardware RAID using an areca PCI-Express raid controller.  Needless to say everything is working fine on the array except for the windows backup. It fails immediately upon running every time.

I did some googling on the error code and didn't really come up with anything. The server has been rebooted several times. I have uninstalled and re-installed windows backup server. I have tried do a single backup instead of the scheduled options to a different location. I can't seem to figure out the problem. 

Here's the error I get in the logs: 

 "The backup operation that started at '2014-02-20T20:03:59.671000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

A few other logs seem to indicate something failing with the ASR writer.  Here's my list of VSS 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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {69e94aa6-dd40-418d-8b58-e032e006ab21}
   State: [7] Failed
   Last error: Timed out
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {b22f5689-133e-4dc2-96fb-fcec2969fda0}
   State: [7] Failed
   Last error: Timed out
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {a3a2bf51-140a-4f4b-8db4-7e12c24cb3ee}
   State: [7] Failed
   Last error: Timed out
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {b9ca33b0-a194-4c08-b51a-0505f68f4dea}
   State: [7] Failed
   Last error: Non-retryable error
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {37d3a214-714d-4f3c-8aca-16fbb3a88513}
   State: [7] Failed
   Last error: Timed out
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a14b514b-df1e-480b-a791-01c7490121bf}
   State: [7] Failed
   Last error: Timed out
Writer name: 'TS Gateway Writer'
   Writer Id: {368753ec-572e-4fc7-b4b9-ccd9bdc624cb}
   Writer Instance Id: {abffe612-601c-4d58-b5f2-5c756ea1b85b}
   State: [7] Failed
   Last error: Timed out
Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {9929c05c-5239-415e-9c16-8b4a1851dd94}
   State: [7] Failed
   Last error: Timed out
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {f42a1131-7bd3-4529-881d-f03d68fc7ae6}
   State: [7] Failed
   Last error: Timed out
Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {a896b5f2-ae2f-480d-8805-0a20c1b8042b}
   State: [7] Failed
   Last error: Timed out
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {b5677d57-84e6-4893-ba45-1386d38bd823}
   State: [7] Failed
   Last error: Timed out
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {5a2407bc-4124-4250-a2dc-2b919227b73c}
   State: [7] Failed
   Last error: Timed out
Any idea's how to resolve this so I can continue using windows backup? 

Viewing all articles
Browse latest Browse all 5334

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>