Step 4.1 Policy Presets
- A PolicyPreset custom resource (CR) in K10 is used to save and reuse configurations of K10 Policies.
- PolicyPresets specify schedule, retention, location, and infrastructure information, while Policies specify application-specific details.
- Users can find detailed information about schedule settings in the Policy Scheduling section.
Create a PolicyPreset
- The example in the demo illustrates creating a preset for policies that execute daily, retain 1 daily and 1 weekly snapshot, and export every daily snapshot with a different retention schedule.
Step 4.2 Profiles
Location Profiles
K10 can usually invoke protection operations such as snapshots within a cluster without requiring additional credentials. While this might be sufficient if K10 is running in some of (but not all) the major public clouds and if actions are limited to a single cluster, it is not sufficient for essential operations such as performing real backups, enabling cross-cluster and cross-cloud application migration, and enabling DR of the K10 system itself.
To enable these actions that span the lifetime of any one cluster, K10 needs to be configured with access to external object storage or external NFS file storage. This is accomplished via the creation of Location Profiles.
Some popular storage locations are:
- Object Storage Location
- Amazon S3 or S3 Compatible Storage
- Azure Storage
- Google Cloud Storage
- NFS File Storage Location
- Veeam Repository Location
A Veeam Repository Location Profile is used to export or import vSphere CSI provisioned volume snapshot data in a supported vSphere cluster from a Veeam Repository. A Veeam Repository cannot be used to save K10 restore points so such a location profile is always used in conjunction with another location profile that can be used to save restore point data.
Infrastructure Profiles
Infrastructure profiles are used specifically for integrating with in-tree provisioners. Below are some supported in-tree provisioners
- AWS
- Azure
- Google Cloud
- VSphere
- Portworx
- Openstack
Step 4.3 Restoring Applications
Once applications have been protected via a policy or a manual action, it is possible to restore them in-place or clone them into a different namespace.
Demo – Kasten Backup Policies and Restores
Demo – Multi App Restore
Step 4.4 Application Mobility
The ability to move an application across clusters is an extremely powerful feature that enables a variety of use cases including Disaster Recovery (DR), Test/Dev with realistic data sets, and performance testing in isolated environments.
Demo – Cross Cluster App Mobility
Step 4.5 K10 Disaster Recovery
K10 Disaster Recovery (DR) aims to protect K10 from the underlying infrastructure failures. In particular, this feature provides the ability to recover the K10 platform in case of a variety of disasters such as the accidental deletion of K10, failure of underlying storage that K10 uses for its catalog, or even the accidental destruction of the Kubernetes cluster on which K10 is deployed.
Get ready for Step 5 of your onboarding journey. At the next step, we will discover how metrics from Prometheus can be leveraged for monitoring, alerting, and visualizing health with Grafana.
If you need more help getting started, you can post your question in the comments section below or contact us at any time and someone from the Customer Success team will be there to assist you.