` against a new license file to activate it. The previous license will be replaced automatically.
#### [Learn more about Licensing Trilio for Kubernetes](https://docs.trilio.io/kubernetes/getting-started/licensing)
## Create a Target
The Target CR (Customer Resource) is defined from the Trilio Management Console or from your own self-prepared YAML.
The Target object references the NFS or S3 storage share you provide as a *target* for your backups/snapshots. Trilio will create a validation pod in the namespace where Trilio is installed and attempt to validate the NFS or S3 settings you have defined in the Target CR.
Trilio makes it easy to automatically create your Target CR from the Management Console.
Learn how to [Create a Target from the Management Console](https://docs.trilio.io/kubernetes/using-trilio/getting-started-with-management-console#create-a-target)
Take control of Trilio and define your own self-prepared YAML and apply it to the cluster using the oc/kubectl tool.
#### Example S3 Target
```
kubectl apply -f sample-secret.yaml
```
```
kubectl apply -f demo-s3-target.yaml
```
```
apiVersion: v1
kind: Secret
metadata:
name: sample-secret
type: Opaque
stringData:
accessKey: AKIAS5B35DGFSTY7T55D
secretKey: xWBupfGvkgkhaH8ansJU1wRhFoGoWFPmhXD6/vVDcode
```
```
apiVersion: triliovault.trilio.io/v1
kind: Target
metadata:
name: demo-s3-target
spec:
type: ObjectStore
vendor: AWS
objectStoreCredentials:
region: us-east-1
bucketName: trilio-browser-test
credentialSecret:
name: sample-secret
namespace: TARGET_NAMESPACE
thresholdCapacity: 5Gi
```
* See more [Example Target YAML](https://docs.trilio.io/kubernetes/using-trilio/getting-started-1#step-2-create-a-target)
## Testing Backup, Snapshot and Restore Operation
Trilio is a cloud-native application for Kubernetes, therefore all operations are managed with CRDs (Custom Resource Definitions). We will discuss the purpose of each Trilio CRs and provide examples of how to create these objects Automatically in the Trilio Management Console or from the [oc/kubectl](https://docs.openshift.com/container-platform/4.8/cli_reference/openshift_cli/getting-started-cli.html) tool.
### About Backup Plans
* The Backup Plan CR is defined from the Trilio Management Console or from your own self-prepared YAML.
The Backup Plan CR must reference the following:
1. Your Application Data (label/helm/operator)
2. BackupConfig
1. Target CR
2. Scheduling Policy CR
3. Retention Policy CR
3. SnapshotConfig
1. Target CR
2. Scheduling Policy CR
3. Retention Policy CR
* A Target CR is defined from the Trilio Management Console or from your own self-prepared YAML. Trilio will test the backup target to insure it is reachable and writable. Look at Trilio validation pod logs to troubleshoot any backup target creation issues.
* Retention and Schedule Policy CRs are defined from the Trilio Management Console or from your own self-prepared YAML.
* Scheduling Policies allow users to automate the backup/Snapshot of Kubernetes applications on a periodic basis. With this feature, users can create a scheduling policy that includes multiple cron strings to specify the frequency of backups.
* Retention Policies make it easy for users to define the number of backups/snapshots they want to retain and the rate at which old backups/snapshots should be deleted. With the retention policy CR, users can use a simple YAML specification to define the number of backups/snapshots to retain in terms of days, weeks, months, years, or the latest backup/snapshots. This provides a flexible and customizable way to manage your backup/snapshots retention policy and ensure you meet your compliance requirements.
* The Backup and Snapshot CR is defined from the Trilio Management Console or from your own self-prepared YAML.
The backup/snapshot object references the actual backup Trilio creates on the Target. The backup is taken as either a Full or Incremental backup as defined by the user in the Backup CR. The snapshpt is taken as Full snapshot only.
### Creating a Backup Plan
Trilio makes it easy to automatically create your backup plans and all required target and policy CRDs from the Management Console.
Take control of Trilio, define your self-prepared YAML, and apply it to the cluster using the oc/kubectl tool.
#### Example Namespace Scope BackupPlan:
```
kind: "Policy"
apiVersion: "triliovault.trilio.io/v1"
metadata:
name: "sample-schedule"
spec:
type: "Schedule"
scheduleConfig:
schedule:
- "0 0 * * *"
- "0 */1 * * *"
- "0 0 * * 0"
- "0 0 1 * *"
- "0 0 1 1 *"
```
```
kubectl apply -f sample-schedule.yaml
```
```
apiVersion: triliovault.trilio.io/v1
kind: Policy
metadata:
name: sample-retention
spec:
type: Retention
default: false
retentionConfig:
latest: 2
weekly: 1
dayOfWeek: Wednesday
monthly: 1
dateOfMonth: 15
monthOfYear: March
yearly: 1
```
```
kubectl apply -f sample-retention.yaml
```
apiVersion: triliovault.trilio.io/v1
kind: BackupPlan
metadata:
name: sample-backupplan
spec:
backupConfig:
target:
namespace: default
name: demo-s3-target
retentionPolicy:
name: sample-retention
namespace: default
schedulePolicy:
fullBackupPolicy:
name: sample-schedule
namespace: default
snapshotConfig:
target:
namespace: default
name: demo-s3-target
retentionPolicy:
name: sample-retention
namespace: default
schedulePolicy:
snapshotPolicy:
name: sample-schedule
namespace: default
```
# kubectl apply -f ns-backupplan.yaml
```
{% hint style="info" %}
Target in the backupConfig and snapshotConfig needs to be the same. User can specify different retention and schedule policies under backupConfig and snapshotConfig.
{% endhint %}
See more [Examples of Backup Plan YAML](https://docs.trilio.io/kubernetes/using-trilio/getting-started-1/triliovault-crds#backupplan)
### Creating a Backup
```
apiVersion: triliovault.trilio.io/v1
kind: Backup
metadata:
name: sample-backup
spec:
type: Full
backupPlan:
name: sample-backupplan
namespace: default
```
```
kubectl apply -f sample-backup.yaml
```
Learn more about [Creating Backups from the Management Console](https://docs.trilio.io/kubernetes/using-trilio/getting-started-with-management-console#step-5-create-backup)
### Creating a Snapshot
```
apiVersion: triliovault.trilio.io/v1
kind: Snapshot
metadata:
name: sample-snapshot
spec:
type: Full
backupPlan:
name: sample-backupplan
namespace: default
```
```
kubectl apply -f sample-snapshot.yaml
```
Learn more about [Creating Snapshots from the Management Console](https://docs.trilio.io/kubernetes/using-trilio/getting-started-with-management-console#step-6-create-snapshot)
### About Restore
A Restore CR (Custom Resource) is defined from the Trilio Management Console or from your own self-prepared YAML. The Restore CR references a backup object which has been created previously from a Backup CR.
In a Migration scenario, the location of the backup/snapshot should be specified within the desired target as there will be no Backup/Snapshot CR defining the location. if you are migrating Snapshot then make sure that then then actual Persistent Volume snapshots are accessible from the other cluster.
Trilio restores the backup/snapshot into a specified namespace and upon completion of the restore operation, the application is ready to be used on the cluster.
### Creating a Restore
Trilio makes it easy to automatically create your Restore CRDs from the Management Console.
Learn more about [Creating Restores from the Management Console](https://docs.trilio.io/kubernetes/using-trilio/getting-started-with-management-console#restore-from-backup)
Take control of Trilio, define your self-prepared YAML, and apply it to the cluster using the oc/kubectl tool.
```
kubectl apply -f sample-restore.yaml
```
```
apiVersion: triliovault.trilio.io/v1
kind: Restore
metadata:
name: sample-restore
spec:
source:
type: Backup
backup:
name: sample-backup
namespace: default
```
See more [Examples of Restore YAML](https://docs.trilio.io/kubernetes/using-trilio/getting-started-1/triliovault-crds#restore)
## Troubleshooting
Problems? Learn about [Troubleshooting Trilio for Kubernetes](https://docs.trilio.io/kubernetes/support/troubleshooting-guide#troubleshooting-guide)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
.png)
