4.1.0 HP PolyServe Software for Microsoft SQL Server administration guide (T5392-96074, October 2010)

backup node, the ClusterPulse process watches the health of the nodes higher in
the list of servers for that Virtual SSAS. When the health of one of these nodes is
equal to or greater than the backup node where the Virtual SSAS currently resides,
the Virtual SSAS will automatically attempt to fail back to that node.
• NOFAILBACK. This policy is intended to minimize failovers and is the default.
The Virtual SSAS remains active on the backup node until a “healthier” node
becomes available, at which point the Virtual SSAS fails over to that node. (On
a “healthier” node, more of the services associated with the Virtual SSAS will be
up than on the node currently hosting the Virtual SSAS. “Up” includes the probe
statuses UP and Standby.)
Network Interfaces Available/Members: Move the interfaces on which the Virtual
SSAS should be configured from the Available column to the Members column. The
first interface that you select is the primary interface. The other interfaces that you
select are backups. You can use the up and down arrows to reorder the interfaces
on the Members column.
When you click OK, a progress report will display the tasks required to create the
Virtual SSAS. Click Run to start the operation.The new Virtual SSAS appears on the
Servers, Virtual Hosts, and Applications tabs of the PolyServe Management Console.
The following example shows a Virtual SSAS configured on two nodes of the matrix.
HP PolyServe Software for Microsoft SQL Server 4.1 administration guide 101