My database dismounted due to the transaction logs drive being full. I ran the eseutil.exe /mh and received the following. I want to remove some of the logs to another partition and is seems to be telling me that I could actually move all of them. Is this correct? I noticed some other things in this file that scared me a little and was wondering if someone can tell me about something I a missing to do in my daily or monthly routine backup or maintenence procedures.Thank-you in advance......C:\PROGRA~1\Exchsrvr\bin>eseutil.exe /mh f:\mdbdata\priv1.edbMicrosoft(R) Exchange Server Database UtilitiesVersion 6.5Copyright (C) Microsoft Corporation. All Rights Reserved.Initiating FILE DUMP mode... Database: f:\mdbdata\priv1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdefFormat ulVersion: 0x620,11Engine ulVersion: 0x620,11Created ulVersion: 0x620,11 DB Signature: Create time:08/08/2005 09:37:00 Rand:338316936 Computer: cbDbPage: 4096 dbtime: 161524743 (0x9a0ac07) State: Clean Shutdown Log Required: 0-0 (0x0-0x0) Streaming File: Yes Shadowed: Yes Last Objid: 67250 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00Old Repair Count: 0 Last Consistent: (0x3EB5,83,1D8) 02/28/2007 07:43:30 Last Attach: (0x3E4C,1DE2,101) 02/23/2007 21:42:43 Last Detach: (0x3EB5,83,1D8) 02/28/2007 07:43:30 Dbid: 1 Log Signature: Create time:08/08/2005 09:36:55 Rand:338342157 Computer: OS Version: (5.2.3790 SP 1)Previous Full Backup: Log Gen: 2075-2076 (0x81b-0x81c) Mark: (0x81C,273,D1) Mark: 10/26/2005 10:52:32Previous Incremental Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00Current Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00Current Shadow copy backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 cpgUpgrade55Format: 0 cpgUpgradeFreePages: 0cpgUpgradeSpaceMapPages: 0 ECC Fix Success Count: none Old ECC Fix Success Count: none ECC Fix Error Count: none Old ECC Fix Error Count: none Bad Checksum Error Count: noneOld bad Checksum Error Count: noneOperation completed successfully in 3.15 seconds.

Yes, at this stage you can move the logs with no problem - this should be done from within ESM though, not manually. To move log files 1. Start Exchange System Manager. 2. Click Administrative Groups. Note If Administrative Groups does not appear, it may not be turned on. To turn on Administrative Groups, right-click Exchange Organization in Exchange System Manager, and then click Properties. Click to select the Display Administrative Groups check box. 3. Locate the storage group where you want to change log file paths, right-click the storage group, and then click Properties. 4. Click the General tab, click the Browse button next to the Transaction log location box, and then specify the new drive or folder location for the log files. One thing I notice is that you dont seem to be backing up your exchangeon a regular basis, either this or the backup software you are using is not exchange aware - this is dangerous and needs to be rectified immediately. Look into it and either get something like ArcServe or BackupExec with the exchange agents to backup onto another medium, i.e. tape / external hdd etc. The best backup strategy is of course to run a daily full backup but this may not be viable in all scenarios so for exchange it is recomended to run at least a weekly full backup and daily incrementals - remember to keep at least one full backup and all subsequent incrementals handy at all times. Never overwrite a complete set until you have the next complete set. If your full / incremental backups are completing successfully then there will never be a need to move / delete the log files since these are flushed after every full / incremental backup completes. Yes, this means they are automatically deleted after the archive attribute is reset, reason being is they are now backed up so no need to have them on the server anymore. Running periodic (quarterly / bi-annual) database defragmentations and consistancy checks using eseutil /d and isinteg is never always a good practice too and will keep your exchange databases in good shape as well as reduce the database size from time to time.

Excellent, thank-you.I need to clarify a little more. I have a drive (mirrored) of 68gig and it is completely full. I would like to move the transaction files off to a storage drive so I can continue using the same drive. Can I not cut and Paste these logs to the storage drive?Thanks.About the backups, we do a daily full back-up with Backup Exec 10d with the exchange agent. I must not have it configured correctly. If you know something about this that I am missing please let me know. Thank-you

Ok, in theory, because your databases wer shut down cleanly this means all logs have been committed and you can move them but in practice this is not considered a "good" practise - its much better for your full backup to flush the logs than it is for you to move them manually. Backup Exec 10d with Exchange Option should flush your logs each time a full backup completes, check your job setup and make sure that the backup type under exchange settings is set to Full Database & Logs and that your backup is completing successfully every night.