Management Console

Learn about using with Trilio for Kubernetes with the Management Console

To get started with Trilio via the management console in your environment, the following steps must be performed:

Prerequisites

Authenticate access to the Management Console (UI). Refer toUI Authentication.
Configure access to the Management Console (UI). Refer toConfiguring the UI.

Steps Overview

Install a compatible CSI Driver
Create a Backup Target - A location where backups will be stored.
Create a retention policy (Optional) - To specify how long to keep the backups for.
Run Example:
- Label Example
- Helm Example
- Operator Example
- Virtual Machine Example
- Namespace Example

Step 1: Install a CSI Driver

Skip this step if your environment already has a CSI driver installed with snapshot capability.

Trilio for Kubernetes requires a compatible Container Storage Interface (CSI) driver that provides the Snapshot feature.

You should check the to select a driver appropriate for your backend storage solution. See the selected CSI driver's documentation for details on the installation of the driver in your cluster.

Step 2: Create a Target

Create a secret containing the credentials for data stores to store backups. An example is provided below:

apiVersion: v1
kind: Secret
metadata:
  name: sample-secret
type: Opaque
stringData:
  accessKey: AKIAS5B35DGFSTY7T55D
  secretKey: xWBupfGvkgkhaH8ansJU1wRhFoGoWFPmhXD6/vVD

You can either create the secret using the above YAML definition or use the management console to create it as part of the workflow for creating the backup target.

Please use one of the provided in the Custom Resource Definition section as a template for creating an NFS, Amazon S3, or any S3-compatible storage target.

Supported values for S3 vendors include:

"AWS", "RedhatCeph", "Ceph", "IBMCleversafe", "Cloudian", "Scality", "NetApp", "Cohesity", "SwiftStack", "Wassabi", "MinIO", "DellEMC", "Other"

An Amazon S3 target example is provided below:

Note: With the above configuration, the target would get created in the current user namespace unless specified. Also, additional information on Bucket permissions can be found here: AWS S3 Target Permissions

Step 3: Create a Retention Policy (Optional)

While the example backup custom resources created by following this Getting Started page can be deleted manually via kubectl commands, Trilio also provides backup retention capability - to automatically delete the backups based on defined time boundaries.

A retention policy is referenced in the .

Note: With the above configuration, the policy would get created in the default namespace unless specified.

Step 4: Create a BackupPlan

This section focuses on creating a BackupPlan to define and manage application backups. A BackupPlan specifies which resources to back up, such as specific applications or namespaces, and can be configured using labels, Helm, Operators, or namespaces.

For more details on using Custom Resource Definitions (CRDs) with BackupPlans, refer to the

Step 4.1: Label Example

This section demonstrates creating a BackupPlan to back up a sample application using label-based selection.

The following steps will be performed.

1. Deploy a sample application

Deploy a sample application, such as MySQL, and assign unique, identifiable labels. These labels will appear under the "Labels" tab in the "Application" section. Refer to the guide for detailed instructions.

2. Create a Label-Based BackupPlan

Create a BackupPlan CR through the management console, specifying the MySQL application by selecting its labels from the UI in the same namespace where the application is deployed.

Step 4.2: Helm Example

This section outlines the steps to create a BackupPlan for a sample application deployed via Helm.

The following steps will be performed.

1. Deploy a Sample Application Using Helm

Deploy a sample Helm application, such as CockroachDB. Trilio will display installed Helm applications under the "Helm and Operators" tab in the "Application" section. Refer to the guide for detailed instructions.

2. Create a Helm-Based BackupPlan

Create a BackupPlan Custom Resource (CR) through the management console, specifying the Helm release of the CockroachDB application in the BackupPlan Helm section.

Ensure the name of the release you specify matches the output from the helm ls command in the previous step.

Step 4.3: Operator Example

This section provides steps for creating a BackupPlan for a sample ETCD operator application.

Steps to perform:

1. Install the Etcd Operator and deploy an Etcd cluster (refer to the "" and "" sections for detailed instructions)

Install the Etcd Operator and deploy an Etcd cluster. Trilio will display installed operator applications under the "Helm and Operators" tab in the "Application" section. Refer to the guide for detailed instructions.

2. Create a Operator-Based BackupPlan.

Create a BackupPlan resource to back up the etcd-operator and its clusters. Use the management console to select the etcd-operator, which is automatically discovered by T4K and listed under the Operator section.

Step 4.4: Virtual Machine Example

This section outlines the process of creating a BackupPlan for a sample Virtual Machine.

Steps to perform:

1. Deploy a Sample VirtualMachine

Deploy a sample Virtual Machine (VM) using the OpenShift Virtualization Operator. To learn about VM deployment, refer to the Red Hat demo linked . Trilio will list installed VMs under the "Virtual Machines" section. For more detailed instructions, see the guide .

2. Create a BackupPlan For VirtualMachine

Create a BackupPlan Custom Resource (CR) through the management console, specifying the Virtual Machine for backup. Ensure that the name of the Virtual Machine specified matches the VM created in the previous step.

Step 4.5: Namespace Example

This section outlines the process of creating a BackupPlan for a k8s namespace.

1. Create a namespace and application

Follow the section to create an application.

Create a namespace named wordpress.
Use Helm to deploy a WordPress application into the wordpress namespace.

Trilio lists the namespaces available in the cluster under the Namespaces section. For detailed instructions, refer to the guide .

2. Create a BackupPlan for a Namespace

Create a BackupPlan Custom Resource (CR) through the management console, specifying the wordpress namespace for backup.

Step 5: Create Backup or Snapshot

Create a Backup or Snapshot CR through the UI to protect the BackupPlan. The backup can be of type Full or Incremental, while snapshots are always created as Full snapshots.

Note: The first backup into a target location will always be a Full backup.

Steps to perform

Select the backupPlan either from the "Backup Plans" tab from the UI and select the "Create Backup" or "Create Snapshot" option from the dropdown.
Or by choosing the application from the "Applications" section, the namespace from the "Namespaces" section, or the VM from the "Virtual Machines" section. And by clicking the "Create Backup" or "Create Snapshot" option in the UI. The available BackupPlans for the selected application will be displayed. Select the desired BackupPlan and proceed with creating the backup or snapshot.

Refer to this example for backing up a Helm application.

Refer to this example for taking a snapshot of a Virtual Machine.

Step 7: Restore the Application Using a Backup or Snapshot

Finally, create the Restore CR using the UI to restore the backup or snapshot, either in the same or a different namespace.

Restore to the same cluster in a same namespace

Note: If restoring into the same namespace, ensure that the original application components have been removed. Especially the PVC of the application is deleted.

Restore to the same cluster but a different namespace

Note: If restoring into another namespace in the same cluster, ensure that the resources that cannot be shared, for example, ports - should be available or transformation should be used to avoid conflict. More information about transformation can be found at .

Before restoring the app in the same cluster, the existing app must be removed if it has cluster-scoped resources. This is necessary to prevent conflicts with cluster-level resources that could interfere with the restore operation.

Restore from Backup

Steps to perform

Select the backup by choosing "View Backup and Restore Summary" from the dropdown in the application selection.
Then, choose the "Restore" option to restore the backup.

See this example for restoring an operator backup.

Refer to this example for a completed restore status.

Restore from Snapshot

Steps to perform

Select the snapshot by choosing "View Backup and Restore Summary" from the dropdown in the application selection.
Then, choose the "Restore" option to restore the snapshot.

See this example for restoring an namespace snapshot.

Step 8: Restore the Application to a Different Cluster

Trilio enables application backups to be restored into a different cluster. This section focuses on the process of restoring a backup to a different cluster.

Note: If restoring to another cluster (migration scenario), ensure that Trilio for Kubernetes is also running in the remote namespace/cluster. To restore into a new cluster (where the Backup CR does not exist), the same target should be created and Target Browsing should be enabled to browse the stored backups.

Steps to perform