Skip to content
English
Customer ticket portal
  • There are no suggestions because the search field is empty.

Recovery Point

What is a recovery point?

A recovery point is a snapshot of your cloud resources and their data at a particular point in time.

Arpio continuously creates recovery points in your recovery environment based on the recovery point objective you set when you are creating an application.

How recovery points work

Arpio uses cloud-native snapshot mechanisms to capture your resources. The underlying technology is specific to each cloud provider and service, but the Arpio experience is consistent: you configure your recovery point objective, Arpio continuously creates recovery points, and when you need to recover, you select a recovery point from your available timeline.

Recovery points on AWS

On AWS, Arpio leverages native AWS services such as AWS Backup, EBS snapshots, RDS snapshots, and other service-specific snapshot mechanisms to capture your resources and their data. These snapshots are stored in your recovery environment (recovery account + recovery region).

 For applications with a real-time RPO, Arpio achieves real-time replication by leveraging various native capabilities like DRS, Aurora global databases, and more.

Recovery points on Azure

On Azure, Arpio uses native Azure capabilities including VM Restore Points and managed disk snapshots to capture your resources. Arpio creates restore point collections for your virtual machines and performs cross-region disk restore point copies to replicate data to your recovery environment (recovery subscription + recovery region).

Azure VM Restore Points can be either application-consistent or crash-consistent, depending on the health of the Azure VM Agent on each virtual machine. Application-consistent restore points coordinate with the guest OS to flush in-memory data and pending I/O operations before the snapshot. Crash-consistent restore points capture the disk state without guest OS coordination.

 

Selecting a recovery point

When performing a failover or test failover, Arpio allows you to choose which recovery point to use:

  • Latest recovery point (“Now”): For applications with a real-time RPO, Arpio restores your most recent data. On AWS, if real-time replication is enabled for Aurora databases, Arpio restores from the secondary cluster. On Azure, Arpio uses the most recent VM restore point and disk snapshots available in your recovery environment.
  • Older recovery point (point in time): Drag the slider back to select a specific point in time. Arpio will use the snapshots stored in your recovery environment that correspond to that time. The available recovery points depend on your retention policy.

Recovery point retention

Your retention policy determines how many recovery points Arpio retains and how far back your available points in time extend. Arpio automatically manages the lifecycle of snapshots in your recovery environment, creating new ones according to your RPO and cleaning up old ones which have aged out of your retention policy.

This applies consistently across both AWS and Azure workloads. You can review your current retention policy configuration and adjust it in your Account Settings.

Viewing recovery points

You can view the status and timing of your recovery points in the Arpio console:

  • RPO graph: Hover over the RPO graph on the top right of the application page to see the latest recovery point timestamp.
  • Test button: Click the Test button on an application and drag the slider to preview the available recovery points and their timestamps.
  • Cloud provider console: On AWS, you can locate snapshots for specific resources in the relevant service console (e.g., RDS > Snapshots, EC2 > Elastic Block Store > Snapshots). Snapshots managed by Arpio will have an arpio:account tag. On Azure, you can view restore point collections and disk snapshots in the Azure Portal under the relevant resource groups.

Recovery point issues

If Arpio encounters an error while creating a recovery point, you will see a recovery point issue on your application page. Common causes include:

  • AWS: Snapshot quota limits, misconfigured RDS option groups, missing cross-account backup permissions (e.g., for EFS), or transient AWS service errors.
  • Azure: VM Agent communication errors, Azure platform timeouts during restore point provisioning, disk restore point copy failures, or transient Azure service issues.

Arpio will automatically retry failed backup operations. If an issue persists, review the issue details in the console and contact Arpio support for assistance.