Version 5.1.X Release Highlights

Version 5.1 of Trilio for Kubernetes introduces major new capabilities as follows

5.1.0

✨ New Features

• File-Level Recovery for VMs File-level recovery is now supported for VM backups using dedicated FileRecovery VMs, extending recovery beyond just PVC-based file system backups. Automated FileRecovery VM Provisioning: FileRecovery VMs are automatically created with appropriate security configurations, target mounts, and SCP file transfer capabilities, maintaining a 1:1 mapping with the backed-up VMs. By default, Trilio uses a CentOS 8–based FileRecovery VM image. However, users also have the option to use a custom FileRecovery VM image, with automated pre-validation to ensure compatibility.

• Enhanced Backup Retention Reliability Improved the backup retention process to prevent backups from becoming unusable during retention failures. Introduced comprehensive state tracking, retry logic, and pre/post-validation to ensure backup chains remain intact. Backups can now continue without interruption, even in case of retention issues.

• Immutable Backups for Azure Blob Storage Added support for creating immutable backups when using Azure Blob storage as the target.

• VM MAC Address Preservation VM restore operations now support retaining original MAC addresses when requested, maintaining network identity for VMs that require specific configurations. Refer the restore flags here

• VM Backup/Restore Enhancements Added backup and restore support for VirtualMachinePool and PriorityClassName objects associated with VMs.

• Trilio UI Improvements

  The user interface has been enhanced with a centralised notification center, improved backup and restore workflows, and multiple UI updates to improve overall usability and navigation throughout the application.

• OCP Plugin Enhancements

  The OpenShift plugin now offers improved access control with permission-based feedback, enhanced compatibility with OpenShift 4.15 and beyond, seamless integration with the Trilio web console, and various UI fixes to elevate the overall user experience.

• TLS Skip Support for Image Repositories Restores now support skipping TLS verification for self-hosted or unsigned HTTPS image repositories. A new skipTLSVerify field has been added for use in registry secrets.

• Helm Backup Restore with Original Release Name Users can now restore Helm application backups using the same release name that was present at the time of backup. For more details, refer this

• Timezone Configuration Support Scheduled Backup and ClusterBackup operations now respect user-configured timezones, enabling localized scheduling.

• PVC Application Data Exclusion Added support to selectively exclude application data from specific PVCs during backup, improving flexibility and storage efficiency.

• ClusterBackupPlan Target Update The target for a ClusterBackupPlan can now be updated, similar to BackupPlan target updates introduced in earlier releases.

• Encrypted Incremental Backup: Continuous Restore Continuous restore is now supported for virtual machines with encrypted incremental backups.

• Pending Job Timeout Support Introduced jobPendingDeadlineSeconds configuration. Backup and restore jobs that remain in a pending state beyond this threshold will now fail gracefully with detailed error messages.

• Enhanced SSL Certificate Handling for S3 Targets SSL certificates for S3 targets can now be referenced from Kubernetes ConfigMaps, replacing the earlier approach of embedding them as ca-bundle.pem.

---

🐞 Bug Fixes

• Secure Token Handling Replaced usage of long-lived service account token secrets with generated, time-bound tokens for improved security.

• ppc64le Architecture Support Container images built with support for the ppc64le architecture are now available.