Onboarding Oracle Database to Recovery Service

Use this checklist to verify the mandatory prerequisites to onboard your Oracle Database to Recovery Service.

You may choose to configure these additional options for Recovery Service.

A service limit is the quota or allowance set on a resource. Autonomous Recovery Service has maximum limits for the number of protected databases and the backup storage space utilization. The limits apply to each region.

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. For Oracle Multicloud Databases, ensure to review and adjust the limits specific to your multicloud subscription from the Limits, Quotas and Usage page.

   Caution:

   If you do not select the multicloud subscription, then the increased limits will be applied to OCI resources.
5. (Optional) You can also control the resource utilization within compartments. See Quota Policy Quick Start for detailed information.

By default, Oracle Databases in OCI are assigned with the permissions to access Recovery Service. The service can also access the network resources within the database VCN. You may choose to assign the additional and optional permissions for OCI Databases, as described in this topic.

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

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

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

Allow service database to manage tagnamespace 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 tagnamespace 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 = 'ORACLEDBATGOOGLE'

Create or use an existing IPv4-only subnet for Recovery Service operations in the database VCN. Define security rules to control the backup traffic between your database and Recovery Service.

• About Using a Private Subnet for Recovery Service Operations
  Recovery Service requires a private subnet in the same virtual cloud network (VCN) where your database resides. The private subnet must include security rules to control the backup network 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.
• Subnet Size 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).

Use this procedure to register a Recovery Service subnet.

1. On the Recovery Service subnets list page, select Register Recovery Service subnet. See Listing Recovery Service Subnets for detailed steps to access the list page.
2. Enter a name for the Recovery Service subnet. Avoid entering confidential information in the Name field.
3. Verify the compartment where you want to create the Recovery Service subnet. Use the Create in compartment field to select a different compartment, if necessary.
4. Select the Compartment that contains the virtual cloud network (VCN) that you want to use. You can select a VCN from only one compartment at a time
5. Select the virtual cloud network.
6. Under Subnets, select these options:
   1. Select the Compartment that contains the private subnet that you want to use.
   2. Select the Subnet that you have configured for Recovery Service operations in the selected VCN.
7. (Optional) Select +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.
   See About Using a Private Subnet for Recovery Service Operations for details.
8. Expand Advanced options to configure these options:
   • Network security groups

     If you have used a network security group (NSG) to implement security rules for Recovery Service in the database VCN or if your target database is an Oracle Multicloud Database, 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.

     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. Select +Another network security group to associate multiple NSGs (maximum five).
     Note
     
     For Oracle Database@Azure and Oracle Database@Google Cloud, you must register the Recovery Service subnet by associating network security groups (NSG).

   • Tags: (Optional) Add one or more tags to the resource. If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.

9. Select Register.
   Note
   
   A Recovery Service subnet must be associated with at least one subnet belonging to your database VCN.

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.