Admin Guide
Table of Contents
This document explains how to use the solution in addition to User Document. In this we are configuring, verifying and performing DR activities for Standard and Premium solutions.
In this scenario, there is again a primary and a secondary Azure region. All the traffic goes to the active deployment on the primary region. The secondary region is better prepared for disaster recovery because the database is running on both regions.
Only the primary region has a deployed cloud service application. Both regions are synchronized with the contents of the database. When a disaster occurs, there are fewer activation requirements. You redeploy azure resources in the secondary region.
Redeployment approach, you should have already stored the service packages. However, you don’t incur most of the overhead that database restore operation requires, because the database is ready and running. This saves a significant amount of time, making this an affordable DR pattern.
Standard Solution requires redeployment of azure resources in secondary region when the primary region is down.
When user chooses Standard Solution type below azure resources will be deployed in primary region and Cosmos DB in both Regions.
- App service
- Application insights
- Automation account
- Azure cosmos DB
- IoT Hub
- Log analytics
- Notification Hub
- Stream analytics job
- Traffic manager profile.
When Primary region is down, and user needs to redeploy azure resources to new region. Once redeployment gets completed below resources will get deployed.
- App service
- Application insights
- Notification hub
- Stream analytics Job
Refer 4.1 and 4.2 Section in Deployment Guide for Standard Solution Deployment.
Go to Resource Group -> Click on IoT Hub.
Go to Manual Failover (Preview) from left side menu.
Click on Initiate failover to initiate manual failover of IoT Hub.
When failover process started, a pop up will be displayed on right top corner.
Once Manual Failover process completed, Primary Location and secondary location will interchange.
Note: This process will take around 15 mins. To initial failover again, user needs wait for 1 hour to run failover again.
Go to Resource Group and click on primary Stream Analytics job
Stop the Stream analytics job by click on Stop and click on Yes for confirmation.
Go to Resource Group and click on Traffic manager resource.
Now you can see the web app as the endpoint of the traffic manager.
Navigate to the Web App from resource group.
click on Stop then click on Yes to stop the Web App.
The Web App in the primary region has been stopped as failover.
Verify the same in traffic manager.
Go to Github and select re-deploy.json file from the master branch.
Click on Raw.
Copy the re-deploy.json template.
Click on Add in existing resource group and re-deploy the ARM template.
Go to Resource Group -> Traffic manager profile -> Endpoints, click on add.
Enter the name for the second End point of traffic manager and select the second web app as the target resource.
Click on Ok.
You can see the second region web app with online status under endpoint of traffic manager and Copy the DNS Name.
Go to Resource Group -> click Cosmos DB.
Navigate to Replicate data globally under Settings section then click Manual failover.
Select the Read Region to become the new write region, check in the check box and click ok.
Go to Resource Group -> Settings -> Deployments, select Microsoft Template.
Select output and copy the devicemanagement_trafficmanager url.
paste the copied URL in new browser to access the Web App using your credentials.
You can see the Device summary as shown below.
Both the primary region and the secondary region have a full deployment. This deployment includes the cloud services and a synchronized database. However, only the primary region is actively handling network requests. The secondary region becomes active only when the primary region experiences a service disruption. In that case, all new network requests route to the secondary region. Azure Traffic Manager can manage this failover automatically.
Failover occurs faster than the database-only variation because the services are already deployed. This topology provides a very low RTO. The secondary failover region must be ready to go immediately after failure of the primary region.
For the fastest response time with this model, you must have similar scale (number of role instances) in the primary and secondary regions.
When user chooses premium as solution type below azure resource will be deployed in both regions.
- 2 app services
- 2 application insights
- 1 automation account
- 1 cosmos DB
- 1 IoT Hub
- 1 Log Analytics
- 2 Notification Hubs
- 2 Stream analytics job
- 1 Traffic manager
Refer 4.1 and 4.2 Section in Deployment Guide for Premium Solution Deployment.
Go to Resource Group and Click on IoT Hub.
Go to Manual Failover(Preview) from left side menu.
Click on Initiate failover to initiate manual failover of IoT Hub.
You can check the status of the failover.
When failover process started, a pop up will be displayed on right top corner. Once Manual Failover process completed, Primary Location and secondary location will interchange.
Note: This process will take around 15 mins. To initial failover again, user needs wait for 1 hour to run failover again.
Go to Resource Group and click on primary Stream Analytics job.
Stop the Stream analytics job by click on Stop and click on Yes for confirmation.
You can see the stream analytics job has been stopped.
Go to Resource Group and click on Traffic manager resource.
Now you can see the web app as the endpoint of the traffic manager.
Navigate to the Web App from the resource group.
Select the primary Web App click on Stop then click on Yes to stop the Web App.
The Web App in the primary region has been stopped as failover.
Verify the Status of primary web app in traffic manager.
Go to Resource Group -> click Cosmos DB.
Navigate to Replicate data globally under Settings section then click Manual failover.
Select the Read Region to become the new write region, check in the check box and click ok.
Go to Resource Group -> Settings -> Deployments, select Microsoft Template.
Select output and copy the devicemanagement_trafficmanager url.
paste the copied URL in new browser to access the Web App using your credentials.
You can see the Device summary as shown below.
