From ec25c8c7316a74f574cb065032adea7f28ffaef5 Mon Sep 17 00:00:00 2001 From: PoAn Yang Date: Wed, 16 Oct 2024 16:02:53 +0800 Subject: [PATCH] Update docs/vm/backup-restore.md Co-authored-by: Jillian <67180770+jillian-maroket@users.noreply.github.com> --- docs/vm/backup-restore.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/vm/backup-restore.md b/docs/vm/backup-restore.md index 0af423a923..3dd273335d 100644 --- a/docs/vm/backup-restore.md +++ b/docs/vm/backup-restore.md @@ -182,19 +182,21 @@ _Available as of v1.4.0_ Volumes consume extra disk space in the cluster whenever you create a new virtual machine backup or snapshot. To manage this, you can configure space usage limits at the namespace and virtual machine levels. The configured values represent the maximum amount of disk space that can be used by all backups and snapshots. No limits are set by default. -### Set Snapshot Space Usage Limit at Namespace Level +### Configure the Snapshot Space Usage Limit at the Namespace Level -1. Go to the `Namespaces` page and click `Edit Quota` button. +1. Go to the **Namespaces** screen. -![edit-quota-namespace.png](/img/v1.4/vm/edit-quota-namespace.png) +1. Locate the target namespace, and then select **⋮ > Edit Quota**. -2. Fill the `Total Snapshot Size` field and click `Save`. + ![edit-quota-namespace.png](/img/v1.4/vm/edit-quota-namespace.png) + +1. Specify the maximum amount of disk space that can be consumed by all snapshots in the namespace, and then and click **Save**. -![edit-quota-namespace-save.png](/img/v1.4/vm/edit-quota-namespace-save.png) + ![edit-quota-namespace-save.png](/img/v1.4/vm/edit-quota-namespace-save.png) -3. Check the `Total Snapshot Size` field in the `Namespaces` page. +1. Verify that the configured value is displayed on the **Namespaces** screen. -![edit-quota-namespace-read.png](/img/v1.4/vm/edit-quota-namespace-read.png) + ![edit-quota-namespace-read.png](/img/v1.4/vm/edit-quota-namespace-read.png) ### Set Snapshot Space Usage Limit at VM Level