Comprehensive data protection for all workloads
Post Reply
trackstar
Expert
Posts: 161
Liked: 4 times
Joined: Mar 11, 2013 9:47 pm
Contact:

Microsoft Exchange Writer

Post by trackstar »

Yesterday I ran a backup on a machine Windows 2008 R2 with Exchange 2010 and within minutes, the backup displayed "4/1/2015 12:34:23 PM :: Unable to release guest. Error: VSSControl: Failed to freeze guest, wait timeout" and immediately started to remove the snapshot.

I went into the Exchange machine and ran "vssadmin list writer" and it showed a lot of errors. On the Veeam's machine, I have already extended the time out value in the registry a while back. In short, I need the machine to have MS Exchange Writer working? I know it has to work for the truncating of the logs based on this link below, but the job that ran yesterday failed very quickly.

https://www.veeam.com/kb1878

Code: Select all

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: 'Microsoft Exchange Replica Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {9acbae8a-7d11-4e92-92f3-1de0e9cb2a0b}
   State: [5] Waiting for completion
   Last error: Retryable error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {d36da2b4-2143-44b4-af4d-b00cecce4a75}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {9559260d-3a7c-4aef-9cf4-019e85648326}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {2c993643-ba9c-4c75-ac34-e0a29046a5b7}
   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: {9820beae-9c1e-4abb-bee6-1fac570892a6}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {d4c5583b-577b-4356-909f-f33930690f39}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f87e3e80-069b-47c2-ab55-51ecf3d725dc}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {6bd6fd5c-70da-48d5-b611-5a682dcc4cff}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {e6f49cc6-68bd-426a-b940-0b16c0e3a447}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {723705c1-bab9-4ee8-8317-b36d947ac33b}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {01aea9f5-57a4-4d38-b90e-2e47b4575a77}
   State: [1] Stable
   Last error: No error
jadams159
Enthusiast
Posts: 80
Liked: 4 times
Joined: Apr 16, 2012 11:44 am
Full Name: Justin Adams
Location: United States
Contact:

Re: Microsoft Exchange Writer

Post by jadams159 » 1 person likes this post

So, this seems to be a VSS issue, not a Veeam issue. Many things can cause problems with VSS, most notable being high I/O, lack of disk space or fragmentation. Luca had a great post on the following thread:
http://forums.veeam.com/vmware-vsphere- ... 15678.html.

It also leads to deeper diagnosis on technet.
alanbolte
Veteran
Posts: 635
Liked: 174 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: Microsoft Exchange Writer

Post by alanbolte »

We have recently expanded our KB on VSS timeouts to clarify between some similar-sounding errors.
http://www.veeam.com/kb1377
trackstar
Expert
Posts: 161
Liked: 4 times
Joined: Mar 11, 2013 9:47 pm
Contact:

Re: Microsoft Exchange Writer

Post by trackstar »

I did this modification a while ago and changed to 1800000. Last week I updated patch 4 for version 7 and just checked and it now has 18874368 (decimal).
alanbolte
Veteran
Posts: 635
Liked: 174 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: Microsoft Exchange Writer

Post by alanbolte »

Had you opened a support case for this? Even if it isn't exactly a Veeam issue, you should open support cases for technical issues rather than relying entirely on the forum. Please post a case number when you do.

Anyway, I'm not sure if you were looking at a cached version of KB1377 or what, but the new version explains how "Failed to freeze" and "Failed to prepare" are two different errors, and only the preparation timeout is configurable. Your error is more likely to be this:
http://www.veeam.com/kb1680
Post Reply

Who is online

Users browsing this forum: DBerns, Google [Bot] and 106 guests