Upgrading a Multiple-Server Installation
Technical Note 2191
Last Reviewed 02-Aug-2007
Applies to:
Mobility XE server 6.00 and higher
Printer-friendly version
Summary
For a server pool with more than one Mobility XE server, it's possible to upgrade your servers without having any client downtime. Follow the steps below to upgrade all of the servers in your pool incrementally. Additional upgrade information is covered in Tech Note 2206 and Tech Note 2147.
You'll be upgrading just the Mobility server software, not the Mobility warehouse. We strongly recommend backing up your servers and/or settings before you upgrade; see Tech Note 2129 for details.
Take one Mobility server offline (in the Mobility Console —> Server Status page) a day or so in advance of when you want to upgrade it. Current client connections on that server will not be disrupted, but new clients will not be allowed to connect. Over the course of a day or so, as clients disconnect and reconnect, they should all migrate over to the other server(s). It doesn't matter if this is the server hosting the primary or standby warehouse—you can upgrade them in any order.
When a minimal number of clients are still connected to the offline server, upgrade Mobility server software on that machine. This will require a reboot, which will disconnect any clients remaining on that machine. At this point they should fail over to another server.
Bring the upgraded server back online.
Repeat this process for the other Mobility server(s) in your pool.
Related Information
2206
|
Upgrading From Mobility XE Version 6.x or 7.x to 7.21
|
2147
|
Upgrading From Mobility XE Version 6.x to 6.7
|
2167
|
Upgrading From Mobility XE Version 4.0/5.0 to 6.7
|
2129
|
Backing Up the Mobility XE Warehouse Settings
|
9979
|
NetMotion Mobility Technical Notes
|
Please comment on this technical note.