Skip to content

Commit 7d39d13

Browse files
committed
raising acrolinx score
1 parent 8df1717 commit 7d39d13

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ Data recovery protects you from losing your data in an unfortunate event like co
1515

1616
FarmBeats stores data in three Azure first party services, which are **Azure storage**, **Cosmos DB** and **Time Series Insights**. Below are the steps to enable data redundancy for these services to a paired Azure region:
1717

18-
1. **Azure Storage** : Follow this guideline to enable data redundancy for each storage account in your FarmBbeats deployment.
19-
2. **Azure Cosmos DB** : Follow this guideline to enable data redundancy for Cosmos DB account your FarmBeats deployment.
20-
3. **Azure Time Series Insights (TSI)** : TSI currently does not offer data redundancy. To recover Time Series Insights data, go to your sensor/weather partner and push the data again to FarmBeats deployment.
18+
1. **Azure Storage** - Follow this guideline to enable data redundancy for each storage account in your FarmBbeats deployment.
19+
2. **Azure Cosmos DB** - Follow this guideline to enable data redundancy for Cosmos DB account your FarmBeats deployment.
20+
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.
2121

2222
## Restoring service from online backup
2323

24-
You can initiate failover and recover data stored for which, each of the above mentioned data stores for your FarmBeats deployment. Once you have 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:
24+
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:
2525

26-
1. **Configure Cosmos DB** : Copy the access key of the restored Cosmos DB and update the new FarmBeats Datahub Key Vault.
26+
1. **Configure Cosmos DB** - Copy the access key of the restored Cosmos DB and update the new FarmBeats Datahub Key Vault.
2727

2828

2929
![Disaster Recovery](./media/disaster-recovery-for-farmbeats/keyvault-secrets.png)
@@ -33,7 +33,7 @@ You can initiate failover and recover data stored for which, each of the above m
3333
3434
![Disaster Recovery](./media/disaster-recovery-for-farmbeats/northeu-ehub-api-configuration.png)
3535

36-
2. **Configure Storage Account** : Copy the access key of the restored storage account and update it in the new FarmBeats Datahub Key Vault.
36+
2. **Configure Storage Account** - Copy the access key of the restored storage account and update it in the new FarmBeats Datahub Key Vault.
3737

3838
![Disaster Recovery](./media/disaster-recovery-for-farmbeats/keyvault-7udqm-secrets.png)
3939

0 commit comments

Comments
 (0)