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

mx vssas move [--policy autofailback|nofailback] [--application
<application_name>][--force yes|no] <ip> <name>
([<networkinterface> ...])
The --force yes option causes the move to complete even if the operation
encounters an error.
Other Virtual SSAS procedures
Maintenance mode
When you need to apply a service pack or perform other SSAS maintenance, you
can move a Virtual SSAS to maintenance mode. This mode disconnects all clients
accessing the SSAS instances associated with the Virtual SSAS. The associated SSAS
service monitors also stop probing on the primary node.
NOTE:
If an instance on a backup node is also being used as a backup for a primary
instance associated with a different Virtual SSAS, that instance will no longer have
a backup. To minimize the time without a backup, we recommend that you perform
the maintenance on the backup instance first and then reenable the SSAS service
monitor for that instance. The backup instance will then be available for the other
primary instance.
To move a Virtual SSAS to maintenance mode, select the Virtual SSAS on the
PolyServe Management Console, right-click, and select Maintain.
When you have completed the maintenance activities, you can return the Virtual
SSAS to operation mode. Select the VSSAS on the PolyServe Management Console,
right-click, and select Operate.
To place a VSSAS in maintenance mode from the command line, use this command:
mx vssas maintain <vssas>
To return the Virtual SQL Server to operation mode, use this command:
mx vssas operate <vssas>
Configure SQL Server Analysis Services110