Moving Transaction Logs (Full Version)

All Forums >> [Microsoft Exchange 2000] >> Information Stores


thehutch -> Moving Transaction Logs (23.Feb.2009 7:57:24 AM)

Hi all,

My .edb and .log files were living on the same volume and were causing me some diskspace headaches.  The problem started with my backups not purging logfiles and I solved that by creating a new backup job.  When I originally configured my Exchange environment I created 2 volumes, one for database and the other for logs. 

In order to properly utilize that configuration I am going to perform a Transaction Log move this weekend. This will be a first as I I have usually used the eseutil but this time around I plan to to use this article instead:

Hopefully this will clear up all my issues.  If anyone has any thoughts please let me know. -> RE: Moving Transaction Logs (23.Feb.2009 9:49:56 AM)

Why is it that you cannot just use: to do the move?

You would never use eseutil to do the move so I'm not entirely clear where you're coming from.

I would have a go at doing an ntbackup.exe job to clear the logs, then do the move and then do another ntbackup.exe job.

thehutch -> RE: Moving Transaction Logs (23.Feb.2009 3:10:23 PM)

That article you posted pertains to Exchange 2003 and I am running Exchange 2007 SP1.  This either means that I posted in the wrong area by mistake or that the last equinox reverted my brain to follow some sort of backwards compatibilty pattern that is sure to soon have me wearing parachute pants and running Exchange 5.5 by the end of the year. 

I've used eseutil in the past to index the database in Exchange 5.5 which in turn would occassionally clear logs and free up diskspace. -> RE: Moving Transaction Logs (23.Feb.2009 4:07:15 PM)

Doesn't matter. It's the whole "doing it in the GUI" that is the point. Right click on the storage group, select properties and then browse to the location you want it.

You have not used eseutil in 5.5 to 'index' the database.

Just follow the right click, properties, browse method. Do nothing else. Do not use eseutil and probably don't even bother with PowerShell just yet.

Page: [1]