You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
Create a schedule with defaultVolumesToFsBackup enabled and manually trigger a backup from the schedule. /velero backup create --from-schedule velero-backup-metering
It turns out no restic backup triggered but only velero-native snapshots: Velero-Native Snapshots: 1 of 1 snapshots completed successfully (specify --details for more information)
What did you expect to happen:
This is the output with /velero backup create test807-2 --default-volumes-to-fs-backup
restic Backups (specify --details for more information):
Completed: 20
And everything looks fine. I would expect the same result when creating backup from schedule.
The output of the following commands will help us better understand what's going on:
This is the description of the backup from schedule:
Phase: Completed
Namespaces:
Included: *
Excluded: kube-system, kube-public, kube-node-lease, velero-restore-test, velero
Resources:
Included: pv, pvc
Excluded: <none>
Cluster-scoped: auto
Label selector: k8s-app in (metering)
Storage Location: default
Velero-Native Snapshot PVs: auto
TTL: 48h0m0s
CSISnapshotTimeout: 10m0s
ItemOperationTimeout: 1h0m0s
Hooks: <none>
Backup Format Version: 1.1.0
Started: 2023-08-07 08:08:18 +0000 UTC
Completed: 2023-08-07 08:09:04 +0000 UTC
Expiration: 2023-08-09 08:08:18 +0000 UTC
Velero-Native Snapshots: 1 of 1 snapshots completed successfully (specify --details for more information)
Anything else you would like to add:
The schedule is:
What steps did you take and what happened:
Create a schedule with defaultVolumesToFsBackup enabled and manually trigger a backup from the schedule.
/velero backup create --from-schedule velero-backup-metering
It turns out no restic backup triggered but only velero-native snapshots:
Velero-Native Snapshots: 1 of 1 snapshots completed successfully (specify --details for more information)
What did you expect to happen:
This is the output with
/velero backup create test807-2 --default-volumes-to-fs-backup
And everything looks fine. I would expect the same result when creating backup from schedule.
The output of the following commands will help us better understand what's going on:
This is the description of the backup from schedule:
Anything else you would like to add:
The schedule is:
Environment:
helm version
): v3.6.3helm list -n <YOUR NAMESPACE>
): non-relevantkubectl version
): 1.25.10/etc/os-release
): Debian GNU/Linux 11 (bullseye)The text was updated successfully, but these errors were encountered: