You should now be able to select your Oracle database as a backup resource. All the information you entered here should correspond to the information you entered in the “Database Access” tab.ĩ. Again, I used the local host IP address, 127.0.0.1, since our Oracle database is on the same server as the Backup Exec. This needs to match the user you created in Step 6 on the “Database access” tab. Add the IP address of the Oracle Server and pick the Domain\Administrator account from the “Logon Account” drop-down box and hit “OK”. Go to the menu item “Tools>Options>Oracle>Modify List” and click “New”. Add this user even if “System Logon Account” already exists since they need to match the format exactly with the user you entered in the “Database Access” tab of the “Backup Exec Remote Agent Utility” per the Symantec/VERITAS support article 292442.Ĩ. If it does not exist, also add the Domain\Administrator user also and set it as default by clicking the “Set as default” button to the right. This needs to match the user you created in Step 5 on the “Oracle” tab.
Add the Oracle user “SYS” with the proper password and hit “OK”. Go to the menu item “Network>Logon Accounts” and click “New”.
Go to the main Backup Exec for Windows Servers program. If you use the server name to back up, you will need to use the server name to restore, etc.ħ. NOTE: The documentation states that whatever you filled in here to backup, you must use the same exact value to restore. Again, since our Oracle was on that server, I used the local host IP address, 127.0.0.1. Enter the “Name or IP address” of the Oracle Server.
Check the “Use the full computer name or IP address for Oracle and DB2 operations” check box. This user will correspond to the user we will create later during step 8 in the main program in “Tools>Options>Oracle>Modify List”. Enter the user as Domain\Administrator and click the “Change password” button and set the proper password for the Domain\Administrator account. On the “Database Access” tab, check the “Enable media server authentication for Oracle and DB2 operations” check box. This user will correspond to the user we will create later during step 7 in the main program in “Network>Logon Accounts”.Ħ. Again, I recommend using the local host IP address, 127.0.0.1. Enter the media server IP address or server name. The user name here should be the Oracle “SYS” user and the proper password. On the “Oracle” tab, click new, and select the “instance” you wish to backup. NOTE: The definition of Symantec term “media server” is the server where the main Backup Exec services reside.ĥ.
Assuming that your main Backup Exec application is on that server, I recommend using the local host IP address (127.0.0.1) for ease since you would never have to change it if you later change the server name or IP address. Click “add” and add the media server IP address or server name. On the “Publishing” tab, check the “Enable the Remote Agent to publish information to the media servers in the list” check box. On the “Status” tab, check the “Start the Remote Agent Utility every time you log on” check box.Ĥ. Start the “Backup Exec Remote Agent Utility” from the “Backup Exec for Windows Servers” start menu group or if the shortcut is missing, from “c:\Program Files\Symantec\Backup Exec\vxmon.exe”.ģ. This should also work for DB2 by substituting the DB2 component where I mention an Oracle component since they appear to configure the exact same way, but again, I could not verify this with certainty since I do not have a DB2 database.Ģ. I cannot verify that it will work for any other versions. First, this should work for at least versions 11d and 12 since I did this on version 12 and compared it to a version 11d installation. I had a few problems with this, even after a support call, so I thought I would publish a detailed "click-here", "click-there" how-to article.ġ.