search

vmware-tanzu / velero

Backup and migrate Kubernetes applications and their persistent volumes
https://velero.io
Apache License 2.0
8.69k stars 1.4k forks source link

Scheduled backups are being taken but velero get schedules doesnt show any data #8050

Closed vishalc95 closed 3 weeks ago

vishalc95 commented 3 months ago

vishakumar@VISHAKUMAR-LT1:~$ velero get backups NAME STATUS ERRORS WARNINGS CREATED EXPIRES STORAGE LOCATION SELECTOR backup-infra-ns-twiceaweek-20240725053637 Completed 0 1 2024-07-25 11:06:37 +0530 IST 179d default backup-infra-ns-twiceaweek-20240721173634 Completed 0 1 2024-07-21 23:06:34 +0530 IST 176d default backup-infra-ns-twiceaweek-20240718053631 Completed 0 1 2024-07-18 11:06:31 +0530 IST 172d default backup-infra-ns-twiceaweek-20240714173628 Completed 0 1 2024-07-14 23:06:28 +0530 IST 169d default backup-infra-ns-twiceaweek-20240711053624 Completed 0 1 2024-07-11 11:06:24 +0530 IST 165d default backup-infra-ns-twiceaweek-20240707173621 Completed 0 1 2024-07-07 23:06:21 +0530 IST 162d default backup-infra-ns-twiceaweek-20240704053618 Completed 0 1 2024-07-04 11:06:18 +0530 IST 158d default kube-system-ns Completed 0 0 2024-07-04 11:04:24 +0530 IST 8d default whole-prodcluster-every-2days-20240725053737 Completed 0 2 2024-07-25 11:07:37 +0530 IST 179d default whole-prodcluster-every-2days-20240723053735 Completed 0 2 2024-07-23 11:07:35 +0530 IST 177d default whole-prodcluster-every-2days-20240721053733 Completed 0 2 2024-07-21 11:07:33 +0530 IST 175d default

======================================================= vishakumar@VISHAKUMAR-LT1:~$ velero get schedules vishakumar@VISHAKUMAR-LT1:~$ vishakumar@VISHAKUMAR-LT1:~$ vishakumar@VISHAKUMAR-LT1:~$ velero get schedules -n velero vishakumar@VISHAKUMAR-LT1:~$ vishakumar@VISHAKUMAR-LT1:~$ k get schedules -A No resources found vishakumar@VISHAKUMAR-LT1:~$

============================================================= vishakumar@VISHAKUMAR-LT1:~$ velero version Client: Version: v1.8.0 Git commit: a818c97dde2034385d7bf25e0ac2a2e055a0b372 Server: Version: v1.8.0

====================================================

Logs : Describe output of one the scheduled backup -

vishakumar@VISHAKUMAR-LT1:~$ velero backup describe backup-infra-ns-twiceaweek-20240725053637 Name: backup-infra-ns-twiceaweek-20240725053637 Namespace: velero Labels: velero.io/schedule-name=backup-infra-ns-twiceaweek velero.io/storage-location=default Annotations: velero.io/source-cluster-k8s-gitversion=v1.16.3 velero.io/source-cluster-k8s-major-version=1 velero.io/source-cluster-k8s-minor-version=16

Phase: Completed

Errors: 0 Warnings: 1

Namespaces: Included: kube-system, default, blossom-system, trident, jenkins-system, certify-system-ns, kube-public Excluded:

Resources: Included: * Excluded: Cluster-scoped: auto

Label selector:

Storage Location: default

Velero-Native Snapshot PVs: auto

TTL: 4320h0m0s

Hooks:

blackpiglet commented 3 months ago

Is it possible those backups are synced from another cluster? If there is more than one k8s cluster installed with Velero, and they all share the same Backup Storage(BSL), then the backups are synced between them.

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands.

github-actions[bot] commented 3 weeks ago

This issue was closed because it has been stalled for 14 days with no activity.