Trilio aims to simplify the backup creation process by providing intuitive workflows for protecting applications and namespaces.
From the landing page, the user can either select a namespace via the navigation panel or choose specific applications within the selected namespace for backup. As mentioned in the previous sections, if the user does not select any application from the application discovery panel and clicks the backup button, it automatically results in a namespace backup.
A user can also select multiple namespaces from the navigation panel for a multi-namespace backup.
Users can navigate between the 4 views provided in the application discovery panel and select the items present within to build their protection scope or backupPlan. The BackupPlan can be a combination of any number of items from any of the views. For example, 1 helm + 1 label can be a backupPlan or 2 Helm + 2 Operator + 3 Objects can be the backupPlan.
Users can leverage existing backupPlans as part of the new backupPlan they create, which will automatically copy all the backupPlan components into the new BackupPlan along with the other items selected from the different views provided.
Trilio takes out the complexity in building the backupPlan components manually by preloading the specifications for the user based on the selections. For example, selecting an Operator automatically populates the Custom Resources associated with the Operator, the resources for the Operator as well as application resources managed by the Operator. All of this population happens behind the scenes with the user only having to select the Operator item from the application discovery panel. Along with this, Trilio also provides the user the ability to edit the data populated as well as add to it manually.
Similarly, if the the user had chosen items from the labels view, those items would be populated under the Custom tab, and if helm items were chosen as well, those releases would get populated under the Helm Release tab.
After the protection scope has been defined by the user either in terms of namespaces or application items from the discovery panel, the user can define the rest of the backupPlan by clicking Backup on the top right and driving through the Backup workflow.
Based on the applications/namespace selected the Backup workflow first scans the system to check if there are existing backupPlans with the same components that the user has selected and presents it to the user in case they would want to reuse it. If not, the user can choose to create a net-new backupPlan. The user can also edit an existing backupPlan and save that as a new BackupPlan.
As part of the backup workflow, the user can:
Simple workflow to create a new NFS or S3 target on-demand
Simple workflows to define pre/post hooks along with specifying a regex pattern for pods to execute the hooks on.
Multiple Hooks can be applied to a BackupPlan.
Simple click-driven workflow to define a scheduled based backup policy Note: A default retention policy is automatically selected if a scheduled policy is applied
Simple workflows to define retention in terms of days/weeks/months/years
After setting the configuration and component details satisfactorily, the user can proceed to perform the backup.