Performing a Failback

How to failback your application with Arpio

Note: Failback is a feature of the Arpio Enterprise subscription only. Learn more.


Failback is an Arpio feature that allows you to quickly and easily copy the most recent data from your Recovery Environment back to your Primary Environment.

Failback is currently available for EC2, RDS, Aurora, and DynamoDB resource types.

Performing a Failback

To perform a test or actual failback, click on the “Failback” button in your application dashboard.

This will open the following dialog:

Failback Access

As part of our strategy for maintaining high security standards, Arpio has very limited access to your primary environment. However, in order to perform a failback, Arpio will temporarily need some extra permissions. To enable these expanded permissions, you will be provided with an additional CloudFormation template to install a new CloudFormation stack in your Primary Environment.

The process of adding a new CloudFormation template is the same that you went through when creating a new application. When you have completed your failback, you can delete this additional stack to restore Arpio to its original state.

The "Failback" button will be enabled once Arpio detects that it has the right access.

Once you click “Failback,” Arpio will take over and begin copying the latest data from your Recovery Environment back to your Primary Environment.

Your application will remain in the recovery state while the failback operation completes. Once you are satisfied that your application has been properly restored, click Conclude Recovery to use Arpio to turn down the AWS resources that cost money in your recovery environment, and update other resources to the latest recovery point. Your recovery environment will be ready for re-use in the future.