You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/backup-azure-netapp-files-datastores-vms.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Back up Azure NetApp Files datastores and VMs using Cloud Backup
3
3
description: Learn how to back up datastores and Virtual Machines to the cloud.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 12/03/2024
6
+
ms.date: 1/30/2026
7
7
ms.author: anfdocs
8
8
ms.custom: engagement-fy23
9
9
# Customer intent: "As an IT administrator, I want to back up Azure NetApp Files datastores and Virtual Machines to the cloud, so that I can ensure data protection and quick recovery in case of data loss or system failures."
@@ -112,7 +112,7 @@ You can add or remove resources from a resource group at any time.
112
112
When you select **Next**, the system first checks that Cloud Backup for Virtual Machines manages and is compatible with the storage on which the selected resources are located.
113
113
114
114
>[!IMPORTANT]
115
-
>If you receive the message `selected <resource-name> is not Cloud Backup for Virtual Machines compatible` then a selected resource is not compatible with Cloud Backup for Virtual Machines.
115
+
>If you receive the message `selected <resource-name> is not Cloud Backup for Virtual Machines compatible` that means that a selected resource isn't compatible with Cloud Backup for virtual machines.
116
116
117
117
1. On the **Spanning disks** page, select an option for VMs with multiple VMDKs across multiple datastores:
118
118
* Always exclude all spanning datastores
@@ -153,7 +153,7 @@ Backup operations are performed on all the resources defined in a resource group
153
153
154
154
* You must have a resource group created with a policy attached.
155
155
>[!NOTE]
156
-
> Do not start an on-demand backup job when a job to back up the Cloud Backup for Virtual Machines MySQL database is already running. Use the maintenance console to see the configured backup schedule for the MySQL database.
156
+
> Don't start an on-demand backup job when a job to back up the Cloud Backup for Virtual Machines MySQL database is already running. Use the maintenance console to see the configured backup schedule for the MySQL database.
157
157
158
158
### Back up resource groups on demand
159
159
@@ -165,9 +165,9 @@ Backup operations are performed on all the resources defined in a resource group
165
165
166
166
1. Select **OK** to initiate the backup.
167
167
>[!NOTE]
168
-
>You can't rename a backup once it's created.
168
+
>After a backup is created, you can't rename it.
169
169
1. **Optional:** Monitor the operation progress by selecting **Recent Tasks** at the bottom of the window or on the dashboard Job Monitor for more details.
170
-
If the pause operation fails for any of the VMs in the backup, then the backup completes with a warning. It's marked as not VM-consistent even if the selected policy has VM consistency selected. In this case, it's possible that some of the VMs were successfully paused. In the job monitor, the failed VM details show the pause operation as failed.
170
+
If the pause operation fails for any of the VMs in the backup, then the backup completes with a warning. It gets marked as not VM-consistent even if the selected policy has VM consistency selected. In this case, it's possible that some of the VMs were successfully paused. In the job monitor, the failed VM details show the pause operation as failed.
0 commit comments