Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

mdbdata log files

Status
Not open for further replies.

compartmentalist

IS-IT--Management
Apr 8, 2003
5
GB
Hi all,

I have a problem in the fact that the *.log files that are stored in the mdbdata folder are taking up what little disk space I have left. Can I safely delte these log files or are they neccesary for the *.edb files that are also stored in that directory?

Desperately in need of assistance!

Cheers.
 
If you run an exchange aware backup (even NTbackup on the exchange server) it will clear the log files for you.
 
Yeah, so I'm led to believe, but I'm running arcserve 2000 with the exchange back up agent and it's not having a bar of it.
 
I am having same exact problem using arcserve2k b/u agent for Exchange2k on Win2k server. Have over 100G of E00000##.log files in mdbdata. Anyone have any suggestions? Much thanks!
 
In the backup software you should have the option to remove commited log files or similar.
 
Ladybugofga,

We run arc2k and we too were have the same probs as you some time ago. The way I got round it was to make sure you have every available sp & patch for arc2k and the exch option installed on your mail server. As speedracercjr said, once the b/up has run successfully the E**.log files will disappear from the mdbdata folder.

You may like to try uninstalling arc2k and then putting it back on again. A real pain I know, but it worked for me. Make sure that arc2k is not on a disk that doesn't have a lot of space on it - arc2k likes to gobble-up disk space!

Andy.
 
Cheers for the advice. I have totally re-installed arcserve, re applied all the patches ( for the upteenth time) and it seems to have done the trick.


Thanks to all.
 
Reinstalled AS2k/ BU agent /AS SP4; then re-established rights for dbagent. Realized err problem was ongoing on 1st storage group. Brick level b/u were working, so wasn't a huge concern...until the 5M log files started adding up. Used named pipes instead of TCP/IP for Exch b/u agent config. Ran a 'successful' full backup on Exch -both 1st storage and brick level and regained the much needed space. 1st storage uses dbaexchis user, not dbagent and if err outs-the log files build up until successful 1st storage b/u. Thx for advise!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top