Share via

Enable-StorageGroupCopy (RTM)

  • Article

Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Applies to: Exchange Server 2007

This topic explains how to use the Enable-StorageGroupCopy cmdlet to create a copy of a storage group on a server running Microsoft Exchange Server 2007 in a local continuous replication (LCR) configuration.

Syntax

enable-StorageGroupCopy -Identity <StorageGroupIdParameter> [-CopyLogFolderPath <NonRootLocalLongFullPath>] [-CopySystemFolderPath <NonRootLocalLongFullPath>] [-DomainController <Fqdn>] [-SeedingPostponed <SwitchParameter>]

Detailed Description

An Exchange administrator may want to add an LCR copy to an existing storage group on an Exchange 2007 server with the Mailbox server role installed.

To successfully initiate an Enable-StorageGroupCopy operation, the following conditions must be met:

  • The specified storage group must exist, and all databases in it must have its copy enabled with Enable-DatabaseCopy.

  • The location of the paths must be on a fixed drive.

  • The path cannot be shared by more than one storage group under the same server in the Active Directory directory service.

  • The paths must be unique. They may not correspond to an already defined storage group or another storage group copy.

  • The server specified must be a stand-alone Exchange 2007 Mailbox server. The server specified cannot be a clustered implementation of Exchange 2007, for example, cluster continuous replication (CCR) or a single copy cluster (SCC).

After an Enable-StorageGroupCopy cmdlet operation has completed, all of the following occur:

  • The storage group has all of the required attributes.

  • The paths specified in the task overwrite any paths found in Active Directory.

    Note

    The default path will be used if a path is not specified in the task.

  • Unless the SeedingPostponed parameter is specified, the database copy will be seeded.

This task requires that the account you use to initiate the task is delegated the 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 Exchange Server 2007, see Permission Considerations.

Parameters

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.StorageGroupIdParameter

The Identity parameter takes one of the following values:

  • GUID

  • Name of storage group

CopyLogFolderPath

Optional

Microsoft.Exchange.Data.NonRootLocalLongFullPath

The CopyLogFolderPath parameter specifies the path where the storage group logs are stored. The default path is: <ExchangeInstallPath>\ LocalCopies\<SGName>

CopySystemFolderPath

Optional

Microsoft.Exchange.Data.NonRootLocalLongFullPath

The CopySystemFolderPath parameter specifies the path where the storage group system files are stored. The default path is: <ExchangeInstallPath>\ LocalCopies\<SGName>

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

To specify the fully qualified domain name (FQDN) of the domain controller that locates the clustered mailbox server in Active Directory, include the DomainController parameter in the command.

SeedingPostponed

Optional

System.Management.Automation.SwitchParameter

Use of the SeedingPostponed parameter results in the task not seeding the storage group copy. The administrator must then explicitly seed the storage group copy.

Errors

Error Description

The LogFolderPath and CopyLogFolderPath that you specified must not be the same. Specified folder path: %logfolderpath%

Another storage group on the same server uses the same copy log file location as this storage group. You must specify a unique path for the copy log file location.

The SystemFolderPath and CopySystemFolderPath that you specified must not be the same. Specified folder path: %logfolderpath%

Another storage group on the same server uses the same copy system file location as this storage group. You must specify a unique path for the copy system file location.

The storage group you specified is a recovery storage group. Specified storage group: %SGIdentity%

The specified storage group is a recovery storage group. LCR does not support recovery storage groups.

A storage group copy is already defined for '<SGName>'.

The storage group already has LCR enabled.

The database under this storage group is not local continuous replication enabled. Please enable local continuous replication on the database before enabling local continuous replication on this storage group.

One or more databases under this storage group are not LCR enabled. You must enable LCR on all databases before you can enable LCR on this storage group

This task is not supported on a cluster.

The Enable-StorageGroupCopy cmdlet cannot be performed on a cluster because LCR is not supported on the cluster.

The location for log files is not a fixed drive.

The location of the copy log file is not on a fixed drive. You must specify a fixed drive location to run the Enable-StorageGroupCopy cmdlet.

The location for system files is not a fixed drive.

The copy system file location is not on a fixed drive. You must specify a fixed drive location to run the Enable-StorageGroupCopy cmdlet.

The location specified for log file copies (<LogPath>) is illegal/invalid. Please verify that the directory exists and is empty.

The location specified for the transaction log file copies is illegal or invalid. You must verify that the directory exists, and that there are no files in it before running the Enable-StorageGroupCopy cmdlet.

The location of the copy's system files (<SystemPath>) is not available in the file system.

The location of the copy system file is not available in the file system. You must verify that the location specified exists and is accessible prior to running the Enable-StorageGroupCopy cmdlet.

The log path (<logPath>) for the copy already contains files with a matching prefix. To avoid overwriting the existing files, use Move-StorageGroupPath -ConfigurationOnly to change the configuration without moving any files.

The log path that you specified for the LCR copy already contains files with a matching prefix. You can avoid overwriting the existing files by using the Move-StorageGroup command –ConfigurationOnly optional parameter to change the configuration without moving any files.

The system path (<SystemPath>) for the copy already contains files with a matching prefix. To avoid overwriting the existing files, use Move-StorageGroupPath -ConfigurationOnly to change the configuration without moving any files.

The system path that you specified for the LCR copy already contains files with a matching prefix. You can avoid overwriting the existing files by using the Move-StorageGroup command –ConfigurationOnly optional parameter to change the configuration without moving any files.

Automatic initial seed failed for <SGName> with error code <ErrorCode>. Use Update-StorageGroupCopy task to retry.

The Enable-StorageGroupCopy cmdlet did not complete automatic initial seeding successfully for the specified storage group. You must reseed by using the Update-StorageGroupCopy cmdlet.

Automatic initial seed was not attempted for <SGName>.

The Enable-StorageGroupCopy cmdlet did not perform automatic initial seeding for the specified storage group. You will need to perform an initial seed by using the Update-StorageGroupCopy cmdlet.

Example

The following code is an example of the Enable-StorageGroupCopy command to enable a storage group copy for the storage group named SG1 while specifying the path locations for the CopyLogFolderPath and CopySystemFolderPath parameters.

Enable-StorageGroupCopy -Identity SG1 -CopyLogFolderPath:"D:\logs1\SG1" -CopySystemFolderPath:"D:\logs1\SG1"