Upgrading Guide

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Tue May 19, 2009 1:43 pm
This guide can also be used for VaultPro/Fortress upgrades.

  1. Always perform a backup of the sgvault database before starting.
      - If you are on Vault 4.x or later, backup both the sgvault and sgmaster databases before starting.
      - If you are on Fortress or Vault Pro, you will backup sgvault, sgmaster, and sgdragnet.
      - If you are on Vault 6.0 or later, you will backup sgvault, sgmaster, sgindex, sgnotify. If you are using Vault Pro, you will also backup sgdragnet.

  2. If you are upgrading to a new full release, you will need upgraded license keys. Maintenance releases, such as going from Vault 6.0 to Vault 6.1 are usually free upgrades.

    For instance, if you are on Vault 4.x, then you will need upgraded license keys for the latest version of Vault. If your Vault Maintenance is current, new license keys may be free. Contact our Sales Department (contact info) if you have any questions on licensing or cost of upgrades.


  3. Check the release notes for additional information. Those are located in our KB Article Index http://support.sourcegear.com/viewtopic.php?t=792.. Known issues are documented there as well. The release notes are located towards the bottom of that Index.


  4. Check the compatibility chart to insure that the software you use with Vault is compatible: http://www.sourcegear.com/vault/documen ... chart.html.
  5. If you need to move to a different server at the same time, then review this article on moving during an upgrade: http://support.sourcegear.com/viewtopic ... 13&t=22663.


  6. If you are more than one major release behind, then we recommend upgrading in increments (except in certain cases listed below), using the last version of each major release and certain intermediate releases. Previous releases are available on our downloads pages. If you are only one release behind, such as Vault 9.x and going to Vault 10.x, you only need to install the last version of Vault 10.x.

    Previous Vault Standard Downloads: http://www.sourcegear.com/vault/downloa ... ltstandard
    Previous Vault Professional Downloads: http://www.sourcegear.com/vault/downloa ... ofessional.

    You may want to try the upgrade on a test machine (this could be a workstation) before you upgrade your production machine to see if you run into any issues.

    1. Current Release: http://www.sourcegear.com/vault/downloads.html
    2. Previous Releases: http://www.sourcegear.com/vault/downloads2.html
    During an upgrade, the installers run fixes for known database issues. By upgrading in increments, there’s less work for the installer to do in each stage of the upgrade. Some versions can be skipped over.

    We recommend upgrading in stages with these releases:
      - 2.0.6
      - 3.0.7
      - 3.1.9
      - 3.5.3
      - 4.0.6
      - 4.1.4
      - 5.0.4
      - 5.1.2
      - 6.1
      - 7.2.1 (not needed if going to Vault 10.x)
      - 8.0.1 (not needed if going to Vault 10.x)
      - 9.1.0 (not needed if going to Vault 10.x)
      - 10.0.0 (or the latest Vault release)
    If you are upgrading Fortress, you will go in this order:
      - 1.0.6
      - 1.1.4
      - 2.0.4 (uninstall Fortress to go to Vault Pro)
      - Vault Pro 5.1.2
      - Vault Pro 6.1
      - Vault Pro 7.2.1 (not needed if going to Vault Pro 10.x)
      - Vault Pro 8.0.1 (not needed if going to Vault Pro 10.x)
      - Vault Pro 9.1.0 (not needed if going to Vault Pro 10.x)
      - Vault Pro 10.0.0 (or the latest Vault Pro release)
    Start the upgrade from the final minor release number for the version you are on. For example, if you are on 3.1.7, upgrade to 3.1.9 and then 3.5.3, 4.0.6, 4.1.4, 5.0.4, 5.1.x, 6.1, and then you can make the leap to 10.x.

    If you are upgrading from very far back, then you may want to add in an additional backup somewhere in the middle to prevent having to reinstall all old versions in case of failure.

      NOTE ON VAULT 10: Vault 10 has been tested in upgrades from Vault 6 - 9. If you are on at a minimum of Vault 6, then you can just install Vault 10 without additional installs.

      NOTE ON VAULT 4.0.6: There was a bug in the uninstall routine for the 4.0.6 if you install the server and the client together using the server's installer. Upgrading will succeed, but leave two client shortcuts on the desktop. Please follow the instructions at support.sourcegear.com/viewtopic.php?t=9653 for instructions on removing the 4.0.6 server and client before upgrading to 4.1.4.
  7. When you are upgrading, make sure you have the following:
    - Previous Admin Password
    - Admin level rights to the SQL Server.
    - Knowledge of the installation options that were chosen previously (Document this somewhere when you are installing or upgrading for future use.)
    1. More information can be found in our Install Guide.
    2. Those options are:
      1. IIS process model
      2. SQL server authentication mode (SQL authentication or Windows authentication).
    3. The options can also be found by looking at the vault_install.log from the previous install. It can be found etiher in C:\Documents and Settings\<user who did the install>\Local Settings\temp or in C:\Windows\temp. If you need assistance finding the options chosen before, send the vault_install.log to support at sourcegear.com
  8. Rules for the users:
    1. Users should not be connected to Vault during the upgrade.
    2. Users are not required to check in their changes, since checkouts are stored in the database, but it’s a good idea to do so. Or, users may wish to make a backup of their working folder so that if any problems are encountered, they won’t accidentally lose their changes.
    3. If you are upgrading through a number of versions, users may also need to reset their client-side cache after the upgrade. http://support.sourcegear.com/viewtopic ... 13&t=11513
    4. After the server is upgraded, users can download the latest client from your Vault server at http://<your Vault server>/vaultservice.
  9. Switching to Vault Professional:
    1. All the same information here also applies when upgrading Vault Professional.
    2. The Vault Standard version number must be at least no more than one major release behind the Vault Professional Version or the same version. For example, if you are currently on Vault Standard 4.1.4, you can upgrade to Vault Pro 5.1.2 without having to install Vault Standard 5.1.1 first. Or you can switch from Vault Standard 6.1 to Vault Professional 6.1.
    3. Uninstall Vault Standard or Fortress, but choose the option to save your databases. Then just run the Vault Professional .msi installer. It will find the previous databases and convert them to Vault Professional databases.
    4. The users should uninstall their Vault Standard Clients and then run the installer for the Vault Professional Client.
    5. You may keep the Vault Standard Client if you need to connect to a Vault Standard Server and Vault Professional Client will then just install separately.
  10. Upgrading when you have Shadow Folders:
    1. The .NET permissions change in some versions. In some cases, you may need to set permissions on your Shadow Folders to allow the VaultShadowFolderAppPool to have read/write access.
    2. If you would like to backup the entries you have for your shadow folders, you can backup the Vault Shadow Folder web.config found in vaultservice/vaultshadowfolder/web.config.
  11. Upgrading and moving at the same time:
    1. Use the following KB on moving during an upgrade: http://support.sourcegear.com/viewtopic ... 13&t=22663.
    2. If you are using Visual Studio integration, then the clients will need to go through the rebinding process: http://support.sourcegear.com/viewtopic ... 403#p68403.
Beth Kieler
SourceGear Technical Support

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 10 guests

cron