Recovery Service failure checks

 When using the Autonomous Recovery Service there are some prerequisites that need be met. I have a checklist that goes through these requirements, and you can find that checklist here.

This blog post will help you perform some basic debugging and demonstrate what errors you will see if you miss some of the steps.

This post is broken into two possible places where you will have issues.

1. Unable to Submit request. This can be caused by
• Policy issues
• Limits issue
2. You submitted backup, but it failed to configure the Recovery Service. This can be caused by
• DNS issues with resolving FQDN used by Recovery Service
• Routing/port issues accessing the Recovery Service or Object Storage

Unable to submit Autonomous Recovery Service as a backup location

Policies for the tenancy

The first step is to ensure that you have configured policies for the recovery service.  The easiest way to do this is by utilizing Policy Builder.

NOTE: There is a policy that grants access to the "ADMIN" group. If your administrator group is a different group, you would 

Visible Issue

 If policies are not configured properly, you find that "Recovery Service" is greyed out as an option.

Limits for the Recovery Service

By default if you are not in a multi-cloud environment your paid tenancy will have a limit of

• 10 Database
• 10 TB of backups storage

If you are using Multi-cloud, and your database is in partner cloud, there is no default limits.

By default there are no limits set.

This is the most common issue I see with multicloud.  You need to set the limit specifically for the multi-cloud subscription.

Visible Issue

 If limits  are not configured properly, you find that "Recovery Service" is greyed out as an option.

Below the choice for "Recovery service", you will see that there is a warning, telling you that you have exceeded your limits.