Octopus Deploy Documentation

Manual Upgrade

Last updated

You can upgrade from Octopus 2.6.5 to Octopus 2018.10 LTS by downloading the latest MSI's for both Octopus and Tentacle, and installing them manually. If you're working with a large number of Tentacles, see the section on upgrading larger installations.

Summary

  1. Backup your Octopus 2.6.5 database and master key.
  2. Install Octopus 2018.10 LTS on your Octopus Server.
  3. Migrate your data from Octopus 2.6.5 to Octopus 2018.10 LTS.
  4. Install the latest version of Tentacle on your deployment targets.
  5. Verify the connectivity between the Octopus 2018.10 LTS Server and your Tentacles.
  6. [Optional] Clean up your Octopus Home folder, follow the instructions on this page.

Step by Step

To perform an in-place upgrade, follow these steps:

1. Back up Your Octopus 2.6.5 Database and Master Key

See the Backup and restore page for instructions on backing up your database.

2. Install Octopus 2018.10 LTS On Your Octopus Server

Upgrade to the latest version
When upgrading to Octopus 2018.10 LTS please use the latest version available. We have been constantly improving the Octopus 2.6.5 to Octopus 2018.10 LTS data migration process whilst adding new features and fixing bugs.

See the Installing Octopus 2018.10 LTS page for instructions on installing a new Octopus 2018.10 LTS instance.

After installing the MSI, you will be presented with an upgrade page.

Click "Get started..." and set up your database connection. You may need to grant permission to the NT AUTHORITY\SYSTEM account at this stage.

Click Next, and then Install to install the Octopus 2018.10 LTS server over the Octopus 2.6.5 instance.

3. Restore the Octopus 2.6.5 Database Using the Migration Tool

After upgrading, the Octopus Manager will prompt to import your Octopus 2.6.5 database. Click the "Import data..." button and follow the prompts to import your Octopus 2.6.5 data.

See the Migrating data from Octopus 2.6.5 to 2018.10 LTS page for more detailed instructions on importing your Octopus 2.6.5 database backup into Octopus 2018.10 LTS.

Migration taking a long time?
By default we migrate everything from your backup including historical data. You can use the maxage= argument when executing the migrator to limit the number of days to keep. For example: maxage=90 will keep 90 days of historical data ignoring anything older.

To see the command syntax click the Show script link in the wizard

Using the built-in Octopus NuGet repository?
If you use the built-in Octopus NuGet repository you will need to move the files from your Octopus 2.6.5 server to your Octopus 2018.10 LTS server. They are not part of the backup. In a standard Octopus 2.6.5 install the files can be found under C:\Octopus\OctopusServer\Repository\Packages You will need to transfer them to the new server to C:\Octopus\Packages. Once the files have been copied, go to Library ➜ Packages ➜ Package Indexing and click the RE-INDEX NOW button. This process runs in the background, so if you have a lot of packages it could take a while (5-20 mins) to show in the UI or be usable for deployments.

4. Install the Latest Tentacle MSI

At this point, the machines should appear in your Environments page inside Octopus 2018.10 LTS, but a health check will fail - the communication protocol used by modern Octopus Servers isn't compatible with Tentacle 2.6.

On each machine that ran Tentacle 2.6, connect to the machine, and install the latest Tentacle MSI.

5. Verify Connectivity Between the 2018.10 LTS Server and Your Tentacles

Log in to your new Octopus 2018.10 LTS server and run health checks on all of your environments. If the upgrade completed successfully, they should succeed.

If one or more health checks do not succeed after a few attempts, see the Troubleshooting section to identify possible issues.

Welcome! We use cookies and data about how you use our website allow us to improve the website and your experience, and resolve technical errors. Our website uses cookies and shares some of your data with third party analytics companies for these purposes.

If you decline, we will respect your privacy. A single cookie will be used in your browser to remember your preference.