Skip to content

Commit f22f1c0

Browse files
authored
Merge pull request #106515 from dcurwin/mar4-brokenlinks
Fix broken links
2 parents 5d765f4 + 194e7f7 commit f22f1c0

File tree

4 files changed

+17
-17
lines changed

4 files changed

+17
-17
lines changed

articles/backup/backup-azure-exchange-mabs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Before you continue, make sure that Azure Backup Server is [installed and prepar
1717

1818
To install the MABS protection agent on the Exchange server, follow these steps:
1919

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).
2121
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.
2222

2323
## 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:
4444
6. Click **Next**.
4545
7. Select the **Run Eseutil to check data integrity** option if you want to check the integrity of the Exchange Server databases.
4646

47-
After you select this option, backup consistency checking will be run on MABS to avoid the I/O traffic thats 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.
4848

4949
> [!NOTE]
5050
> 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:
5555
9. Select the database for **Copy Backup**, and then click **Next**.
5656

5757
> [!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.
5959
>
6060
>
6161
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:
7070
![Specify online backup schedule](./media/backup-azure-backup-exchange-server/specify-online-backup-schedule.png)
7171

7272
> [!NOTE]
73-
> Note Online recovery points are based on express full recovery points. Therefore, you must schedule the online recovery point after the time thats 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.
7474
>
7575
>
7676
16. Configure the retention policy for **Azure Backup**, and then click **Next**.

articles/backup/backup-azure-files-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ Backup for Azure File shares is currently in Preview and is available only in th
7878
- NWW (Norway West)
7979
- SZN (Switzerland North)
8080

81-
Write to [[email protected]](email:[email protected]) if you need to use it in a specific geo that is not listed above.
81+
Write to [[email protected]](mailto:[email protected]) if you need to use it in a specific geo that is not listed above.
8282

8383
### How many Azure file shares can I protect in a Vault?
8484

articles/backup/backup-azure-restore-files-from-vm.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -196,10 +196,10 @@ If you run the script on a computer with restricted access, ensure there is acce
196196
197197
- `download.microsoft.com`
198198
- Recovery Service URLs (geo-name refers to the region where the recovery service vault resides)
199-
- <https://pod01-rec2.geo-name.backup.windowsazure.com> (For Azure public geos)
200-
- <https://pod01-rec2.geo-name.backup.windowsazure.cn> (For Azure China 21Vianet)
201-
- <https://pod01-rec2.geo-name.backup.windowsazure.us> (For Azure US Government)
202-
- <https://pod01-rec2.geo-name.backup.windowsazure.de> (For Azure Germany)
199+
- `https://pod01-rec2.geo-name.backup.windowsazure.com` (For Azure public geos)
200+
- `https://pod01-rec2.geo-name.backup.windowsazure.cn` (For Azure China 21Vianet)
201+
- `https://pod01-rec2.geo-name.backup.windowsazure.us` (For Azure US Government)
202+
- `https://pod01-rec2.geo-name.backup.windowsazure.de` (For Azure Germany)
203203
- Outbound ports 53 (DNS), 443, 3260
204204
205205
> [!NOTE]

articles/backup/backup-azure-troubleshoot-slow-backup-performance-issue.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.date: 07/05/2019
99

1010
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:
1111

12-
* [There are performance bottlenecks on the computer thats being backed up.](#cause1)
12+
* [There are performance bottlenecks on the computer that's being backed up.](#cause1)
1313
* [Another process or antivirus software is interfering with the Azure Backup process.](#cause2)
1414
* [The Backup agent is running on an Azure virtual machine (VM).](#cause3)
1515
* [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
3939

4040
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.
4141

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.
4343

4444
Here are some performance counters and ranges that can be helpful in diagnosing bottlenecks for optimal backups.
4545

4646
| Counter | Status |
4747
| --- | --- |
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 |
5050
| 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 |
5555

5656
> [!NOTE]
5757
> If you determine that the infrastructure is the culprit, we recommend that you defragment the disks regularly for better performance.

0 commit comments

Comments
 (0)