Before you enable and use Recovery Service as the backup destination, you must ensure to verify the minimum requirements and complete all the prerequisite tasks specific to your Oracle Cloud Database service.

Figure 2-1 Prerequisite Configuration Steps to Enable Recovery Service for Database Backups

You can use Oracle Database Autonomous Recovery Service as the backup destination for Oracle Cloud databases provisioned with the following Oracle Database releases.

A service limit is the quota or allowance set on a resource. Use the console to verify that your tenancy's Recovery Service resource limits are adequate to meet your database backup demands.

1. In the navigation menu, select Governance & Administration, and then select Tenancy Management.
2. Select Limits, Quotas and Usage.
3. Select Autonomous Recovery Service from the Service list.
   Review the current limits and usage information.
4. Request a service resource limit increase, if necessary.
   See Requesting a Service Limit Increase for detailed steps.
   Note
   
   You can also control the resource utilization within compartments. See Quota Policy Quick Start for detailed information.

Create Oracle Cloud Infrastructure (OCI) user accounts and groups to manage Recovery Service resources.

Assign the permissions required for OCI Databases to use Recovery Service for backups.

Allow group RecoveryServiceUser to manage recovery-service-policy in compartment ABC

Allow group RecoveryServiceAdmin to manage recovery-service-subnet in compartment ABC

Assign the permissions required for Oracle Database@Azure or Oracle Database@Google Cloud to use Recovery Service for backups.

Allow service database to manage recovery-service-family in tenancy
Allow service database to manage tagnamespace in tenancy
Allow service rcs to manage recovery-service-family in tenancy
Allow service rcs to manage virtual-network-family in tenancy
Allow group admin to manage recovery-service-family in tenancy
Allow service database to use organizations-assigned-subscription in tenancy 
where target.subscription.serviceName = 'ORACLEDBATAZURE'

Allow service database to manage recovery-service-family in tenancy
Allow service database to manage tagnamespace in tenancy
Allow service rcs to manage recovery-service-family in tenancy
Allow service rcs to manage virtual-network-family in tenancy
Allow group admin to manage recovery-service-family in tenancyAllow service database to use 
organizations-assigned-subscription in tenancy where 
target.subscription.serviceName = 'ORACLEDBATGOOGLE'

Use an IP4-only subnet in the database VCN for Recovery Service operations. Define security rules to control the backup traffic between your database and Recovery Service. Finally, register the private subnet as a Recovery Service subnet.

• About Using a Private Subnet for Recovery Service
  Recovery Service uses a private subnet inside a virtual cloud network (VCN) where your database resides. The private subnet defines the network path for backups between your database and Recovery Service.
• Review Networking Service Permissions to Configure a Subnet
  Ensure that you have these Networking Service permissions required to create a subnet in the database VCN and to assign security rules for Recovery Service.
• Review Subnet Size Requirements and Security Rules for Recovery Service Subnet
  The security rules are necessary to allow backup traffic between a database and Recovery Service.
• Create a Recovery Service Subnet in the Database VCN
  Use the OCI Console to configure a private subnet for Recovery Service in your database virtual cloud network (VCN).

After you have created a private subnet for Recovery Service in your database VCN, use this procedure to register the subnet in Recovery Service.

1. Log in to your OCI tenancy.
2. In the navigation menu, click Oracle Database, and select Database Backups to display the Database Backups page.
3. Click Recovery Service Subnets.
4. In the Compartment field, select a compartment where you want to create the Recovery Service subnet.
5. Click Register Recovery Service subnet, and specify the details.
6. In the Name field, enter a name for the Recovery Service subnet.
7. In the Compartment field, select the compartment where you want to create the Recovery Service subnet.
8. In the Virtual cloud network field, select the database VCN.
   Click Change Compartment to select a VCN belonging to a different compartment.
9. In the Subnet field, select a private subnet that you have configured for Recovery Service operations in your database VCN.
   Click Change Compartment to select a private subnet from a different compartment.
10. (Optional) Click +Another Subnet to assign an additional subnet to the Recovery Service subnet.
    If a single subnet does not contain enough IP addresses to support the Recovery Service private endpoints, then you can assign multiple subnets.
11. Click Show advanced options to configure these additional features.
    • Network security groups
    • Tags

    If you have used a network security group (NSG) to implement security rules for Recovery Service in the database VCN, then you must add the Recovery Service NSG to the Recovery Service subnet. The Recovery Service NSG can reside in the same compartment or in a different compartment. However, the NSG must belong to the same VCN to which the specified subnet belongs.

    Note
    
    For Oracle Database@Azure and Oracle Database@Google Cloud, you must register the Recovery Service subnet by associating network security groups (NSG).
    1. In the Network security groups section, select Use network security groups to control traffic.
    2. Select the Recovery Service NSG you have created in the database VCN.
    3. Click +Another network security group to associate multiple NSGs (maximum five).
    (Optional) In the Tag Namespace field, consider adding a tag namespace, or tagging the control with an existing tag namespace.
12. Click Register.

You can replace a subnet or add more subnets to support the required number of private endpoints.

13. Use these steps to update an existing Recovery Service subnet:
    1. In the Recovery Service subnet details page, under Resources, click Subnets.
    2. Click Add subnets and select the subnets you want to add.
    3. To replace an existing subnet, click the Action menu, and select Remove subnet. You can then add another subnet.
    Note
    
    A Recovery Service subnet must be associated with at least one subnet belonging to your database VCN.
14. Use these steps to manage the network security groups (NSGs) for an existing Recovery Service subnet:
    1. In the Network security groups section, click Add network security groups.
    2. Select and add the Recovery Service network security groups (maximum five).
    3. To remove an NSG, select the resource and click Remove.

Recovery Service provides predefined protection policies to suit common use cases for backup retention. You can optionally create custom protection policies to suit your internal data retention requirements.

1. In the navigation menu, select Oracle Database, and then select Database Backups to view the Database Backups page.
2. Click Protection Policies.
3. Recovery Service provides four Oracle-defined protection policies based on typical use cases for backup retention. You cannot modify these policies:
   • Platinum: 95 days
   • Gold: 65 days
   • Silver: 35 days
   • Bronze: 14 days
4. Optionally, create a custom policy to suit your backup retention requirements. See: Creating a Protection Policy.

In Oracle Cloud Infrastructure (OCI), you can create and manage Recovery Service resources using a variety of interfaces provided to fit your different management use cases.