3.4.0 Matrix Server Upgrade Guide

Chapter 2: Rolling Upgrades 5

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.

Rolling Upgrade Procedures

The rolling upgrade procedure does not require any matrix downtime.

Each server is removed from the matrix, upgraded, and then returned to

the matrix.

There are two procedures:

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

• Upgrade Matrix Server without reinstalling the operating system. See

page 9.

Rolling Upgrade Considerations

You should be aware of the following when upgrading Matrix Server to

the 3.4.0 release:

• Servers can be upgraded one-at-a-time during the rolling upgrade.

The server with the numerically highest primary IP address must be

upgraded first. Then continue to upgrade the servers in descending

order of IP address, with the server with the lowest primary IP

address being upgraded last.

• During the rolling upgrade, the matrix will include a mix of servers

running 3.4.0 and the older version. Although Matrix Server supports

this mix of versions during the rolling upgrade, on-going operation of

a mixed-version cluster is not supported. All servers should be

upgraded to 3.4.0 as quickly as possible.

• Maintenance operations performed via MxDB for SQL Server are not

supported while the matrix includes a mix of 3.4.0 and 3.2.1/2.7.2