Export (0) Print
Expand All

Resume-MailboxDatabaseCopy

Applies to: Exchange Server 2010

Topic Last Modified: 2011-03-19

Use the Resume-MailboxDatabaseCopy cmdlet to resume activation, replication and replay activities (log copying and replay) for a mailbox database.


Resume-MailboxDatabaseCopy -Identity <DatabaseCopyIdParameter> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-ReplicationOnly <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

Parameter Required Type Description

Identity

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseCopyIdParameter

The Identity parameter specifies the name of the database whose copying is being resumed.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that writes this configuration change to Active Directory.

ReplicationOnly

Optional

System.Management.Automation.SwitchParameter

The ReplicationOnly parameter is used resume replication without affecting the activation setting (for example, the ActivationSuspended property for the database copy remains set to True).

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

The Resume-MailboxDatabaseCopy cmdlet resumes replication and replay from a suspended state. If a database copy was suspended without administrator intervention, it is because the database copy is in a bad state. You can use the Get-MailboxDatabaseCopyStatus cmdlet to see if there are any messages indicating a failure. If the copy of the database is in a bad state, resuming the copy causes replication to fail and the mailbox database copy to return to a suspended state.

You need to be assigned permissions before you can run this cmdlet. Although all parameters for this cmdlet are listed in this topic, you may not have access to some parameters if they're not included in the permissions assigned to you. To see what permissions you need, see the"mailbox database copy" entry in the High Availability Permissions topic.

Error Description

 

This example resumes replication and replay activity for the copy of a database named DB1 that is hosted on a Mailbox server named MBX3.

Resume-MailboxDatabaseCopy -Identity DB1\MBX3

This example resumes replication and replay activity for the copy of a database named DB2 that is hosted on a Mailbox server named MBX4. After the copy is resumed, it remains administratively blocked for activation.

Resume-MailboxDatabaseCopy -Identity DB2\MBX4 -ReplicationOnly
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft