text improvement: We completed the Rancher backup and restore procedure and observed the following: Our Rancher management setup is deployed on two Kubernetes clusters: Primary Secondary (DR) The rancher url is load balanced between these two clusters with help of a traffic manager After taking a backup of Rancher on the primary cluster, bringing down the primary cluster, and restoring the backup on the DR cluster, we had to restart the Cattle system pods in every cluster that to points Rancher cluster. This is because the existing pods have an IP binding with the primary cluster. Can you please help me here