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/backup/archive-tier-support.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Azure Backup - Archive tier overview
3
3
description: Learn about Archive tier support for Azure Backup.
4
4
ms.topic: overview
5
-
ms.date: 05/07/2025
5
+
ms.date: 05/13/2025
6
6
ms.custom: references_regions
7
7
ms.service: azure-backup
8
8
author: jyothisuri
@@ -23,7 +23,7 @@ Archive tier supports the following workloads:
23
23
24
24
| Workloads | Operations |
25
25
| --- | --- |
26
-
| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported. <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active daily and weekly dependencies. There are no un-expired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
26
+
| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported. <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active on-demand, daily, and weekly dependencies. There are no un-expired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
27
27
| SQL Server in Azure Virtual Machines <br><br> SAP HANA in Azure Virtual Machines | Only full recovery points. Logs and differentials aren't supported. <br><br> Age >= 45 days in Vault-standard tier. <br><br> Retention left >= 6 months. <br><br> No dependencies. |
28
28
29
29
A recovery point becomes archivable only if all the above conditions are met.
Copy file name to clipboardExpand all lines: articles/backup/blob-backup-support-matrix.md
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Support matrix for Azure Blobs backup
3
3
description: Provides a summary of support settings and limitations when backing up Azure Blobs.
4
4
ms.topic: reference
5
-
ms.date: 04/17/2025
5
+
ms.date: 05/12/2025
6
6
ms.custom: references_regions, engagement-fy24
7
7
ms.service: azure-backup
8
8
author: jyothisuri
@@ -61,6 +61,7 @@ Operational backup of blobs uses blob point-in-time restore, blob versioning, so
61
61
- If your storage account contains more than 100 containers, you need to select *up to 100 containers* to back up.
62
62
- To back up any new containers that get created after backup configuration for the storage account, modify the protection of the storage account. These containers aren't backed up automatically.
63
63
- The storage accounts to be backed up must contain *a minimum of one container*. If the storage account doesn't contain any containers or if no containers are selected, an error may appear when you configure backup.
64
+
- Only `$web` and `$root` system containers are supported for vaulted backup.
64
65
- If you stop protection (vaulted backup) on a storage account, it doesn't delete the object replication policy created on the storage account. In these scenarios, you need to manually delete the *OR policies*.
65
66
- Archive tier blob backup isn't supported. Cool and cold tier blobs are restored in hot tier.
66
67
- The backup operation isn't supported for blobs that are uploaded by using [Data Lake Storage APIs](/rest/api/storageservices/data-lake-storage-gen2).
Copy file name to clipboardExpand all lines: articles/backup/restore-azure-database-postgresql-flex.md
+22-15Lines changed: 22 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Restore Azure PostgreSQL-Flexible server as Files using Azure portal
3
3
description: Learn about how to restore Azure PostgreSQL-Flexible server as Files.
4
4
ms.topic: how-to
5
-
ms.date: 04/30/2025
5
+
ms.date: 05/12/2025
6
6
ms.service: azure-backup
7
7
ms.custom:
8
8
- ignite-2024
@@ -24,47 +24,39 @@ Before you restore from Azure Database for PostgreSQL Flexible server backups, r
24
24
25
25
- Ensure the target storage account for restoring backup as a file is accessible via a public network. If the storage account uses a private endpoint, [update its public network access settings](backup-azure-database-postgresql-flex-manage.md#enable-public-network-access-for-the-database-storage-account) before executing a restore operation.
26
26
27
-
## Restore Azure PostgreSQL-Flexible database
27
+
## Restore Azure PostgreSQL - Flexible server backups as files
28
28
29
29
>[!Note]
30
-
>The restore operation transfers all PostgreSQL – flexible server databases to a designated storage account container. After restoration, move the files to a new or existing PostgreSQL – Flexible server.
30
+
>Restore operation is a two step process:
31
+
>1. Restore the backup from Backup vault to a storage container.
32
+
>2. Restore the backup files from storage container to a new or existing flexible server.
31
33
32
34
To restore Azure PostgreSQL-Flexible database, Follow these steps:
33
35
34
36
1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL - Flexible server to be restored and select **Restore**.
35
37
36
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/restore.png" alt-text="Screenshot showing how to restore a database.":::
37
-
38
38
Alternatively, go to [Backup center](./backup-center-overview.md) and select **Restore**.
39
39
40
40
1. Select the point in time you would like to restore by using **Select restore point**. Change the date range by selecting **Time period**.
41
41
42
-
:::image type="content" source="./media/restore-azure-database-postgresql/select-restore-point-inline.png" alt-text="Screenshot showing the process to select a recovery point.":::
43
-
44
42
1. Choose the target storage account and container in **Restore parameters** tab. Select **Validate** to check the restore parameters permissions before the final review and restore.
45
43
46
44
1. Once the validation is successful, select **Review + restore**.
47
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/review-restore.png" alt-text="Screenshot showing the restore parameter process.":::
48
45
49
46
1. After final review of the parameters, select **Restore** to restore the selected PostgreSQL - Flexible server backup in target storage account.
50
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/review.png" alt-text="Screenshot showing the review process page.":::
51
47
52
48
1. Submit the Restore operation and track the triggered job under **Backup jobs**.
53
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/validate.png" alt-text="Screenshot showing the validate process page.":::
54
-
55
49
56
50
After the restore job is completed successfully, go to the storage account container to view the restored databases as files (`.sql` files) from your PostgreSQL – Flexible server. Azure Backup also generates the following backup files:
57
51
58
52
-`Database.sql file` per database: Contains data and schema information for a particular database.
59
-
-`Roles.sql files` for entire instance: Contains all role information ((azure_su(superuser) azure_pg_admin, replication, local admin, Microsoft Entra admins and any other custom roles on the server)) that exists at server level.
53
+
-`Roles.sql files` for entire instance: Contains all role information that exists at server level.
60
54
-`Tablespace.sql file`: Tablespace file.
61
55
-`Schema.sql file`: Contains schema information for all the databases on the server.
62
56
63
57
>[!Note]
64
58
>We recommend you not to run this script on the PostgreSQL - Flexible server because the schema is already part of the `database.sql` script.
65
59
66
-
:::image type="content" source="./media/restore-azure-database-postgresql-flex/database-files.png" alt-text="Screenshot shows the database schema per database." lightbox="./media/restore-azure-database-postgresql-flex/database-files.png":::
67
-
68
60
## Restore the backup files from storage container to a new or existing PostgreSQL – Flexible server
69
61
70
62
To restore the backup files from storage container to a new or existing PostgreSQL – Flexible server, follow these steps:
@@ -121,7 +113,22 @@ Here are the key considerations:
121
113
Before you restore the database objects, ensure that you properly dump and clean up the roles. To perform this action, download the `roles.sql`script from your storage container and create all required logins.
122
114
-**Create Non-Entra Roles**: Use a local admin account to run the role creation scripts.
123
115
-**Create Microsoft Entra Roles**: If you need to create roles for Microsoft Entra users, use a Microsoft Entra administrator account to run the necessary scripts.
116
+
117
+
You can download the roles script from your storage account as shown in the following screenshot:
118
+
119
+
When you migrate the output file, `roles.sql` might include certain roles and attributes that aren't applicable in the new environment. You must consider the following:
120
+
121
+
-**Removing attributes that can be set only by superusers**: If you migrate to an environment where you don't have superuser privileges, remove attributes such as *NOSUPERUSER* and *NOBYPASSRLS* from the roles dump.
122
+
-**Excluding service-specific users**: Exclude Single server service users, such as `azure_superuser` or `azure_pg_admin`. These are specific to the service and are created automatically in the new environment.
123
+
124
+
Use the following sed command to clean up your roles dump:
125
+
126
+
```
127
+
sed -i '/azure_superuser/d; /azure_pg_admin/d; /azuresu/d; /^CREATE ROLE replication/d; /^ALTER ROLE replication/d; /^ALTER ROLE/ {s/NOSUPERUSER//; s/NOBYPASSRLS//;}' roles.sql
128
+
```
129
+
130
+
This command deletes the lines containing `azure_superuser`, `azure_pg_admin`, `azuresu`, lines starting with *CREATE ROLE* replication and *ALTER ROLE* replication, and removes the *NOSUPERUSER* and *NOBYPASSRLS* attributes from *ALTER ROLE* statements.
124
131
125
-
## Next steps
132
+
## Next steps
126
133
127
134
[Manage backup of Azure PostgreSQL - Flexible Server using Azure portal](backup-azure-database-postgresql-flex-manage.md).
Do I have permission to turn on video, do I have permission to turn on mic, do I have permission to share screen? Those permissions are examples of participant capabilities that you can learn from the capabilities API. Learning the capabilities can help build a user interface that only shows the buttons related to the actions the local user has permissions to.
16
18
17
19
## Prerequisites
20
+
18
21
- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
19
22
- A deployed Communication Services resource. [Create a Communication Services resource](../../quickstarts/create-communication-resource.md).
20
23
- A user access token to enable the calling client. For more information, see [Create and manage access tokens](../../quickstarts/identity/access-tokens.md).
@@ -37,26 +40,36 @@ Do I have permission to turn on video, do I have permission to turn on mic, do I
37
40
::: zone-end
38
41
39
42
## Supported call types
40
-
The feature is currently supported only for Azure Communication Services Rooms call type and teams meeting call type
43
+
44
+
The following tables define the ability to get capabilities using the Azure Communication Services Calling SDK.
45
+
46
+
### Identities and call types
47
+
48
+
| Identities | Teams meeting | Room | 1:1 call | Group call | 1:1 Teams interop call | Group Teams interop call |
49
+
| --- | --- | --- | --- | --- | --- | --- |
50
+
| Communication Services user | ✔️ | ✔️ |||||
51
+
| Microsoft 365 user | ✔️ | ✔️ |||||
41
52
42
53
## Reasons
43
54
44
55
The following table provides additional information about why action isn't available and provides tips how to make the action available.
| CapabilityNotApplicableForTheCallType | Call type blocks the action. | Consider other type of call if you need this action. The call types are: 1:1 call, group call, 1:1 Teams interop call, 1:1 Teams interop group call, Room, and Meeting. |
50
-
| ClientRestricted | The runtime environment is blocking this action | Unblock the action on your device by changing operating system, browsers, platform, or hardware. You can find supported environment in our documentation. |
51
-
| UserPolicyRestricted | Microsoft 365 user's policy blocks the action. | Enable this action by changing policy that is assigned to the organizer of the meeting, initiator of the call or Microsoft 365 user using ACS SDK. The target user depends on the type of action. Learn more about Teams policy in Teams. Teams administrator can change policies. |
52
-
| RoleRestricted | Assigned role blocks the action. | Promote user to different role to make the action available. |
53
-
| FeatureNotSupported | The capabilities feature isn't supported in this call type. | Let us know in Azure Feedback channel that you would like to have this feature available for this call type. |
54
-
| MeetingRestricted | Teams meeting option blocks the action. | Teams meeting organizer or co-organizer needs to change meeting option to enable this action. |
55
-
| NotInitialized | The capabilities feature isn't initialized yet. | Subscribe to event `capabilitiesChanged` on `this.call.feature(Features.Capabilities)` to know when capability is initialized. |
56
-
| NotCapable | User type blocks the action. | The action is only allowed to specific type of identity. Enable this action by using Microsoft 365 identity. |
57
-
| TeamsPremiumLicenseRestricted | Microsoft 365 user needs to have Teams Premium license assigned. | Enable this action by assigning Teams Premium license to the Teams meeting organizer or the Microsoft 365 user using SDK. The target user depends on the type of action. Microsoft 365 admin can assign required license. |
58
-
| ExplicitConsentRequired | Consent is required to allow the action. | Provide the consent for recording or transcription by calling method `grantTeamsConsent()` under `this.call.feature(Features.Recording)` or `this.call.feature(Features.Transcription)` .|
57
+
| Reason | Description | Resolution |
58
+
| --- | --- | --- |
59
+
| Capable | Action is enabled. ||
60
+
| CapabilityNotApplicableForTheCallType | Call type blocks the action. | Consider other type of call if you need this action. The call types are: 1:1 call, group call, 1:1 Teams interop call, 1:1 Teams interop group call, Room, and Meeting. |
61
+
| ClientRestricted | The runtime environment is blocking this action | Unblock the action on your device by changing operating system, browsers, platform, or hardware. You can find supported environment in our documentation. |
62
+
| UserPolicyRestricted | Microsoft 365 user's policy blocks the action. | Enable this action by changing policy that is assigned to the organizer of the meeting, initiator of the call or Microsoft 365 user using ACS SDK. The target user depends on the type of action. Learn more about Teams policy in Teams. Teams administrator can change policies. |
63
+
| RoleRestricted | Assigned role blocks the action. | Promote user to different role to make the action available. |
64
+
| FeatureNotSupported | The capabilities feature isn't supported in this call type. | Let us know in Azure Feedback channel that you would like to have this feature available for this call type. |
65
+
| MeetingRestricted | Teams meeting option blocks the action. | Teams meeting organizer or co-organizer needs to change meeting option to enable this action. |
66
+
| NotInitialized | The capabilities feature isn't initialized yet. | Subscribe to event `capabilitiesChanged` on `this.call.feature(Features.Capabilities)` to know when capability is initialized. |
67
+
| NotCapable | User type blocks the action. | The action is only enabled for specific identities. Enable this action by using Microsoft 365 identity. |
68
+
| TeamsPremiumLicenseRestricted | Microsoft 365 user needs to have Teams Premium license assigned. | Enable this action by assigning Teams Premium license to the Teams meeting organizer or the Microsoft 365 user using SDK. The target user depends on the type of action. Microsoft 365 admin can assign required license. |
69
+
| ExplicitConsentRequired | Consent is required to allow the action. | Provide the consent for recording or transcription by calling method `grantTeamsConsent()` under `this.call.feature(Features.Recording)` or `this.call.feature(Features.Transcription)` .|
0 commit comments