LogoLogo
5.0.X
5.0.X
  • About Trilio for Kubernetes
    • Welcome to Trilio For Kubernetes
    • Version 5.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
            • Virtual Machines
              • Virtual Machine -Actions
              • Virtual Machine - Bulk Actions
            • Backup Plans
              • Create Backup Plans
              • Backup Plans - Actions
            • Targets
              • Create New Target
              • Targets - Actions
            • Hooks
              • Create Hook
              • Hooks - Actions
            • Policies
              • Create Policies
              • Policies - Actions
          • Monitoring
          • Guided Tours
        • UI How-to Guides
          • Multi-Cluster Management
          • Creating Backups
            • Pause Schedule Backups and Snapshots
            • Cancel InProgress Backups
            • Cleanup Failed Backups
          • Restoring Backups & Snapshots
            • Cross-Cluster Restores
            • Namespace & application scoped
            • Cluster scoped
          • 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
      • Observability of Trilio with Openshift Monitoring
      • 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
    • 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
  • 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
    • T4K Best Practices
Powered by GitBook
On this page
  • Trilio Pods and CPU/Memory requirements
  • Continuous Restore
  • Estimating Memory and CPU requirements for Trilio

Was this helpful?

  1. Advanced Configuration

Resource Request Requirements

This page provides resource requirements for Trilio for Kubernetes pods

PreviousConfiguring the UINextFine Tuning Resource Requests and Limits

Was this helpful?

Trilio Pods and CPU/Memory requirements

The table below provides resource related information for Trilio for Kubernetes pods.

The information contained can be leveraged to assign Resource Quotas and Limit Ranges for namespaces and resources within namespaces.

Pod Name

CPU request (milliCore)

Memory request

  • Target Validator

  • Metadata Snapshot

  • Quiesce

  • Unquiesce

  • Metadata Upload

  • Retention

  • Restore Validation

  • Restore Metadata

  • Backup Cleaner

100

500 Mi

  • Datamover Upload

  • Datamover Restore

  • Target Browser

100

800 Mi

  • Dex

  • Web

  • Ingress-controller

  • Backup CronJob

10

10 Mi

  • Webhook

700

512Mi

  • Exporter

50

512Mi

  • Resource Cleaner

400

512Mi

  • Web-backend

400

1024 Mi

  • Control-plane

400

512 Mi

Pods in bold run continuously. Other pods only run, and not in parallel, when a backup or restore operation is triggered.

Target Browser pod will run as long as a target browsing feature is enabled.

Continuous Restore

When Continuous restore is enabled, following services pod will run forever

Pod Name

CPU request (milliCore)

Memory request

  • Continuous restore Syncer

  • Continuous restore Manager

  • Continuous restore Watcher

  • Continuous restore Service

500Mi

When Continuous restore is enabled and consistentSet is getting created, then following services pod will run (not forever. Only till the job is done)

Pod Name

CPU request (milliCore)

Memory request

  • Continuous restore PreconsistentSetJob

100

500Mi

  • Continuous restore Data Restore

100

800Mi

Estimating Memory and CPU requirements for Trilio

The overall resource requirements of Trilio for Kubernetes will be dependent on the resources of the control plane pods and along with that dependent on the number of data protection and data management activities that are being performed. For example, a Kubernetes cluster with 10 backupPlans may need more resources if all backupPlans are configured to trigger the backup at the same time, compared to a Kubernetes cluster with 15 BackupPlans configured to be triggered at staggered intervals.

Control Plane

At the control plane level, Trilio uses the following pods: webhook, control-plane, exporter, web, web-backend, and ingress controller. Based on the table above, the following requirements can be calculated:

  1. CPU requests 1970 milliCore approximately

  2. Memory requests 3092 Mi approximately

Data Plane

Depending on the number of backup, restore and target operations happening concurrently and the overall features those operations use, the CPU and memory requirements can be calculated at the data plane level.

  1. Backup operations include -> Metadata snapshot, Quiesce (optional), Unquiesce (optional), Data Upload, Metadata upload, Retention (optional), Backup Cleaner (optional)

  2. Restore operations include -> Restore Validation, Data Restore, Restore Metadata, Unquiesce (optional)

  3. Target Operations include -> Target Validator, Target Browsing (Optional)

Adding up the resources requirements for the different phases for a particular operation will provide the requirements for the entire backup or restore operation.

Every phase will consume different amount of resources, they are not running in paralell. As one task is completed, those resources will be freed up, and the next task will do some CPU and RAM requests.

Maximum Resource Requirements

In order to estimate the maximum memory and CPU that could be utilized by Trilio, the biggest pods need to be evaluated running in parallel. For 5 concurrent backups and restores with one PVC/PV each, the maximum amount of CPU and Memory required would be dictated by the Datamover pods running in parallel. Based on the table above, the following can be calculated:

  1. CPU request of 500 milliCore approximately

  2. Memory requests of 4000 Mi approximately

herein