Even though Tanzu Mission Control will manage your data protection amd lifecycle velero on the cluster, at times it may be useful to have the velero cli.
Download and install the Velero cli from the TKG 2.1.0 page at https://www.vmware.com/go/get-tkg.
The scripts to prepare the YAML to deploy velero depend on a parameters to be set. Ensure the following are set in params.yaml
based upon your environment. This should be the target location you created above
tmc.data-protection-backup-location-name: my-tmc-data-protection-target-location
velero.bucket: velero-backups
We will place our TMC Data Protection backups in the Minio server we deployed.
Follow the Tanzu Mission Control docs:
- Create a Account Credential. Again, this is IaaS dependent. For AWS you will provide your S3 credentials. For vSphere your Minio account credentials. For Azure, your Azure Blob Storage credentials.
- Create a Target Location with your IaaS dependent target location. You must set your bucket name to match
velero.bucket
in the parmams.yaml file
Orchestrate commands for the tmc
cli to enable data protection on the cluster and then setup a daily backup.
./scripts/dataprotection.sh $(yq e .shared-services-cluster.name $PARAMS_YAML)
Ensure schedule is created and the first backup is starting
velero schedule get
velero backup get | grep daily