You can make secondary servers into primary servers, or ensure that a primary server is
always the one hosting the role as long as it is running.
What you should know
To minimize system disruption, the role
remains on the secondary server after a failover occurs, by default. You can change the
server priority and force the highest priority server to always be the one hosting the
role.
Procedure
-
From the Config
Tool home page, open the
System task, and click the Roles view.
-
Select the role and then click the Resources tab where the
role’s primary server is listed.
-
Select a server from the list, and click the or
buttons to change the server priority.
The higher a server is in the list, the higher its priority.
-
Select the Force execution on highest priority server option and
click Apply.
This option forces the server with the highest priority (at the top of the list) to
always be the one hosting the role, as long as it is online. If the first server is
offline, then the priority goes to the second sever on the list, and so on and so
forth.
After a few seconds, the green LED moves to the server that is at the top of the list,
indicating that it is now the one hosting the role.
IMPORTANT: Servers are
displayed in the order they are picked if a failover occurs. When the primary server
fails, the role automatically switches to the next server in the list.