Restore Data - SAP for Oracle and SAP for MAXDB

Topics | How To | Full System Restore | Troubleshoot | Related Topics

In-Place Restore
Out-of-Place Restore
Cross-Platform Restores

Overview

The following page describes the agent-specific restore options. Additional restore options are accessible from the Related Topics menu.

Data Recovery operations for the SAP for Oracle and SAP for MAXDB iDataAgents are currently not run from the CommCell Console. Rather, they are run from the SAP command line. For complete details, see the appropriate SAP documentation.

The SAP for Oracle iDataAgent supports the following types of restores:

Restoring Oracle database files, including datafiles (*.dbf) and control files (*.ctl)
Restoring archived redo logs.

The SAP for MAXDB iDataAgent supports the following types of restores:

Restoring MAXDB database files
Restoring log files

Whenever the MAXDB database is corrupted and a restore is required, both the MAXDB application software and the MAXDB database must be restored.

When there is a problem with the affected database or the client system (such as a damaged or destroyed operating system, hardware, hard drives, etc.), full system restores may be required. See the following:

Restore Data - SAP iDataAgent - Full System Restore

Restore Considerations for this Agent

For the SAP for Oracle iDataAgent, data is restored using the BRRESTORE program. From the SAP command line, the BRRESTORE program can restore the following:

Database data files, control files, and online redo log files that were saved using BRBACKUP
Non-database files that were saved using BRBACKUP
Profiles and logs

For the SAP for MAXDB iDataAgent, data is restored using the recover_start program. From the SAP command line, the recover_start program can restore the following:

Database data files that were saved using backup_start
Log files that were saved using backup_start

For any SAP for Oracle version, if your backups and restores will be using the SAP utility and you want to use the UTIL_FILE option, be sure to modify the init<SID>.utl file by adding values for the following parameters. Note that some parameters are optional.

CvInstanceName <name of instance>, which specifies the name of the instance for the SAP for Oracle iDataAgent (for example, Instance001)
CvClientName <name of client>, which specifies the name of the computer with the installed SAP for Oracle iDataAgent (for example, bumblebee)
numstreams <number of streams> (optional), which specifies the number of streams. Default value is 1 (for example,1)

NOTES:

Ensure that you modify the storage policy as appropriate.

CV_restCopyPrec <name of copy> (optional), which specifies the copy to restore from. Default value is 0, which means any available copy (for example, copy1)
srcCrossClient <name of source client> (optional), which specifies the name of the source client with the SAP for Oracle iDataAgent for cross-machine restore purposes (for example, hotdog)

NOTES:

Ensure that the SAP for Oracle iDataAgent is installed on both the source computer and the target computer, and run the restore on the target computer.

SelectiveOnlineFull <option> (optional), which specifies whether you can run a selective online full backup from the client. To enable this capability, set the parameter value to 1; to disable this capability, set the parameter value to 0.

For example:

CvInstanceName

Instance001

CvClientName

bumblebee

numstreams

CV_restCopyPrec

srcCrossClient

hotdog

SelectiveOnlineFull

Also, do or note the following:

Ensure that the required media resources are available before running restores. Such resources include tapes, drives, etc.
If you run a restore using RMAN, the job may not be listed in the Restore Job History window at the instance level. We recommend viewing the job details from the Restore Job History window at the iDataAgent or client level.
For SAP for Oracle, Job Details may display the name defaultDummyInstanceForSAP as the SID when a restore is run from the command line.
The Job Controller progress bar will not display the progress of SAP for MAXDB backup and restore jobs accurately. This is true because Calypso cannot detect data or objects transferred by SAP for MAXDB due to the way SAP for MAXDB transfers these items.
For SAP for MAXDB, consider increasing the CACHE_SIZE value on the client before running restores. If the CACHE_SIZE value is too small, restores may fail.
You can restore the control file from a RMAN log backup (i.e,. BRARCHIVE backup) using the following command:
brrestore -b2 <archive file ID> -m <control file path>

For example,

brrestore -b2 SAP_1445_18400 -m /u01/app/oracer/product/10.2.0/db_1/CER/sapreorg/cntrlCER.dbf

Restore Destinations

By default, the SAP for Oracle iDataAgent or the SAP for MAXDB iDataAgent restores data to the client computer from which it originated; this is referred to as an in-place restore. You can also restore the data to another client computer in the CommCell. Keep in mind the following considerations when performing such restores:

The destination client must reside in the same CommCell as the client whose data was backed up.
Note that when you perform restores other than in-place restores, the restored data assumes the rights (i.e., permissions) of the parent directory.

The following section enumerates the types of restore destinations that are supported by the SAP iDataAgent. See Restore/Recover/Retrieve Destinations - Support for a list of Agents supporting each restore destination type.

In-Place Restore

Same path/destination

Out-of-Place Restore

Keep in mind that out-of-place restore operations are also subject to the conditions described in Cross-Platform Restores.

Same path/destination

You should restore SAP database data to a different host (or out of place) if the original host is damaged. This is sometimes called a cross-machine restore. Whenever you perform such a restore, ensure that the destination machine has sufficient disk space to accommodate the restored database.

See the following as appropriate for step-by-step instructions:

Cross-Platform Restores

Same Operating System - Different Version

See the following as appropriate for step-by-step instructions: