Merge pull request #215434 from v-amallick/Oct-21-2022-OnPremTS

DPM - TLS 1.2 support updates

Author: prmerger-automator[bot]

articles/backup/backup-azure-dpm-introduction.md

@@ -2,7 +2,10 @@
 title: Prepare the DPM server to back up workloads
 description: In this article, learn how to prepare for System Center Data Protection Manager (DPM) backups to Azure, using the Azure Backup service.
 ms.topic: conceptual
-ms.date: 06/11/2020
+ms.date: 10/21/2020
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 # Prepare to back up workloads to Azure with System Center DPM
 
@@ -43,7 +46,7 @@ Unsupported file types | <li>Servers on case-sensitive file systems<li> hard lin
 Local storage | Each machine you want to back up must have local free storage that's at least 5% of the size of the data that's being backed up. For example, backing up 100 GB of data requires a minimum of 5 GB of free space in the scratch location.
 Vault storage | There’s no limit to the amount of data you can back up to an Azure Backup vault, but the size of a data source (for example a virtual machine or database) shouldn’t exceed 54,400 GB.
 Azure ExpressRoute | You can back up your data over Azure ExpressRoute with public peering (available for old circuits) and Microsoft peering. Backup over private peering isn't supported.<br/><br/> **With public peering**: Ensure access to the following domains/addresses:<br/><br/> URLs:<br> `www.msftncsi.com` <br> .Microsoft.com <br> .WindowsAzure.com <br> .microsoftonline.com <br> .windows.net <br>`www.msftconnecttest.com`<br><br>IP addresses<br>  20.190.128.0/18 <br>  40.126.0.0/18<br> <br/>**With Microsoft peering**, select the following services/regions and relevant community values:<br/><br/>- Azure Active Directory (12076:5060)<br/><br/>- Microsoft Azure Region (according to the location of your Recovery Services vault)<br/><br/>- Azure Storage (according to the location of your Recovery Services vault)<br/><br/>For more information, see [ExpressRoute routing requirements](../expressroute/expressroute-routing.md).<br/><br/>**Note**: Public peering is deprecated for new circuits.
-Azure Backup agent | If DPM is running on System Center 2012 SP1, install Rollup 2 or later for DPM SP1. This is required for agent installation.<br/><br/> This article describes how to deploy the latest version of the Azure Backup agent, also known as the Microsoft Azure Recovery Service (MARS) agent. If you have an earlier version deployed, update to the latest version to ensure that backup works as expected.
+Azure Backup agent | If DPM is running on System Center 2012 SP1, install Rollup 2 or later for DPM SP1. This is required for agent installation.<br/><br/> This article describes how to deploy the latest version of the Azure Backup agent, also known as the Microsoft Azure Recovery Service (MARS) agent. If you have an earlier version deployed, update to the latest version to ensure that backup works as expected. <br><br> [Ensure your server is running on TLS 1.2](transport-layer-security.md).
 
 Before you start, you need an Azure account with the Azure Backup feature enabled. If you don't have an account, you can create a free trial account in just a couple of minutes. Read about [Azure Backup pricing](https://azure.microsoft.com/pricing/details/backup/).
 

articles/backup/backup-azure-scdpm-troubleshooting.md

@@ -2,7 +2,10 @@
 title: Troubleshoot System Center Data Protection Manager
 description: In this article, discover solutions for issues that you might encounter while using System Center Data Protection Manager.
 ms.topic: troubleshooting
-ms.date: 01/30/2019
+ms.date: 10/21/2022
+author: v-amallick
+ms.service: backup
+ms.author: v-amallick
 ---
 
 # Troubleshoot System Center Data Protection Manager
@@ -86,3 +89,11 @@ This error occurs during the encryption process when recovering Data Protection
 >
 > When you're recovering data, always provide the same encryption passphrase that's associated with the Data Protection Manager/Azure Backup server.
 >
+
+## 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.
+
+To resolve this issue:
+
+- Ensure network connectivity and proxy settings.
+- Ensure that you are running the latest MARS agent.
+- [Ensure your server is running on TLS 1.2](transport-layer-security.md).