1 understanding and using planned failover, 1 planned failover in windows server 2012 – Avago Technologies Syncro CS 9286-8e User Manual
Page 60
Avago Technologies
- 60 -
Syncro CS 9286-8e Solution User Guide
November 2014
Chapter 4: System Administration
Understanding Failover Operations
4.2.1
Understanding and Using Planned Failover
A planned failover occurs when you deliberately transfer control of the drive groups from one controller node to the
other. The usual reason for initiating a planned failover is to perform some kind of maintenance or upgrade on one of
the controller nodes—for example, upgrading the controller firmware, as described in the following section. A
planned failover can occur when there is active data access to the shared drive groups.
Before you start a planned failover on a Syncro
CS system, be sure that no processes are scheduled to run during that
time. Be aware that system performance might be impacted during the planned failover.
NOTE
Failed-over VDs with exclusive host access cannot be accessed unless
the VD host access is set to SHARED. Do not transition operating
system boot volumes from exclusive to SHARED access.
4.2.1.1
Planned Failover in Windows Server 2012
Follow these steps to perform a planned failover on a Syncro CS 9286-8e system running Windows Server 2012.
1.
Create a backup of the data on the Syncro CS 9286-8e system.
2.
In the Failover Cluster Manager snap-in, if the cluster that you want to manage is not displayed in the console
tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that
you want.
3.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
4.
Expand Services and Applications, and click the name of the virtual machine.
5.
On the right-hand side of the screen, under Actions, click Move this service or application to another node,
and click the name of the other node.
As the virtual machine is moved, the status is displayed in the results panel (center panel). Verify that the move
succeeded by inspecting the details of each node in the RAID management utility.