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

Recreating a missing VMFS datastore partition in VMware vSphere 5.x and 6.x

    Symptoms A datastore has become inaccessible. A VMFS partition table is missing.   Purpose The partition table is required only during a rescan. This means that the datastore may become inaccessible on a host during a rescan if the VMFS partition was deleted after the last rescan. The partition table is physically located on the LUN, so all vSphere hosts that have access to this LUN can see the change has taken place. However, only the hosts that do a rescan will be affected.   This article provides information on: Determining whether this is the same problem Resolving the problem   Cause This issue occurs because the VMFS partition can be deleted by deleting the datastore from the vSphere Client. This is prevented by the software, if the datastore is in use. It can also happen if a physical server has access to the LUN on the SAN and does an install, for example.   Resolution To resolve this issue: Run the  partedUtil  command on the host with the issues and verify if your output

ما هى ال FSMO Roles

  بأختصار ال FSMO Roles هى اختصار ل Flexible Single Operation Master و هى عباره عن 5 Roles فى ال Active Directory و هما بينقسموا لقسمين A - Forest Roles 1- Schema Master Role و هى ال Role اللى بتتحكم فى ال schema و بيكون فى Schema Master Role واحد فى ال Forest بيكون موجود على Domain Controller و بيتم التحكم فيها من خلال ال Active Directory Schema Snap in in MMC بس بعد ما يتعمل Schema Register بواسطه الامر التالى من ال Cmd regsvr32 schmmgmt.dll 2-Domin Naming Master و هى ال Role المسئوله عن تسميه ال Domains و بتتأكد ان مفيش 2 Domain ليهم نفس الاسم فى ال Forest و بيتم التحكم فيها من خلال ال Active Directory Domains & Trusts B- Domain Roles 1-PDC Emulator و هى ال Role اللى بتتحكم فى ال Password change فى ال domain و بتتحكم فى ال time synchronization و هى تعتبر المكان الافتراضى لل GPO's و هى تعتبر Domain Role مش زى الاتنين الاولانيين و بيتم التحكم فيها من خلال ال Active directory Users & Computers عن طريق عمل كليك يمين على اسم الدومين و نختار operations master فى تاب ال PDC Emu

Unlock the VMware VM vmdk file

  Unlock the VMware VM vmdk file Kill -9 PID Sometimes a file or set of files in a VMFS become locked and any attempts to edit them or delete will give a device or resource busy error, even though the vm associated with the files is not running. If the vm is running then you would need to stop the vm to manipulate the files. If you know that the vm is stopped then you need to find the ESX server that has the files locked and then stop the process that is locking the file(s). 1. Logon to the ESX host where the VM was last known to be running. 2.  vmkfstools -D /vmfs/volumes/path/to/file  to dump information on the file into /var/log/vmkernel 3.  less /var/log/vmkernel  and scroll to the bottom, you will see output like below: a. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)FS3: 130: <START vmware-16.log> b. Nov 29 15:49:17 vm22 vmkernel: 2:00:15:18.435 cpu6:1038)Lock [type 10c00001 offset 30439424 v 21, hb offset 4154368 c. Nov 29 15:49:17 vm22 vmkernel: gen 664