From bd6a6b446fb3e461abbf52e973ac3acf16e48484 Mon Sep 17 00:00:00 2001 From: nidhi251289 Date: Tue, 10 Feb 2026 13:28:18 +0100 Subject: [PATCH 1/4] Added the workaround for Back up documentation --- .../docs/deployment/mx-azure/mx-azure-backups.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index 60e76a5091b..6752f4b27cf 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -65,6 +65,10 @@ To delete a backup snapshot, perform the following steps: ## Restoring a Backup Snapshot {#restore-backup} +{{% alert color="warning" %}} +Restore backup is only supported within the same namespace. For the workaround to restore across namespaces, see [Known Limitations](#known-limitations). +{{% /alert %}} + {{% alert color="info" %}} Restore requires **Manage Apps Backups** and **Stop Apps** permissions on the namespace. {{% /alert %}} @@ -135,8 +139,14 @@ Automatic backups only run when the app is deployed. If the first nightly backup occurs after the first Sunday, no monthly backup will be retained that month. Download a nightly or weekly backup to extend retention. -## Known Limitations +## Known Limitations{#known-limitations} * Partial data restoration may occur if a restore process fails. * No API support exists currently for backup and restore. -* Although the portal UI suggests cross-namespace restores, only restores within the same namespace are supported. +* Although the portal UI suggests cross-namespace restores, only restores within the **same namespace** are supported. + +Below is the supported workaround to restore across namespaces: +1. Retrieve Snapshot: Download the desired backup snapshot from your source environment to your local machine. +2. Transfer Snapshot: Upload the downloaded backup snapshot from your local machine to the target environment. +3. Initiate Restoration: Begin the restore process within the target environment using the newly uploaded backup snapshot. + From 7a142d6df6d614cbc1387bd68a7fea05995e44d9 Mon Sep 17 00:00:00 2001 From: nidhi251289 Date: Wed, 11 Feb 2026 08:56:50 +0100 Subject: [PATCH 2/4] Replaced namespace with cluster --- content/en/docs/deployment/mx-azure/mx-azure-backups.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index 6752f4b27cf..a42090c5796 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -66,7 +66,7 @@ To delete a backup snapshot, perform the following steps: ## Restoring a Backup Snapshot {#restore-backup} {{% alert color="warning" %}} -Restore backup is only supported within the same namespace. For the workaround to restore across namespaces, see [Known Limitations](#known-limitations). +Restore backup is only supported within the same cluster. For the workaround to restore across clusters, see [Known Limitations](#known-limitations). {{% /alert %}} {{% alert color="info" %}} @@ -143,9 +143,9 @@ If the first nightly backup occurs after the first Sunday, no monthly backup wil * Partial data restoration may occur if a restore process fails. * No API support exists currently for backup and restore. -* Although the portal UI suggests cross-namespace restores, only restores within the **same namespace** are supported. +* Although the portal UI suggests cross-cluster restores, only restores within the **same cluster** are supported. -Below is the supported workaround to restore across namespaces: +Below is the supported workaround to restore across cluster: 1. Retrieve Snapshot: Download the desired backup snapshot from your source environment to your local machine. 2. Transfer Snapshot: Upload the downloaded backup snapshot from your local machine to the target environment. 3. Initiate Restoration: Begin the restore process within the target environment using the newly uploaded backup snapshot. From 3d4ef0ba19260b595d02bee5b52e3421741ff216 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Fri, 13 Feb 2026 12:00:56 +0100 Subject: [PATCH 3/4] Update mx-azure-backups.md --- content/en/docs/deployment/mx-azure/mx-azure-backups.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index a42090c5796..8cf7ab2d3d1 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -66,7 +66,7 @@ To delete a backup snapshot, perform the following steps: ## Restoring a Backup Snapshot {#restore-backup} {{% alert color="warning" %}} -Restore backup is only supported within the same cluster. For the workaround to restore across clusters, see [Known Limitations](#known-limitations). +Restoring a backup is only supported within the same cluster. For the workaround to restore backups across clusters, see [Known Limitations](#known-limitations). {{% /alert %}} {{% alert color="info" %}} @@ -139,7 +139,7 @@ Automatic backups only run when the app is deployed. If the first nightly backup occurs after the first Sunday, no monthly backup will be retained that month. Download a nightly or weekly backup to extend retention. -## Known Limitations{#known-limitations} +## Known Limitations {#known-limitations} * Partial data restoration may occur if a restore process fails. * No API support exists currently for backup and restore. From 4654c7d81ae81ce145d57b98e46593238d31e9e1 Mon Sep 17 00:00:00 2001 From: katarzyna-koltun-mx <108737161+katarzyna-koltun-mx@users.noreply.github.com> Date: Fri, 13 Feb 2026 12:02:56 +0100 Subject: [PATCH 4/4] Update mx-azure-backups.md --- .../en/docs/deployment/mx-azure/mx-azure-backups.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/en/docs/deployment/mx-azure/mx-azure-backups.md b/content/en/docs/deployment/mx-azure/mx-azure-backups.md index 8cf7ab2d3d1..61353b5e3b6 100644 --- a/content/en/docs/deployment/mx-azure/mx-azure-backups.md +++ b/content/en/docs/deployment/mx-azure/mx-azure-backups.md @@ -143,10 +143,11 @@ If the first nightly backup occurs after the first Sunday, no monthly backup wil * Partial data restoration may occur if a restore process fails. * No API support exists currently for backup and restore. -* Although the portal UI suggests cross-cluster restores, only restores within the **same cluster** are supported. +* Although the portal UI suggests that cross-cluster backup restorations are, only restorations within the same cluster are actually supported. -Below is the supported workaround to restore across cluster: -1. Retrieve Snapshot: Download the desired backup snapshot from your source environment to your local machine. -2. Transfer Snapshot: Upload the downloaded backup snapshot from your local machine to the target environment. -3. Initiate Restoration: Begin the restore process within the target environment using the newly uploaded backup snapshot. +As a workaround, you can restore a backup across clusters by performing the following steps: + +1. Download the backup snapshot from your source environment to your local machine. +2. Upload the downloaded backup snapshot from your local machine to the target environment. +3. Begin the restore process within the target environment using the newly uploaded backup snapshot.