Merge pull request #111088 from uhabiba04/master

added new article

Author: v-albemi

articles/industry/agriculture/disaster-recovery-for-farmbeats.md

@@ -0,0 +1,61 @@
+---
+title: Disaster recovery for FarmBeats
+description: This article describes how data recovery protects from losing your data.
+author: uhabiba04
+ms.topic: article
+ms.date: 04/13/2020
+ms.author: v-umha
+---
+
+# Disaster recovery for FarmBeats
+
+Data recovery protects you from losing your data in an event like collapse of Azure region. In such an event, you can start failover, and recover the data stored in your FarmBeats deployment.
+
+Data recovery is not a default feature in Azure FarmBeats. You can configure this feature manually by configuring the required Azure resources that are used by FarmBeats to store data in an Azure paired region. Use Active – Passive approach to enable recovery.
+
+The following sections provide information about how you can configure data recovery in Azure FarmBeats:
+
+- [Enable data redundancy](#enable-data-redundancy)
+- [Restore service from online backup](#restore-service-from-online-backup)
+
+
+## Enable data redundancy
+
+FarmBeats stores data in three Azure first party services, which are **Azure storage**, **Cosmos DB** and **Time Series Insights**. Use the following steps to enable data redundancy for these services to a paired Azure region:
+
+1.	**Azure Storage** - Follow this guideline to enable data redundancy for each storage account in your FarmBbeats deployment.
+2.	**Azure Cosmos DB** - Follow this guideline to enable data redundancy for Cosmos DB account your FarmBeats deployment.
+3.	**Azure Time Series Insights (TSI)** - TSI currently doesn't offer data redundancy. To recover Time Series Insights data, go to your sensor/weather partner and push the data again to FarmBeats deployment.
+
+## Restore service from online backup
+
+You can initiate failover and recover data stored for which, each of the above mentioned data stores for your FarmBeats deployment. Once you've recovered the data for Azure storage and Cosmos DB, create another FarmBeats deployment in the Azure paired region and then configure the new deployment to use data from restored data stores (i.e. Azure Storage and Cosmos DB) by using the below steps:
+
+1. [Configure Cosmos DB](#configure-cosmos-db)
+2. [Configure Storage Account](#configure-storage-account)
+
+
+### Configure Cosmos DB
+
+Copy the access key of the restored Cosmos DB and update the new FarmBeats Datahub Key Vault.
+
+
+  ![Disaster Recovery](./media/disaster-recovery-for-farmbeats/keyvault-secrets.png)
+
+> [!NOTE]
+> Copy the URL of restored Cosmos DB and update it in the new FarmBeats Datahub App Service Configuration. You can now delete Cosmos DB account in the new FarmBeats deployment.
+
+  ![Disaster Recovery](./media/disaster-recovery-for-farmbeats/northeu-ehub-api-configuration.png)
+
+### Configure Storage Account
+
+Copy the access key of the restored storage account and update it in the new FarmBeats Datahub Key Vault.
+
+![Disaster Recovery](./media/disaster-recovery-for-farmbeats/keyvault-7udqm-secrets.png)
+
+>[!NOTE]
+> Ensure to Update Storage Account name in the new FarmBeats Batch VM config file.
+
+![Disaster Recovery](./media/disaster-recovery-for-farmbeats/batch-prep-files.png)
+
+Similarly, if you have enabled data recovery for your Accelerator storage account,  follow the step 2 to update the accelerator Storage Account access key and name, in the new FarmBeats instance.

articles/industry/agriculture/media/disaster-recovery-for-farmbeats/batch-prep-files.png

@@ -37,6 +37,8 @@
      href: configure-rules-alerts-in-azure-farmbeats.md
    - name: Get drone imagery
      href: get-drone-imagery-in-azure-farmbeats.md
+   - name: Disaster recovery
+     href: disaster-recovery-for-farmbeats.md
 - name: Troubleshoot
   items:
    - name: Troubleshoot Azure FarmBeats