Upgrade to CMS 5 R1 SP3 on a load balanced webbsite



I want to upgrade a webbsite to CMS 5 R1 SP3 because we have problems with the load balancing that is solved in that version. The webbsite is now running on version 5.1.422.256.

I know how to make the upgrade in CMS Manager BUT I can´t find any information about how the upgrade will affect the webbsite and the visitors during the upgrade!

We are running the webbsite on two load balanced servers, and my question is:

Can/should I do the upgrade when the webbsite is "on-line"  for visitors/editors?

If so, what happens if a take one of the servers "off-line" and make the upgrade? Will the other one still work or is there anything in the database that make it stop working?

A workflow of how an upgrade should be done - needed backups, closing and so on - wouldn´t be wrong.

And what happens if something goes wrong? What back-out plan should I have.

Anyone having done this before?

Nov 05, 2008 17:30

I would do like this.

  1. Get the SQL scripts for the database upgrade. (that the manager uses)
  2. Get an backup of the database.
  3. Get an copy of all websitecode.
  4. Put it up running on an other server. (still keep an backup)
  5. Make the uppgrade on your new server.
  6. Check that everything is working.
  7. Run the sql scripts on the live server database.
  8. Copy your uppgraded websitecode to your live servers.
  9. Check that everything is working again.


Nov 06, 2008 8:36

Normally whe first upgrade in a staging/test environment to see that everything works, then we run the installer on the live machines (with backups of course).

You'll get some downtime when the installer runs but you can add a app_offline.htm file to display a friendly message to the users.

Another more complex approach to get zero downtime would be (I still recommend testing on a staging/test site first and to have backups).

1. Create a copy of the database
1. Bring site #1 offline
2. Point #1 to the copied database
3. Make sure it works and bring it online again
4. Take #2 offline from the load balancer
5. Upgrade #2
6. If everything works bring #2 online
7. Bring #1 offline
8. Point #1 to the new database (you can do it either before or after the upgrade)
9. Run the upgrade
10. If #1 also works bring it online

Note! Information entered during the upgrade will be lost. I haven't tested this approach myself but it should work perfectly fine.

Nov 06, 2008 10:17
This thread is locked and should be used for reference only.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.