Azure Recovery

To initiate the recovery from Cloud Assembly, follow the steps below.
  1. Navigate to “Cloud Assemblies” in the left navigation menu
  2. Select a Cloud Assembly to recover
  3. Select the “Timeline” tab, which will list down all the timeline events for that Cloud Assembly
  4. Select a fully protected timeline for recovery. It will open the protection details of the Cloud Assembly for that point in time
  5. From the “Timeline Details,” select “RECOVER” in the top right corner
  6. Enter a name for the recovery and select the recovery type
  7. Select the recovery regions from the list of recovery regions selected during the Cloud Connection configuration, and choose to recover the “Entire Assembly” (Recover all the resources in the assembly) or only the “Specific Resources” (Recover selected resources in the assembly)
  8. Enable the "Select specific resources" and click on the drop down near the resources. You can select only the required few resources for recovery from the list of associated resources listed under the Resource Group
  9. Click “Recover” to recover the protected resources

Recovery Scenarios

Appranix covers the following recovery scenarios during the protected resource's recovery.

  1. The selected resource's recovery will only recover the resources of the selected “resource groups”
  2. For SQL, MySQL and PostgreSQL Servers,
    • Only 'Same-Region' & 'Same-Resource group' selected resource recovery is supported
    • Cross-region recovery is not supported due to Azure limitation
  3. For VM's/ VMSS following configurations will not be recovered.
    • Any Extentions
    • Any storage account associated with compute will not be recovered, any fileshares associated will not be mounted.
    • Any auto scaling that is configured will not be recovered.


  • Appranix supports PaaS database protection and recovery only if the Azure backups are enabled for it
  • SQL Servers cannot be restored. Only Databases inside the SQL Server can be restored into the same SQL Server

Other region recovery

The user can recover the entire assembly or only the selected resource groups to the recovery region. Appranix creates a new resource group and recovers all the protected resources from the chosen resource group or the entire assembly to the recovery region.

Advanced recovery options

  1. Recover scale set without instances: By enabling this option, Appranix will recover the scale set without instances. Once the recovery is over, the scale sets can be scaled up manually or through Appranix webhooks.
    Note: Appranix retains most service private IPs during recovery. However, recovering other services with scale sets may cause static IP loss. VMSS IPs are dynamic by default, potentially increasing the risk of taking other resources' static IPs during recovery. To prevent this, enable 'Recover Scale Set with Zero Instances'.

  2. Enable VNet mapping: By enabling this option, Appranix provides the capability of choosing a custom recovery VNet that already exists in your Azure account. By using this feature, customers have control over mapping their recovery VNet and subnet.

  3. Retain Private IP Range: By enabling this option, Appranix retains all the same source private IPs in the recovered resource. Click here for details
    Note: If you enable "Retain Private IP" along with custom VNet recovery, the recovery VNet CIDR needs to be the same as the source VNet.

  4. Override Resource Dependencies: This option is available only for same VNet recovery. By enabling this option, Appranix recover only VMs and VM Scale Sets all the other dependencies like Load Balancers, Application Gateways, and Network Security Groups will be overridden with the backup configuration.

Delete recovered resources

Appranix allows the deletion of recovered resources using the RESET option. The reset of the recovered instances can be scheduled or performed on demand. The reset helps to delete the recovered resources and roll back the Azure resources to the original state. Resetting helps to reduce the Azure cloud cost that can incur due to recovery testing.

  1. Recovery can be deleted by either scheduling a reset or by triggering a reset immediately
  2. The reset schedule can either be set while configuring recovery or after the completion of recovery
  3. Schedule a reset by choosing the number of hours or days after which the reset has to be triggered
  4. Select the “Reset Now” option to trigger reset immediately
  5. The “Recovery Details” tab has the list of recoveries with essential details of the recovery along with the status of the reset
  6. Once the reset action is triggered, the reset status changes to “Reset In Progress.” When deleted, it changes to “Reset completed”
  7. The “Recovery Logs” tab contains recovery and reset logs. It provides all the details of the execution for recovery, and the reset process details
Need more help? Submit a ticket