LogoLogo
4.0.X
4.0.X
  • About Trilio for Kubernetes
    • Welcome to Trilio For Kubernetes
    • Version 4.0.X Release Highlights
    • Compatibility Matrix
    • Marketplace Support
    • Features
    • Use Cases
  • Getting Started
    • Getting Started with Trilio on Red Hat OpenShift (OCP)
    • Getting Started with Trilio for Upstream Kubernetes (K8S)
    • Getting Started with Trilio for AWS Elastic Kubernetes Service (EKS)
    • Getting Started with Trilio on Google Kubernetes Engine (GKE)
    • Getting Started with Trilio on VMware Tanzu Kubernetes Grid (TKG)
    • More Trilio Supported Kubernetes Distributions
      • General Installation Prerequisites
      • Rancher Deployments
      • Azure Cloud AKS
      • Digital Ocean Cloud
      • Mirantis Kubernetes Engine
      • IBM Cloud
    • Licensing
    • Using Trilio
      • Overview
      • Post-Install Configuration
      • Management Console
        • About the UI
        • Navigating the UI
          • UI Login
          • Cluster Management (Home)
          • Backup & Recovery
            • Namespaces
              • Namespaces - Actions
              • Namespaces - Bulk Actions
            • Applications
              • Applications - Actions
              • Applications - Bulk Actions
            • Backup Plans
              • Create Backup Plans
              • Backup Plans - Actions
            • Targets
              • Create New Target
              • Targets - Actions
          • Trilio Monitoring
          • Resource Management
          • Guided Tours
        • UI How-to Guides
          • Multi-Cluster Management
          • Creating Backups
            • Cleanup Failed Backups
          • Restoring Backups
            • Cross-Cluster Restores
          • Monitoring Details
          • Disaster Recovery Plan
          • Continuous Restore
      • Command-Line Interface
        • YAML Examples
        • Trilio Helm Operator Values
    • Upgrade
    • Air-Gapped Installations
    • Uninstall
  • Reference Guides
    • T4K Pod/Job Capabilities
      • Resource Quotas
    • Trilio Operator API Specifications
    • Custom Resource Definition - Application
  • Advanced Configuration
    • AWS S3 Target Permissions
    • Management Console
      • KubeConfig Authenticaton
      • Authentication Methods Via Dex
      • UI Authentication
      • RBAC Authentication
      • Configuring the UI
    • Resource Request Requirements
      • Fine Tuning Resource Requests and Limits
    • Observability
      • Observability of Trilio with Prometheus and Grafana
      • Exported Prometheus Metrics
      • T4K Integration with Observability Stack
    • Modifying Default T4K Configuration
  • T4K Concepts
    • Supported Application Types
    • Support for Helm Releases
    • Support for OpenShift Operators
    • T4K Components
    • Backup and Restore Details
      • Immutable Backups
      • Application Centric Backups
    • Backup Retention Process
      • Retention Use Case
    • Continuous Restore
      • Architecture and Concepts
  • Performance
    • S3 as Backup Target
      • T4K S3 Fuse Plugin performance
    • Measuring Backup Performance
  • Ecosystem
    • T4K Integration with Slack using BotKube
    • Monitoring T4K Logs using ELK Stack
    • Rancher Navigation Links for Trilio Management Console
    • Optimize T4K Backups with StormForge
    • T4K GitHub Runner
    • AWS RDS snapshots using T4K hooks
    • Deploying Trilio For Kubernetes with Openshift ACM Policies
  • Krew Plugins
    • T4K QuickStart Plugin
    • Trilio for Kubernetes Preflight Checks Plugin
    • T4K Log Collector Plugin
    • T4K Cleanup Plugin
    • OCP ETCD Plugin
    • RKE ETCD Plugin
  • Support
    • Troubleshooting Guide
    • Known Issues and Workarounds
    • Contacting Support
  • Appendix
    • Ignored Resources
    • OpenSource Software Disclosure
    • CSI Drivers
      • Installing VolumeSnapshot CRDs
      • Install AWS EBS CSI Driver
    • T4K Product Quickview
    • OpenShift OperatorHub Custom CatalogSource
      • Custom CatalogSource in a restricted environment
    • Configure OVH Object Storage as a Target
    • Connect T4K UI hosted with HTTPS to another cluster hosted with HTTP or vice versa
    • Fetch DigitalOcean Kubernetes Cluster kubeconfig for T4K UI Authentication
    • Force Update T4K Operator in Rancher Marketplace
    • Backup and Restore Virtual Machines running on OpenShift
    • T4K For Volumes with Generic Storage
Powered by GitBook
On this page
  • Initiating Restores
  • Restore Workflow
  • Restore Flags
  • Transforms
  • Exclude Resources and Restore Hooks
  • Restoring Encrypted Backups
  1. Getting Started
  2. Using Trilio
  3. Management Console
  4. UI How-to Guides

Restoring Backups

This page describes the process for restoring backups.

PreviousCleanup Failed BackupsNextCross-Cluster Restores

Last updated 12 months ago

Similar to the backup workflow, Trilio provides intuitive restore workflows that reduce the complexity dramatically for recovering and migrating applications for a Kubernetes based environment.

Initiating Restores

  1. Backups can be restored by name if within the same cluster or namespace scope of T4K

    1. Restore from via the RestorePoints Tab

    2. Restore from Backup Overview Page

  2. Backups can be restored by location if restoring from a target repository.

    1. Restore from

Restore Workflow

Regardless of where the Restore operation is initiated, the workflow for the operation is the same, ensuring consistency and simplicity.

For the restore workflow, there are two tabs presented to the user - Basic and Advanced. Basic restores cover general restore properties for the backup - skip resources, patch CRDs etc. whereas Advanced restores cover resource transformation, resource exclusions, and resource hooks.

Restore Flags

As part of every restore, users can select different restore flags to define how the restore should happen.

The following flags are provided:

SkipIfAlreadyExists - Specifies whether to skip restoring resources if they are already found in the namespace in which the backup is being restored. This is only applicable for metadata resources and not data resources (PV/PVC).

PatchIfAlreadyExists - Specifies whether to patch the spec section of an already existing resource found in the namespace at the time of restore.

OmitMetadata - Specifies whether to omit metadata labels, annotations of resources while restoring them.

PatchCRD - Specifies whether to patch spec of an already existing CRD

SkipOperatorResources - Specifies whether to omit operator resources at the time of restore (for the use case when an Operator is already present, but the application of that operator needs to be restored)

CleanupOnFailure - Specifies whether to perform cleanup of resources created along with reverting updated resources in case the restore operation fails.

ProtectRestoredApp - Specifies whether to create a backupplan at the destination namespace/cluster to protect the application after it has been restored. With this flag, users can ensure that their application is protected no matter which cluster it runs on.

DisableIgnoreResources - Specifies the behavior of the default list of resources being ignored at the time of restore. If set to true, those resources will not be ignored.

OnlyData - Restores only the data volume components from a backup.

OnlyMetaData - Restores only the metadata components from a backup.

UseOCPNamespaceUIDRange - Openshift specific flag to restore the data with the ocp namespace UID range.

Transforms

From a resource transform perspective, Trilio provides the ability to transform Helm Charts and transform custom resources. Helm charts can be transformed based on Key:Value pairs whereas custom resources can be transformed by specifying GVKO and Operation (Replace, Move etc.) type.

For both Helm and Custom Transforms - Trilio fetches the metadata and populates it via dropdown menus and tables - to make is easy for the user to manage the granular details of the transforms

Exclude Resources and Restore Hooks

Users can choose to exclude resources by specifying the GVK through the Exclude Resources Tab

Upon satisfactorily entering restore workflow information and triggering the restore, the user a presented with a status log for the restore performed.

Once a restore operation is initiated, the restore progress can be tracked via the Monitoring page or from the restore dialog box itself, if kept open

Restoring Encrypted Backups

Restoring Encrypted Backup on the same K8s cluster

Restoring the Encrypted Backup on same cluster needs Target Browsing enabled. On the restore form, user will get the option to enable the target browsing. Once the target browser is up, user can select the Encryption Secret from the list. After selecting, it will get verified and then user can continue with the restore.

Restoring Encrypted Backup on the different K8s cluster

Similarly, the user can specify hooks to inject before and after the restore. The hooks workflow and behavior is the same as the within the backup workflow. By default, the same hooks are loaded for the user to reuse.

While creating , user need to configure the first then create the secret with Encryption key. Similarly, while restoring the encrypted backups, user need to create the secret with Encryption key.

User need to configure the on the cluster where restore operation will be running. After enabling target browsing, user need to select the backup to restore and create the secret with same Encryption Key(which was used at the time of Backup). Refer following video.

Encrypted Backups
Master Encryption Key
Master Encryption key
Home page
Cross-Cluster Restores page
hooks workflow
Restoring from the Home Page
Restore from Monitoring Page
Restoring from Target Browser for cross-cluster or DR use cases
Restore Basic Workflow
Summary Screen based on Tranforms
Restore Exclusions and Restore Hooks
Restore Encrypted Backup
Restore Encrypted backup on different cluster