Re: Exchange log files growing
- From: "Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
- Date: Wed, 4 Oct 2006 14:10:57 -0500
Hi Colin,
Be aware that there's a reason why Exchange is backed up twice using SBS
Backup. The backups aren't exactly the same - one is an exchange aware
backup which commits and flushes the logfiles, the other is a flat file
backup. The reason the second (flat file) backup is performed is for ease of
recovery. i.e. if you follow the SBS backup and restore documentation (which
is a complete and proven method), you'll need SBS Backup.
BE might be fine for the backup half of the equation, but they're not very
helpful when it comes to the restore, which is the reason you back up in the
first place ;-).
--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius
"colin" <colin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:684656BB-A6A3-4C72-92EF-27686C880E87@xxxxxxxxxxxxxxxx
Thanks for the reply Kevin,
I did backup the Microsoft Information Store as I mentioned but it didn't
remove the log files. NTBackup (using the SBS Backup Wizard) is scheduled
to
run nightly and has been removing them OK up to now. That's why I ran it
again manually but the files remain.
Funny you mentioned Backup Exec in your reply. I'm actually going to
install
the trial B/U Exec for SBS soon and convince the customer to switch. One
problem with the SBS Backup wizard is it backs up the IS twice using up
the
tape space. I'm hoping that B/U Exec only does a single backup of the IS.
Should I just install the trial B/U Exec and abandon SBS Backup?
Regards,
Colin
"Kevin Weilbacher" wrote:
you need to rerun your NTBackup, and drill down on the left pane
Microsoft
Exchange Server > YourServerName > Microsoft Information Store -- and
back
that up. That will remove the .log files.
As far as Backup Exec not working, generally when you install BE, it
loads
its own Veritas tape drivers, which then makes NTBackup not function. The
fact that NTBackup "seems" to work, may indictae something is broke or
disabled in BE.
Essentially, you either use BE or you use NTBackup.
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"colin" <colin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:416351EC-0217-4778-AFC9-7CF362DF4BE0@xxxxxxxxxxxxxxxx
I have a server running SBS 2003 with Exchange SP2. I've noticed that
there
are over 300 log files in the MDBDATA folder and running the nightly
backup
doesn't clear them. So I ran NTBackup and selected only the IS but they
are
still there. I haven't made any changes or modified Exchange to
increase
it's
maximum Store size from the default of 16GB. priv1.edb is 6.8GB,
priv1.stm
4.5GB, pub1.edb 5.8GB. Do I need to make the registry change to
increase
the
Store limit? Do I have to reboot the Server?
Anyone have an idea why these log files are still there?
Colin
.
- Follow-Ups:
- Re: Exchange log files growing
- From: colin
- Re: Exchange log files growing
- References:
- Re: Exchange log files growing
- From: Kevin Weilbacher
- Re: Exchange log files growing
- Prev by Date: RE: sysprep causes SAM corruption
- Next by Date: Re: SBS 2003 Premium, Hardware RAID-5, defrag or not?
- Previous by thread: Re: Exchange log files growing
- Next by thread: Re: Exchange log files growing
- Index(es):
Relevant Pages
|
