Velero- 特定命名空间的还原部分失败

问：

所以我遇到了以下问题，我想备份和恢复我在 Openshift 集群上拥有的特定命名空间（演示）。备份已成功完成，但是当我尝试还原时，每次都部分失败。我最后一次尝试，状态更改为“已完成”，但容器无法正确构建，导致无法拉取或推送映像。

我读到至少在恢复过程中应该排除 CSV 等系统资源 [在以下链接中][1] [1]
：https://docs.openshift.com/container-platform/4.9/backup_and_restore/application_backup_and_restore/troubleshooting.html

这是我一直在尝试的命令，并针对我收到的警告和错误对其进行了多次修改

velero restore create --from-backup demo \
--exclude-resources=configmaps/kube-root-ca.crt,configmaps/openshift-service-ca.crt,builds,rolebindings,clusterserviceversions.operators.coreos.com,imagetags.image.openshift.io

我目前收到的错误和警告：

Warnings:   Velero:     <none>   Cluster:  could not restore, CustomResourceDefinition "clusterserviceversions.operators.coreos.com" already exists. Warning: the in-cluster version is different than the backed-up version.   Namespaces:
    demo:  could not restore, ConfigMap "kube-root-ca.crt" already exists. Warning: the in-cluster version is different than the backed-up version.
           could not restore, ConfigMap "openshift-service-ca.crt" already exists. Warning: the in-cluster version is different than the backed-up version.
           could not restore, RoleBinding "system:deployers" already exists. Warning: the in-cluster version is different than the backed-up version.
           could not restore, RoleBinding "system:image-builders" already exists. Warning: the in-cluster version is different than the backed-up version.
           could not restore, RoleBinding "system:image-pullers" already exists. Warning: the in-cluster version is different than the backed-up version.

Backup:  demo-backup-full

Namespaces:   Included:  all namespaces found in the backup   Excluded:  <none>

Resources:   Included:        *   Excluded:        configmaps/kube-root-ca.crt, configmaps/openshift-service-ca.crt, builds, rolebindings, clusterserviceversions.operators.coreos.com, imagetags.image.openshift.io, nodes, events, events.events.k8s.io, backups.velero.io, restores.velero.io, resticrepositories.velero.io, csinodes.storage.k8s.io, volumeattachments.storage.k8s.io, backuprepositories.velero.io   Cluster-scoped:  auto

Namespace mappings:  <none>

Label selector:  <none>

Restore PVs:  auto

Existing Resource Policy:   <none> ItemOperationTimeout:       1h0m0s

请帮忙，因为我一直在为这个问题而苦苦挣扎。