Comprehensive data protection for all workloads
Post Reply
qvantas
Novice
Posts: 3
Liked: never
Joined: Nov 06, 2009 4:24 pm
Full Name: Johan Hammarstrom
Contact:

Exchange 2003 no flushing of logs

Post by qvantas » Mar 29, 2010 8:59 pm

Hi all,

I backup several exchange 2007 servers and Veeam and VSS flushes the E00 logfiles during backup.
I backup 1 exhange 2003 server with Veeam but the E00 logfiles wont be flushed!?

Enviroment:
vsphere
esx 4
Veeam backup (sanbased)

Problem Exchange VM is a windows 2003 server with exchange 2003.

On the Exchange 2007 servers i can see following in the eventlog:
"Exchange VSS Writer (instance 1e2eb4c9-bb5a-4865-a220-3b713d8405f7:11) has processed the backup completion event successfully."

I do not see this event on my problem VM i only see "The VeeamVssSupport service entered the running state" and "The VeeamVssSupport service entered the stopped state"
Anyone?

Regards
Johan

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Exchange 2003 no flushing of logs

Post by Gostev » Mar 29, 2010 9:14 pm

Hello Johan,

Try running the following two commands on the problem VM and see if output contains any errors:

Code: Select all

vssadmin list writers
vssadmin list providers

qvantas
Novice
Posts: 3
Liked: never
Joined: Nov 06, 2009 4:24 pm
Full Name: Johan Hammarstrom
Contact:

Re: Exchange 2003 no flushing of logs

Post by qvantas » Mar 30, 2010 7:41 pm

Hi Gostev,

Thanks for your replay.

-------------------------------------------------------------------
C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {1caf70f0-2a27-4ef7-9cc9-4f068599fa82}
State: [1] Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {b1708c37-8fe2-44d0-8ed6-6f7eb2c3800b}
State: [1] Stable
Last error: No error

Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {0cb1fc94-13ec-477a-8519-9307c71a97d1}
State: [1] Stable
Last error: No error

Writer name: 'TermServLicensing'
Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
Writer Instance Id: {f08a797c-5b4d-47c3-b0c6-ba4510844e14}
State: [1] Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {6923bcc7-a0fe-4dee-9249-0e3d8e8e0633}
State: [1] Stable
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {8863d27b-ae2a-4483-9f56-8fc530568469}
State: [1] Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {52b35071-684c-4f76-8c09-1178e800d38b}
State: [1] Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {c3d38e20-552f-49ac-b4de-65fd21c968e6}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {0ba1a0e1-f70f-48e5-8ee0-521b4c2d5ebd}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {86a98e35-63c8-431a-96bd-f64aa77e76d1}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {52ddafd5-ba1d-484b-bdb9-a8551bcee67d}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {c4852d5f-e011-49a3-a083-782e75ec1f7b}
State: [1] Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {46631aa8-f1e1-4e97-ad14-735b9405a5a3}
State: [1] Stable
Last error: No error


C:\Documents and Settings\Administrator>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7

------------------------------------------------------------------------------------------------------------------------

Regards
Johan

Gostev
SVP, Product Management
Posts: 24017
Liked: 3254 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Exchange 2003 no flushing of logs

Post by Gostev » Mar 30, 2010 10:16 pm

Johan, but there is no Microsoft Exchange writer in the output?

qvantas
Novice
Posts: 3
Liked: never
Joined: Nov 06, 2009 4:24 pm
Full Name: Johan Hammarstrom
Contact:

Re: Exchange 2003 no flushing of logs

Post by qvantas » Apr 05, 2010 5:28 pm

Gostev, Thank you very much!

The problem had nothing to do with Veeam.
Exchange VSS writer on SBS 2003 is for some reason disabled by default....
Now enabled and the logs are flushed.

Regards
Johan

Post Reply

Who is online

Users browsing this forum: iafifi, Karinne and 23 guests