From 449f9ed8b570d1c9f27a373af8b87aeb336e1c34 Mon Sep 17 00:00:00 2001
From: PoAn Yang <yangpoan@gmail.com>
Date: Mon, 22 Jul 2024 17:43:03 +0800
Subject: [PATCH 1/2] feat: add content about vmimage backup

Signed-off-by: PoAn Yang <yangpoan@gmail.com>
---
 docs/vm/backup-restore.md | 37 +++----------------------------------
 1 file changed, 3 insertions(+), 34 deletions(-)

diff --git a/docs/vm/backup-restore.md b/docs/vm/backup-restore.md
index e91989e929e..85fcc3e00f8 100644
--- a/docs/vm/backup-restore.md
+++ b/docs/vm/backup-restore.md
@@ -84,42 +84,11 @@ You can choose to either delete or retain the previous volumes. By default, all
 
 ### Restore a new VM on another Harvester cluster
 
-_Available as of v1.0.0_
+_Available as of v1.4.0_
 
 Users can now restore a new VM on another cluster by leveraging the VM metadata & content backup feature.
-
-:::info prerequisites
-
-You must manually configure the virtual machine images with the same name on the new cluster first, otherwise the virtual machines will be failed to recover.
-
-:::
-
-#### Upload the same VM images to a new cluster
-
-1. Check the existing image name (normally starts with `image-`) and create the same one on the new cluster.
-```
-$ kubectl get vmimages -A
-NAMESPACE   NAME                               DISPLAY-NAME                              SIZE         AGE
-default     image-79hdq                        focal-server-cloudimg-amd64.img           566886400    5h36m
-default     image-l7924                        harvester-v1.0.0-rc2-amd64.iso            3964551168   137m
-default     image-lvqxn                        opensuse-leap-15.3.x86_64-nocloud.qcow2   568524800    5h35m
-```
-2. Apply a VM image YAML with the same name and content in the new cluster.
-```
-$ cat <<EOF | kubectl apply -f -
-apiVersion: harvesterhci.io/v1beta1
-kind: VirtualMachineImage
-metadata:
-  name: image-lvqxn
-  namespace: default
-spec:
-  displayName: opensuse-leap-15.3.x86_64-nocloud.qcow2
-  pvcName: ""
-  pvcNamespace: ""
-  sourceType: download
-  url: http://download.opensuse.org/repositories/Cloud:/Images:/Leap_15.3/images/openSUSE-Leap-15.3.x86_64-NoCloud.qcow2
-EOF
-```
+Harvester will handle VM image data automatically. If a volume is based on a VM image and there is a backup for it, Harvester will automatically sync the VM image to backup target.
+In a new cluster, it the VMbackup is restored to a new VM, Harvester will automatically create the VM image from the backup target.
 
 #### Restore a new VM in a new cluster
 

From eadf8777ff93f227833cc3a86ad9cfab1d38883a Mon Sep 17 00:00:00 2001
From: PoAn Yang <yangpoan@gmail.com>
Date: Mon, 5 Aug 2024 09:32:49 +0800
Subject: [PATCH 2/2] Update docs/vm/backup-restore.md

Co-authored-by: Jillian <67180770+jillian-maroket@users.noreply.github.com>
---
 docs/vm/backup-restore.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/vm/backup-restore.md b/docs/vm/backup-restore.md
index 85fcc3e00f8..e52fba8410e 100644
--- a/docs/vm/backup-restore.md
+++ b/docs/vm/backup-restore.md
@@ -87,7 +87,7 @@ You can choose to either delete or retain the previous volumes. By default, all
 _Available as of v1.4.0_
 
 Users can now restore a new VM on another cluster by leveraging the VM metadata & content backup feature.
-Harvester will handle VM image data automatically. If a volume is based on a VM image and there is a backup for it, Harvester will automatically sync the VM image to backup target.
+Harvester automatically handles VM image data. If a volume is based on a VM image with a backup, Harvester automatically syncs the VM image with the backup target.
 In a new cluster, it the VMbackup is restored to a new VM, Harvester will automatically create the VM image from the backup target.
 
 #### Restore a new VM in a new cluster