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

How to resolve application issues

Arpio console issues are raised for configuration steps, warnings about your backup & recovery health, and errors from your cloud provider.

Overview

There are 2 main categories of issues:

Backup issues
  • If your RPO graph on the top right still shows regular recovery points, then the issue is informational.
  • If new recovery point captures are blocked, an additional "Backups failing" email is sent. Resolve the issue, or de-select the problematic resource from the application.
Recovery Environment issues
  • When there is not an active failover, issues are raised for the infrastructure resources that are maintained during standby.
    • It is optimal to resolve these issues before launching a Test or Recovery. If unresolved, you can expect the named resource and dependent resources to fail.
  • When there is an active Test or Recovery, additional issues are raised for compute resources that are only created in your recovery environment during a failover.
    • Use the Recovery Environment tab to identify which resources are in a Failed or Queued state. If your recovery application is functional without these resources, then you can choose to ignore the issues and address them before a future test.
    • If critical resources are in a Failed state, see below.

How to remediate

When you receive an email notification about a novel issue, click the link to sign into your Arpio console.

On the application Issues tab, expand the issue to view more details.

  • The timestamp on the bottom right shows the most recent occurrence of this issue. If the timestamp pre-dates changes to your application, then the issue should clear on the next backup or restore attempt.
  • If an "original error" message is shown, this likely originated from AWS, Azure, or the Kubernetes control plane. Jump to those environments to address the root cause.
After remediating the root cause, click Retry Backup or Resume Restore to clear the issue. It is recommended to address all blocking issues before clicking these buttons, which will cause Arpio to reprocess all interdependent applications.

 

Common types of issues

  • Kubernetes timeouts: Pod logs can indicate what's preventing the resource from deploying, if it has not already become healthy.
  • Quota limits: Your recovery environment may require even higher limits than your source environment. Request a limit increase through the AWS/Azure console, then click Resume Restore.