Skip to main content

Exchange 2007-2003- How to Set or Change the Location of Storage Group Log Files CCR

 How to Set or Change the Location of Storage Group Log Files


Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007 Topic Last Modified: 2007-01-02
This topic explains how to use the Exchange Management Console or the Exchange Management Shell to set or change the location of storage group log files. The transaction log file location is where log files are written for the storage group. These log files record every change that is made to a database in that storage group.
 Before You Begin
To perform the following procedures, the account you use must be delegated the following:

  • Exchange Server Administrator role and local Administrators group for the target server

For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
Important: When you change log file locations, all the associated databases in the storage group are dismounted and remounted. During this time, they are inaccessible to any user.



 Procedure
 To use the Exchange Management Console to set the log file location when you create a storage group

  1. Start the Exchange Management Console on the server on which the storage group is located.
  2. In the console tree, expand Server Configuration, and then click Mailbox.
  3. In the result pane, click the Mailbox server on which you want to create the storage group.
  4. In the action pane, click New Storage Group. The New Storage Group wizard appears.
  5. On the New Storage Group page, the Log files path box displays the default location where your transaction log files will be stored. Click Browse to change the default location.
    Note: You cannot use the Exchange Management Console to change the log file location for remote Mailbox servers. To create storage groups on other Mailbox servers, use the New-StorageGroup cmdlet in the Exchange Management Shell.
  6. Enter any other information in the remaining boxes as needed, and then click New to create the new storage group. For more information about creating storage groups, see How to Create a New Storage Group.



 To use the Exchange Management Console to change log file locations for an existing database

  1. Start the Exchange Management Console on the server on which the storage group is located.
  2. In the console tree, expand Server Configuration, and then click Mailbox.
  3. In the result pane, click the Mailbox server that contains the storage group for which you want to change the log file location.
  4. In the work pane, click the storage group for which you want to change the log file location.
  5. In the action pane, click Move Storage Group Path. The Move Storage Group Path wizard appears.
  6. On the Introduction page, the Log files path box displays the location where your log files are currently stored. Click Browse to specify a location to which to move these files.
    Note: You cannot use the Exchange Management Console to change the log file location for remote Mailbox servers.
  7. Click Move. A warning appears that all databases in the storage group must be temporarily dismounted, which will make them inaccessible to any user. To continue, click Yes.
  8. On the Completion page, confirm whether the log file path was changed successfully. A status of Completed indicates that the wizard completed the task successfully. A status of Failed indicates that the task was not completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes. Click Finish to complete the Move Storage Group Path wizard.



 To use the Exchange Management Shell to set the log file location when you create a storage group

  • Run the following command to create a new storage group, using the LogFolderPath parameter to set the location of the log file:


    New-StorageGroup -Name MyNewStorageGroup -Server ExchangeServer1 -LogFolderPath:"D:\Mailbox\First Storage Group" -SystemFolderPath:"D:\Mailbox\First Storage Group"



For detailed syntax and parameter information, see the New-StorageGroup reference topic.
 To use the Exchange Management Shell to change the log file location for an existing database

  • Run the following command on the server that contains the storage group for which you want to change the log file location:


    Move-StorageGroupPath -Identity "MyStorageGroup" -LogFolderPath "D:\MyNewLogFolder"



For detailed syntax and parameter information, see the Move-StorageGroupPath reference topic.

If you are working in Mailbox CCR follow the below steps.

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\SG1Make 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.

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...