Applies to: Exchange Server 2007
Topic Last Modified: 2007-06-05

This topic explains how to use the Enable-DatabaseCopy cmdlet to create a copy of a database on the specified Mailbox server that is running Microsoft Exchange Server 2007 in a local continuous replication (LCR) configuration.

Syntax


`enable-DatabaseCopy -Identity <DatabaseIdParameter> [-CopyEdbFilePath <EdbFilePath>] [-DomainController <Fqdn>]`

Parameters

Parameter	Required	Type	Description
Identity	Required	Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter	The Identity parameter takes one of the following values: GUID Name of the database
CopyEdbFilePath	Optional	Microsoft.Exchange.Data.EdbFilePath	The CopyEdbFilePath parameter specifies the path where the database will be created. The default path is: <ExchangeInstallDirectory>\LocalCopies\Storage Group\MBDatabase.edb
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.

Parameter

Required

Type

Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter

The Identity parameter takes one of the following values:

GUID
Name of the database

CopyEdbFilePath

Optional

Microsoft.Exchange.Data.EdbFilePath

The CopyEdbFilePath parameter specifies the path where the database will be created. The default path is: <ExchangeInstallDirectory>\LocalCopies\Storage Group\MBDatabase.edb

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.

Detailed Description

An Exchange administrator may want to enable LCR on a database on an Exchange 2007 server.

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

The server containing the specified database 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).
The specified storage group and database must exist.

Note:

The storage group and database can be mounted or dismounted.
The specified database must not be a recovery database.
The specified location for the copy must have sufficient available disk space to hold the copy.
The path and file name must be unique. They may not correspond to an already defined database copy.
If the database path ends in MySample.edb, the copy path must also end in MySample.edb.

Note:
The storage group and database can be mounted or dismounted.

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

The mailbox database object in the Active Directory directory service has all of the required attributes.
The LCR copy of the production database is created, but is not functional or seeded until the storage group copy is enabled.

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.

Note:
LCR restricts a storage group so that it contains precisely one database. This check is not performed until the Enable-StorageGroupCopy cmdlet is run.

Note:
There is no Disable-DatabaseCopy cmdlet because the LCR copy is not fully enabled until the Enable-StorageGroupCopy runs and the LCR copy is fully disabled with the Disable-StorageGroupCopy cmdlet all the way to the database level.

Errors

Error	Description
`The path, '<DBPath>', that you specified for the local continuous replication copy is used by another database on the same server (<serverName>). Please specify a different path for the copy's database.`	The EDBFilePath and CopyEDBFilePath that you specified must not be the same.
`The mailbox database you specified is a recovery mailbox database. Specified mailbox database: %Identity%`	The mailbox database you specified is a recovery mailbox database. LCR is not supported on a recovery storage group.
`Storage group '<SGName>' is enabled for local continuous replication. The database in the storage group must also be enabled.`	The database and storage group already have LCR enabled.
`There is not enough space on drive %drivename% to complete this operation.`	There is not enough space in the copy location to host the production .edb file. You must ensure that the copy location has sufficient free disk space to host the production .edb file.
`The database file path of '<DBPath>' is not available. Please correct the issue before continuing.`	The .edb file path of the specified database is not available. You must correct this issue before running the Enable-DatabaseCopy cmdlet.
`Local continuous replication cannot be enabled on a cluster.`	The Enable-DatabaseCopy cmdlet cannot be performed on a cluster because LCR is not supported on the cluster.
`Failed to retrieve mailbox database '<DBName>' due to error (<ErrorCode>). Please correct the problem before continuing.`	The Enable-DatabaseCopy cmdlet failed to retrieve the specified mailbox database.
`The location, '<DBLocation>' must be a fixed (non-removable) storage.`	The CopyEdbFilePath that you specified is not on a fixed drive. Only fixed (non-removable) storage can be used for LCR file paths.
`The copy EDB file path is not available. There is already a directory named '<filePath>' on server '<server>'.`	The CopyEdbFilePath specified is not available. There is already a directory with the specified name on the server. You must specify a unique path for CopyEdbFilePath to run the Enable-DatabaseCopy cmdlet.
`The database file path that you specified (<DBPath>) for the local continuous replication copy of the database already contains a database file. To avoid overwriting the existing files, use move-database -configurationOnly to change the configuration without moving any files.`	The path that was specified for the location of the copy already contains a database file. To avoid overwriting the existing files, use the Move-Database command –ConfigurationOnly parameter to change the configuration without moving any files.
`Failed to check the status of copy's database file at (<DBPath>) on <ServerName>. To avoid overwriting the existing files, use "Move-DatabasePath -ConfigurationOnly" to change the configuration without moving any files.`	The Enable-DatabaseCopy cmdlet failed to check the status of the copy's database file because the specified server is not accessible. The server must be online to check the status of the copy's database.

Example

The following example shows the Enable-DatabaseCopy command being used to enable a database copy for the database named Mailbox Database, which is contained in the storage group named SG1, and is located on the server named EXLCR1.

	Copy Code
Enable-DatabaseCopy -Identity:"EXLCR1\SG1\Mailbox Database" -CopyEdbFilePath:"D:\DBs\SG1\Mailbox Database.edb"