Skip to content

Commit be4c102

Browse files
author
AbhishekMallick-MS
committed
Freshness - Az Backup Glossary
1 parent c55cfad commit be4c102

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

articles/backup/azure-backup-glossary.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Backup glossary
33
description: This article defines terms helpful for use with Azure Backup.
44
ms.topic: conceptual
55
ms.custom: devx-track-azurepowershell, devx-track-arm-template, devx-track-azurecli
6-
ms.date: 12/21/2020
6+
ms.date: 01/22/2024
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
99
---
@@ -23,7 +23,7 @@ Refer to [Azure Files documentation](../storage/files/storage-files-introduction
2323

2424
## Alternate location recovery
2525

26-
A recovery done from the recovery point to a location other than the original location where the backups were taken. When using Azure VM backup, this would mean restoring the VM to a server other than the original server where the backups were taken. When using Azure File share backup, this would mean restoring data to a file share that is different from the backed-up file share.
26+
A recovery done from the recovery point to a location other than the original location where the backups were taken. When you use Azure VM backup, this would mean to restore the VM to a server other than the original server where the backups were taken. When you use Azure File share backup, this would mean to restore data to a file share that is different from the backed-up file share.
2727

2828
## Application consistent backup
2929

@@ -200,7 +200,7 @@ Refer to the [Managed disks documentation](../virtual-machines/managed-disks-ove
200200

201201
(Workload-specific term)
202202

203-
Also known as **Azure Backup agent** or **Recovery Services agent**, the MARS agent is used by Azure Backup to back up data from on-premises machines and Azure VMs to a backup Recovery Services vault in Azure. [Learn more](backup-support-matrix-mars-agent.md).
203+
This is also known as **Azure Backup agent** or **Recovery Services agent**, the MARS agent is used by Azure Backup to back up data from on-premises machines and Azure VMs to a backup Recovery Services vault in Azure. [Learn more](backup-support-matrix-mars-agent.md).
204204

205205
## NSG (Network Security Group)
206206

@@ -216,7 +216,7 @@ A backup job that is triggered by a user on a one-time need basis, and not based
216216

217217
## Original location recovery (OLR)
218218

219-
A recovery done from the restore point to the source location from where the backups were taken, replacing it with the state stored in the recovery point. When using Azure VM backup, this would mean restoring the VM to the original server where the backups were taken. When using Azure File share backup, this would mean restoring data to the backed-up file share.
219+
A recovery done from the restore point to the source location from where the backups were taken, replacing it with the state stored in the recovery point. When you use Azure VM backup, this would mean to restore the VM to the original server where the backups were taken. When you use Azure File share backup, this would mean to restore data to the backed-up file share.
220220

221221
## Passphrase
222222

@@ -310,6 +310,10 @@ Currently, Azure Backup supports the following backup storage tiers:
310310

311311
Backup data for all workloads supported by Azure Backup is stored in vaults which hold backup storage, an auto-scaling set of storage accounts managed by Azure Backup. The Vault-Standard tier is an online storage tier that enables you to store an isolated copy of backup data in a Microsoft managed tenant, thus creating an additional layer of protection. For workloads where snapshot tier is supported, there is a copy of the backup data in both the snapshot tier and the vault-standard tier. Vault-standard tier ensures that backup data is available even if the datasource being backed up is deleted or compromised.
312312

313+
## Trusted Access
314+
315+
Many Azure services depend on clusterAdmin kubeconfig and the publicly accessible kube-apiserver endpoint to access AKS clusters. The AKS Trusted Access feature enables you to bypass the private endpoint restriction. Without using Microsoft Entra application, this feature enables you to give explicit consent to your system-assigned identity of allowed resources to access your AKS clusters using an Azure resource RoleBinding. The Trusted Access feature allows you to access AKS clusters with different configurations, which aren't limited to private clusters, clusters with local accounts disabled, Microsoft Entra ID clusters, and authorized IP range clusters. [Learn more](azure-kubernetes-service-cluster-backup-concept.md#trusted-access).
316+
313317
## Unmanaged disk
314318

315319
Refer to the [Unmanaged disks documentation](../storage/common/storage-disaster-recovery-guidance.md#azure-unmanaged-disks).

0 commit comments

Comments
 (0)