Forum Discussion

DerekHsueh's avatar
DerekHsueh
Level 4
12 months ago
Solved

Kubernetes namespace restore from snapshot copy returned partial success.

Hi Everyone

My NBU 10.3.0.1

My K8S v1.27.15 + Netapp storage with CSI (NFS)

I only create a namespace : test-for-backup , just for backup and restore test.

kubectl create ns test-for-backup

 

Netbackup start k8s backup , successful.

When restore k8s , the message show : 

Warning nbcs (pid=3718529) Namespace: test-for-backup-restore01, could not restore, ConfigMap "kube-root-ca.crt" already exists. Warning: the in-cluster version is different than the backed-up version
Warning nbcs (pid=3718529) Kubernetes namespace restore from snapshot copy returned partial success.

What does it mean ? partial success ?

Thank you.

  • bhdrkzltn's avatar
    bhdrkzltn
    12 months ago

    Those are the cluster level resources and K8s does not allow to restore. So it's expected to see restore job ends with EC1.

2 Replies

  • bhdrkzltn's avatar
    bhdrkzltn
    Level 4
    12 months ago

    Those are the cluster level resources and K8s does not allow to restore. So it's expected to see restore job ends with EC1.

  • DerekHsueh's avatar
    DerekHsueh
    Level 4
    12 months ago

    Veritas Support  :

    1. NBU will restore the Persistent Volume Claims (PVC). 
    2. As part of this restore process some Secrets and RoleBindings are created by the underlying Kubernetes system, this is part of how K8s works * IF one or more of these Secrets or RoleBindings already exist then the Velero SDK issues a warning stating: "Warning: the in-cluster version is different than the backed-up version." 
    3. Once the PVC(s) have been restored NetBackup proceeds to restore the namespace, pods, Secrets, RoleBindings, etc. So in essence we're saying that it is quite normal for some warnings to be generated, and these can generally be disregarded.