Use the following steps to restore the backed-up directory to the new primary node after a disaster:

1. Use PowerProtect Data Manager to perform a file-level recovery on the VM Image backup or the file system backup and restore the contents of the specific directory to the new primary node.

2. After the k8backupforDELLDR directory is restored, run the following etcdctl command to restore the etcd database to the point when the backup was taken:

ETCDCTL_API=3 etcdctl --endpoints=https://<etcd-server-IP>:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt \

--name=master \

--cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key \

--data-dir /var/lib/etcd-from-backup \

--initial-cluster=master=https://<etcd-server-IP>:2380 \

--initial-cluster-token etcd-cluster-1 \

--initial-advertise-peer-urls=https://<etcd-server-IP>:2380 \

snapshot restore /k8backupforDELLDR/etcd-snapshot.db

3. Modify the file /etc/kubernetes/manifests/etcd.yaml:

--data-dir=/var/lib/etcd-from-backup

Add entry : --initial-cluster-token=etcd-cluster-1

Change volumeMounts: -mountPath to /var/lib/etcd-from-backup

Change volumes: -hostPath to /var/lib/etcd-from-backup

4. Refresh the serviceaccount tokens for the application, default, and kube-system namespaces by removing the existing tokens in the serviceaccount config:

kubectl edit serviceaccount <serviceaccount-name> -n <namespace-name>

Verify new tokens are generated : kubectl get secrets -n <namespace-name>