Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.10 Oracle RMAN User Guide

Performing self-service backups of Oracle databases

To enable self-service protection, when you create the Oracle protection policy, select Self-Service Protection.

NOTE

For clients that are configured with a self-service protection policy, you must perform each type of data backup (full, incremental, cumulative) in a separate RMAN session. You can perform the archived log, spfile, and controlfile backups either with the data backups or in separate RMAN sessions.

When you perform the different types of data backups in the same RMAN session, the backups are reported incorrectly. The following example RMAN scripts in this topic perform a database backup and archived log backup by using separate backup commands.

RMAN sessions must be exited for every backup and restore operation. Otherwise, the self-service job that monitors the progress will continue to run indefinitely or until the session exits.

To perform a self-service or manual backup of an Oracle database, you must create and run an RMAN backup script. The following example shows how to generate the backup scripts.

To identify the storage unit and DD hostname, run the ddutil -s command on the Oracle client. For example, run the following command in the $RMAN_AGENT_HOME/bin directory:

./ddutil -s

Only if the autobackup is enabled for the protected database and you have created a self-service protection policy for Oracle, complete the required top-level directory changes:

  1. Log in to the Oracle host as an Oracle user.
  2. To obtain the top-level directory information, run the following command:

    $RMAN_AGENT_HOME/bin/ddutil -s
    
    PowerProtect DD hostname: 10.125.136.106
    
       FC service name: None
       FC service enabled: false
    
       Storage Unit: oracle-self_policy-blrv034d018-R-df3c7
       Top Level Path: PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522
       Protection Policy Name: self_policy
    
               User: oracle-self-blrv034d018-R-df3c7
               Type: PROTECTION
  3. To complete the changes to the control file configuration for the Oracle database, run the following RMAN command, which includes the top-level pathname from the ddutil -s command output:

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';
  4. Similarly, in the existing backup scripts that you use for backups, change the format specification accordingly. For example:

    BACKUP INCREMENTAL LEVEL 0 DATABASE INCLUDE CURRENT CONTROLFILE FORMAT './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/OCK/Automated_data_%d_%I_%u_%p';

    After you complete these changes, all the database backup pieces including the autobackups will be written under the top-level directory created in the storage unit.

    NOTE

    If changing the backup scripts or the control file format is not a feasible option, then create the .disable.tlp file under the $RMAN_AGENT_HOME/settings directory. Alternatively, add the IGNORE_TLP_SU_DIR=TRUE environment variable setting in the ALLOCATE CHANNEL command of the existing backup scripts. In both of these cases, the backup pieces will not be written under the top-level directory created by the protection policy.

    In an Oracle RAC environment, create the .disable.tlp file on each node of the system under the $RMAN_AGENT_HOME/settings directory.

Specify the storage unit, top-level pathname, and DD hostname in the RMAN backup script.

The following example shows an RMAN script that performs a full backup of the database and its archive logs in separate statements:

connect target username/password;

run {
configure controlfile autobackup on;
set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

allocate channel c1 type SBT_TAPE parms 'SBT_LIBRARY=rman_agent_home/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com)';

backup database include current controlfile format './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

backup archivelog all delete input format './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

release channel c1;
}

The libddobk.so library location and the RMAN_AGENT_HOME, STORAGE_UNIT, and BACKUP_HOST settings must be specified in the allocate channel command. All other parts of the script are standard RMAN commands.

To increase the parallelism of the backup, you can allocate more channels:

connect target username/password;

run {
set CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

allocate channel c1 type SBT_TAPE parms 'SBT_LIBRARY=rman_agent_home/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com)';
allocate channel c2 type SBT_TAPE parms 'SBT_LIBRARY=rman_agent_home/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com)';
allocate channel c3 type SBT_TAPE parms 'SBT_LIBRARY=rman_agent_home/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com)';
allocate channel c4 type SBT_TAPE parms 'SBT_LIBRARY=rman_agent_home/lib/libddobk.so, ENV=(RMAN_AGENT_HOME=rman_agent_home, STORAGE_UNIT=XYZ, BACKUP_HOST=bu-ddbealin-17.lss.emc.com)';

backup database include current controlfile format './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

backup archivelog all delete input format './ PLCTLP-4eb04bd9-b825-4e72-b668-14e9aacaa522/%F';

release channel c1;
release channel c2;
release channel c3;
release channel c4;
}

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\