Api::error Backups Are Not Configured on This Db Instance. Configure the Backup and Try Again Dbaas

When you create an Oracle Database Classic Cloud Service database deployment, you specify whether automatic backups are configured by choosing a backup destination. After the deployment is created yous tin change the configuration past changing the deployment'due south backup destination.

The instructions in this topic describe how to switch backup destinations for an existing database deployment. Specifically, the post-obit changes are possible using the instructions in this topic:

• From None to Both Deject Storage and Local Storage

• From None to Deject Storage Only (not currently available for database deployments that use Oracle RAC)

• From Both Cloud Storage and Local Storage to Cloud Storage But

• From Cloud Storage Only to Both Cloud Storage and Local Storage

For background information on the destinations, see Virtually Bankroll Upwardly Database Deployments on Database Classic Cloud Service.

Note:

The Oracle Database Classic Cloud Service console does not currently recognize changes to the backup destination made by using the bkup.cfg file with the fill-in banana. Therefore, the console will not reflect the new backup destination and may not display whatever backups taken, depending on what backup destination change you accept made. If the backups are not displayed, you will not be able to employ the Oracle Database Classic Cloud Service panel to perform recovery.

Prerequisites

• If you are switching to the backup destination Both Cloud Storage and Local Storage, you must increment the size of the local storage used for backups. Use the Extend Fill-in Storage Volume option of the Oracle Database Classic Cloud Service panel's scaling feature to add together storage such that the backup storage is 1.7 times the size of your database storage. For instructions, see Scaling a Database Deployment.

• If you are switching to the backup destination Both Cloud Storage and Local Storage or Deject Storage But, you must have an Oracle Storage Deject Service container in your business relationship that is reserved for backups. If you lot 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.

The commands you utilise to alter the backup destination depend on the blazon of database running in the database deployment.

Irresolute the Backup Configuration on Database Deployments Hosting Single-Instance Databases

Oracle Database Classic Cloud Service allows yous to change the backup destination for your database deployments after creating them.

Earlier changing the fill-in destination, make sure you accept performed applicative Prerequisites.

1. Connect as the oracle user to the compute node.
2. Offset an RMAN session:

   $                    rman target=/                    ... RMAN>                  

3. Delete any existing backups.

   All backups for this database recorded in the RMAN repository are deleted. (This process may take several minutes.)

4. Exit the RMAN session:
5. If y'all are switching from the None destination, and this is the first time you lot have done so, you lot must configure Transparent Data Encryption (TDE). Run the following command:

   $                    /var/opt/oracle/dbaascli/dbaascli tde config --ks_login automobile                  

   TDE provides encryption of database files at the file level. For information about TDE, including machine login, meet Oracle Database Avant-garde Security Guide for Release 18, 12.two, 12.1 or 11.two.

6. Close your connection to the compute node equally the oracle user.
7. Connect every bit the opc user to the compute node.
8. Start a root-user command beat:
9. Enter this bkup_api command to generate a file containing the current backup settings:

   #                    /var/opt/oracle/bkup_api/bkup_api become config [--file=filename] --dbname=dbname                                      

   where filename is an optional parameter used to specify a name for the file that will be generated and dbname is the database name for the database that yous want to human activity on.

10. Edit the parameter values in the generated file to alter any settings you desire to update in the current fill-in configuration. The following parameters are used to customize the current backup configuration:

    Parameter	Clarification
    bkup_disk	Enable backup to disk. Valid values are yes and no.
    bkup_disk_recovery_window	Recovery window expressed in number of days between 1 and xiv.
    bkup_oss	Enable backup to an Oracle Storage Cloud container. Valid values are yes and no.
    bkup_oss_passwd	Oracle Storage Deject user password. Only applicative when bkup_oss is prepare to yes.
    bkup_oss_recovery_window	Recovery window for backups to an Oracle Storage Cloud container, expressed in number of days betwixt ane and 30. Only applicative when bkup_oss is set to aye. Just applicative when bkup_oss is set to yeah.
    bkup_oss_url	URL for an Oracle Storage Deject container such as https://storage.oraclecorp.com/v1/Storage-test/test.
    bkup_oss_user	Oracle Storage Cloud username. Only applicative when bkup_oss is set to yeah.

11. Enter this bkup_api command to update the backup settings using the file you generated:

    #                    /var/opt/oracle/bkup_api/bkup_api set config --file=filename                      --dbname=dbname                                      

    where filename is used to specify a name for the file that volition be used to update the backup settings and dbname is the database name for the database that you want to human activity on.

12. You can employ this bkup_api command to check the status of the update:

    #                    /var/opt/oracle/bkup_api/bkup_api configure_status                  

13. Get out the root-user control shell:

Changing the Backup Configuration on Database Deployments Hosting Oracle RAC Databases

This topic does not apply to Oracle Cloud Infrastructure or to Oracle Deject at Client.

Oracle Database Classic Cloud Service allows you to change the backup destination for your database deployments after creating them.

Before changing the backup destination, brand sure you have performed applicable Prerequisites.

1. Connect equally the opc user to compute node ane.
2. Employ the raccli update backupconfig command to update the configuration.

   To change the backup destination to Both Deject Storage and Local Storage, enter the following command. Line breaks have been added for clarity; you must enter the command on a unmarried line.

   $                    raccli update backupconfig -params '{"diskEnabled" : true, "ossEnabled" : truthful,   "cloudStorageUser" : "username", "cloudStoragePwd" : "countersign",   "cloudStorageContainerUrl" : "container-URL"}'                  

   where:

   • username is the user name of an Oracle Cloud user who has read/write access to the container.

   • password is the countersign of the user specified in cloudStorageUser.

   • container-URL is the URL of the Oracle Storage Cloud container.

Increasing Local Storage for Backups on Older Database Deployments

This topic does not utilise to Oracle Cloud Infrastructure.

Older database deployments on Oracle Database Classic Cloud Service do not support the Extend Fill-in Storage Book feature, so you lot must manually add backup storage.

To create a larger storage volume and use it for backups:

1. Create a storage book for backups. Its size should be 1.7 times the infinite allocated for data storage.

   Apply the Create New Storage Volume pick of the Oracle Database Classic Cloud Service console's scaling characteristic to add together a storage book of the appropriate size. For instructions, run into Scaling a Database Deployment.

2. Connect as the opc user to the compute node.

   For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).

3. Confirm the addition of the storage volume by listing the devices:

   $                    lsblk                    NAME    MAJ:MIN RM  SIZE RO Blazon MOUNTPOINT xvdb    202:sixteen   0   21G  0 disk ├─xvdb1 202:17   0  200M  0 part /kicking ├─xvdb2 202:xviii   0 15.8G  0 office / └─xvdb3 202:xix   0    4G  0 part [Bandy] xvdc    202:32   0   10G  0 disk └─xvdc1 202:33   0   10G  0 part /u04 xvdd    202:48   0    7G  0 disk └─xvdd1 202:49   0    7G  0 part /u03 xvde    202:64   0   30G  0 disk └─xvde1 202:65   0   30G  0 function /u01 xvdf    202:lxxx   0   11G  0 deejay └─xvdf1 202:81   0   11G  0 part /u02                    xvdg    202:96   0   17G  0 disk └─xvdg1 202:97   0   17G  0 function /u05                  

4. Modify from the opc user to the oracle user:

   $                    sudo su - oracle                  

5. Equally the oracle user, use RMAN to close downwardly the database instance:

   $                    rman target=/                    ... RMAN> shutdown immediate;  using target database control file instead of recovery catalog database airtight database dismounted Oracle case shut downwardly                  

   Quit RMAN and leave the oracle user session:

   RMAN>                    quit;  Recovery Manager complete. $ exit

6. As the root user, copy the content from /u03 (which y'all accept been using for backup storage) to /u05:

   #                    cp -R /u03/* /u05/                  

7. Unmount the /u05 and /u03 mountain points:

   #                    umount /u05/                    #                    umount /u03/                  

   Note:

   The Linux unmount command is umountain (with no n).

8. Mount the partition of new storage volume you but created to /u03, which Oracle Database Classic Cloud Service uses for backups. For case:

                       #                      mount /dev/xvdg1 /u03                                      

9. Await at the results:

                       #                      lsblk                      Name    MAJ:MIN RM  SIZE RO Blazon MOUNTPOINT xvdb    202:16   0   21G  0 disk ├─xvdb1 202:17   0  200M  0 part /kicking ├─xvdb2 202:eighteen   0 15.8G  0 part / └─xvdb3 202:19   0    4G  0 part [Swap] xvdc    202:32   0   10G  0 deejay └─xvdc1 202:33   0   10G  0 part /u04                      xvdd    202:48   0    7G  0 disk └─xvdd1 202:49   0    7G  0 function                      xvde    202:64   0   30G  0 disk └─xvde1 202:65   0   30G  0 part /u01 xvdf    202:lxxx   0   11G  0 disk └─xvdf1 202:81   0   11G  0 part /u02                      xvdg    202:96   0   17G  0 disk └─xvdg1 202:97   0   17G  0 part /u03                                      

   The old 7 GB partition xvdd1, which was previously mounted to /u03, is no longer mounted at all. The new 17 GB partition xvdg1 is now mounted to /u03 and will therefore exist used for backups. Notation that the space used for xvdd1 is at present no longer available for any use.

10. Set the ownership and permissions of the mount-signal directory /u03. For example:

    #                    chown -R oracle:oinstall /u03                    #                    chmod 755 /u03                  

11. As the oracle user, commencement SQL*Plus, connect to the database as SYSDBA, and start it. For example:

    $                    sqlplus /nolog                    SQL*Plus: Release 12.i.0.ii.0 Product on Sat Feb 21 13:19:51 2015  Copyright (c) 1982, 2014, Oracle.  All rights reserved.  SQL>                    connect sys/password                      as sysdba                    Connected to an idle instance. SQL>                    startup                    ORACLE example started.  Full System Global Area 3170893824 bytes Fixed Size                  2929400 bytes Variable Size            1845497096 bytes Database Buffers         1308622848 bytes Redo Buffers               13844480 bytes Database mounted. Database opened.                  

12. If yous want to come across the current setting for the limit on the total space to exist used past target database recovery files, show the values of the parameter DB_RECOVERY_FILE_DEST, for example:

                        SQL>                      bear witness parameter db_recovery_file_dest                                            Proper noun                         Blazon        VALUE ---------------------------- ----------- ------------------------------ db_recovery_file_dest        string      /u03/app/oracle/fast_recovery_                                                  expanse                      db_recovery_file_dest_size                      big integer                      7G                                      

13. Increment the parameter DB_RECOVERY_FILE_DEST_SIZE to utilize the new extra infinite in /u03, for instance:

    SQL>                    alter arrangement set db_recovery_file_dest_size=17G;                                        System contradistinct.

14. Evidence the new value:

                        SQL>                      show parameter db_recovery_file_dest;                                            NAME                         TYPE        VALUE ---------------------------- ----------- ------------------------------ db_recovery_file_dest        string      /u03/app/oracle/fast_recovery_                                                  area                      db_recovery_file_dest_size   large integer 17G                                                            

15. Quit SQL*Plus and log out:

    SQL>                    quit;                    Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production $                    get out                  

atchleysconly.blogspot.com

Source: https://docs.oracle.com/en/cloud/paas/database-dbaas-cloud/csdbi/change-backup-config-different-destination.html

Share this post