4.0.0 HP PolyServe Software for Microsoft SQL Server Administration Guide (T5392-96056, March 2010)

After making your changes, click OK. A progress report then appears. The report lists the tasks required
to rehost the Virtual SQL Server.
Click Run to start the rehost operation. The tasks are checked off as they are performed. When all
tasks are completed successfully, the PolyServe Management Console will show the new primary node
for the Virtual SQL Server.
If a particular task fails, it is marked with an X on the progress report and you are asked if you want
to continue the operation. The progress report provides two options that can be used if a task fails:
• Run. Click this button again to retry the failed task.
• Undo. Click this button to undo all tasks in the list and return the Virtual SQL Server to its original
state.
You can also cancel the operation at any time by clicking Cancel. HP PolyServe Software will undo
each of the completed steps and return the Virtual SQL Server to its original state.
You can also use the following command to rehost a Virtual SQL Server:
mx vsql move [--force yes|no] [--policy autofailback|nofailback]
[--application <application_name> [––msdtc] <ip> <name>
([<networkinterface> ...])
The --force yes option causes the move to complete even if the operation encounters an error.
Be sure to specify the --msdtc option if MSDTC is currently virtualized under the control of the Virtual
SQL Server. If this option is omitted, MSDTC will not be virtualized under the Virtual SQL Server.
Performance monitoring with perfmon
The Windows perfmon utility can be used to collect performance statistics for Virtual SQL/SSAS
instances based on the performance counters installed with SQL Server. Virtual SQL/SSAS instances
are monitored in the same manner as stand-alone SQL/SSAS instances or instances installed on a
MSCS cluster. You must have the appropriate permissions to access the target server (via a physical
or virtual hostname). When connected, you can select the desired SQL counters to monitor.
Also note the following:
• Remote Registry Service must be running on the target node.
• You must have remote registry access right to browse the counter.
HP PolyServe Software for Microsoft SQL Server administration guide 69