Pages

▼

Wednesday, April 8, 2009

How to Move Exchange 2007 Log Files on a CCR Cluster

You cannot move the Exchange 2007 transaction logs to a different location while the CCR cluster is running. You must suspend the cluster, move the transaction log configuration *only* using EMS, and then resume the cluster.

Here are the detailed steps to do this:

  • First, create the folders for the new location of the Exchange transaction logs. For this example, L:\ExchangeLogs\SG1. Make sure to do this on both nodes.

  • Open the Exchange Management Shell (EMS) and run the following commands:

Suspend-StorageGroupCopy -Identity "exchange1\First Storage Group" -SuspendComment "Moving transaction logs" -Confirm:$False

move-StorageGroupPath -Identity 'exchange1\First Storage Group' -LogFolderPath 'L:\ExchangeLogs\SG1' -SystemFolderPath 'L:\ExchangeLogs\SG1' -ConfigurationOnly

move [oldpath]\*.* [newpath]

Resume-StorageGroupCopy -Identity "exchange1\First Storage Group"

Where exchange1 is the name of your CCR cluster, First Storage Group is the name of the storage group logs you want to move, oldpath is the current path of the logs, and newpath is the new target path.

The first line suspends log shipping for the CCR cluster. The second line updates the Exchange configuration in Active Directory to use the new storage group path. The third line moves the existing log files from the old location to the new one. And finally, the fourth line resumes log shipping for the cluster.

at

3 comments:

  1. Nathan CachilaNovember 19, 2009 at 8:08 AM

    Morning Jeff,

    Thanks in advance for your help. I hope you can give me an expert answer on this.
    I have Exchange 2007 running on Windows 2008 server with two storage groups, one for mailboxes and the other for public folders. Unfortunately, we had to get this mail server up and running quickly a year ago and I didn't plan space and logging very well. Exchange system files and transaction log files are on C: and the actual database (edb) are on much larger D: drive. I don't have circular logging on so I ran space problem on C: and manually moved old transaction logs to back up dir on D:. Everything is running well but I have two new issues.

    1. I am trying to back up Exchange using Back Exec and it fails because the logs are incomplete in the default location (C:).
    2. I'm starting to run out of space again on C:

    The plan is to move both storage groups to the D: drive completely now so I can get them backed up and I don't run into space issues anymore.

    Will Exchange move the storage groups with incomplete logs using the "Move storage group" function in the Exchange console or will it fail?

    What is the best procedure to perform this move successfully?
    Thanks again for your help!

    -Nathan Cachila

    ReplyDelete
  2. JeffNovember 19, 2009 at 8:28 PM

    Hi Nathan,

    It sounds like you don't have the complete set of transaction logs or they are physically corrupt. Assuming that your database is functioning properly (no errors or problems), you can dismount the database, delete all the files in the transaction log folder, and then mount the database. This will create a new .CHK file and new transaction logs. This is safe to do, since you don't have a full set of logs anyway.

    Then you can run a full database backup and/or move the transaction logs to the new location.

    Jeff

    ReplyDelete
  3. AnonymousMarch 4, 2013 at 5:22 PM

    I was affraid in using these very simple steps but tried directly in the production... and resolved my issue amazingly...........

    Very simple and very useful blog.


    Thanks alot for the help by writingthis blog.

    Thanks,
    KantaPrasad@hotmail.com

    ReplyDelete

Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.