Merge pull request #108094 from davidsmatlak/ds-docsfresh01

Docs freshness updates

Author: GitHubber17

articles/site-recovery/site-recovery-overview.md

@@ -1,33 +1,32 @@
 ---
-title: About Azure Site Recovery 
+title: About Azure Site Recovery
 description: Provides an overview of the Azure Site Recovery service, and summarizes disaster recovery and migration deployment scenarios.
 author: rayne-wiselman
 ms.service: site-recovery
 ms.topic: overview
-ms.date: 09/09/2019
+ms.date: 03/17/2020
 ms.author: raynew
 ms.custom: MVC
 ---
+
 # About Site Recovery
 
 Welcome to the Azure Site Recovery service! This article provides a quick service overview.
 
-As an organization you need to adopt a business continuity and disaster recovery (BCDR) strategy that keeps your data safe, and your apps and workloads up and running, when planned and unplanned outages occur.
+As an organization you need to adopt a business continuity and disaster recovery (BCDR) strategy that keeps your data safe, and your apps and workloads online, when planned and unplanned outages occur.
 
-Azure Recovery Services contribute to your BCDR strategy:
+Azure Recovery Services contributes to your BCDR strategy:
 
-- **Site Recovery service**: Site Recovery helps ensure business continuity by keeping business apps and workloads running during outages. Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to secondary location, and access apps from there. After the primary location is running again, you can fail back to it.  
-- **Backup service**: The [Azure Backup](https://docs.microsoft.com/azure/backup/) service keeps your data safe and recoverable by backing it up to Azure.
+- **Site Recovery service**: Site Recovery helps ensure business continuity by keeping business apps and workloads running during outages. Site Recovery replicates workloads running on physical and virtual machines (VMs) from a primary site to a secondary location. When an outage occurs at your primary site, you fail over to secondary location, and access apps from there. After the primary location is running again, you can fail back to it.
+- **Backup service**: The [Azure Backup](/azure/backup/) service keeps your data safe and recoverable.
 
 Site Recovery can manage replication for:
 
 - Azure VMs replicating between Azure regions.
-- On-premises VMs, Azure Stack VMs and physical servers.
-
+- On-premises VMs, Azure Stack VMs, and physical servers.
 
 ## What does Site Recovery provide?
 
-
 **Feature** | **Details**
 --- | ---
 **Simple BCDR solution** | Using Site Recovery, you can set up and manage replication, failover, and failback from a single location in the Azure portal.
@@ -38,24 +37,22 @@ Site Recovery can manage replication for:
 **RTO and RPO targets** | Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce RTO further by integrating with [Azure Traffic Manager](https://azure.microsoft.com/blog/reduce-rto-by-using-azure-traffic-manager-with-azure-site-recovery/).
 **Keep apps consistent over failover** | You can replicate using recovery points with application-consistent snapshots. These snapshots capture disk data, all data in memory, and all transactions in process.
 **Testing without disruption** | You can easily run disaster recovery drills, without affecting ongoing replication.
-**Flexible failovers** | You can run planned failovers for expected outages with zero-data loss, or unplanned failovers with minimal data loss (depending on replication frequency) for unexpected disasters. You can easily fail back to your primary site when it's available again.
-**Customized recovery plans** | Using recovery plans, can customize and sequence the failover and recovery of multi-tier applications running on multiple VMs. You group machines together in a recovery plan, and optionally add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.
+**Flexible failovers** | You can run planned failovers for expected outages with zero-data loss. Or, unplanned failovers with minimal data loss, depending on replication frequency, for unexpected disasters. You can easily fail back to your primary site when it's available again.
+**Customized recovery plans** | Using recovery plans, you can customize and sequence the failover and recovery of multi-tier applications running on multiple VMs. You group machines together in a recovery plan, and optionally add scripts and manual actions. Recovery plans can be integrated with Azure automation runbooks.
 **BCDR integration** | Site Recovery integrates with other BCDR technologies. For example, you can use Site Recovery to protect the SQL Server backend of corporate workloads, with native support for SQL Server AlwaysOn, to manage the failover of availability groups.
 **Azure automation integration** | A rich Azure Automation library provides production-ready, application-specific scripts that can be downloaded and integrated with Site Recovery.
-**Network integration** | Site Recovery integrates with Azure for simple application network management, including reserving IP addresses, configuring load-balancers, and integrating Azure Traffic Manager for efficient network switchovers.
-
+**Network integration** | Site Recovery integrates with Azure for application network management. For example, to reserve IP addresses, configure load-balancers, and use Azure Traffic Manager for efficient network switchovers.
 
 ## What can I replicate?
 
 **Supported** | **Details**
 --- | ---
-**Replication scenarios** | Replicate Azure VMs from one Azure region to another.<br/><br/>  Replicate on-premises VMware VMs, Hyper-V VMs, physical servers (Windows and Linux), Azure Stack VMs to Azure.<br/><br/> <br/><br/> Replicate AWS Windows instances to Azure.<br/><br/> Replicate on-premises VMware VMs, Hyper-V VMs managed by System Center VMM, and physical servers to a secondary site.
+**Replication scenarios** | Replicate Azure VMs from one Azure region to another.<br/><br/>  Replicate on-premises VMware VMs, Hyper-V VMs, physical servers (Windows and Linux), Azure Stack VMs to Azure.<br/><br/> Replicate AWS Windows instances to Azure.<br/><br/> Replicate on-premises VMware VMs, Hyper-V VMs managed by System Center VMM, and physical servers to a secondary site.
 **Regions** | Review [supported regions](https://azure.microsoft.com/regions/services/) for Site Recovery. |
 **Replicated machines** | Review the replication requirements for [Azure VM](azure-to-azure-support-matrix.md#replicated-machine-operating-systems) replication, [on-premises VMware VMs and physical servers](vmware-physical-azure-support-matrix.md#replicated-machines), and [on-premises Hyper-V VMs](hyper-v-azure-support-matrix.md#replicated-vms).
-**Workloads** | You can replicate any workload running on a machine that's supported for replication. In addition, the Site Recovery team have performed app-specific testing for a [number of apps](site-recovery-workload.md#workload-summary).
-
-
+**Workloads** | You can replicate any workload running on a machine that's supported for replication. And, the Site Recovery team did app-specific tests for a [number of apps](site-recovery-workload.md#workload-summary).
 
 ## Next steps
-* Read more about [workload support](site-recovery-workload.md).
-* Get started with [Azure VM replication between regions](azure-to-azure-quickstart.md). 
+
+- Read more about [workload support](site-recovery-workload.md).
+- Get started with [Azure VM replication between regions](azure-to-azure-quickstart.md).

articles/site-recovery/vmware-physical-azure-config-process-server-overview.md

@@ -5,17 +5,17 @@ author: rayne-wiselman
 ms.service: site-recovery
 services: site-recovery
 ms.topic: conceptual
-ms.date: 11/12/2019
+ms.date: 03/17/2020
 ms.author: raynew
 ---
 
 # About Site Recovery components (configuration, process, master target)
 
-This article describes the configuration, process, and master target servers used when replicating VMware VMs and physical servers to Azure with the [Site Recovery](site-recovery-overview.md) service.
+This article describes the configuration, process, and master target servers used by the [Site Recovery](site-recovery-overview.md) service to replicate VMware VMs and physical servers to Azure.
 
 ## Configuration server
 
-For disaster recovery of on-premises VMware VMs and physical servers, you need a Site Recovery configuration server deployed on-premises.
+For disaster recovery of on-premises VMware VMs and physical servers, deploy an on-premises Site Recovery configuration server.
 
 **Setting** | **Details** | **Links**
 --- | --- | ---
@@ -26,25 +26,25 @@ For disaster recovery of on-premises VMware VMs and physical servers, you need a
 **Physical server requirements** | For disaster recovery on on-premises physical servers, you deploy the configuration server manually. | [Learn about](physical-azure-set-up-source.md#prerequisites) the prerequisites.
 **Physical server deployment** | If it can't be installed as a VMware VM, you can install it on a physical server. | [Deploy](physical-azure-set-up-source.md#set-up-the-source-environment) the configuration server manually.
 
-
 ## Process server
 
+A process server handles replication data during failover and failback, and installs the Mobility service for on-premises VMware VMs and physical servers.
+
 **Setting** | **Details** | **Links**
 --- | --- | ---
-**Deployment**  | For disaster recovery and replication of on-premises  VMware VMs and physical servers, you need a process server on-premises. By default, the process server is installed on the configuration server when you deploy it. | [Learn more](vmware-azure-architecture.md?#architectural-components).
-**Role (on-premises** | - Receives replication data from machines enabled for replication.<br/> - Optimizes replication data with caching, compression, and encryption, and sends it to Azure Storage.<br/> - Performs a push installation of the Site Recovery Mobility Service on on-premises VMware VMs and physical servers that you want to replicate.<br/> - Performs automatic discovery of on-premises machines. | [Learn more](vmware-physical-azure-config-process-server-overview.md#process-server). 
+**Deployment**  | By default, when the configuration server is deployed the process server is installed. <br/><br/> An on-premises process server is needed for disaster recovery and replication of on-premises VMware VMs and physical servers. | [Learn more](vmware-azure-architecture.md#architectural-components).
+**Role (on-premises**) | Receives replication data from machines enabled for replication. <br/><br/> Optimizes replication data with caching, compression, and encryption, and sends it to Azure Storage. <br/><br/> Performs a push installation of the Site Recovery Mobility service on on-premises VMware VMs and physical servers that you want to replicate. <br/><br/> Performs automatic discovery of on-premises machines. | [Learn more](vmware-azure-enable-replication.md).
 **Role (failback from Azure)** | After failover from your on-premises site, you set up a process server in Azure, as an Azure VM, to handle failback to your on-premises location.<br/><br/> The process server in Azure is temporary. The Azure VM can be deleted after failback is done. | [Learn more](vmware-azure-set-up-process-server-azure.md).
-**Scaling** | For larger deployments, on-premises you can set up additional, scale-out process servers. Additional servers scale out capacity, by handling larger numbers of replicating machines, and larger volumes of replication traffic.<br/><br/> You can move machines between two process servers, in order to load balance replication traffic. | [Learn more](vmware-azure-set-up-process-server-scale.md),
-
+**Scaling** | For larger deployments, on-premises you can set up additional, scale-out process servers. Additional servers scale out capacity, by handling larger numbers of replicating machines, and larger volumes of replication traffic.<br/><br/> You can move machines between two process servers, in order to load balance replication traffic. | [Learn more](vmware-azure-set-up-process-server-scale.md).
 
 ## Master target server
 
 The master target server handles replication data during failback from Azure.
 
-- It's installed by default on the configuration server.
+- By default, the master target server is installed on the configuration server.
 - For large deployments, you can add an additional, separate master target server for failback.
 
-
 ## Next steps
+
 - Review the [architecture](vmware-azure-architecture.md) for disaster recovery of VMware VMs and physical servers.
-- Review the [requirements and prerequisites](vmware-physical-azure-support-matrix.md) for disaster recovery of VMware VMs and physical servers to Azure. 
+- Review the [requirements and prerequisites](vmware-physical-azure-support-matrix.md) for disaster recovery of VMware VMs and physical servers to Azure.