vianceadmin
asked on
***Help*** Delete Exchange Transaction Logs (Exchange 2003)
MDBDATA folder is filling up with transaction logs. I know I can do a full backup and that will flush the logs but I only have 2GB left so I don't have time to run a full backup before the D:\ fills up. I read I could:
Enable circular logging
Stop Information Store service
Delete or move old transaction logs
Start Information Store service
Is this OK?
Thanks so much for any help
Enable circular logging
Stop Information Store service
Delete or move old transaction logs
Start Information Store service
Is this OK?
Thanks so much for any help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Me again,
I just realize you were talking about Exchange 2003... (I'm tired)
Forget my comment about DAG...
About deleting the log files. Enable Circular Logging and wait for some hours. This will permit you to identify log files that are no more used, looking at their last access date/time.
I just realize you were talking about Exchange 2003... (I'm tired)
Forget my comment about DAG...
About deleting the log files. Enable Circular Logging and wait for some hours. This will permit you to identify log files that are no more used, looking at their last access date/time.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The database was in a good state so I was able to move the logs elsewhere. Thanks all for the help!
By the way, enabling circular logging will make things so that Exchange will not create new log files. Exchange will always reuse the same log file.
Also, circular logging will no more permit you to make a database restore without loosing informations.
If your database becomes corrupted and you have to restore it from the last full backup (with circular logging you can ONLY do FULL backup and of course you can ONLY restore from last FULL backup) you will loose all modifications that occurred since the last full backup... You'll loose any message received since the last backup...
So, for now, if you're sure that your disk will become full before being able to backup database, and if you're not able to expand disk volume your only temporay solution is to enable circular logging... but THIS IS NOT the final solution !!
The final solution is to bring enough disk space to your messaging platform regarding your needs.
If your disk became full then that means you NEED more space !!
Have a good day.