Skip to content

Commit 7404b73

Browse files
committed
add missing colons
1 parent c433eed commit 7404b73

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

articles/azure-vmware/backup-azure-netapp-files-datastores-vms.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Back up Azure NetApp Files datastores and VMs using Cloud Backup
33
description: Learn how to back up datastores and Virtual Machines to the cloud.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 08/10/2022
6+
ms.date: 08/12/2022
77
---
88

99
# Back up Azure NetApp Files datastores and VMs using Cloud Backup for Virtual Machines
@@ -59,15 +59,15 @@ Do not add VMs in an inaccessible state to a resource group. Although a resource
5959
### Considerations for resource groups
6060

6161
You can add or remove resources from a resource group at any time.
62-
* Back up a single resource
62+
* Back up a single resource: <br>
6363
To back up a single resource (for example, a single VM), you must create a resource group that contains that single resource.
64-
* Back up multiple resources
64+
* Back up multiple resources: <br>
6565
To back up multiple resources, you must create a resource group that contains multiple resources.
66-
* Optimize snapshot copies
66+
* Optimize snapshot copies: <br>
6767
To optimize snapshot copies, group the VMs and datastores that are associated with the same volume into one resource group.
68-
* Backup policies
68+
* Backup policies: <br>
6969
Although it's possible to create a resource group without a backup policy, you can only perform scheduled data protection operations when at least one policy is attached to the resource group. You can use an existing policy, or you can create a new policy while creating a resource group.
70-
* Compatibility checks
70+
* Compatibility checks: <br>
7171
Cloud Backup for VMs performs compatibility checks when you create a resource group. Reasons for incompatibility might be:
7272
* Virtual machine disks (VMDKs) are on unsupported storage.
7373
* A shared PCI device is attached to a VM.

articles/azure-vmware/restore-azure-netapp-files-vms.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Restore VMs using Cloud Backup for Virtual Machines
33
description: Learn how to restore virtual machines from a cloud backup to the vCenter.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 08/10/2022
6+
ms.date: 08/12/2022
77
---
88

99
# Restore VMs using Cloud Backup for Virtual Machines
@@ -35,11 +35,11 @@ You must have created a backup of the VM using the Cloud Backup for Virtual Mach
3535

3636
### Considerations for restoring VMs from backups
3737

38-
* VM is unregistered and registered again
38+
* VM is unregistered and registered again: <br>
3939
The restore operation for VMs unregisters the original VM, restores the VM from a backup snapshot, and registers the restored VM with the same name and configuration on the same ESXi server. You must manually add the VMs to resource groups after the restore.
40-
* Restoring datastores
40+
* Restoring datastores: <br>
4141
You cannot restore a datastore, but you can restore any VM in the datastore.
42-
* VMware consistency snapshot failures for a VM
42+
* VMware consistency snapshot failures for a VM: <br>
4343
Even if a VMware consistency snapshot for a VM fails, the VM is nevertheless backed up. You can view the entities contained in the backup copy in the Restore wizard and use it for restore operations.
4444

4545
### Restore a VM from a backup

0 commit comments

Comments
 (0)