Re: Cannot backup Exchange VSS Error

Tech-Archive recommends: Fix windows errors by optimizing your registry




It's the system writer that's failing, not the Exchange writer. Try
seperating your system state backup and Exchange backup.


"introtologic" <otgkhan@xxxxxxxxx> wrote in message
news:cccf264b-1038-4107-af21-df6391269f99@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am having trouble setting up a backup on Exchange 2007 Server. The
OS is Windows Server 2008 64 bit (as required by Exchange 07) and has
all the latest updates installed. I am using ArcServe 12 to try to
backup the server over the network using ArcServe Exchange2007 backup
agent on the exchange server. The backup fails every time and I get
the following error in application log for VSS:

Log Name: Application
Source: VSS
Date: 9/24/2008 12:02:26 PM
Event ID: 8194
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: email.company.net
Description:
Volume Shadow Copy Service error: Unexpected error querying for the
IVssWriterCallback interface. hr = 0x80070005. This is often caused
by incorrect security settings in either the writer or requestor
process.

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {06f554de-6613-4fe3-9e08-8062faed56af}
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";>
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8194</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-09-24T17:02:26.000Z" />
<EventRecordID>70393</EventRecordID>
<Channel>Application</Channel>
<Computer>email.asms.net</Computer>
<Security />
</System>
<EventData>
<Data>0x80070005</Data>
<Data>

Operation:
Gathering Writer Data

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer
Writer Instance ID: {06f554de-6613-4fe3-9e08-8062faed56af}</Data>

<Binary>2D20436F64653A20575254575254494330303030313038382D2043616C6C3A20575254575254494330303030313035362D205049443A202030303030303832302D205449443A202030303030373036342D20434D443A2020433A5C57696E646F77735C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202020202020202D20557365723A204E5420415554484F524954595C4E4554574F524B2053455256494345202020202D205369643A2020532D312D352D3230</
Binary>
</EventData>
</Event>

I have tried using TrueImage Echo Server (with VSS enabled to backup
exchange) and Norton backup Exec 12 as well. Both of them run into
similar errors as well so I am sure its the exchange server and not
the ArcServe backup that is causing the probem.

I really appreciate any assistance or suggestions any one can provide


.



Relevant Pages

  • Re: Ghost on a server and Differential backups
    ... ShadowProtect Ghost/LiveState, True Image) you should first enable the ... Exchange writer for the Volume Shadow Copy Service. ... and retrieve individual files from the imaged backup. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event ID 9840 When Backing Up Exchange 2007 Information Store
    ... The three components to VSS are the requestor, the writer, and the provider. ... THe writer is built into Exchange. ... provider or one specific to backup exec. ... Microsoft Certified Partner ...
    (microsoft.public.exchange.admin)
  • Backup Failed with VSS Writer Error following Reboot
    ... Back up using Backup Exec 10.d failed on Windows Server 2003 SP1, ... Category: Exchange VSS Writer ... Check the Windows Event Viewer for details. ...
    (microsoft.public.exchange.admin)
  • Re: Backup Final error: 0xe000fed1 A failure occurred querying the Wri
    ... Have you tried applying the latest VSS updates? ... Backup Final error: 0xe000fed1 A failure occurred querying the Writer ... Every time I backup Exchange. ...
    (microsoft.public.exchange.admin)
  • Re: Cannot backup Exchange VSS Error
    ... backup the server over the network using ArcServe Exchange2007 backup ... Gathering Writer Data ... Writer Name: System Writer ... similar errors as well so I am sure its the exchange server and not ...
    (microsoft.public.exchange.admin)