Best practices for Backup Exec 2010 Agent for SAP Applications
|Article:HOWTO21784|||||Created: 2010-01-27|||||Updated: 2012-09-18|||||Article URL http://www.symantec.com/docs/HOWTO21784|
Best practices include tips and recommendations to help you use the Backup Exec 2010 Agent for SAP Applications (SAP Agent). For more information about Backup Exec's SAP Agent, see the Backup Exec 2010 Administrator's Guide.
The following best practices can help ensure the effective configuration of the SAP Agent for RMAN:
The following best practices can help ensure effective backups from the SAP Agent:
Test recovery scenarios often to become familiar with the procedures. SAP/R3 recovery can be complex and it is often time-sensitive because of the nature of the data. Coordinate testing and configuration with database administrators to ensure that recovery procedures are understood.
Ensure that the Remote Agent Utility is running before you submit an RMAN job. If the Remote Agent Utility is not running, the job fails. The Remote Agent Utility is not necessary if you use BACKINT to run backup jobs.
Confirm that you have at least two successful backups of archived log files before you delete them from the server. Oracle recommends that you save at least two copies of each log on external media. The loss of Oracle redo records can cause significant loss of data in a recovery scenario.
Configure biparam.ini to back up the SAP Agent catalog frequently. You should back up the catalog with every backup job, if possible, or at least each week. The SAP Agent catalog is important for restore jobs since it associates Oracle catalog data with Backup Exec catalog data.
Article URL http://www.symantec.com/docs/HOWTO21784