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/backup-azure-alternate-dpm-server-troubleshoot.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Troubleshoot data recovery from Microsoft Azure Backup Server by using Azure Backup
3
3
description: Learn how to troubleshoot data recovery from Microsoft Azure Backup Server.
4
4
ms.topic: troubleshooting
5
-
ms.date: 01/26/2024
5
+
ms.date: 01/31/2025
6
6
ms.service: azure-backup
7
7
ms.custom: engagement-fy24
8
8
author: jyothisuri
@@ -11,11 +11,12 @@ ms.author: jsuri
11
11
12
12
# Troubleshoot data recovery from Microsoft Azure Backup Server
13
13
14
-
This article provides troubleshooting steps that help you resolve error massages caused during data recovery from Microsoft Azure Backup Server.
14
+
This article provides recommendations for troubleshooting common errors encountered during data recovery from Microsoft Azure Backup Server.
15
+
15
16
16
17
## Troubleshoot error messages
17
18
18
-
| Error Message | Cause |Resolution|
19
+
| Error Message | Cause |Recommendation|
19
20
|:--- |:--- |:--- |
20
21
|This server is not registered to the vault specified by the vault credential. | This error appears when the vault credential file selected doesn't belong to the Recovery Services vault associated with Azure Backup Server on which the recovery is attempted. | Download the vault credential file from the Recovery Services vault to which the Azure Backup Server is registered. |
21
22
|Either the recoverable data isn't available or the selected server isn't a DPM server. | There are no other Azure Backup Servers registered to the Recovery Services vault, or the servers haven't yet uploaded the metadata, or the selected server isn't an Azure Backup Server (using Windows Server or Windows Client). | If there are other Azure Backup Servers registered to the Recovery Services vault, ensure that the latest Azure Backup agent is installed. <br>If there are other Azure Backup Servers registered to the Recovery Services vault, wait for a day after installation to start the recovery process. The nightly job will upload the metadata for all the protected backups to cloud. The data will be available for recovery. |
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-scdpm-troubleshooting.md
+17-9Lines changed: 17 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Troubleshoot System Center Data Protection Manager
3
3
description: In this article, discover solutions for issues that you might encounter while using System Center Data Protection Manager.
4
4
ms.topic: troubleshooting
5
-
ms.date: 10/21/2022
5
+
ms.date: 01/31/2025
6
6
ms.service: azure-backup
7
7
author: jyothisuri
8
8
ms.author: jsuri
@@ -14,7 +14,11 @@ This article describes solutions for issues that you might encounter while using
14
14
15
15
For the latest release notes for System Center Data Protection Manager, see the [System Center documentation](/system-center/dpm/dpm-release-notes). You can learn more about support for Data Protection Manager in [this matrix](/system-center/dpm/dpm-protection-matrix).
16
16
17
-
## Error: Replica is inconsistent
17
+
## Common errors
18
+
19
+
This section lists the common errors and the recommended actions to resolve them.
20
+
21
+
### Error: Replica is inconsistent
18
22
19
23
A replica can be inconsistent for the following reasons:
20
24
@@ -36,7 +40,7 @@ To resolve this issue, perform the following actions:
36
40
- Ensure that the disk is healthy and that there's enough space for the replica.
37
41
- Ensure that there are no duplicate backup jobs that are running concurrently.
38
42
39
-
## Error: Online recovery point creation failed
43
+
###Error: Online recovery point creation failed
40
44
41
45
To resolve this issue, perform the following actions:
42
46
@@ -48,7 +52,7 @@ To resolve this issue, perform the following actions:
48
52
- Ensure that the replica is present and not missing.
49
53
- Ensure that the replica has sufficient space to create the update sequence number (USN) journal.
50
54
51
-
## Error: Unable to configure protection
55
+
###Error: Unable to configure protection
52
56
53
57
This error occurs when the Data Protection Manager server can't contact the protected server.
54
58
@@ -58,7 +62,7 @@ To resolve this issue, perform the following actions:
58
62
- Ensure that there's connectivity (network/firewall/proxy) between your Data Protection Manager server and the protected server.
59
63
- If you're protecting a SQL server, ensure that the **Login Properties** > **NT AUTHORITY\SYSTEM** property shows the **sysadmin** setting enabled.
60
64
61
-
## Error: Server not registered as specified in vault credential file
65
+
###Error: Server not registered as specified in vault credential file
62
66
63
67
This error occurs during the recovery process for Data Protection Manager/Azure Backup server data. The vault credential file that's used in the recovery process doesn't belong to the Recovery Services vault for the Data Protection Manager/Azure Backup server.
64
68
@@ -67,7 +71,7 @@ To resolve this issue, perform these steps:
67
71
1. Download the vault credential file from the Recovery Services vault to which the Data Protection Manager/Azure Backup server is registered.
68
72
2. Try to register the server with the vault by using the most recently downloaded vault credential file.
69
73
70
-
## Error: No recoverable data or selected server not a Data Protection Manager server
74
+
###Error: No recoverable data or selected server not a Data Protection Manager server
71
75
72
76
This error occurs for the following reasons:
73
77
@@ -80,7 +84,7 @@ When other Data Protection Manager/Azure Backup servers are registered to the Re
80
84
1. Ensure that the latest Azure Backup agent is installed.
81
85
2. After you ensure that the latest agent is installed, wait one day before you start the recovery process. The nightly backup job uploads the metadata for all of the protected backups to the cloud. The backup data is then available for recovery.
82
86
83
-
## Error: Provided encryption passphrase doesn't match passphrase for server
87
+
###Error: Provided encryption passphrase doesn't match passphrase for server
84
88
85
89
This error occurs during the encryption process when recovering Data Protection Manager/Azure Backup server data. The encryption passphrase that's used in the recovery process doesn't match the server's encryption passphrase. As a result, the agent can't decrypt the data and the recovery fails.
86
90
@@ -90,10 +94,14 @@ This error occurs during the encryption process when recovering Data Protection
90
94
> When you're recovering data, always provide the same encryption passphrase that's associated with the Data Protection Manager/Azure Backup server.
91
95
>
92
96
93
-
## Error: The server registration status could not be verified with Microsoft Azure Backup. Verify that you are connected to the internet and that the proxy settings are configured correctly.
97
+
###Error: The server registration status could not be verified with Microsoft Azure Backup. Verify that you are connected to the internet and that the proxy settings are configured correctly.
94
98
95
99
To resolve this issue:
96
100
97
101
- Ensure network connectivity and proxy settings.
98
102
- Ensure that you are running the latest MARS agent.
99
-
-[Ensure your server is running on TLS 1.2](transport-layer-security.md).
103
+
-[Ensure your server is running on TLS 1.2](transport-layer-security.md).
104
+
105
+
## Next step
106
+
107
+
[Prepare to back up workloads to Azure with System Center DPM](backup-azure-dpm-introduction.md)
# Soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads
10
+
# Soft delete backups for SQL server in Azure VM and SAP HANA in Azure VM workloads
11
+
12
+
This article describes how to soft-delete backups for SQL server in Azure VM and SAP HANA in Azure VM workloads.
11
13
12
14
Azure Backup now provides soft delete for SQL server in Azure VM and SAP HANA in Azure VM workloads. This is in addition to the already supported [Azure Virtual machine soft delete scenario](soft-delete-virtual-machines.md).
13
15
14
16
[Soft delete](backup-azure-security-feature-cloud.md) is a security feature to help protect backup data even after deletion. With soft delete, even if a malicious actor deletes the backup of a database (or backup data is accidentally deleted), the backup data is retained for 14 additional days. This allows the recovery of that backup item with no data loss. This additional retention of 14 days of the backup data in the "soft delete" state doesn’t incur any cost to the customer.
15
17
16
-
## Soft delete for SQL server in Azure VM using Azure portal
18
+
## Soft delete backups
17
19
18
20
>[!NOTE]
19
21
>These instructions also apply to SAP HANA in Azure VM.
20
22
23
+
**Choose a client**:
24
+
25
+
# [Azure portal](#tab/azure-portal)
26
+
27
+
To perform soft delete operation on the database, follow these steps:
28
+
21
29
1. To delete the backup data of a database in a SQL server, the backup must be stopped. In the Azure portal, go to your Recovery Services vault, go to the backup item, and choose **Stop backup**.
A window will appear warning that if undelete is chosen, all restore points for the database will be undeleted and available for performing a restore operation. The backup item will be retained in a “stop protection with retain data” state with backups paused and backup data retained forever with no backup policy effective.
45
+
A window with warning appears that says if undelete is chosen, all restore points for the database are undeleted and available for performing a restore operation. The backup item will be retained in a “stop protection with retain data” state with backups paused and backup data retained forever with no backup policy effective.
## Soft delete for SQL server in VM using Azure PowerShell
57
+
#[Azure PowerShell](#tab/azure-powershell)
50
58
51
59
>[!NOTE]
52
60
>The Az.RecoveryServices version required to use soft-delete using Azure PowerShell is minimum 2.2.0. Use `Install-Module -Name Az.RecoveryServices -Force` to get the latest version.
The **DeleteState** of the backup item will revert to **NotDeleted**. But the protection is still stopped. Resume the backup to re-enable the protection.
83
91
84
-
## How to disable soft delete
92
+
---
93
+
94
+
## Disable soft delete
85
95
86
96
Disabling this feature isn't recommended. The only circumstance where you should consider disabling soft delete is if you're planning on moving your protected items to a new vault, and can't wait the 14 days required before deleting and reprotecting (such as in a test environment.) For instructions on how to disable soft delete, see [Enabling and disabling soft delete](backup-azure-security-feature-cloud.md#enable-and-disable-soft-delete).
Copy file name to clipboardExpand all lines: articles/dev-box/how-to-create-dev-boxes-developer-portal.md
+22-12Lines changed: 22 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: dev-box
6
6
ms.service: dev-box
7
7
author: RoseHJM
8
8
ms.author: rosemalcolm
9
-
ms.date: 01/03/2024
9
+
ms.date: 01/30/2025
10
10
ms.topic: how-to
11
11
12
12
# customer intent: As a developer, I want to learn what tasks I can perform through the developer portal so that I can manage my dev boxes.
@@ -41,19 +41,21 @@ You can also create a dev box through the Azure CLI dev center extension. For mo
41
41
42
42
After you create your dev box, you can connect to it through a Remote Desktop application or via the browser.
43
43
44
-
The new Windows App remote desktop client is the recommended client for Microsoft Dev Box; it provides an enhanced user experience, including support for multiple monitors. It is also available on multiple platforms, including Windows, macOS, iOS/iPadOS, Android/Chrome OS (preview), and web browsers. For more information, see [Get started with Windows App](https://aka.ms/dev-box/windows-app).
44
+
The new Windows App remote desktop client is the recommended client for Microsoft Dev Box; it provides an enhanced user experience, including support for multiple monitors. It's also available on multiple platforms, including Windows, macOS, iOS/iPadOS, Android/Chrome OS (preview), and web browsers. For more information, see [Get started with Windows App](https://aka.ms/dev-box/windows-app).
45
45
46
46
You can use the **browser** for lighter workloads. When you access your dev box via your phone or laptop, you can use the browser. The browser is useful for tasks such as a quick bug fix or a review of a GitHub pull request. For more information, see the [steps for using a browser to connect to a dev box](./quickstart-create-dev-box.md#connect-to-a-dev-box).
47
47
48
-
## Shut down, restart, or start a dev box
48
+
## Explore dev box actions
49
49
50
-
You can perform many actions on a dev box in the Microsoft Dev Box developer portal by using the actions menu (**...**) on the dev box tile. The available options depend on the state of the dev box and the configuration of the dev box pool it belongs to. For example, you can shut down or restart a running dev box, or start a stopped dev box.
50
+
You can perform many actions on a dev box in the Microsoft Dev Box developer portal by using the actions menu on the dev box tile. The available options depend on the state of the dev box and the configuration of the dev box pool it belongs to. For example, you can shut down or restart a running dev box, or start a stopped dev box.
51
+
52
+
### Shut down, restart, or start a dev box
51
53
52
54
To shut down or restart a dev box:
53
55
54
56
1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
55
57
56
-
1. On the dev box you that want to shut down or restart, select the actions menu (**...**).
58
+
1. On the dev box you that want to shut down or restart, select the actions menu.
57
59
58
60
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-actions-shutdown.png" alt-text="Screenshot of the developer portal showing the actions menu for a running dev box." border="false":::
59
61
@@ -63,29 +65,29 @@ To start a dev box:
63
65
64
66
1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
65
67
66
-
1. On the dev box you that want to start, select the actions menu (**...**).
68
+
1. On the dev box you that want to start, select the actions menu.
67
69
68
70
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-actions-start.png" alt-text="Screenshot of the developer portal showing the actions menu for a stopped dev box." border="false":::
69
71
70
72
1. For a stopped dev box, you can select **Start**.
71
73
72
-
## Get information about a dev box
74
+
###Get information about a dev box
73
75
74
76
You can use the Microsoft Dev Box developer portal to view information about a dev box, such as the creation date, and the dev center and dev box pool it belongs to. You can also check the source image in use.
75
77
76
78
To get more information about your dev box:
77
79
78
80
1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
79
81
80
-
1. On the dev box that you want to view, select the actions menu (**...**) and then select **More Info**.
82
+
1. On the dev box that you want to view, select the actions menu, and then select **More Info**.
81
83
82
84
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-actions-more-info.png" alt-text="Screenshot of the developer portal showing the actions menu for a dev box and More Info selected." border="false":::
83
85
84
86
1. In the dev box details pane, you see more information about your dev box, like the following example:
85
87
86
88
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-details-pane.png" alt-text="Screenshot of the dev box more information pane, showing creation date, dev center, dev box pool, and source image for the dev box." border="false":::
87
89
88
-
## Delete a dev box
90
+
###Delete a dev box
89
91
90
92
When you no longer need a dev box, you can delete it in the developer portal.
91
93
@@ -94,18 +96,26 @@ There are many reasons why you might not need a dev box anymore. Maybe you compl
94
96
You can delete dev boxes after you finish your tasks. Suppose you finish fixing your bug and merge your pull request. Now, you can delete your dev box and create new dev boxes to work on new items.
95
97
96
98
> [!IMPORTANT]
97
-
> You can't retrieve a dev box after it's deleted. Before you delete a dev box, confirm that neither you nor your team members need the dev box for future tasks.
99
+
> You can't retrieve a dev box after it's deleted. Before you delete a dev box, confirm that you and your team members don't need the dev box for future tasks.
98
100
99
101
1. Sign in to the [developer portal](https://aka.ms/devbox-portal).
100
102
101
-
1. For the dev box that you want to delete, select the actions menu (**...**) and then select **Delete**.
103
+
1. For the dev box that you want to delete, select the actions menu and then select **Delete**.
102
104
103
-
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-delete.png" alt-text="Screenshot of the developer portal showing the actions menu for a dev box and Delete selected." border="false":::
105
+
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-actions-delete.png" alt-text="Screenshot of the developer portal showing the actions menu for a dev box and Delete selected." border="false":::
104
106
105
107
1. To confirm the deletion, select **Delete**.
106
108
107
109
:::image type="content" source="media/how-to-create-dev-boxes-developer-portal/dev-box-confirm-delete.png" alt-text="Screenshot of the confirmation message after you select to delete a dev box." border="false":::
108
110
111
+
### Discover more dev box actions
112
+
113
+
Dependent on how your dev box is configured, you can perform more actions on a dev box in the Microsoft Dev Box developer portal. For example, you can:
114
+
115
+
**Hibernate or resume:** If your dev box has hibernation enabled, you can hibernate or resume the dev box. Hibernation is useful when you want to save the current state of your dev box and resume it later. For more information, see [Hibernate a dev box in Microsoft Dev Box](how-to-hibernate-your-dev-box.md).
116
+
117
+
**Troubleshoot & repair:** If you encounter issues connecting to your dev box, you can use the Troubleshoot and repair to relsove the issue. For more information, see [Troubleshoot and repair a dev box in Microsoft Dev Box](how-to-troubleshoot-repair-dev-box.md).
118
+
109
119
## Related content
110
120
111
121
-[Use a remote desktop client to connect to a dev box](./tutorial-connect-to-dev-box-with-remote-desktop-app.md)
0 commit comments