Upgrading Subversion Stand-alone Access Control

Use these instructions to upgrade your Subversion Access Control to a later build or version, rather than those found in The Deployment Guide: 2.2 Installation Procedure section, which are intended for a first time installation.

The correct method for upgrading Subversion Stand-alone Access Control depends on which versions you are moving between. Use the guide below to ensure that you upgrade with the right method.

Upgrading from Subversion Stand-alone Access Control 3.6 or earlier - See our Knowledge base articles on Upgrade Access Control 3.6.0.x to 3.6.0.y

tip"Upgrade rule of thumb

When looking to upgrade Stand-alone Access Control, apply the following rule:

Upgrading within a version, e.g. 4.0 build x --> 4.0 build y , use the Upgrade with Script

Upgrading between 'point' versions. e.g. 4.0 --> 4.2 will require you to Upgrade from backup

Upgrade from backup

Use this procedure if you are upgrading between versions rather than builds (4.0 to 4.2 rather than 4.2 build x to 4.2 build y etc).
To upgrade between builds, see Upgrade with script.

Running SVN Stand-alone Access Control 4.0 Build 1895 or later

You're running a build that is up-to-date enough to be able to upgrade directly to version 4.2. Proceed to Upgrade to 4.2.

Running SVN Stand-alone Access Control 4.0 Build 1254 or earlier

You're running a build that can't upgrade directly to 4.2. Before you can continue you need to contact WANdisco and get SVN Stand-alone Access Control 4.0 Build: 3937.

Use the upgrade from script method to first upgrade to the latest version of 4.0. You'll need to contact WANdisco about getting the latest 4.0 build.

Upgrading from backup requires that Stand-alone Access Control be installed from scratch. First you export your user settings so they can be imported into the new version.

tip"Installing in order to perform an upgrade using the backup files?
Don't enable Authz during the installation - wait until the import is completed, then enable Authz from the Subversion Settings screen.
Enabling Authz during the installation can greatly impact the performance of the backup file import.

1. Shutdown Access Control

2. Backup your settings from the Admin Console

3. Create a backup in case you need to back out of the upgrade

4. Extract and run the setup file

5. Complete the upgrade through a browser.

6. Import your saved settings

So you backed up your data, installed the latest version Access Control, it's now time to import your backed up data.

Use this procedure to restore user information, although any system settings will need to be manually applied

Upgrade from Script

Use this procedure to upgrade to a later build (e.g. version 4.0 build x to version 4.0 build y). If you are upgrading to a different version (e.g. 4.0 to 4.2 then see Upgrade from Backup)

7. Before you begin

Things you must know before you make a start:

8. Upgrade steps

9. Create a backup in case a rollback is required

10. Run the upgrader script

** Alert! ** Benefits of the upgrade script
The upgrade script gets your working installation up-to-date without losing any settings.
Unlike setting up a fresh installation (and importing access control settings, LDAP authorities are retained and previous LDAP users and teams are retained, although admin user becomes an LDAP account.

** Alert! ** Alert
Don't forget to remove your temporary installation before restarting your upgraded proxy.

Using the Upgrader script

You can read more about how to use the upgrader script by running it with the -help flag.

$ java -jar svnsec.jar -help

** Alert! ** Alert
Valid parameters are:

-dprefs show dynamic preferences.
-nodes show node information.
-upgrade <path> upgrade an existing installation at the specified path.
-upgradeNoConfirm <path> upgrade an existing installation at the specified path WITHOUT PROMPTING FOR CONFIRMATION.
-help | -h show help