Skip to content

Commit 9c5c95b

Browse files
authored
Merge pull request #230201 from mepand/patch-56
Update blob-backup-configure-manage.md
2 parents 914ca2e + 2907864 commit 9c5c95b

File tree

1 file changed

+2
-63
lines changed

1 file changed

+2
-63
lines changed

articles/backup/blob-backup-configure-manage.md

Lines changed: 2 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ For instructions on how to create a Backup vault, see the [Backup vault document
4545

4646
Operational backup also protects the storage account (that contains the blobs to be protected) from any accidental deletions by applying a Backup-owned Delete Lock. This requires the Backup vault to have certain permissions on the storage accounts that need to be protected. For convenience of use, these minimum permissions have been consolidated under the **Storage Account Backup Contributor** role.
4747

48-
We recommend you to assign this role to the Backup vault before you configure backup. However, you can also perform the role assignment while configuring backup. [Learn more](#using-backup-center) on configure backup using Backup Center.
48+
We recommend you to assign this role to the Backup vault before you configure backup. However, you can also perform the role assignment while configuring backup.
4949

5050
To assign the required role for storage accounts that you need to protect, follow these steps:
5151

@@ -145,68 +145,7 @@ To configure backup for storage accounts, follow these steps:
145145

146146
You'll receive notifications about the status of configuring protection and its completion.
147147

148-
### Using Backup Center
149-
150-
To start configuring backup:
151-
152-
1. Search for **Backup Center** in the search bar.
153-
154-
1. Go to **Overview** > **+Backup**.
155-
156-
![Backup Center overview](./media/blob-backup-configure-manage/backup-center-overview.png)
157-
158-
1. On the **Initiate: Configure Backup** tab, choose **Azure Blobs (Azure Storage)** as the DataSource type.
159-
160-
![Initiate: Configure Backup tab](./media/blob-backup-configure-manage/initiate-configure-backup.png)
161-
162-
1. On the **Basics** tab, specify **Azure Blobs (Azure Storage)** as the DataSource type, and select the Backup vault to which you want to associate your storage accounts.<br></br>You can view details of the selected vault in the same pane.
163-
164-
![Basics tab](./media/blob-backup-configure-manage/basics-tab.png)
165-
166-
>[!NOTE]
167-
>Only operational backups will be enabled for blobs, which stores backups in the source storage account (and not in the Backup vault). So, the backup storage redundancy type selected for the vault doesn’t apply for the backup of blobs.
168-
169-
1. Select the backup policy that you want to use for specifying the retention.<br></br>You can view the details of the selected policy in the bottom part of the screen. The operational data store column displays the retention defined in the policy. **Operational** implies that the data is maintained locally in the source storage account.
170-
171-
![Choose backup policy](./media/blob-backup-configure-manage/choose-backup-policy.png)
172-
173-
You can also create a new backup policy. To do this, select **Create new** and follow these steps:
174-
175-
1. Provide a name for the policy you want to create.<br></br>Ensure that the other boxes display the correct DataSource type and Vault name.
176-
177-
1. On the **Backup policy** tab, select the **Edit retention rule** icon for the retention rule to modify the duration for the data retention.<br></br>You can set the retention up to **360** days.
178-
179-
>[!NOTE]
180-
>While backups are unaffected by the retention period, the restore operation for restoring older backups might take longer to complete.
181-
182-
![Create new backup policy](./media/blob-backup-configure-manage/new-backup-policy.png)
183-
184-
1. Select **Review + create** to create the backup policy.
185-
186-
1. Choose the required storage accounts for configuring protection of blobs. You can choose multiple storage accounts at once and choose Select.<br></br>However, ensure that the vault you have chosen has the required Azure role-based access control (Azure RBAC) role assigned to configure backup on storage accounts. Learn more about [Grant permissions to the Backup vault on storage accounts](#grant-permissions-to-the-backup-vault-on-storage-accounts).<br></br>If the role isn't assigned, you can still assign the role while configuring backup. See step 7.
187-
188-
![Verify permissions of the vault](./media/blob-backup-configure-manage/verify-vault-permissions.png)
189-
190-
Backup validates if the vault has sufficient permissions to allow configuring backup on the selected storage accounts. This takes a while to finish validations.
191-
192-
![Permissions to allow configuring backup](./media/blob-backup-configure-manage/permissions-for-configuring-backup.png)
193-
194-
1. After validations are complete, the **Backup readiness** column will inform if the Backup vault has enough permissions to configure backups for each storage account.
195-
196-
![Information of Backup vault permissions](./media/blob-backup-configure-manage/information-of-backup-vault-permissions.png)
197-
198-
If validation displays errors (for two of the storage accounts), you haven't assigned the **Storage account backup contributor** role for these [storage accounts](#grant-permissions-to-the-backup-vault-on-storage-accounts). Also, you can assign the required role here, based on your current permissions. The error message can help you understand if you have the required permissions, and take the appropriate action:
199-
200-
- **Role assignment not done:** This error (as shown for the item _blobbackupdemo3_ in the figure above) indicates that you (the user) have permissions to assign the **Storage account backup contributor** role and the other required roles for the storage account to the vault. Select the roles, and select **Assign missing roles** on the toolbar. This will automatically assign the required role to the Backup vault, and also trigger an autorevalidation.<br><br>At times, role propagation may take a while (up to 10 minutes) causing the revalidation to fail. In such scenario, please wait for a few minutes and select the ‘Revalidate’ button retry validation.
201-
202-
- **Insufficient permissions for role assignment:** This error (as shown for the item _blobbackupdemo4_ in the figure above) indicates that the vault doesn’t have the required role to configure backup, and you (the user) don’t have enough permissions to assign the required role. To make the role assignment easier, Backup allows you to download the role assignment template, which you can share with users with permissions to assign roles for storage accounts. To do this, select such storage accounts, and select **Download role assignment template** to download the template.<br><br>Once the roles are assigned, you can share it with the appropriate users. On successful assignment of the role, select **Revalidate** to validate permissions again, and then configure backup.
203-
>[!NOTE]
204-
>The template would only contain details for selected storage accounts. So, if there are multiple users that need to assign roles for different storage accounts, you can select and download different templates accordingly.
205-
1. Once the validation is successful for all selected storage accounts, continue to **Review and configure backup**.
206-
207-
You'll receive notifications about the status of configuring protection and its completion.
208-
209-
### Using Data protection settings of the storage account to configure operational backup
148+
### Using Data protection settings of the storage account to configure backup
210149

211150
You can configure backup for blobs in a storage account directly from the ‘Data Protection’ settings of the storage account.
212151

0 commit comments

Comments
 (0)