Upgrading the Backup Exec Oracle Agent

Article:HOWTO24331  |  Created: 2010-01-01  |  Updated: 2011-08-30  |  Article URL http://www.symantec.com/docs/HOWTO24331
Article Type
How To


Subject


Upgrading the Backup Exec Oracle Agent

The Backup Exec Oracle RMAN Agent replaces the legacy GRFS Oracle Agent. All existing Oracle jobs are upgraded for use with the new agent. When you upgrade to the Backup Exec Oracle RMAN Agent, backup jobs for Oracle instances that were created with the legacy Oracle Agent are placed on hold. You must do the following:

Table: Upgrading the Backup Exec Oracle Agent

Step

Action

Step 1

Verify that the logon account for each resource that was backed up by the previous Oracle Agent is valid for the new Oracle Agent.

See Changing and testing resource credentials for restore jobs.

Step 2

Use the Remote Agent Utility to configure information about the Oracle instances for the Oracle Agent, and to enable media server access to the Oracle databases.

See Configuring the Oracle Agent on Windows computers and Linux servers.

Step 3

Add the fully qualified domain name and logon account of the Oracle server to the media server's list of authentication credentials.

See Setting authentication credentials on the media server for Oracle operations.

Step 4

Take the associated jobs off hold.

See Removing the hold on the job queue.

After upgrading, the database control file resource no longer appears in the backup selections tree under the Oracle server node. Backup Exec automatically backs up the database control file whenever a tablespace or other resource on the Oracle server is backed up.

Note:

If you have a backup selections list that contains the database control file as its single resource, create another selection list that contains other resources. The database control file is then automatically backed up whenever the other resources in the selection list are backed up. This applies only to selection lists created with the legacy GRFS Oracle Agent.


Legacy ID



id-SF700143310_be2010_adm


Article URL http://www.symantec.com/docs/HOWTO24331


Terms of use for this information are found in Legal Notices