acrofix

Author: Ankita Dutta

articles/site-recovery/site-recovery-sharepoint.md

@@ -17,11 +17,11 @@ This article describes in detail how to protect a SharePoint application using
 
 Microsoft SharePoint is a powerful application that can help a group or department organize, collaborate, and share information. SharePoint can provide intranet portals, document and file management, collaboration, social networks, extranets, websites, enterprise search, and business intelligence. It also has system integration, process integration, and workflow automation capabilities. Typically, organizations consider it as a Tier-1 application sensitive to downtime and data loss.
 
-Today, Microsoft SharePoint  does not provide any out-of-the-box disaster recovery capabilities. Regardless of the type and scale of a disaster, recovery involves the use of a standby data center that you can recover the farm to. Standby data centers are required for scenarios where local redundant systems and backups cannot recover from the outage at the primary data center.
+Today, Microsoft SharePoint  does not provide any out-of-the-box disaster recovery capabilities. Regardless of the type and scale of a disaster, recovery involves the use of a standby data center that you can recover the farm to. Standby data centers are required for scenarios where local redundant systems and backups can't recover from the outage at the primary data center.
 
 A good disaster recovery solution should allow modeling of recovery plans around the  complex application architectures such as SharePoint. It should also have the ability to add customized steps to handle application mappings between various tiers and hence providing a single-click failover with a lower RTO in the event of a disaster.
 
-This article describes in detail how to protect a SharePoint application using [Azure Site Recovery](site-recovery-overview.md). This article will cover best practices for replicating a three tier SharePoint application to Azure, how you can do a disaster recovery drill, and how you can failover the application to Azure.
+This article describes in detail how to protect a SharePoint application using [Azure Site Recovery](site-recovery-overview.md). This article covers the best practices for replicating a three tier SharePoint application to Azure, how you can do a disaster recovery drill, and how you can failover the application to Azure.
 
 
 ## Prerequisites
@@ -46,7 +46,7 @@ SharePoint can be deployed on one or more servers using tiered topologies and se
 
 ## Site Recovery support
 
-Site Recovery is application-agnostic and should work with any version of SharePoint running on a supported machine. For creating this article, VMware virtual machines with Windows Server 2012 R2 Enterprise were used. SharePoint 2013 Enterprise edition and SQL server 2014 Enterprise edition were used.
+Site Recovery is application-agnostic and should work with any version of SharePoint running on a supported machine. For this article, VMware virtual machines with Windows Server 2012 R2 Enterprise was used. SharePoint 2013 Enterprise edition and SQL server 2014 Enterprise edition were used.
 
 ### Source and target
 
@@ -66,7 +66,7 @@ If you're using a shared disk-based cluster as any tier in your application, the
 
 Follow [this guidance](./vmware-azure-tutorial.md) to start replicating the virtual machine to Azure.
 
-* Once the replication is complete, make sure you go to each virtual machine of each tier and select same availability set in 'Replicated item > Settings > Properties > Compute and Network'. For example, if your web tier has 3 virtual machines, ensure all the 3 virtual machines are configured to be part of same availability set in Azure.
+* Once the replication is complete, make sure you go to each virtual machine of each tier and select same availability set in **Replicated item**> **Settings** > **Properties** > **Compute and Network**. For example, if your web tier has 3 virtual machines, ensure all the 3 virtual machines are configured to be part of the same availability set in Azure.
 
 	![Set-Availability-Set](./media/site-recovery-sharepoint/select-av-set.png)
 
@@ -83,7 +83,7 @@ Follow [this guidance](./vmware-azure-tutorial.md) to start replicating the virt
 	![Select Network](./media/site-recovery-sharepoint/select-network.png)
 
 
-* If you are using a static IP, then specify the IP that you want the virtual machine to take in the **Target IP** field
+* If you're using a static IP, then specify the IP that you want the virtual machine to take in the **Target IP** field
 
 	![Set Static IP](./media/site-recovery-sharepoint/set-static-ip.png)
 
@@ -124,17 +124,17 @@ A recovery plan allows sequencing the failover of various tiers in a multi-tier
 
 ### Adding scripts to the recovery plan
 
-You can deploy the most commonly used Azure Site Recovery scripts into your Automation account clicking the 'Deploy to Azure' button. When you are using any published script, ensure you follow the guidance in the script.
+You can deploy the most commonly used Azure Site Recovery scripts into your Automation account clicking the 'Deploy to Azure' button. When you're using any published script, ensure you follow the guidance in the script.
 
 [![Deploy to Azure](https://azurecomcdn.azureedge.net/mediahandler/acomblog/media/Default/blog/c4803408-340e-49e3-9a1f-0ed3f689813d.png)](https://aka.ms/asr-automationrunbooks-deploy)
 
-1. Add a pre-action script to 'Group 1' to failover SQL Availability group. Use the 'ASR-SQL-FailoverAG' script published in the sample scripts. Ensure you follow the guidance in the script and make the required changes in the script appropriately.
+1. Add a pre action script to 'Group 1' to failover SQL Availability group. Use the `ASR-SQL-FailoverAG` script published in the sample scripts. Ensure you follow the guidance in the script and make the required changes in the script appropriately.
 
 	![Add-AG-Script-Step-1](./media/site-recovery-sharepoint/add-ag-script-step1.png)
 
 	![Add-AG-Script-Step-2](./media/site-recovery-sharepoint/add-ag-script-step2.png)
 
-2. Add a post action script to attach a load balancer on the failed over virtual machines of Web tier (Group 2). Use the 'ASR-AddSingleLoadBalancer' script published in the sample scripts. Ensure you follow the guidance in the script and make the required changes in the script appropriately.
+2. Add a post action script to attach a load balancer on the failed over virtual machines of Web tier (Group 2). Use the `ASR-AddSingleLoadBalancer` script published in the sample scripts. Ensure you follow the guidance in the script and make the required changes in the script appropriately.
 
     ![Add-LB-Script-Step-1](./media/site-recovery-sharepoint/add-lb-script-step1.png)
 
@@ -158,9 +158,9 @@ You can deploy the most commonly used Azure Site Recovery scripts into your Auto
 
 6. For starting with a new Search service application, follow these steps:
 
-	* This method assumes that a backup of the “Search Administration” database is available at the DR site.
-	* Since the other Search Service Application databases are not replicated, they need to be re-created. To do so, navigate to Central Administration and delete the Search Service Application. On any servers which host the Search Index, delete the index files.
-	* Re-create the Search Service Application and this re-creates the databases. It is recommended to have a prepared script that re-creates this service application since it is not possible to perform all actions via the GUI. For example, setting the index drive location and configuring the search topology are only possible by using SharePoint PowerShell cmdlets. Use the Windows PowerShell cmdlet Restore-SPEnterpriseSearchServiceApplication and specify the log-shipped and replicated Search Administration database, Search_Service__DB. This cmdlet gives the search configuration, schema, managed properties, rules, and sources and creates a default set of the other components.
+	* This method assumes that a backup of the *Search Administration* database is available at the DR site.
+	* Since the other Search Service Application databases aren't replicated, they need to be re-created. To do so, navigate to Central Administration and delete the Search Service Application. On any servers which host the Search Index, delete the index files.
+	* Re-create the Search Service Application and this re-creates the databases. It is recommended to have a prepared script that re-creates this service application since it's not possible to perform all actions via the GUI. For example, setting the index drive location and configuring the search topology are only possible by using SharePoint PowerShell cmdlets. Use the Windows PowerShell cmdlet Restore-SPEnterpriseSearchServiceApplication and specify the log-shipped and replicated Search Administration database, Search_Service__DB. This cmdlet gives the search configuration, schema, managed properties, rules, and sources and creates a default set of the other components.
 	* Once the Search Service Application has be re-created, you must start a full crawl for each content source to restore the Search Service. You lose some analytics information from the on-premises farm, such as search recommendations.
 
 7. Once all the steps are completed, save the recovery plan and the final recovery plan looks like following: