The T4K backup workflow from the T4K Home Page allows users to create BackupPlans, Targets, Policies, Hooks as part of the backup workflow. However, these resources can be managed (CRUD) outside of the backup workflow, to be used within the backup workflow itself. The Resource Management Tab enables users to manage independent T4K resources outside of the regular backup workflow from the Home Page.
For all Trilio Resources, users have the ability to:
Edit the resource
Clone the resource
View YAMLs for the resource
Delete the resource
The list of resources that can be created and managed separately are as follows:
New BackupPlans can be created and existing BackupPlans can be viewed and edited from the reusable resources page by navigating to the BackupPlans tab.
When selecting applications for backup from the application discovery panel, backupPlans are automatically created for the user and are shown here. However, this view provides the user the ability to create backupPlans to execute at a future time.
As shown on the Operate page, a backupPlan includes the following:
Applications to protect
Hooks
Policies
Target
Hooks, Policies and Targets (as shown on this page) can be created separately and referenced within the BackupPlan, or can be created on-demand as part of the backupPlan creation workflow.
BackupPlans across multiple namespaces can be viewed together by multi-selecting the namespaces on the left panel.
Editing a backupPlan is available through the edit option for a BackupPlan. The schema is the same as a user goes through when creating a backup via the application discovery panel on the landing page.
Cloning a backupPlan can be performed by clicking on a BackupPlan, selecting 'Clone', the cluster/namespace to clone to, and providing a name for the cloned resource.
Similarly, the YAML of the backupPlan can be viewed by clicking the "View YAML" button. The YAMLs for all referenced resources within the BackupPlan will also be shown.
BackupPlans that use an immutable target must have a scheduling policy and retention policy defined. If the Trilio calculated net retention (based on these policies) is less than the default retention that was set on the bucket, then the creation of the backupPlan will fail with appropriate error messages.
Hooks can also be created and managed via the reusable resources page. Users can create Hooks on-demand while going through the backup workflow or have them pre-created here and leverage them in their backup workflows.
The schema for creating hooks from the reusable resources page is the same as creating them via backupPlan workflows
Hooks across multiple namespaces can be viewed together by multi-selecting the namespaces on the left panel.
Hooks can be edited by clicking the edit action for a specific hook.
Cloning a Hook can be performed by clicking on a Hook, selecting Clone and providing a name for the Clone
Similarly, the YAML output of the Hook can be viewed by clicking the "View YAML" button.
Retention policies can also be created and managed via the reusable resources page. Users can create retention policies on-demand while going through the backup workflow or have them pre-created here and leverage them in their backup workflows. The schema for creating retention policies from the reusable resources page is the same as creating them via backup workflows.
Retention Policies across multiple namespaces can be viewed together by multi-selecting the namespaces on the left panel.
Retention Policies can be edited by clicking the edit option for a particular retention policy.
Cloning a Policy can be performed by clicking on a Policy, selecting Clone and providing a name for the Clone
Similarly, the YAML output of the Policy can be viewed by clicking the "View YAML" button.
Targets can also be created and managed via the reusable resources page. Users can create Targets on-demand while going through the backup workflow or have them pre-created here and leverage them in their backup workflows.
Target browsing is a new feature that enables a user to browse the target repository and choose a backup to restore. Target browsing can be enabled on a target by toggling the button under the 'Browsing' column.
After browsing has been enabled (may take a minute to launch the necessary pods and resources in the backend), users can browse the different backupPlans and backups based on those backupPlans while selecting one that they want to restore.
Before restoring the backup, users also have the ability to view the metadata to understand the transforms that they would need to apply.
Targets can be edited by clicking the edit option for a particular target.
Cloning a Target can be performed by clicking on a Target, selecting Clone and providing a name for the Clone.
Similarly, the YAML output of the Target can be viewed by clicking the "View YAML" button.
Trilio supports the creation of immutable backups on S3 devices that support object locking and versioning capabilities. Immutable backups once created can only be deleted via the Trilio retention process. Manual deletes from the T4K management console or from the target device itself will not remove the backup. In case of manual deletion from the T4K management console, the backup will be soft-deleted (only the backup reference will be removed from the cluster).
Pre-requisites:
In order for Trilio to support immutability the S3 bucket must have:
Object Locking enabled
Versioning enabled (this is generally enabled automatically with Object Locking if not a separate switch/flag)
In order to create an Immutable target toggle the Object Locking switch in the configuration screen. Trilio will automatically validate that the target is actually an immutable target with the correct settings and configuration.
When an Immutable target is created and used within a backupPlan, a scheduling policy and a retention policy will be required for the backupPlan. Trilio validates that the default retention on the bucket and the retention specified by the user are in alignment. If not, Trilio will fail the creation of the backupPlan with appropriate error messages.
Disaster Recovery Plans can be created and triggered from the resource management page as well. Please refer to the DRPlan page for more information
