3.4.0 Matrix Server Upgrade Guide

Chapter 3: Non-Rolling Upgrades 16

• A Virtual SQL 2005 instance cannot be a backup for a Virtual SQL 2000

instance having the same name (and vice versa). A Virtual SQL

Instance and all of its backups must be running the same version of

SQL Server.

DNS Requirement for Virtual SQL Servers

MxDB for SQL Server 3.4.x requires that DNS be configured; using local

host files is not supported. A DNS entry must exist for each Virtual SQL

Server/IP address. The entry must include an A record and a [PTR] record

for forward and reverse lookup. Windows authentication may fail if these

records do not exist. Matrix Server can add the A record when it creates

the Virtual SQL Server; however, you will need to add the [PTR] record

manually.

Upgrade Procedures

There are two procedures:

• Upgrade Matrix Server and reinstall the operating system. See page

16.

• Upgrade Matrix Server without reinstalling the operating system. See

page 21.

Upgrade Matrix Server and Reinstall the OS

To minimize overall downtime, divide your servers into two groups and

then upgrade one group at a time while the other group runs the matrix.

The upgrade procedure assumes that the servers are divided into group

A and group B.

To perform the upgrade, complete the following steps.

NOTE: Upgrade the server with the highest IP address first. Then

continue to upgrade the servers in descending order of IP address,

with the lowest numbered server being upgraded last.

1. If MxDB for SQL Server 3.2.1 hotfix 1 is installed on the servers in the

matrix, you will need to back out references to the SetvSQL.wsf script

provided with the hotfix. Complete the following steps for each

Virtual SQL Instance configured in the matrix.