Using Velero commands for SPI Backup and Restore

velero is a tool for managing disaster recovery, specifically for kubernetes (k8s) cluster resources it provides a simple, configurable, and operationally robust way to back up your application state and associated data if you're familiar with kubectl, velero supports a similar model, allowing you to execute commands such as 'velero get backup' and 'velero create schedule' the same operations can also be performed as 'velero backup get' and 'velero schedule create' instead of using the spi admin ui to do backup and restore, one can also use velero cli to achieve the same create spi backup velero create backup \<backupname> or \<backupid> schedule a backup velero create schedule \<name> schedule \[flags] examples \# create a backup every 6 hours velero create schedule name schedule="0 /6 " \# create a backup every 6 hours with the @every notation velero create schedule name schedule="@every 6h" \# create a daily backup of the web namespace velero create schedule name schedule="@every 24h" include namespaces web \# create a weekly backup, each living for 90 days (2160 hours) velero create schedule name schedule="@every 168h" ttl 2160h0m0s troubleshooting a failed backup please use velero debug backup \<backupname> to generate the support bundle, and attach to the ticket, more options please refer to velero debug help sample velero debug backup instance 2hg5z 2023/06/28 05 00 19 collecting velero resources in namespace velero 2023/06/28 05 00 23 collecting velero deployment logs in namespace velero 2023/06/28 05 00 31 collecting log and information for backup instance 2hg5z 2023/06/28 05 00 37 generated debug information bundle /root/bundle 2023 06 28 05 00 18 tar gz to check the status and get information on the backup velero backup describe \<backupname or id> velero backup logs \<backupname or id> to fetch the logs of the velero server pod this provides the output of the velero server processes kubectl logs deployment/velero n velero getting velero debug logs you can increase the verbosity of the velero server by editing your velero deployment to look like this kubectl edit deployment/velero n velero containers name velero image velero/velero\ latest command /velero args server log level # add this line debug # add this line download all kubernetes manifests for a backup velero backup download \<backupname or id> to list all backups and to see the status and date created velero backup get to find a backup location velero backup location get to create a backup location with read/write velero backup location create \<locationname> acess mode readonly (default is read/write) backup to s3 location using ca cert velero install provider aws plugins velero/velero plugin for aws\ v1 1 0 bucket \<bucket name> backup location config region=\<region> snapshot location config region=\<region> secret file \<secret file> use restic cacert \<path to cacert> to delete backup velero delete backup \<backupname> or \<backupid> if after issuing the above command, the backup is still stuck in deleting force deletion with the command below kubectl delete backup n velero \<backupname> use the velero help to get more information and all the available commands and flags velero help use "velero \[command] help" for more information about a particular command velero backup location help to restore velero restore create \<restore name> from backup \<backup name> common errors inprogress velero (or a pod it was backing up) restarted during a backup and the backup is stuck inprogress velero cannot currently resume backups that were interrupted backups stuck in the inprogress phase can be deleted with kubectl delete backup \<name> n \<velero namespace> backups in the inprogress phase have not uploaded any files to object storage