This page details the steps needed to upgrade the Redgate Clone using Admin Console.

Contents

How are updates managed?

You can manually check for updates & update Redgate clone using Admin Console. These actions can be controlled via Version history tab.

Updates

There are two main types of updates at present: Regular and Rebuild (clean slate).

Regular update

This update type applies on top of your existing cluster and doesn't require any external changes.

It basically behaves like a normal desktop software update where the old version is replaced automatically by the new one and conducted completely from within Admin Console.

Steps

1. Access the Admin Console as explained in the Admin Console page.
2. Go either to the Dashboard or to the Version History tab.
3. Click Check for update to manually check for new versions of the application (preflight checks will be automatically triggered).
   1. 
   2. OPTIONAL You can compare the changes between them by clicking View diff in bottom left corner of the upgraded version.
      1. 
   3. OPTIONAL You can check what's new in the release notes for the application by clicking the Release notes link next to the upgraded version in the version history list in Admin Console.
      1. 
4. Once a new version is displayed, click Deploy next to the target version (after the preflight checks complete).
   1. 
5. Go to the dashboard of the Admin Console and wait for the Application Status to change to Ready.
   1.  
   2. NOTE: For more details about application status see Admin Console.
   3. NOTE2: If the update comes with new configuration changes (listed in the release notes), you'll additionally need to:
      • Go to the Config tab in the Admin Console dashboard.
      • Make the necessary changes.
      • Hit the Save Config button.
      • Click Go to updated version in the pop-up window.
      • Deploy the new config change version that is applied by clicking the Deploy button.
6. Download the new version of the rgclone CLI utility to all the machines requiring access to the cluster.
   1. NOTE: Some updates might not affect the Using the CLI directly, but it's advisable to upgrade it nevertheless as part of the normal update process to prevent client-side problems.

Rebuild (clean slate) update

As the name implies, this is basically equivalent to a new deployment where the existing cluster needs to be destroyed before applying the update. This means that you'll need to reconfigure the cluster and re-create any required data images and data containers.

This results from breaking changes that are incompatible with the previous cluster infrastructure. Failure to destroy the cluster beforehand will lead to unpredictable and incorrect behaviour.

Steps

This requires:

1. Release and clean the attached storage volumes.
2. Destroy the VM(s) hosting the cluster.
3. Reconstruct the cluster following the Installation steps instructions.