Choose from the following topics:
The SAP for Oracle iDataAgent is responsible for backing up and restoring Oracle databases. The SAP for MAXDB iDataAgent is responsible for backing up and restoring MAXDB databases. For either iDataAgent, backups and restores are run from the SAP command line. For the SAP for Oracle iDataAgent, backups can also be run from the CommCell Console.
|
You cannot run the SAP tools commands brbackup and brrestore for SAP for Oracle on Windows backups and
restores from remote desktops on Windows. Instead, you must run
these commands either from the client console or by using a Telnet or
NetMeeting session. Third-party command line operations (including those for the SAP for Oracle and SAP for MAXDB iDataAgents) may produce details in the various CommServe job-reporting windows and job results that differ from the details produced by such operations run from the CommCell Console. For more information, see Third-Party Command Line Operations. |
The SAP for Oracle iDataAgent and the SAP for MAXDB iDataAgent are just two of several iDataAgents that provide backup and restore support for different kinds of data in what is often a mixed network environment. Remember that this product secures only the Oracle or MAXDB databases (e.g., system and user databases). To secure Oracle or MAXDB application files that reside on a local hard drive or file system data that resides on an Oracle or MAXDB computer, you must use the File System iDataAgent. (For information on the SAP entities mentioned, see Databases and Instances.)
The Oracle and MAXDB databases comprise several objects. These objects can be backed up by the appropriate SAP iDataAgent. For more information on these objects, refer to your Oracle or MAXDB documentation.
The following definitions are applicable to the SAP for Oracle and SAP for MAXDB iDataAgents.
Data Protection Operations for the following data types are supported by the SAP for Oracle iDataAgent:
Data Protection Operations for all other data types not mentioned in the previous list are not supported by the SAP for Oracle iDataAgent, including:
Both of these data types can be secured by the appropriate File System iDataAgent.
Data Protection Operations for the following data types are supported by the SAP for MAXDB iDataAgent:
Data Protection Operations for all other data types not mentioned in the previous list are not supported by the SAP for MAXDB iDataAgent, including:
Both of these data types can be secured by the appropriate File System iDataAgent.
When the SAP for Oracle and SAP for MAXDB iDataAgents are installed, the following levels are automatically created in the CommCell Browser.
|
bumblebe: Client SAP for Oracle, SAP for MAXDB: Agent <user_defined_instance>: Instance |
|
|
|
In order to run the first backup, an instance must be added. When you configure an instance for the SAP for Oracle iDataAgent, a default subclient is created. |
To perform a data protection operation using this Agent a specific Product License must be available in the CommServe® Server.
Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.
Within the SAP for Oracle iDataAgent or the SAP for MAXDB iDataAgent, each instance can contain one or more of the table spaces (SAP for Oracle) or databases that you want to back up. Table spaces to be backed up are determined by using the appropriate backup utility from the SAP command line.
In addition to the Oracle or MAXDB database, there may be Oracle or MAXDB application files stored on the computer (that is, the client, as defined above). Such data is not backed up by the SAP for Oracle iDataAgent or the SAP for MAXDB iDataAgent. To secure such data from a SAP for Oracle or SAP for MAXDB client, you must back it up using the appropriate iDataAgent for the computer file system.
