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-exchange-mabs.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Before you continue, make sure that Azure Backup Server is [installed and prepar
17
17
18
18
To install the MABS protection agent on the Exchange server, follow these steps:
19
19
20
-
1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](hhttps://docs.microsoft.com/system-center/dpm/configure-firewall-settings-for-dpm?view=sc-dpm-2019).
20
+
1. Make sure that the firewalls are correctly configured. See [Configure firewall exceptions for the agent](https://docs.microsoft.com/system-center/dpm/configure-firewall-settings-for-dpm?view=sc-dpm-2019).
21
21
2. Install the agent on the Exchange server by clicking **Management > Agents > Install** in MABS Administrator Console. See [Install the MABS protection agent](https://docs.microsoft.com/system-center/dpm/deploy-dpm-protection-agent?view=sc-dpm-2019) for detailed steps.
22
22
23
23
## Create a protection group for the Exchange server
@@ -44,7 +44,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
44
44
6. Click **Next**.
45
45
7. Select the **Run Eseutil to check data integrity** option if you want to check the integrity of the Exchange Server databases.
46
46
47
-
After you select this option, backup consistency checking will be run on MABS to avoid the I/O traffic that’s generated by running the **eseutil** command on the Exchange server.
47
+
After you select this option, backup consistency checking will be run on MABS to avoid the I/O traffic that's generated by running the **eseutil** command on the Exchange server.
48
48
49
49
> [!NOTE]
50
50
> To use this option, you must copy the Ese.dll and Eseutil.exe files to the C:\Program Files\Microsoft Azure Backup\DPM\DPM\bin directory on the MAB server. Otherwise, the following error is triggered:
@@ -55,7 +55,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
55
55
9. Select the database for **Copy Backup**, and then click **Next**.
56
56
57
57
> [!NOTE]
58
-
> If you do not select “Full backup” for at least one DAG copy of a database, logs will not be truncated.
58
+
> If you do not select "Full backup" for at least one DAG copy of a database, logs will not be truncated.
59
59
>
60
60
>
61
61
10. Configure the goals for **Short-Term backup**, and then click **Next**.
@@ -70,7 +70,7 @@ To install the MABS protection agent on the Exchange server, follow these steps:
> Note Online recovery points are based on express full recovery points. Therefore, you must schedule the online recovery point after the time that’s specified for the express full recovery point.
73
+
> Note Online recovery points are based on express full recovery points. Therefore, you must schedule the online recovery point after the time that's specified for the express full recovery point.
74
74
>
75
75
>
76
76
16. Configure the retention policy for **Azure Backup**, and then click **Next**.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.date: 07/05/2019
9
9
10
10
This article provides troubleshooting guidance to help you diagnose the cause of slow backup performance for files and folders when you're using Azure Backup. When you use the Azure Backup agent to back up files, the backup process might take longer than expected. This delay might be caused by one or more of the following:
11
11
12
-
*[There are performance bottlenecks on the computer that’s being backed up.](#cause1)
12
+
*[There are performance bottlenecks on the computer that's being backed up.](#cause1)
13
13
*[Another process or antivirus software is interfering with the Azure Backup process.](#cause2)
14
14
*[The Backup agent is running on an Azure virtual machine (VM).](#cause3)
15
15
*[You're backing up a large number (millions) of files.](#cause4)
@@ -39,19 +39,19 @@ We also strongly recommend that you review the [Azure Backup service FAQ](backup
39
39
40
40
Bottlenecks on the computer that's being backed up can cause delays. For example, the computer's ability to read or write to disk, or available bandwidth to send data over the network, can cause bottlenecks.
41
41
42
-
Windows provides a built-in tool called [Performance Monitor](hhttps://techcommunity.microsoft.com/t5/ask-the-performance-team/windows-performance-monitor-overview/ba-p/375481) (Perfmon) to detect these bottlenecks.
42
+
Windows provides a built-in tool called [Performance Monitor](https://techcommunity.microsoft.com/t5/ask-the-performance-team/windows-performance-monitor-overview/ba-p/375481) (Perfmon) to detect these bottlenecks.
43
43
44
44
Here are some performance counters and ranges that can be helpful in diagnosing bottlenecks for optimal backups.
45
45
46
46
| Counter | Status |
47
47
| --- | --- |
48
-
| Logical Disk(Physical Disk)--%idle |• 100% idle to 50% idle = Healthy</br>• 49% idle to 20% idle = Warning or Monitor</br>• 19% idle to 0% idle = Critical or Out of Spec |
49
-
| Logical Disk(Physical Disk)--%Avg. Disk Sec Read or Write |• 0.001 ms to 0.015 ms = Healthy</br>• 0.015 ms to 0.025 ms = Warning or Monitor</br>• 0.026 ms or longer = Critical or Out of Spec |
48
+
| Logical Disk(Physical Disk)--%idle |* 100% idle to 50% idle = Healthy</br>* 49% idle to 20% idle = Warning or Monitor</br>* 19% idle to 0% idle = Critical or Out of Spec |
49
+
| Logical Disk(Physical Disk)--%Avg. Disk Sec Read or Write |* 0.001 ms to 0.015 ms = Healthy</br>* 0.015 ms to 0.025 ms = Warning or Monitor</br>* 0.026 ms or longer = Critical or Out of Spec |
50
50
| Logical Disk(Physical Disk)--Current Disk Queue Length (for all instances) |80 requests for more than 6 minutes |
51
-
| Memory--Pool Non Paged Bytes |• Less than 60% of pool consumed = Healthy<br>• 61% to 80% of pool consumed = Warning or Monitor</br>• Greater than 80% pool consumed = Critical or Out of Spec |
52
-
| Memory--Pool Paged Bytes |• Less than 60% of pool consumed = Healthy</br>• 61% to 80% of pool consumed = Warning or Monitor</br>• Greater than 80% pool consumed = Critical or Out of Spec |
53
-
| Memory--Available Megabytes |• 50% of free memory available or more = Healthy</br>• 25% of free memory available = Monitor</br>• 10% of free memory available = Warning</br>• Less than 100 MB or 5% of free memory available = Critical or Out of Spec |
54
-
| Processor--\%Processor Time (all instances) |• Less than 60% consumed = Healthy</br>• 61% to 90% consumed = Monitor or Caution</br>• 91% to 100% consumed = Critical |
51
+
| Memory--Pool Non Paged Bytes |* Less than 60% of pool consumed = Healthy<br>* 61% to 80% of pool consumed = Warning or Monitor</br>* Greater than 80% pool consumed = Critical or Out of Spec |
52
+
| Memory--Pool Paged Bytes |* Less than 60% of pool consumed = Healthy</br>* 61% to 80% of pool consumed = Warning or Monitor</br>* Greater than 80% pool consumed = Critical or Out of Spec |
53
+
| Memory--Available Megabytes |* 50% of free memory available or more = Healthy</br>* 25% of free memory available = Monitor</br>* 10% of free memory available = Warning</br>* Less than 100 MB or 5% of free memory available = Critical or Out of Spec |
54
+
| Processor--\%Processor Time (all instances) |* Less than 60% consumed = Healthy</br>* 61% to 90% consumed = Monitor or Caution</br>* 91% to 100% consumed = Critical |
55
55
56
56
> [!NOTE]
57
57
> If you determine that the infrastructure is the culprit, we recommend that you defragment the disks regularly for better performance.
0 commit comments