After you've created a database availability group and have added multiple database copies to the servers
in your organization you'll need to be able to move the active corpus to other servers.
In this video you'll learn how to do this in the exchange management shall manually move in the active
mailbox database to another server or in a dark is a process known as a database we show her in order
to activate passive mailbox database corpus on an other server.
You'll need to use the move active mailbox database cam and LAT so you could type move active mailbox
database D.B. one active on Server Exchange 2 or E X to confirm equal into to false.
In this example the passive mailbox database copy of the B one is activated on the exchange to server
so when activating in a database copy you can optionally sell the move command parameter to history
and you of your choice.
That will be recorded to the event log entry for move operation.
You can choose to activate one mailbox database copy at a time or you can move all the active databases
on a particular server to one or more servers in the dark.
Let's take a look at the following command move active database.
So remove active mailbox Database Server Exchange to activate Server Exchange 1 Confirm equal into false
as you can see here all the active databases on exchange 2 will be moved to exchange 1.
Obviously this requires that you have the database corpus located on exchange one for every mailbox
database on exchange to one move in mailbox database corpus.
You can also override the auto Mondale's sadness for the target server by specifying one of the following.
Well use for the Mount dial override settings you can specify a gnome so when you use a known the currently
configured mount dial certain on the target server will be used in other certain is lossless.
This is the default while here for the amount dial override parameter when performing a lossless mount.
All log files from the active copy must be fully replicated to the passive copy another set and is good
to will ability.
This specifies that the copy queue lands must be less than or equal to 6 log files in order to activate
the passive coordinate.
Next one is best effort.
This month the database regardless of the copy queue lands and could result in data loss and another
set in is best availability.
This specifies that the copy queue lands must be less than or equal to twelve log files in order to
activate the passive copy for example to move the active database of D.B. 1 from mailbox to mailbox
server to 2 mailbox server one with good availability.
Use the Mount dial override parameter when run on the command left.
Like so move active mailbox database W1 1 activate on server X1 mound dial override good availability
confirm falls if you want to forcefully activate an unhealthy database copy it.
There are a few parameters available with a move active mailbox database command let that can be used
depending on the situation.
For example if you have a database copy with a corrupt content index state you can force the activation
of the database using the skip client experience checks parameter like so move active database do be
one active on server X1 skip client experience checks and confirm falls.
At this point the search catalogue on G.B. 1 will need to be Rick Rule 2 or receded.
You also have the option of keeping database health checks when attempting to move the active copy over
database.
In a failed state it is recommended that you only do this when an initial activation attempt has failed
so the command.
Looks like this move active mailbox database would be one act active wait on server x1.
Skip health checks confirm falls and finally you can use this Skip lag checks parameter to allow the
activation on a database copy that has copy and replay.
You lands outside their required dress holds and the command looks as follows.
Move Active mailbox database be 1 activate on Sora x1.
Skip lag checks confirm false.
It's important to point out here that activating databases that are myths and log files will result
in data loss and unhappy users.
Another method of moving all active databases corpus from one server useful one doing maintenance for
example is to use the following command land set mailbox sorrow x 1 database copy activation disable
term move now equals 2 through such a long parameter database copy activation disabled and move.
Now this command led will prevent databases from being moved on server x1.
If there are the healthy corpus on the same databases on other server additionally it immediately moves
and amount to databases on server X1 to other servers.
If corpus exist and are in a house estate.