TechNet
Export (0) Print
Expand All

Move-ActiveMailboxDatabase

 

Applies to: Exchange Server 2016

This cmdlet is available only in on-premises Exchange Server 2016.

Use the Move-ActiveMailboxDatabase cmdlet to perform a database or server switchover.

For information about the parameter sets in the Syntax section below, see Syntax.

Move-ActiveMailboxDatabase -Identity <DatabaseIdParameter> [-ActivateOnServer <MailboxServerIdParameter>] <COMMON PARAMETERS>

Move-ActiveMailboxDatabase -Server <MailboxServerIdParameter> [-ActivateOnServer <MailboxServerIdParameter>] <COMMON PARAMETERS>

Move-ActiveMailboxDatabase -ActivatePreferredOnServer <MailboxServerIdParameter> <COMMON PARAMETERS>

COMMON PARAMETERS: [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-MountDialOverride <None | Lossless | GoodAvailability | BestAvailability | BestEffort>] [-MoveComment <String>] [-SkipActiveCopyChecks <SwitchParameter>] [-SkipAllChecks <SwitchParameter>] [-SkipClientExperienceChecks <SwitchParameter>] [-SkipHealthChecks <SwitchParameter>] [-SkipLagChecks <SwitchParameter>] [-SkipMaximumActiveDatabasesChecks <SwitchParameter>] [-SkipMoveSuppressionChecks <SwitchParameter>] [-TerminateOnWarning <SwitchParameter>] [-WhatIf [<SwitchParameter>]]

This example performs a switchover of the database DB2 to the Mailbox server MBX1. When the command completes, MBX1 hosts the active copy of DB2. Because the MountDialOverride parameter is set to None, MBX1 mounts the database using its own defined database auto mount dial settings.

Move-ActiveMailboxDatabase DB2 -ActivateOnServer MBX1 -MountDialOverride:None

This example performs a switchover of the database DB1 to the Mailbox server MBX3. When the command completes, MBX3 hosts the active copy of DB1. Because the MountDialOverride parameter is specified with a value of Good Availability, MBX3 mounts the database using a database auto mount dial setting of GoodAvailability.

Move-ActiveMailboxDatabase DB1 -ActivateOnServer MBX3 -MountDialOverride:GoodAvailability

This example performs a switchover of the database DB3 to the Mailbox server MBX4. When the command completes, MBX4 hosts the active copy of DB3. Because the MountDialOverride parameter isn't specified, MBX4 mounts the database using a database auto mount dial setting of Lossless.

Move-ActiveMailboxDatabase DB3 -ActivateOnServer MBX4

This example performs a server switchover for the Mailbox server MBX1. All active mailbox database copies on MBX1 will be activated on one or more other Mailbox servers with healthy copies of the active databases on MBX1.

Move-ActiveMailboxDatabase -Server MBX1

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 "Database availability groups" entry in the High availability and site resilience permissions topic.

 

Parameter Required Type Description

ActivatePreferredOnServer

Required

Microsoft.Exchange.Configuration.Tasks.MailboxServerIdParameter

The ActivatePreferredOnServer parameter specifies the name of a Mailbox server on which to activate all mailbox databases that have copies with an ActivationPreference value of 1. You can use this parameter as part of ending maintenance mode on a Mailbox server.

Identity

Required

Microsoft.Exchange.Configuration.Tasks.DatabaseIdParameter

The Identity parameter specifies the identity of the mailbox database being activated.

Server

Required

Microsoft.Exchange.Configuration.Tasks.MailboxServerIdParameter

The Server parameter specifies the identity of the server from which to move all active mailbox databases.

ActivateOnServer

Optional

Microsoft.Exchange.Configuration.Tasks.MailboxServerIdParameter

The ActivateOnServer parameter specifies the name of the Mailbox server on which the mailbox database copy should be activated.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.

  • Destructive cmdlets (for example, Remove-* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false.

  • Most other cmdlets (for example, New-* and Set-* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com.

MountDialOverride

Optional

Microsoft.Exchange.Data.Directory.SystemConfiguration.DatabaseMountDialOverride

The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. The following are possible values:

  • None   When using this value, the currently configured auto database mount dial setting on the target server will be used.

  • Lossless   This is the default value. When using this value, the database doesn't automatically mount until all log files that were generated on the original active copy have been copied to the passive copy.

  • GoodAvailability   If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 6. If the copy queue length is greater than 6, the database doesn't automatically mount. When the copy queue length is less than or equal to 6, Microsoft Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.

  • BestEffort   If you specify this value, the database automatically mounts regardless of the size of the copy queue length. Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss.

  • BestAvailability   If you specify this value, the database automatically mounts immediately after a failover if the copy queue length is less than or equal to 12. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. If the copy queue length is more than 12, the database doesn't automatically mount. When the copy queue length is less than or equal to 12, Exchange attempts to replicate the remaining logs to the passive copy and then mounts the database.

MoveComment

Optional

System.String

The MoveComment parameter specifies an optional administrative reason for the move operation. The comment is recorded in the Event log.

SkipActiveCopyChecks

Optional

System.Management.Automation.SwitchParameter

The SkipActiveCopyChecks parameter specifies whether to skip checking the current active copy to see if it's currently a seeding source for any passive databases. Be aware that when using this parameter, you can move a database that's currently a seeding source, which cancels the seed operation.

SkipAllChecks

Optional

System.Management.Automation.SwitchParameter

PARAMVALUE: SwitchParameter

SkipClientExperienceChecks

Optional

System.Management.Automation.SwitchParameter

The SkipClientExperienceChecks parameter specifies whether to skip the search catalog (content index) state check to see if the search catalog is healthy and up to date. If the search catalog for the database copy you're activating is in an unhealthy or unusable state and you use this parameter to skip the search catalog health check and activate the database copy, you will need to either re-crawl or reseed the search catalog.

SkipHealthChecks

Optional

System.Management.Automation.SwitchParameter

The SkipHealthChecks parameter specifies whether to bypass passive copy health checks. With the SkipHealthChecks parameter, you can move the active copy to a database copy that's in the Failed state. This parameter should be used only if the initial attempt to move the active database has failed. This is because the SkipHealthChecks parameter performs additional validation to ensure that the log files are consistent, which can take a considerable amount of time.

SkipLagChecks

Optional

System.Management.Automation.SwitchParameter

The SkipLagChecks parameter specifies whether to allow a copy to be activated that has replay and copy queues outside of the configured criteria.

SkipMaximumActiveDatabasesChecks

Optional

System.Management.Automation.SwitchParameter

The SkipMaximumActiveDatabasesChecks is used to skip checking the value of MaximumPreferredActiveDatabases during the best copy and server selection (BCSS) process. Any configured value for MaximumActiveDatabases will still be honored during the BCSS process and by the Information Store.

SkipMoveSuppressionChecks

Optional

System.Management.Automation.SwitchParameter

PARAMVALUE: SwitchParameter

TerminateOnWarning

Optional

System.Management.Automation.SwitchParameter

The TerminateOnWarning parameter specifies whether to terminate the task and output an error message if a warning is encountered during the switchover operation.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

 
Show:
© 2016 Microsoft