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

In the following simple example, Virtual SQL Server VSQL1 is providing Instance1,
with the primary on node1 and the backup on node2. Virtual SQL Server VSQL2 is
also providing an Instance1, with the primary on node3 and the backup on node 2.
The Virtual SQL Servers are sharing a backup node for Instance 1, as it is unlikely
that both Virtual SQL Servers will fail over at the same time.
However, with drag and drop, it is possible to move the primary for VSQL2 to node2
and the backup to node1. Now neither of the Virtual SQL Servers has a backup.
Both node1 and node2 are primary for Instance1 and cannot also act as a backup
for another instance having the same name.
Select tasks from a menu
Right-click on a SQL Server resource in either the Name column or a server cell to
see the available options.
Virtual SQL Servers and Virtual SQL instances
Most of the available options are described under “Virtual SQL Server
procedures” on page 92. For information about rehosting, see “Rehost a Virtual SQL
Server” on page 87. For information about adding a new virtual SQL instance, see
“Add a Virtual SQL instance” on page 77.
Virtual SSAS and Virtual SSAS instances
Most of the available options are described under “Other Virtual SSAS
procedures” on page 110. For information about rehosting, see “Rehost a Virtual
SSAS” on page 108. For information about adding a new virtual SSAS instance, see
“Add a Virtual SSAS instance” on page 103.
HP PolyServe Software for Microsoft SQL Server 4.1 administration guide 119