velero use "exclude-namespaces" to backup not worked #3259
Replies: 9 comments 1 reply
-
Hi @liyan-su. I'd like to check - are you able to perform any backups without using |
Beta Was this translation helpful? Give feedback.
-
hi @zubron |
Beta Was this translation helpful? Give feedback.
-
Thanks for the info, @liyan-su! Did the backups using "exclude-namespaces" explicitly fail, or are they not completing? (Your original message said they were stuck in progress for a long time). |
Beta Was this translation helpful? Give feedback.
-
hi @zubron |
Beta Was this translation helpful? Give feedback.
-
I got the same behavior on my clusters. I detected that when using the --exclude-namespaces option the velero pod crashes and it is restarted then the backup gets stuck in "InProgress" but unfortunately the log does not display any error.
Also, I detected a similar behavior with other cluster trying to backup some namespaces individually. The velero pod crashes when try to list the events on that namespace and there are 50522. command: velero create backup ott --include-namespaces ott
the second namespace backup crashes in the same way when it is trying to list the configmaps and I have 1790 configmaps. adding some extra information. I have enabled the debug mode on my velero installation. here is the log before the pod restarted.
|
Beta Was this translation helpful? Give feedback.
-
hi @liyan-su I found that my issue was the limit of memory configured for the velero pod, after increasing the memory all worked for me. how is your pod memory configured? Regards. |
Beta Was this translation helpful? Give feedback.
-
hi @mozz-lx |
Beta Was this translation helpful? Give feedback.
-
I've been trying to reproduce this with a test case but I can't so far. I'm able to backup/restore 5K namespaces. @liyan-su Would you post the YAML that you are using to create the namespaces please? |
Beta Was this translation helpful? Give feedback.
-
@liyan-su: hi, has the issue been resolved. I am considering using exclude_namespaces, but if the issue hasn't been solved then I'd rather not use it. Thank you. |
Beta Was this translation helpful? Give feedback.
-
What steps did you take and what happened:
What did you expect to happen:
I hope velero can backup succefully, but status is "InProgress" for long time, I check backup details
and then check velero log, but didn't find any information about backup-exclude, I try many times, the result is the same.
root@3694960b654b: kubectl logs velero-6c8b8dc5db-sj42j -n velero
The output of the following commands will help us better understand what's going on:
(Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename>
orkubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
velero version
): v1.4.2_vmware.1velero client config get features
):kubectl version
):v1.18.8/etc/os-release
):Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
Beta Was this translation helpful? Give feedback.
All reactions