HP PolyServe Software - Manual (Page 6)

• Matrix Server must be installed and running on all nodes in the cluster.
• HP PolyServe Software for Microsoft SQL Server must be installed on all cluster
nodes that might host the SQL Server instance.
• The Microsoft SQL Server instance must be installed as described in the HP Poly-
Serve Software for Microsoft SQL Server Administration Guide.
Migration scenarios
The following scenarios are supported for migrating a stand-alone, non-virtualized
SQL Server instance into a Matrix Server cluster, making the instance highly available.
The scenarios assume that Matrix Server, HP PolyServe Software for Microsoft SQL
Server, and the SQL Server instance are installed on the target node. In the “New
Matrix” scenarios, the SQL Server instance is virtualized on the target node during
the migration procedure. In the “Existing Matrix” scenario, the SQL Server instance
is virtualized on the target node before starting the migration procedure.
A SQL 2000 or 2005 instance can be migrated to SQL 2005 or SQL 2008. A SQL
2008 instance can be migrated only to SQL 2008.
The supported migration scenarios are:
• Migrate to a new matrix. The SQL Server instance on the source node and the
Virtual SQL Server on the target node will use different hostnames and IP ad-
dresses.
• Migrate to a new matrix. The SQL Server instance on the source node and the
Virtual SQL Server on the target node will use the same hostname and IP address.
• Migrate to an existing matrix. The SQL Server instance on the source node and
the Virtual SQL Server on the target node will use different hostnames and IP ad-
dresses.
Migrate to a new matrix, using different hostnames/IPs
In this scenario, Matrix Server, HP PolyServe Software for Microsoft SQL Server, and
the SQL Server instance are installed on the target node. The SQL Server instance
has not yet been virtualized with HP PolyServe Software for Microsoft SQL Server.
After the target SQL Server instance is virtualized during the procedure, the source
SQL Server and the target Virtual SQL Server will have unique host names and IPs
and can be running side-by-side.
Complete the following steps:
1. Start MxMigrate.
Introduction 6