Although you can update to the latest version of SVN MultiSite Plus by completing a fresh installation (following the Installation Guide), you would need to recreate your configuration for node, repository and replication group settings. This upgrade procedure describes how to upgrade and keep most of your existing configuration.
1. From SVN MultiSite Plus 1.2 Build: 6903 to later
1.1 Before you upgrade
Before starting an upgrade:
- Recheck the deployment checklist.
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: When 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.
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.
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 from build 5435 fails 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 works around the problem. The problem will be fixed in the next release.
- Open a terminal window and log in 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 determines 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 createThe installer stops your nodes, then backs up the application data (repository data is not touched).
- 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, which is required for a synchronized stop.
- Reset all nodes to clean out any pending proposals then retrying the upgrade.
- With the local replicator restarted, log in 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. Also note that the EULA screen only responds to an acceptance when all nodes are up and available.
The version number of each SVN MultiSite Plus component is tracked. You need to know the svn-ms-replicator version which is:
2. Migration from SVN MultiSite 4.2
This section gives important information if you're upgrading from an earlier version of SVN MultiSite.
2.1 Replica consistency
Summary: SVN MultiSite Plus uses a stronger definition of "identical"
SVN MultiSite 4.x and earlier versions require that repository replicas are "identical", in that all replica contain identical revisions. SVN MultiSite Plus uses a stronger definition of "identical" in that the repositories must now be byte-for-byte the same (identical in terms of properties, time-stamps, etc).
A migration from SVN MultiSite to SVN MultiSite Plus therefore requires that you ditch all but one copy of each repository. This remaining copy becomes your "master" and must be copied to each applicable node. This ensures that you start from the position where replica are identical.
2.2 Migration strategy
- Repostories are migrated one at a time.
- There is less risk
- This is the preferred approach if installing on existing servers.
- May not be able to preserve the repository URL.
- All repositories are migrated in a single operation.
- "all your eggs in one basket" risk.
- The preferred approach when installing onto new servers.
- Biggest obstical is managing the migration of repository data.
2.3 Copying strategy
In production, repositories can be extremely large, so large that making copies of them can be challenging. There are a number of strategies you can use to manage the distribution of
Strategy 1: Make a physical copy of each repository for real-world trasit. This option makes most sense when the scale of repository data is so great that a WAN network transfer is not practical (e.g. copying Terrabytes of repository data over a low/moderate bandwith connection).
Strategy 2: Full rsync (without checksum). This option is a direct solution that works best if you have the opportunity to copy all repository data during a maintenance window. You won't be able to continue commiting changes to the original repositories once done.
Strategy 3: Incremental rsync (with checksuming). This option takes a copy of the repository from each location's local server, and then uses an incremental rsync with checksums to make the new copy identical to the master copy. The best way to accomplish this is to mount the storage of the MultiSite 4.2 node in read-only mode on the MultiSite Plus service, then copy the data to the real location on the MultiSiet Plus node.
2.4 Periodic incremental synchronization
This approach updates MultiSite Plus copies of the repository with the commits made since the last rysnc. Note that the following steps will update the MultiSite Plus copies of the repositories with the commits made since the last rsync. However, these repositories are not guaranteed to be correct. The next section explains how to finalise the repository synchronization before it can be replicated by MSP.
2.5. Finalize the copy
To guarantee a correct repository, you need to run a final incremental rsync after the repository has been made read-only.