This GENERALLY means that the last full back up of the database didn't purge
logfiles, for whatever reason. That would be the first thing I check.
According to MSFT, this "should never happen" and they recommend you open a
case. In my experience, it's pretty common, and most people don't want to
Can you perform a reseed after an incremental backup or MUST it be a Full?
From: bounce-9334284-8066...@lyris.sunbelt-software.com
[mailto:bounce-9334284-8066...@lyris.sunbelt-software.com] On Behalf Of Michael
B. Smith
Sent: 12 May 2011 22:29
To: MS-Exchange Admin Issues
Subject: RE: Log files
bounce-9334479-8066...@lyris.sunbelt-software.com
[mailto:bounce-9334479-8066...@lyris.sunbelt-software.com] On Behalf Of Sobey,
Richard A
Sent: 13 May 2011 06:33
To: MS-Exchange Admin Issues
Subject: RE: Log files missing during reseed
Can you perform a reseed after an incremental backup or MUST
was fine then.
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk]
Sent: Friday, May 13, 2011 6:35 AM
To: MS-Exchange Admin Issues
Subject: RE: Log files missing during reseed
Full backup ran this morning
066...@lyris.sunbelt-software.com] On Behalf Of Michael
B. Smith
Sent: 13 May 2011 13:45
To: MS-Exchange Admin Issues
Subject: RE: Log files missing during reseed
I asked again and was told, flat out, by an escalation engineer that "this
should not happen". So...you should be safe to open a case
