You can customize many of the characteristics of a service instance’s current backup configuration.
Topics
• Customizing How the Database Is Backed Up
• Customizing Which System Files Are Backed Up
• Customizing Which Database Configuration Files Are Backed Up
• Customizing Which Grid Infrastructure Configuration Files Are Backed Up
• Customizing the Recovery Window for Backups to Local Storage
• Customizing the Recovery Window for Backups to Cloud Storage
• Customizing the Time of Automatic Daily Backups Customizing How the Database Is Backed Up
To change how the Oracle database is backed up, you use the RMAN utility. For information about using RMAN, see Oracle Database 12c Backup and Recovery User's Guide or Oracle Database 11g Backup and Recovery User's Guide.
Caution:
Do not use the RMAN utility to change the retention period.
To view the current RMAN configuration, use the RMAN command SHOW ALL:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Change to the oracle user: $ sudo -s
# su - oracle
3. Start an RMAN session: $ rman target=/
... RMAN>
4. Enter the SHOW ALL command: RMAN> show all;
...
A listing of your configuration is displayed.
5. Use RMAN commands to make any changes to your configuration. 6. Exit the RMAN session:
RMAN> exit; $
Customizing Which System Files Are Backed Up
To change which system files and directories are backed up:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/oscfg.spec file.
The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file.
Customizing Which Database Configuration Files Are Backed Up
To change which database configuration files are backed up:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/dbcfg.spec file.
The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file.
Customizing Which Grid Infrastructure Configuration Files Are Backed Up
To change which grid infrastructure configuration files are backed up:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/gicfg.spec file.
The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file.
Customizing the Recovery Window for Backups to Local Storage
To change the recovery window for backups to local storage:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Enter this raccli command:
$ raccli update backupconfig -params '{"diskRecoveryWindow" : days}'
where days is the number of days for which you want to retain backups. Customizing the Recovery Window for Backups to Cloud Storage
To change the recovery window for backups to the Oracle Storage Cloud container:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Enter this raccli command:
$ raccli update backupconfig -params '{"ossRecoveryWindow" : days}'
where days is the number of days for which you want to retain backups. Customizing the Time of Automatic Daily Backups
To change the time of day when daily automatic backups are performed:
1. Connect as the opc user to the compute node.
For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
2. Enter this raccli command:
$ raccli update backupconfig -params '{"cronDate" : "time"}'
where time is the time (using 24-hour, HH:MM format) when daily backups are
to occur. For example, "02:45" is 2:45 AM, and "14:45" is 2:45 PM.
Changing the Backup Configuration to a Different Backup Destination
You can change the backup destination option of your Oracle Database Cloud - Database as a Service instance after creating it.
When a service instance is created, it is configured with one of the following backup destination options:
• Both Cloud Storage and Local Storage • Local Storage Only
• None
The instructions in this topic describe how to switch from one of these options to another in an existing Database as a Service instance. For background information on the options, see About Backing Up a Database as a Service Instance.
Prerequisites
• If you are switching from the backup option None to one of the other options, you must increase the size of the local storage used for backups. Use the Extend Backup
Storage Volume option of the Oracle Database Cloud Service console’s scaling feature to add storage such that the backup storage is 1.7 times the size of your database storage. For instructions, see Scaling a Database as a Service Instance.
Note:
Older service instances do not support the Extend Backup Storage Volume option, and an error is displayed when you try to use it. In this case, you must manually add backup storage. For instructions, see Increasing Local Storage for Backups on Older Service Instances.
Use the scaling feature of the Oracle Database Cloud Service console to add a storage volume of the appropriate size to the service instance.
• If you are switching to the backup option Both Cloud Storage and Local Storage, you must have an Oracle Storage Cloud Service container in your account that is reserved for backups. If you don’t have one, you must create one. See Creating Containers in Using Oracle Storage Cloud Service, or see the tutorial Oracle Storage Cloud Service: Creating Containers Using the REST API.
How you change the backup configuration to a different backup destination on a Database as a Service instance depends on the type of database running on the service instance.
Topics
• Changing the Backup Configuration on Service Instances Hosting Single-Instance