Recover your mobile service in the event of a disaster
When you use Azure Mobile Services to deploy an app, you can use its built-in features to ensure business continuity in the event of availability problems, such as server failures, network disruptions, data loss, and widespread facilities loss. By deploying your app using Azure Mobile Services you are taking advantage of many fault tolerance and infrastructure capabilities that you would have to design, implement, and manage if you were to deploy a traditional on-premise solution. Azure mitigates a large fraction of potential failures at a fraction of the cost.
Prepare for possible disasters
To make recovery easier in case of an availability problem, you can prepare for it in advance:
- Back up your data in the Azure mobile service SQL Database
Your mobile service application data is stored in an Azure SQL Database. We recommend that you back it up as prescribed in the SQL Database business continuity guidance.
- Back up your mobile service scripts
We recommend that you store your mobile service scripts in a source-control system such as Team Foundation Service or [GitHub] and not rely only on the copies in the mobile service itself. You can download the scripts via the Azure portal, using the Mobile Services source control feature, or using the Azure command-line tool. Pay close attention to features labeled as "preview" in the portal, as recovery for those scripts is not guaranteed and you might need to recover them from your own source control original.
- Reserve a secondary mobile service
In the event of an availability problem with your mobile service, you may have to redeploy it to an alternate Azure region. To ensure capacity is available (for example under rare circumstances such as the loss of an entire region), we recommend that you create a secondary mobile service in your alternate region and set its mode the same as or higher than the mode of your primary service. (If your primary service is in shared mode, you can make the secondary service either shared or reserved. But if the primary is reserved, then the secondary must also be reserved.)
Watch for signs of a problem
These circumstances indicate a problem that might require a recovery operation:
- Apps that are connected to your mobile service can't communicate with it for an extended period of time.
- Mobile service status is displayed as Unhealthy in the Azure portal.
- An Unhealthy banner appears at the top of every tab for your mobile service in the Azure portal, and management operations produce error messages.
- The Azure Service Dashboard indicates an availability problem.
Recover from a disaster
When a problem occurs, use the Service Dashboard to get guidance and updates.
If you're prompted by the Service Dashboard, execute the following steps to restore your mobile service to a running state in an alternate Azure region. If you created a secondary service in advance, its capacity will be used to restore the primary service. Because the URL and application key of the primary service is unchanged after recovery, you don't have to update any apps that refer to it.
To recover your mobile service after an outage:
In the Azure portal, ensure that the status of your service is reported as Unhealthy.
If you already reserved a secondary mobile service, you can skip this step.
If you haven't already reserved a secondary mobile service, create one now in another Azure region. Set its mode the same as or higher than the mode of your primary service. (If your primary service is in shared mode, you can make the secondary service either shared or reserved. But if the primary is reserved, then the secondary must also be reserved.)
Configure the Azure command-line tools to work with your subscription, as described in Automate mobile services with command-line tools.
Now you can use your secondary service to recover your primary one.
When you execute the command in this step, the secondary service is deleted so that its capacity can be used to recover the primary service. We recommend that you back up your scripts and settings before you run the command, if you would like to keep them.
When you're ready, execute this command:
azure mobile recover PrimaryService SecondaryService
info: Executing command mobile recover
Warning: this action will use the capacity from the mobile service 'SecondaryService' and delete it. Do you want to recover the mobile service 'PrimaryService'? (y/n): y
+ Performing recovery
+ Cleaning up
info: Recovery complete
info: mobile recover command OK
<p>It may take a few minutes after the command completes until you can see the changes in the portal.</p>
Verify that all scripts have been recovered correctly by comparing them to your originals in source control. In most cases, scripts are automatically recovered without data loss, but if you find a discrepancy, you can recover that script manually.
Make sure that your recovered service is communicating with your Azure SQL Database. The recover command recovers the mobile service, but retains the connection to the original database. If the problem in the primary Azure region also affects the database, the recovered service may still not be running correctly. You can use the Azure Service Dashboard to examine the database status for a given region. If the original database is not working, you can recover it:
- Recover your Azure SQL Database to the Azure region where you just recovered your mobile service, as described in SQL Database business continuity guidance.
- In the Azure portal, on the "Configure" tab of your mobile service, choose "Change database" and then select the newly recovered database.
Now you should be in a state where your mobile service has been recovered to a new Azure region and is now accepting traffic from your store apps using its original URL.