Re: Exchange Logs not being committed to database

There's a little terminology confusion here. The logs are committed once
they are written to the database. The logs are not flushed until a full
(normal) backup (or a full and then an incremental or differential) backup
is run.

Run a full (normal) backup ASAP. Because right now, you're in a position
where you might have to end up replaying those 87 GB of logs if your last
good backup really was 87GB of logs ago. I know how long it takes to commit
16 GB of logs, and 87 GB would not be pretty.

I would ditch the brick level backups immediately. They're a waste of time
and tape, IMO.

Missy

"Ryan" <Ryan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4005894B-9D5C-478B-A58F-03EF790E91B0@xxxxxxxxxxxxxxxx
I've just come in as IT Manager for a new company (today is literally
first
day). One of the first problems discussed was Exchange. I've inventoried
the
Exchange environment and found several problems. My biggest concern right
now
is the Exchange transaction logs, there are 4 months worth of logs that
have
not been committed.

They are utilizing Backup Exec 10d, and one thing I've noticed is they
have
the Full backup running nightly with flush committed logs. The strange
thing
is they are also running a bricklevel mailbox backup on the same job.
Would
this prevent the Exchange transaction logs from being committed? I've
always
run Full Database backups, and individual mailbox backups, but they've
always
been separate jobs.

Also my other large concern is I've checked and the transaction logs are
approximately 87GB. What is the possible impact of committing 87GB of log
files to a single exchange store over one backup? Am I looking at possible
DB
corruption? Could this take days to commit all these files? I know it
would
depend a lot on the environment, hardware, etc. I'll try to give you best
run
down I can at this point on the environment.

AD 2003
Exchange 2003 Enterprise(v6.5 Build 7638.2 SP2) on Windows Server 2003
Standard SP1

Everything is lumped together
Databases D:\Exchsrvr\mdbdata (.edb and .stm) - only one storage group,
one
admin group
Logs D:\Exchsrvr\mdbdata

Hardware is Xeon 3GHZ, 2GB memory, plenty of disk space on D:\ drive (RAID
5)

Thank you in advance,
Ryan



.

Relevant Pages

  • RE: Performance Report & backup log
    ... I am glad to know the report is correct now after you delete the backup ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ... <<Server\Support\Backup Logs ...
    (microsoft.public.windows.server.sbs)
  • Re: OK to delete old log files?
    ... I could use this to see which logs I could move (I ... does Exchange commit all the logs every time it is shut ... >>> My backup is having a problem because of space problems on the tape as ... >>> I will probably move the databases or log files to a different drive ...
    (microsoft.public.exchange.admin)
  • Re: Exchange log files growing
    ... I didn't want to mention the capacity issue until the exchange log issue was ... backup with the excluded data may exceed the cost of biting the bullet now. ... Les Connor [SBS Community Member - SBS MVP] ... I also dig out other old logs when I touch a server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Logs not flushing
    ... Definitely doing a full backup each night (flush committed logs). ... Information Store NGS Storage Group: Beginning the backup of the file ...
    (microsoft.public.exchange.admin)
  • Re: Exchange log files growing
    ... Personally i would delete all the logs from 3/10 and 4/10. ... What do you think about the B/U Exec for SBS? ... Is it inferior to SBS Backup? ... the Exchange log files are growing (over 300 log files in the MDBData ...
    (microsoft.public.windows.server.sbs)