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.I have two Dell R-170 servers both running Server 2008 R2 and Hyper -V, each with two VM's installed and running. If the copy queue length is more than 12, the database doesn't automatically mount. The copy queue length is the number of logs recognized by the passive copy that needs to be replicated. 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.Because the database will mount with any amount of log loss, using this value could result in a large amount of data loss. BestEffort: If you specify this value, the database automatically mounts regardless of the size of the copy queue length.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. If the copy queue length is greater than 6, the database doesn't automatically mount. 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.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. None: When using this value, the currently configured auto database mount dial setting on the target server will be used.The MountDialOverride parameter is used to override the auto database mount dial (AutoDatabaseMountDial) setting for the target server and specify an alternate setting. 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. This example performs a server switchover for the Mailbox server MBX1. Example 4 Move-ActiveMailboxDatabase -Server MBX1 Because the MountDialOverride parameter isn't specified, MBX4 mounts the database using a database auto mount dial setting of Lossless. When the command completes, MBX4 hosts the active copy of DB3. This example performs a switchover of the database DB3 to the Mailbox server MBX4. Example 3 Move-ActiveMailboxDatabase DB3 -ActivateOnServer MBX4 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. When the command completes, MBX3 hosts the active copy of DB1. This example performs a switchover of the database DB1 to the Mailbox server MBX3. Example 2 Move-ActiveMailboxDatabase DB1 -ActivateOnServer MBX3 -MountDialOverride:GoodAvailability Because the MountDialOverride parameter is set to None, MBX1 mounts the database using its own defined database auto mount dial settings. When the command completes, MBX1 hosts the active copy of DB2. This example performs a switchover of the database DB2 to the Mailbox server MBX1. Examples Example 1 Move-ActiveMailboxDatabase DB2 -ActivateOnServer MBX1 -MountDialOverride:None To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. You need to be assigned permissions before you can run this cmdlet. In this article Syntax Move-Active Mailbox Database Use the Move-ActiveMailboxDatabase cmdlet to perform a database or server switchover.įor information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax. This cmdlet is available only in on-premises Exchange.
0 kommentar(er)
