Re: Exchange log files growing

There could be two or even three problems.

Something is wrong with backup if the logfiles aren't being committed and
flushed. Or, they are being flushed, but are building up at a very fast
rate. What are the dates/times of the logfiles? Are they older than the most
recent backup, or newer. You might try an NTbackup of exchange only to see
what's going on.

If you could post an SBSbackup logfile, that might shed some light as well.

--
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:1ACC4ACC-E4F9-435B-B03F-6D0A6F76D38F@xxxxxxxxxxxxxxxx
Thanks Les, yes I was aware of the reason Exchange is backed up twice.
The
problem is the tape drive is a DAT72 and I have excluded everything I can
using the SBS Wizard but Windows and Exchange alone are almost exceeding
the
capacity of the tape. I have another DAT72 drive on the Terminal Server
backing up the data. That is what's happening now, the backup failed
because
the Exchange log files are growing (over 300 log files in the MDBData
folder), NTBackup isn't clearing them out and so the tape pops out when
it's
full. Is B/u Exec for SBS not a better idea? I've not used it on a SBS
before
but it looks good on Symantec's web site (of course), the disaster
recovery
is one big feature.

Let me know what you think....

Colin

"Les Connor [SBS Community Member - SBS M" wrote:

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








.

Relevant Pages

  • Re: Disk with NTDS failing
    ... using NTBackup to usb drive starts at 5:00 pm. ... Backup Exec to DLT tape starts at 11:00 pm. ... on total server restores using NTBackup. ... I put those onto the replacement drive, with the same drive letter, and SBS ...
    (microsoft.public.windows.server.sbs)
  • Re: NtBackup hangs during scheduled backups
    ... In your logs, ntbackup isn't starting. ... You may try deleting them all if they exist, and then try sbsbackup wizard, which will create a scheduled backup. ... Les Connor [SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup requires 18-23 hours to complete.
    ... I'm not sure if you use SBSbackup, or only the native NTbackup to configure your backups. ... Considering you want something different than SBSBackup offers, I'd suggest you run the backup configuration wizard and elect *not* to use SBS backup, and do your configuration via NTbackup, or a third party backup application. ...
    (microsoft.public.windows.server.sbs)
  • RE: Backup and Sharepoint
    ... I can confirm that Backup still fails after your recommendations. ... DCOM issue. ... Do I fix before or should I leave this until I have redone SBS SP1 ... > When opening a new thread via the web interface, we recommend you check the ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange log files growing
    ... yes I was aware of the reason Exchange is backed up twice. ... the backup failed because ... the Exchange log files are growing (over 300 log files in the MDBData ... Is B/u Exec for SBS not a better idea? ...
    (microsoft.public.windows.server.sbs)
Loading