Configuring Recovery Service
Review and complete the configuration tasks required to implement Recovery Service in your tenancy.
- Prerequisite Tasks for Using Recovery Service
Before you enable and use Recovery Service as the backup destination, you must ensure to verify the common minimum requirements and complete all the prerequisite tasks specific to your Oracle Cloud Database service. - Oracle Database Releases That Support Recovery Service
You can use Oracle Database Autonomous Recovery Service as the backup destination for Oracle Cloud databases provisioned with the following Oracle Database releases. - Review Limits for Recovery Service
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. - Create Groups and Users to Manage Recovery Service
Create Oracle Cloud Infrastructure (OCI) user accounts and groups to manage Recovery Service resources. - Permissions Required for Oracle Databases in OCI to Use Recovery Service
Assign the permissions required for OCI Databases to use Recovery Service for backups. - Permissions Required for Multicloud Oracle Databases to Use Recovery Service
Assign the permissions required for Oracle Database@Azure or Oracle Database@Google Cloud to use Recovery Service for backups. - Configuring Network Resources for Recovery Service
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. - Register Recovery Service Subnet
After you have created a private subnet for Recovery Service in your database VCN, use this procedure to register the subnet in Recovery Service. - (Optional) Review Protection Policies for Database Backup Retention
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. - Ways to Manage Recovery Service Resources
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.
Prerequisite Tasks for Using Recovery Service
Before you enable and use Recovery Service as the backup destination, you must ensure to verify the common minimum requirements and complete all the prerequisite tasks specific to your Oracle Cloud Database service.
- Common Minimum Requirements for Oracle Database Services to Use Recovery Service, see Table 2-1
Common mandatory prerequisites required for using Recovery Service.
- Prerequisites for Oracle Databases in OCI, see Table 2-2
Specific prerequisites for Oracle Exadata Database Service on Dedicated Infrastructure and Oracle Base Database Service to use Recovery Service for backups.
- Prerequisites for Multicloud Oracle Databases, see Table 2-3
Specific prerequisites for multicloud Oracle Database services to use Recovery Service for backups.
Operational backups to two different backup destinations may create data loss scenarios. Therefore, before you enable automatic backups to Recovery Service, you must disable manual backup scripts and processes to other storage destinations.
Table 2-1 Common Minimum Requirements for Oracle Database Services to Use Recovery Service
Minimum Requirement | More Information |
---|---|
Verify whether Recovery Service is supported for your target database version. |
|
Ensure that Recovery Service resource limits are adequate. |
|
As a tenancy administrator, create the Oracle Cloud Infrastructure IAM users and groups to manage Recovery Service related tasks. |
Table 2-2 Prerequisites for Supported Oracle Databases in OCI
Step | Task | More Information |
---|---|---|
1 |
Use the Autonomous Recovery Service policy templates to assign permissions for Oracle Cloud Databases in OCI to use Recovery Service for backups. |
Permissions Required for Oracle Databases in OCI to Use Recovery Service |
2 |
Configure the required network resources to enable the backup network path to Recovery Service. |
|
3 |
Register a Recovery Service subnet. |
|
4 |
Review protection policies and enable automatic backups to Autonomous Recovery Service. |
(Optional) Review Protection Policies for Database Backup Retention |
Table 2-3 Prerequisites for Oracle Database@Azure and Oracle Database@Google Cloud
Step | Task | More Information |
---|---|---|
1 |
Use the Autonomous Recovery Service policy templates to assign the permissions required for Oracle Database@Azure or Oracle Database@Google Cloud to use Recovery Service for backups. |
Permissions Required for Multicloud Oracle Databases to Use Recovery Service |
2 |
Do one of the following for Oracle Database@Azure and Oracle Database@Google Cloud:
|
|
3 |
Register a Recovery Service subnet. For multicloud Oracle Databases, such as Oracle Database@Azure or Oracle Database@Google Cloud, you must register the Recovery Service subnet by associating NSGs. |
|
4 |
Review protection policies and then enable automatic backups to Recovery Service. |
(Optional) Review Protection Policies for Database Backup Retention |
Related Topics
Parent topic: Configuring Recovery Service
Oracle Database Releases That Support Recovery Service
You can use Oracle Database Autonomous Recovery Service as the backup destination for Oracle Cloud databases provisioned with the following Oracle Database releases.
Table 2-4 Oracle Database Releases that Support Recovery Service
Oracle Database Edition and Version | More Information |
---|---|
Oracle Database 19c Release 16 (19.16) or later |
Your target database must meet these minimum requirements:
|
Oracle Database 21c Release 7 (21.7) or later |
Your target database must meet these minimum requirements:
|
Oracle Database 23ai (23.4) or later |
To use Recovery Service, your target database must have a minimum compatibility level of 19.0 (the |
Related Topics
Parent topic: Configuring Recovery Service
Review Limits for Recovery Service
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.
Autonomous Recovery Service has maximum limits for the number of protected databases and the backup storage space utilization. The limits apply to each region.
Table 2-5 Autonomous Recovery Service Resource Limits
Resource | Oracle Universal Credits | Pay As You Go or Trial |
---|---|---|
Autonomous Recovery Service Protected Database Count |
||
Autonomous Recovery Service Space Used for Recovery Window (GB) |
Use the console to review the current service limits and usage information, and request an increase in resource limits, if necessary.
Related Topics
Parent topic: Configuring Recovery Service
Create Groups and Users to Manage Recovery Service
Create Oracle Cloud Infrastructure (OCI) user accounts and groups to manage Recovery Service resources.
You can then assign Recovery Service policy statements to the groups. For example, create a group called recoveryserviceadmin
and assign the policy that allows the group to manage protected databases, protection policies, and Recovery Service subnets.
Table 2-6 Creating Groups and Users for Recovery Service
Task | More Information |
---|---|
Create a group |
|
Create users |
|
Add users to a group |
|
Assign policies to groups |
Permissions Required for Oracle Databases in OCI to Use Recovery Service |
Parent topic: Configuring Recovery Service
Permissions Required for Oracle Databases in OCI to Use Recovery Service
Assign the permissions required for OCI Databases to use Recovery Service for backups.
In the Policy Builder, select Autonomous Recovery Service as the Policy Use Case, and then select these predefined policy templates:
Recovery Service includes separate policy templates for Oracle Database@Azure and Oracle Database@Google Cloud. If you are configuring Recovery Service for your multicloud Oracle Database, then skip this step and proceed to Permissions Required for Multicloud Oracle Databases to Use Recovery Service.
Ability to do all things with Autonomous Recovery Service
The Ability to do all things with Autonomous Recovery Service policy template includes all the policy statements required to provide permissions for the supported database services to use Recovery Service, and for Recovery Service to use the network resources to access databases in a VCN.
You can either select the policy template or add these policy statements using the manual editor in the Policy Builder.
Table 2-7 Policy Statements Required for Using Recovery Service
Policy Statement | Create In | Purpose |
---|---|---|
|
Root compartment |
Enables the OCI Database Service to access protected databases, protection policies, and Recovery Service subnets within your tenancy. |
|
Root compartment |
Enables the OCI Database Service to access the tag namespace in a tenancy. |
|
Root compartment |
Enables Recovery Service to access and manage protected databases, Recovery Service subnets, and protection policies within your tenancy. |
|
Root compartment |
Enables Recovery Service to access and manage the private subnet in each database VCN within your tenancy. The private subnet defines the network path for backups between a database and Recovery Service. |
|
Root compartment |
Enables users in a specified group to access all Recovery Service resources. Users belonging to the specified group can manage protected databases, protection policies, and Recovery Service subnets. |
Let users manage protection policies in Autonomous Recovery Service
The Let users manage protection policies in Autonomous Recovery Service policy template grants permissions for users in a specified group to create, update, and delete protection policy resources in Recovery Service.
You can either select the policy template or add this policy statement using the manual editor in the Policy Builder.
Table 2-8 Policy Statement for Managing Protection Policies
Policy Statement | Create In | Purpose |
---|---|---|
|
Compartment that owns the protection policies. |
Enables all users in a specified group to create, update, and delete protection policies in Recovery Service. |
Consider this example.
RecoveryServiceUser
group with the permissions to create, update, and delete protection policies in ABC
compartment.Allow group RecoveryServiceUser to manage recovery-service-policy in compartment ABC
Let users manage Autonomous Recovery Service Subnets
The Let users manage Autonomous Recovery Service subnets policy template grants permissions for users in a specified group to create, update, and delete Recovery Service subnet resources.
You can either select the policy template or add this policy statement in the Policy Builder.
Table 2-9 Policy Statement for Managing Recovery Service Subnets
Policy Statement | Create In | Purpose |
---|---|---|
|
Compartment that owns the Recovery Service subnets. |
Enables all users in a specified group to create, update, and delete Recovery Service subnets. |
Consider this example.
RecoveryServiceAdmin
group with the permissions to manage Recovery Service subnets in ABC
compartment.Allow group RecoveryServiceAdmin to manage recovery-service-subnet in compartment ABC
Related Topics
Parent topic: Configuring Recovery Service
Permissions Required for Multicloud Oracle Databases to Use Recovery Service
Assign the permissions required for Oracle Database@Azure or Oracle Database@Google Cloud to use Recovery Service for backups.
Let Oracle Database@Azure use Autonomous Recovery Service for backup
This policy template includes these policy statements required by 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'
ORACLEDBATAZURE
indicates the service name for Oracle Database@Azure.
Let Oracle Database@Google Cloud use Autonomous Recovery Service for backup
This policy template includes these policy statements required by 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 tenancyAllow service database to use
organizations-assigned-subscription in tenancy where
target.subscription.serviceName = 'ORACLEDBATGOOGLE'
ORACLEDBATGOOGLE
indicates the service name for Oracle Database@Google Cloud.
See Multicloud Oracle Database Backup Support for more information about using Recovery Service for multicloud Oracle Database backups.
Parent topic: Configuring Recovery Service
Configuring Network Resources for Recovery Service
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.
For Oracle Database@Azure and Oracle Database@Google Cloud, if your backup subnet meets the recommended /24 subnet size requirement, then skip this section and directly proceed to register the Recovery Service subnet using network security groups (NSGs). Otherwise, you must first complete the steps described in this section, and then proceed to register the 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).
Parent topic: Configuring Recovery Service
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.
Oracle recommends that your database VCN must have a single private subnet dedicated for backups to Recovery Service. Your Oracle Cloud database can reside in the same private subnet used by Recovery Service, or in a different subnet within the same VCN.
You can either create a private subnet or use a preexisting subnet in your database VCN. Oracle recommends that you use a subnet size of /24 (256 IP addresses).
Select an IPv4-only subnet for Recovery Service in your database VCN. Do not select an IPv6-enabled subnet as Recovery Service does not support using an IPv6-enabled subnet. See Creating a Subnet to learn more.
- Security Lists
A security list allows you to add security rules at the subnet level. In your database VCN, select the security list that is used for the Recovery Service subnet, and add the ingress rules to allow destination ports 8005 and 2484.
- Network Security Groups (NSG)Network security groups (NSG) enable granular control over security rules that apply to individual VNICs in a VCN. Recovery Service supports these options to configure security rules using NSGs:
- To implement network isolation, create one NSG for the database VNIC (add egress rules to allow ports 2484 and 8005) and a separate NSG for Recovery Service (add ingress rules to allow ports 2484 and 8005).
- Create and use a single NSG (with egress and ingress rules) for the database VNIC and Recovery Service.
If you have configured a security list and an NSG within your database VCN, then the rules defined in the NSGs takes precedence over the rules defined in a security list.
See Comparison of Security Lists and Network Security Groups to learn more.
After you create a private subnet in the database VCN, assign the security rules and then register the subnet as a Recovery Service subnet in Recovery Service. If you have created NSGs to implement security rules, then you must also ensure to associate the Recovery Service NSG with the Recovery Service subnet.
Oracle recommends using a private subnet for your backups. However, it is possible to use a public subnet.
Parent topic: Configuring Network Resources for 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.
Table 2-10 Networking Service Permissions Required to Create a Private Subnet and Configure Security Rules for Recovery Service
Operation | Required IAM Policies |
---|---|
Configure a private subnet in a database VCN |
|
Alternatively, you can create a policy that allows a specified group with broader access to networking components.
For example, use this policy to allow a NetworkAdmin
group to manage all networks in any compartment in a tenancy.
Example 2-1 Policy for Network Administrators
Allow group NetworkAdmin to manage virtual-network-family in tenancy
Parent topic: Configuring Network Resources 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.
Select an IPv4-only subnet for Recovery Service in your database VCN. Do not select an IPv6-enabled subnet as Recovery Service does not support using an IPv6-enabled subnet. See Creating a Subnet to learn more.
Table 2-11 Subnet Size Requirements and Ingress Rules for the Recovery Service Private Subnet
Item | Requirements |
---|---|
Recommended subnet size |
/24 (256 IP addresses) |
General ingress rule 1: Allow HTTPS traffic from Anywhere |
This rule allows backup traffic from your Oracle Cloud Infrastructure Database to Recovery Service.
|
General ingress rule 2: Allows SQLNet Traffic from Anywhere |
This rule allows recovery catalog connections and real-time data protection from your Oracle Cloud Infrastructure Database to Recovery Service.
|
If you use network security groups (NSG) to implement security rules or if your database VCN restricts network traffic between subnets, then ensure to add an egress rule for ports 2484 and 8005 from the database NSG or subnet to the Recovery Service NSG or subnet that you create.
Parent topic: Configuring Network Resources for 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).
For Oracle Database@Azure and Oracle Database@Google Cloud, if your backup subnet meets the recommended /24 subnet size requirement, then skip this section and directly proceed to register the Recovery Service subnet using network security groups (NSGs). Otherwise, you must first complete the steps described in this section, and then proceed to register the Recovery Service subnet.
Parent topic: Configuring Network Resources for Recovery Service
Register Recovery Service Subnet
After you have created a private subnet for Recovery Service in your database VCN, use this procedure to register the subnet in Recovery Service.
- Select an IPv4-only subnet for Recovery Service in your database VCN. Do not select an IPv6-enabled subnet as Recovery Service does not support using an IPv6-enabled subnet.
- For Oracle Database@Azure and Oracle Database@Google Cloud, you must register the Recovery Service subnet by associating network security groups (NSG).
You can replace a subnet or add more subnets to support the required number of private endpoints.
Parent topic: Configuring Recovery Service
(Optional) Review Protection Policies for Database Backup Retention
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.
Related Topics
Parent topic: Configuring Recovery Service
Ways to Manage Recovery Service Resources
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.
Interface | More Information |
---|---|
OCI Console |
|
Application Programming Interfaces (APIs) |
|
Command-Line Interfaces (CLIs) |