diff --git a/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md b/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
index 3c10d9d37e2..74378e009fa 100644
--- a/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
+++ b/content/rancher/v2.x/en/backups/rollbacks/ha-server-rollbacks/_index.md
@@ -3,6 +3,7 @@ title: Roll Backs—High Availability Installs
 weight: 50
 aliases:
   - /rancher/v2.x/en/upgrades/rollbacks/ha-server-rollbacks/
+  - /rancher/v2.x/en/backups/restorations/ha-restoration
 ---
 
 There are two scenarios where you'll need to rollback to prior image of Rancher. The instructions change slightly for each scenario.
diff --git a/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md b/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md
index 3b97214f35b..4ef752240bd 100644
--- a/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md
+++ b/content/rancher/v2.x/en/installation/ha-server-install-external-lb/_index.md
@@ -331,7 +331,7 @@ During installation, RKE automatically generates a config file named `kube_confi
 
 You have a couple of options:
 
-- Create a backup of your Rancher Server in case of a disaster scenario: [High Availablility Back Up and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/ha-backup-and-restoration).
+- Create a backup of your Rancher Server in case of a disaster scenario: [High Availablility Back Up and Restoration]({{< baseurl >}}/rancher/v2.x/en/backups/backups/ha-backups).
 - Create a Kubernetes cluster: [Creating a Cluster]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/creating-a-cluster/).
 
 <br/>
diff --git a/content/rancher/v2.x/en/installation/single-node-install/_index.md b/content/rancher/v2.x/en/installation/single-node-install/_index.md
index 6e16cafbc2f..22419a7bed8 100644
--- a/content/rancher/v2.x/en/installation/single-node-install/_index.md
+++ b/content/rancher/v2.x/en/installation/single-node-install/_index.md
@@ -164,7 +164,7 @@ Run the following commands from your Linux host.
 
 You have a couple of options:
 
-- Create a backup of your Rancher Server in case of a disaster scenario: [Single Node Backup and Restoration]({{< baseurl >}}/rancher/v2.x/en/installation/backups-and-restoration/single-node-backup-and-restoration/).
+- Create a backup of your Rancher Server in case of a disaster scenario: [Single Node Backup and Restoration]({{< baseurl >}}/rancher/v2.x/en/backups/rollbacks/single-node-rollbacks).
 - Create a Kubernetes cluster: [Provisioning Kubernetes Clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/).
 
 <br/>
diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
index f0631f3b1b6..7475c5e6841 100644
--- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
+++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md
@@ -66,4 +66,4 @@ docker run -d --volumes-from rancher-data --restart=unless-stopped \
 
 **Result:** Rancher Server is upgraded to the latest version.
 
->**Note:** If your upgrade does not complete successfully, you can roll Rancher Server and its data back to its last healthy state. For more information, see [Restoring Backups—Single Node Installs]({{< baseurl >}}/rancher/v2.x/en/backups/restorations/single-node-restoration/).
+>**Note:** If your upgrade does not complete successfully, you can roll Rancher Server and its data back to its last healthy state. For more information, see [Restoring Backups—Single Node Installs]({{< baseurl >}}/rancher/v2.x/en/backups/rollbacks/single-node-rollbacks).