Now that your environment meets the technical requirements for Redgate Clone, you are ready to install. This page will guide you through the process.

Contents

Installation

The installation instructions below are tailored to a single node.

1. Make sure you have a machine ready based on the prerequisites above. You can check this manually by following our documentation or run a prerequisites check script with the following command:

   curl -sSL https://rd.gt/3RL6ioU | sudo bash

2. Create a new Kubernetes cluster with Redgate Clone by running the following command in the VM:

   curl -sSL https://k8s.kurl.sh/cloning-capability-app | sudo bash

   1. When asked about disabling swap to continue, press ‘Y’

   2. Store the temporary password generated by the installer for usage in Admin Console access below. For example:

      1. 

   3. If you get errors during host preflight checks, retry the above command using the flag host-preflight-ignore or exclude-builtin-host-preflights flag:

      # This will transform errors into warnings
      curl -sSL https://k8s.kurl.sh/cloning-capability-app | sudo bash -s host-preflight-ignore
      
      # This will bypass host preflights completely (should only be used as last resort)
      curl -sSL https://k8s.kurl.sh/cloning-capability-app | sudo bash -s exclude-builtin-host-preflights

   4. Once completed, reload the bash using:

      bash -l

3. Check that you can access the Kubernetes cluster on the VM through kubectl:
   1. Running kubectl get pods should return a short list of pods. 

   2. If you get an error like: error loading config file "/etc/kubernetes/admin.conf": open /etc/kubernetes/admin.conf: permission denied you should unset the KUBECONFIG  file by running the following command:

      echo unset KUBECONFIG >> ~/.bash_profile
      bash -l

4. Finish configuring the cluster by running kubectl commands:

   kubectl label nodes redgate.com/infrastructure-node=true --overwrite --all
   kubectl label nodes redgate.com/cloning-node=true --overwrite --all
   kubectl label nodes redgate.com/cloning-mssql-node=true --overwrite --all
   kubectl label nodes redgate.com/cloning-oracle-node=true --overwrite --all

5. Gather access details to various web-based elements in the application from the previous script's output:
   1. Take hold of the access details to Admin Console (if you forget in the future, you can change the password).
      • 
6. RECOMMENDED k9s is a great helper tool to debug issues directly in the machine hosting the cluster. It's likely we'll ask you to install it if we run a debug session together, so we recommend you get it setup as soon a possible:

   curl -sS https://webinstall.dev/k9s | bash

7. Go to Admin Console web UI (http://<IPv4 address>:8800) and proceed with the installation.
   
   • You will need to provide the password. 
   • You will need to provide the application license file (see requirements). Failure to do so halts the installation.
   • You will need to setup Admin Console TLS to enforce secure connections.
   • You should configure data storage according to your needs.
   • A file share is needed if you want to be able to create data images and data containers from database backups.
8. Wait until the application is ready. For more information about managing the application see Admin Console.
   1. If the application does not become ready within 20 minutes, see this troubleshooting guide.
9. Start using the application by downloading the rgclone CLI utility. 

Further Configuration

Adding storage disks

Please see instructions on how to add more disks.

Where to next?

You are now in a position to start using the application by downloading the rgclone CLI utility.

For example, you can start by creating data images from SQL Server 2019 backups and data containers.

Before going any further, you might want to familiarise yourself with some of our concepts and check which database engines are supported.

Then, please head over to the CLI Reference guide and to our series of CLI How To for instructions on how to use our command-line tool rgclone to interact with the web API in the Kubernetes cluster.

We also recommend the following:

• Ensuring nodes shutdown gracefully. 
• Creating an admin user for Redgate Clone.
• Monitor your cluster with notifications on critical alerts.