Scenario #1: Configure Multiple Protected Databases to Send Backups to Recovery Appliance

Uses Enterprise Manager to manage the configuration of multiple protected databases.

After the Recovery Appliance administrator has enrolled a protected database, the database must be configured locally to send backups and redo to the Recovery Appliance. This configuration procedure can be performed for an individual database from the Enterprise Manage (EM) Backup Settings page. However, performing this procedure on multiple databases might not be practical through the EM user interface.

Enrolling multiple databases is more easily achieved through the EM command line interface (EMCLI) and the configure_db_ha -configureRABackup command. It performs the configuration procedure for multiple databases concurrently.

The following examples illustrate different usages of this command to perform the initial configuration for individual and multiple databases.

Single-instance Database

The following example of emcli configure_db_ha –configureRABackup configures one single-instance database to send backups to and ship redo to a Recovery Appliance.

If the RMAN backup module is already installed in the database Oracle home, it does not install the latest RMAN backup module from the software library. The command uses the EM named database and host credentials.

emcli configure_db_ha –configureRABackup –ra_target_name="Chicago ZDLRA" –ra_user="rauser1" –target_name="Finance" –target_type="oracle_database" –db_cred="DB_USER" –db_host_cred="DB_HOST_USER" –enable_redo_ship

One Cluster Database

The following example of emcli configure_db_ha –configureRABackup configures one cluster database to send backups to a Recovery Appliance.

The command does not use the –enable_redo_ship option, so redo logs are not shipped. The –force_backup_module_install option specifies that the latest RMAN backup module from the software library should be installed in the Oracle home of each cluster database instance. The command uses the EM named database and host credentials.

emcli configure_db_ha –configureRABackup –ra_target_name="Chicago ZDLRA" –ra_user="rauser1" –target_name="Finance" –target_type="rac_database" –force_backup_module_install

Single-Instance and Cluster Databases

The following example of emcli configure_db_ha –configureRABackup uses an input file, –input_file="/tmp/dblist", to specify the single-instance and cluster databases to be configured..

The –enable_redo_ship option is specified so that backups and redo logs are shipped to the Recovery Appliance. The –force_backup_module_install option specifies that the latest RMAN backup module from the software library should be installed in the Oracle home of each database. The command uses the same EM named database and host credentials for all databases.

emcli configure_db_ha –configureRABackup –ra_target_name="Chicago ZDLRA" –ra_user="rauser1" –input_file="/tmp/dblist" –db_cred="DB_USER" –db_host_cred=" DB_HOST_USER" –enable_redo_ship –force_backup_module_install –staging_directory=”/tmp/stage"

The content of the input file, /tmp/dblist, used by in this example specifies a single-instance database and a cluster database 

target.0.target_name=db1
target.0.target_type=oracle_database
target.1.target_name=rac1
target.1.target_type=rac_database

Multiple Databases from an Input File

The following example of emcli configure_db_ha –configureRABackup uses an input file, –input_file="/tmp/dblist", to specify the databases to be configured.

The –enable_redo_ship option is specified so that backups and redo logs are shipped to the Recovery Appliance. If the RMAN backup module is already installed in the database Oracle home, then it does not install the latest RMAN backup module from the software library. The -schedule option sets a future time for the operation. The command uses the same EM named database and host credentials for all databases.

emcli configure_db_ha –configureRABackup –ra_target_name="Chicago ZDLRA" –ra_user="rauser1" –input_file="/tmp/dblist" –db_cred="DB_USER" –db_host_cred="DB_HOST_USER" –enable_redo_ship -schedule="start_time:2016/06/28 18:31;tz:PST;"

Maintaining Protected Database Configurations

Variations of emcli configure_db_ha -configureRABackup command can be re-run as needed against the same databases to update the configuration.

All aspects of the local database configuration (such as the wallet, backup module, RMAN configuration) are automatically updated if needed by the EM deployment procedure invoked by the command. In this way, ongoing maintenance of the configuration for multiple database can be accomplished with one command.

Example maintenance scenarios include the following:

  • Update the Virtual Private Catalog (VPC) credentials used by each protected database to send backups to Recovery Appliance after a VPC user password change: Assuming the EM named credentials corresponding to the VPC user have been updated (required for EM operations that use this VPC user), the EM deployment procedure automatically updates all the protected database wallets with the new credentials.

  • Update the Recovery Appliance RMAN backup module in all Oracle homes of each protected database: This can be done as part of a complete protected database configuration, or separately as a stand-alone operation. If the -force_backup_module_install option was specified during the database configuration, the EM deployment procedure updates the backup module in each Oracle home with the latest version present in the EM Software Library.

  • Enable redo shipping to Recovery Appliance for databases where it was not previously enabled: This can be done by re-running the command with the -enable_redo_ship option and an input file listing the databases that need redo shipping enabled.

The complete syntax and input file format can be found in EM Command Line Interface .