Upgrade Guide

From: SVN MultiSite Plus Build: 5435 to 5778 (prior to 6903)

This guide runs through the procedure to upgrade to the latest version of SVN MultiSite Plus from build 5041 or earlier.

Before you upgrade

Prior to starting an upgrade you should first complete the steps outlined below:

stop All repositories must have unique names
It has previously been possible to give separate repositories the same name. While doing so would not cause a problem for the replication engine it could obviously lead to confusion and serious user error. As a result we've added logic to ensure that the use of duplicate repository names is no longer allowed.

Important: Before upgrading you should check your existing repositories and ensure that there are no duplicate names.
If necessary you should take steps to rename any existing repositories that currently share a name.
stop Notifications are lost after an upgrade
The email notification system has not yet been incorporated into the upgrade process. Performing an upgrade will remove any notifications that you have setup on your system. To restore your notication settings you'll either need to re-enter them after completing the upgrade or use the following procedure before starting an upgrade Backup and Restore Notification Settings

These steps are only required if you are upgrading to version 1.2.1 from version 1.2.0 or earlier.
stop Upgrading From SVN MultiSite Plus 1.2.1 Build::
For Red Hat Enterprise Linux (RHEL 6) deployments that are moving from version 1.0 Build 5778 or earlier to the latest version (1.2): You should first complete the following procedure for an upgrade to version 1.0 Build 6383). Once you have verified the upgrade was successful, only then should you repeat the upgrade with the 1.2 files. If you have any questions or concerns contact WANdisco's support team.

stop Before you begin - IMPORTANT
Run these instructions on each node one at a time -- don't attempt to run them simultaneously. The process would still complete successfully, although you are likely to see pending transactions that won't ever complete.

Although you can update to the latest version of SVN MultiSite Plus by completing a fresh installation (using the installation guide), you would need to recreate your configuration in terms of node, repository and replication group settings. This upgrade procedure offers a method for upgrading while keeping your established setup.

Overview

There are a number of different upgrade procedures, you need to make sure that you use the one that matches your current installed version of SVN MultiSite Plus.

Roll-back

In the unlikely even that the upgrade leaves you in a state where you need to return to your orginal setup, see the Roll-back procedure at the end of this document




stop SSL Upgrades - IMPORTANT
SSL upgrades from build 5435 will fail with the error:
"Unable to determine application version numbers, curl returned 60", Issue NV-2273.
There is a simple workaround: Open the backup script at svn-multisite-plus/bin/backup Modify line 27 by adding a -k after the -f, i.e. from
alias curl='curl -f -u $USERNAME:$PASSWORD'
to
alias curl='curl -f -k -u $USERNAME:$PASSWORD'
This will work around the problem. The problem will be fixed in the next release.

Upgrades Procedure

  1. Open a terminal window and login to the server.

  2. Get the latest installer file and make sure it is executable:
    chmod a+x svn-multisite-plus.sh
        
  3. Run the installer:
        ./svn-multisite-plus.sh
    Verifying archive integrity... All good.
    Uncompressing WANdisco SVN MultiSite Plus.............
        ::   ::  ::     #     #   ##    ####  ######   #   #####   #####   #####
       :::: :::: :::    #     #  #  #  ##  ## #     #  #  #     # #     # #     #
      ::::::::::: :::   #  #  # #    # #    # #     #  #  #       #       #     #
     ::::::::::::: :::  # # # # #    # #    # #     #  #   #####  #       #     #
      ::::::::::: :::   # # # # #    # #    # #     #  #        # #       #     #
       :::: :::: :::    ##   ##  #  ## #    # #     #  #  #     # #     # #     #
        ::   ::  ::     #     #   ## # #    # ######   #   #####   #####   #####
    
    Checking SVN
    SVN version 1.7.9-2 is already installed, will not install SVN
    
    
    Beginning WANdisco SVN MultiSite Plus Installation...
    Attempting to run backup on existing install of SVN MultiSite Plus...
    As SVN MultiSite Plus is already installed and running, the installer will determine that you wish to perform an upgrade instead of an initial installation:
    SVN MultiSite Plus Pre-Upgrade Backup Script
    
    Please enter password for the 'admin' administrative user:
    
    Enter the SVN MultiSite Plus admin credentials:
    Initiating synchronised stop...
    Node has achieved synchronised stop
    Initiating database dump...
    Database dump complete
    Stopping ui:.                                              [  OK  ]
    Stopping replicator:.                                      [  OK  ]
    Performing backup...
    Backup has been stored in /opt/wandisco/svn-multisite-plus/var/backups
    
    Starting ui:[  OK  ]
    Starting replicator:[  OK  ]
    
    
    So the installer brings your nodes to a stop, then backs up the application data (repository data is not touched).
  4. stop If the synchronized stop failed in the previous step:

    • Ensure that no corresponding repositories are stuck in Local Read-only mode.
    • Ensure that there's at least one defined replication group on the nodes -- a requirement for a synchronized stop.
    • Reset all nodes to clean out any pending proposals then retrying the upgrade.

  5. With the local replicator restarted, login to the admin UI, click on the Settings tab. You can confirm that SVN MultiSite Plus has been updated by looking at the Module versions.

  6. When each node has been updated (one at a time), navigate to the Nodes tab on the admin UI and wake up the nodes. You can do this on each individual node in turn or you can use the Start All button - 14. Starting nodes.
    stop Before you begin - IMPORTANT
    Restart nodes ONLY after all nodes have been successfully upgraded.