Skip to content

Commit dcc1f53

Browse files
minor changes
1 parent 751c7fd commit dcc1f53

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/backup/backup-azure-arm-restore-vms.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,8 @@ Some details about storage accounts:
4040
- **Storage type**: Blob storage isn't supported.
4141
- **Storage redundancy**: Zone redundant storage (ZRS) isn't supported. The replication and redundancy information for the account is shown in parentheses after the account name.
4242
- **Premium storage**:
43-
- When restoring non-premium VMs, premium storage accounts aren't supported.
44-
- When restoring managed VMs, premium storage accounts configured with network rules aren't supported.
43+
- When you restore non-premium VMs, premium storage accounts aren't supported.
44+
- When you restore managed VMs, premium storage accounts configured with network rules aren't supported.
4545

4646
## Before you start
4747

@@ -224,7 +224,7 @@ In summary, the **Availability Zone** will only appear when
224224

225225
## Restoring unmanaged VMs and disks as managed
226226

227-
You're provided with an option to restore [unmanaged disks](../storage/common/storage-disaster-recovery-guidance.md#azure-unmanaged-disks) as [managed disks](../virtual-machines/managed-disks-overview.md) during restore. By default, the unmanaged VMs / disks are restored as unmanaged VMs / disks. However, if you choose to restore as managed VMs / disks, it's now possible to do so. These restores aren't triggered from the snapshot phase but only from the vault phase. This feature isn't available for unmanaged encrypted VMs.
227+
You're provided with an option to restore [unmanaged disks](../storage/common/storage-disaster-recovery-guidance.md#azure-unmanaged-disks) as [managed disks](../virtual-machines/managed-disks-overview.md) during restore. By default, the unmanaged VMs / disks are restored as unmanaged VMs / disks. However, if you choose to restore as managed VMs / disks, it's now possible to do so. These restore aren't triggered from the snapshot phase but only from the vault phase. This feature isn't available for unmanaged encrypted VMs.
228228

229229
![Restore as managed disks](./media/backup-azure-arm-restore-vms/restore-as-managed-disks.png)
230230

@@ -240,7 +240,7 @@ There are many common scenarios in which you might need to restore VMs.
240240
**Restore VMs with special network configurations** | Special network configurations include VMs using internal or external load balancing, using multiple NICS, or multiple reserved IP addresses. You restore these VMs by using the [restore disk option](#restore-disks). This option makes a copy of the VHDs into the specified storage account, and you can then create a VM with an [internal](../load-balancer/quickstart-load-balancer-standard-internal-powershell.md) or [external](../load-balancer/quickstart-load-balancer-standard-public-powershell.md) load balancer, [multiple NICS](../virtual-machines/windows/multiple-nics.md), or [multiple reserved IP addresses](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-powershell.md), in accordance with your configuration.
241241
**Network Security Group (NSG) on NIC/Subnet** | Azure VM backup supports Backup and Restore of NSG information at vnet, subnet, and NIC level.
242242
**Zone Pinned VMs** | If you back up an Azure VM that's pinned to a zone (with Azure Backup), then you can restore it in the same zone where it was pinned. [Learn more](../availability-zones/az-overview.md)
243-
**Restore VM in any availability set** | When restoring a VM from the portal, there's no option to choose an availability set. A restored VM doesn't have an availability set. If you use the restore disk option, then you can [specify an availability set](../virtual-machines/windows/tutorial-availability-sets.md) when you create a VM from the disk using the provided template or PowerShell.
243+
**Restore VM in any availability set** | When you restore a VM from the portal, there's no option to choose an availability set. A restored VM doesn't have an availability set. If you use the restore disk option, then you can [specify an availability set](../virtual-machines/windows/tutorial-availability-sets.md) when you create a VM from the disk using the provided template or PowerShell.
244244
**Restore special VMs such as SQL VMs** | If you're backing up a SQL VM using Azure VM backup and then use the restore VM option or create a VM after restoring disks, then the newly created VM must be registered with the SQL provider as mentioned [here](/azure/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm?tabs=azure-cli%2cbash). This will convert the restored VM into a SQL VM.
245245

246246
### Restore domain controller VMs

articles/backup/backup-azure-security-feature-cloud.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ If items were deleted before soft-delete was disabled, then they'll be in a soft
147147

148148
### Do I need to enable the soft-delete feature on every vault?
149149

150-
No, it's built-in and enabled by default for all the Recovery Services vaults.
150+
No, it's a built-in feature and enabled by default for all the Recovery Services vaults.
151151

152152
### Can I configure the number of days for which my data will be retained in soft-deleted state after the delete operation is complete?
153153

@@ -169,13 +169,13 @@ Yes.
169169

170170
Undelete followed by a resume operation will protect the resource again. The resume operation associates a backup policy to trigger the scheduled backups with the selected retention period. Also, the garbage collector runs as soon as the resume operation completes. If you wish to perform a restore from a recovery point that's past its expiration date, you're advised to do it before triggering the resume operation.
171171

172-
### Can I delete my vault if there are soft deleted items in the vault?
172+
### Can I delete my vault if there are soft-deleted items in the vault?
173173

174174
The Recovery Services vault can't be deleted if there are backup items in soft-deleted state in the vault. The soft-deleted items are permanently deleted 14 days after the delete operation. If you can't wait for 14 days, then [disable soft delete](#enabling-and-disabling-soft-delete), undelete the soft deleted items, and delete them again to permanently get deleted. After ensuring there are no protected items and no soft deleted items, the vault can be deleted.
175175

176176
### Can I delete the data earlier than the 14 days soft-delete period after deletion?
177177

178-
No. You can't force delete the soft-deleted items. They're automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes. You should wait for 14 days before performing any other action on the item. Soft-deleted items won't be charged. If you need to reprotect the items marked for soft-delete within 14 days in a new vault, then contact Microsoft support.
178+
No. You can't force-delete the soft-deleted items. They're automatically deleted after 14 days. This security feature is enabled to safeguard the backed-up data from accidental or malicious deletes. You should wait for 14 days before performing any other action on the item. Soft-deleted items won't be charged. If you need to reprotect the items marked for soft-delete within 14 days in a new vault, then contact Microsoft support.
179179

180180
### Can soft delete operations be performed in PowerShell or CLI?
181181

articles/backup/backup-center-monitor-operate.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Azure Backup provides a set of built-in metrics via Azure Monitor that allows yo
7474

7575
Azure Backup offers the following key capabilities:
7676

77-
* Ability to view out-of-the-box metrics related to backup and restore health of your backup items along with associated trends.
77+
* Ability to view out-of-the-box metrics related to back up and restore health of your backup items along with associated trends.
7878
* Ability to write custom alert rules on these metrics to efficiently monitor the health of your backup items.
7979
* Ability to route fired metric alerts to different notification channels supported by Azure Monitor, such as email, ITSM, webhook, logic apps, and so on.
8080

@@ -97,7 +97,7 @@ Currently, the following types of alerts are displayed in Backup center:
9797
>- Currently, Backup center displays only alerts for Azure-based workloads. To view alerts for on-premises resources, go to the Recovery Services vault and click **Alerts** from the menu.
9898
>- Backup center displays only Azure Monitor alerts. Alerts raised by the older alerting solution (accessed under the [Backup Alerts](backup-azure-monitoring-built-in-monitor.md#backup-alerts-in-recovery-services-vault) tab in Recovery Services vault) aren't displayed in Backup center.
9999
100-
For more details about Azure Monitor alerts, see [Overview of alerts in Azure](../azure-monitor/alerts/alerts-overview.md).
100+
For more information about Azure Monitor alerts, see [Overview of alerts in Azure](../azure-monitor/alerts/alerts-overview.md).
101101

102102
### Datasource and Global Alerts
103103

0 commit comments

Comments
 (0)