Recurring Snapshots and Backups
From the Longhorn UI, recurring snapshots and backups can be scheduled.
To set up a schedule, you will go to the volume detail view in Longhorn. Then you will set:
Then Longhorn will automatically create snapshots or backups for the user at that time, as long as the volume is attached to a node.
Recurring snapshots can be configured using the Longhorn UI, or by using a Kubernetes StorageClass.
For more information on how snapshots and backups work, refer to the concepts section.
Recurring snapshots and backups can be configured from the volume detail page. To navigate to this page, click Volume, then click the name of the volume.
Scheduled backups and snapshots can be configured in the recurringJobs
parameters in a StorageClass.
Any future volumes created using this StorageClass will have those recurring jobs automatically set up.
The recurringJobs
field should follow JSON format:
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: longhorn
provisioner: driver.longhorn.io
parameters:
numberOfReplicas: "3"
staleReplicaTimeout: "30"
fromBackup: ""
recurringJobs: '[
{
"name":"snap",
"task":"snapshot",
"cron":"*/1 * * * *",
"retain":1
},
{
"name":"backup",
"task":"backup",
"cron":"*/2 * * * *",
"retain":1
}
]'
The following parameters should be specified for each recurring job:
name
: Name of one job. Do not use duplicate name in one recurringJobs
. And the length of name
should be no more than 8 characters.
task
: Type of one job. It supports snapshot
(periodically create snapshot) or backup
(periodically create snapshot then do backup) only.
cron
: Cron expression. It tells execution time of one job.
retain
: How many snapshots/backups Longhorn will retain for one job. It should be no less than 1.
© 2019-2024 Longhorn Authors | Documentation Distributed under CC-BY-4.0
© 2024 The Linux Foundation. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page.