Upgrade Guide

From: SVN MultiSite Plus 1.2 Build: 6903 to later

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. Check which version you're running.

Before you upgrade

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

Recheck the deployment checklist.

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.

Back up existing Apache config files - Once the upgrade is completed you should verify that it hasn't made Apache configuration changes that will adversely affect your operation.
You shouldn't make any system changes like adding new repositories until the upgrade has been completed.

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 upgrading from 1.2. or earlier.

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.

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'

alias curl='curl -f -k -u $USERNAME:$PASSWORD'

This will work around the problem. The problem will be fixed in the next release.

Open a terminal window and login to the server.

Get the latest installer file and make sure it is executable:
```
chmod a+x svn-multisite-plus.sh
    
```

Run the installer:

./svn-multisite-plus.sh
Verifying archive integrity... All good.
Uncompressing WANdisco SVN MultiSite Plus........................
Running in non-interactive mode, installing with user 'wandisco' and group 'wandisco'. Output will be logged
to the daemon.info syslog facility

Please enter the username of an administrative user: admin
Please enter password for the 'admin' administrative user:xxxxxxxxxx

This process must be run on ALL nodes individually, in sequence. NOT AT THE SAME TIME
If this is the first node we will use this node to co-ordinate the upgrade.
Is this the first node? y/N: y

Stopping ui:..[  OK  ]
Stopping replicator:..[  OK  ]

Backup process logged at /opt/wandisco/svn-multisite-plus/logs/backup.log

Version 1.2.2-SNAPSHOT Build: 29412 backup found in /opt/wandisco/svn-multisite-plus/replicator/database
/backup/2014-06-17T16:58:54Z_DConE_Backup

......................................

Transformation complete
Jun 17, 2014 4:59:22 PM com.wandisco.fsfs.backup.FsfsRestore main
INFO: main:[About to restore database from /opt/wandisco/svn-multisite-plus/replicator/database/
backup/2014-06-17T16:58:54Z_DConE_Backup to /opt/wandisco/svn-multisite-plus/replicator/database]



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  ]

Backup process logged at /opt/wandisco/svn-multisite-plus/logs/backup.log

Version 1.2.2-SNAPSHOT Build: 29412 backup found in
/opt/wandisco/svn-multisite-plus/replicator/database/backup/2014-06-17T16:58:54Z_DConE_Backup
......................................

Transformation complete
Jun 17, 2014 4:59:22 PM com.wandisco.fsfs.backup.FsfsRestore main
INFO: main:[About to restore database from /opt/wandisco/svn-multisite-plus/replicator/
database/backup/2014-06-17T16:58:54Z_DConE_Backup to /opt/wandisco/svn-multisite-plus/replicator/database]
Jun 17, 2014 4:59:22 PM com.wandisco.database.prevayler.DatabaseInstance createLocation
INFO: main:[Writing to database location /opt/wandisco/svn-multisite-plus/replicator/database]
Jun 17, 2014 4:59:22 PM com.wandisco.database.prevayler.Manager create

So the installer brings your nodes to a stop, then backs up the application data (repository data is not touched).

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.

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.

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.
Before you begin - IMPORTANT
Restart nodes ONLY after all nodes have been successfully upgraded.

SVN MultiSite Plus
Last doc build: 17:59am - Tuesday 15th January 2014