Database

464 Topics

How to configure the Backup Exec Oracle Agent - Practical Step by Step Instructions
Hi All, 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. 1. 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 cannot verify that it will work for any other versions. 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. 2. 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”. 3. On the “Status” tab, check the “Start the Remote Agent Utility every time you log on” check box. 4. On the “Publishing” tab, check the “Enable the Remote Agent to publish information to the media servers in the list” check box. Click “add” and add the media server IP address or server name. 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. NOTE: The definition of Symantec term “media server” is the server where the main Backup Exec services reside. 5. On the “Oracle” tab, click new, and select the “instance” you wish to backup. The user name here should be the Oracle “SYS” user and the proper password. Enter the media server IP address or server name. Again, I recommend using the local host IP address, 127.0.0.1. This user will correspond to the user we will create later during step 7 in the main program in “Network>Logon Accounts”. 6. On the “Database Access” tab, check the “Enable media server authentication for Oracle and DB2 operations” check box. Enter the user as Domain\Administrator and click the “Change password” button and set the proper password for the Domain\Administrator account. This user will correspond to the user we will create later during step 8 in the main program in “Tools>Options>Oracle>Modify List”. Check the “Use the full computer name or IP address for Oracle and DB2 operations” check box. Enter the “Name or IP address” of the Oracle Server. Again, since our Oracle was on that server, I used the local host IP address, 127.0.0.1. NOTE: The documentation states that whatever you filled in here to backup, you must use the same exact value to restore. If you use the server name to back up, you will need to use the server name to restore, etc. 7. Go to the main Backup Exec for Windows Servers program. Go to the menu item “Network>Logon Accounts” and click “New”. Add the Oracle user “SYS” with the proper password and hit “OK”. This needs to match the user you created in Step 5 on the “Oracle” tab. 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. 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. 8. Go to the menu item “Tools>Options>Oracle>Modify List” and click “New”. Add the IP address of the Oracle Server and pick the Domain\Administrator account from the “Logon Account” drop-down box and hit “OK”. This needs to match the user you created in Step 6 on 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. All the information you entered here should correspond to the information you entered in the “Database Access” tab. 9. You should now be able to select your Oracle database as a backup resource. You should also check the credentials for your job by going to the “Job Setup” tab and double-clicking any backup selections you have in the “Backup Selection Lists” pane, then going to the “Resource Credentials” in the left pane, and then hit “Test All”. The computer level at the top should use the Domain\Administrator account, the rest will inherit from that, with the exception of the “Oracle Database”, which should be using the SYS account we created in step 7. If not, highlight it and click “Change” on the right side. Other common problems include the database needing to be placed in “automatic archive log mode” as described in Symantec/VERITAS support article 266835; and the need to change the “Archive Log Mode” from “NOARCHIVE LOG” to “ARCHIVE LOG” (in version 9, in the Oracle Enterprise Manager Console, go to “Network>Databases>DatabaseName>Instance>Configuration” and then to the “Recovery” tab, and check “Archive Log Mode” box. This needs to be done as the Oracle SYS user and this can be changed in “Configuration>Edit Local Preferred Credentials” if necessary. KEYWORDS: 0xe0001403; 0xe0001014; “Failed to access Oracle database”; “Cannot start an Oracle session. Check that the logon credentials are correct, and have sufficient privileges.”; “The database is in NOARCHIVELOG mode and is OPEN. To back up the database when it is in NOARCHIVELOG mode, the database must be MOUNTED but not OPEN.” Relevant Symantec/VERITAS support articles regarding common errors, setup, backup, and restoration using the Oracle agent: 266835; 292497; 292442; 300135; 300134; 300133; 300130; 300119; 300125; 300123; 300118; 300116. You may also go to this page for a complete list of Backup Exec for Windows Server support articles, including those regarding the Oracle agent: http://seer.entsupport.symantec.com/docs/BEWNT_index.htm. Best Regards, Kevin Cotreau MCSE+I, MCNE, et al.
Solved
Kevin_Cotreau
17 years ago Place Backup Exec
8KViews
3likes
8Comments
Security Update for SQL Server 2005 Service Pack 3 (KB970892) fails to install
Microsoft released Security Update for SQL Server 2005 Service Pack 3 (KB970892) on October patch Tuesday. It fails to install on the SQLExpress 2005 SP3 x64 BKUPEXEC instances on two of my my BEWS 12.5 SP2 media servers, as well as on a couple of other servers running SQLExpress 2005 SP3 with other products, e.g. VMware vCenter Server, HPDigital Sending Software 4.0. Various forum posts found by Google suggest that having any of the SQL Server services disabled may cause this problem. In my case, the only disabled service is SQLServer Active DirectoryHelper. This service can be set to manual, but it will not start, and just setting it to manual doesn't solve the problem. These posts also suggest that having the SQL Server program folder compressed can cause the error, but this is not applicable to my situation. I took a look at the Windows Update log and other than an error message with the return code 0x0000737d, I didn't see any useful information. I also looked at the hotfix installation log at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB970892_sqlrun_sql.msp.log, and found the error message:"Error 29565. SQL Server Setup cannot upgrade the specified instance because the previous upgrade did not complete. Start the Remote Registry service and go to Add/Remove Programs, select the Change button for Microsoft SQL Server 2005, and then select SQL instance HPDSDB and complete the setup." The description of this security update at http://support.microsoft.com/kb/970892,in the More Information section, lists four TechNet articles with troubleshooting procedures for known issues. Article 955250 seems like it may be applicable, although the error message doesn't match. I'm still trying to work through this. The security update is available at http://www.microsoft.com/downloads/details.aspx?familyid=0d878f4b-71e8-4170-9a14-1bce684811ce&displaylang=enfor anybody who does not wish to rely on Windows Update. Thanks for any additional thoughts that anyone may have.
Solved
jaspain
15 years ago Place Backup Exec
6.3KViews
4likes
28Comments
Backing up (exporting) BackupExec Config
Hi, we have a 12.5 Server running wihich I did not configure. There are quite a lot off backup jobs configured with policies. Now I shall upgrade the system to SP2. Before that I would like to create a backup or export file with the configuration of the BackupExec Server itself. The DB we are using is a local SQLExpress. Do have to backup the DB or how can I backup the Backup Exec Server itself including the job config, policies and so on? Thanks in advance! regards /noodles
noodles
16 years ago Place Backup Exec
5.3KViews
1like
4Comments
Resource connection errors when trying to backup Oracle
Dear Sirs, on a new install of Backup Exec, we are trying to configure a DBA-initiated backup of an Oracle instance. So far, we haven't had any success. If the job is triggered by RMAN, BE queues it ok, but it immediately fails with this error: << Final error: 0xe000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. Final error category: Resource Errors Remote Agent not detected on QMS. >> If the job is configured in BE (which, by the way, can see the instance's tablespaces, etc.), when started it hangs indefinitely in the "Pre-processing" state. You'll find here attached two sets of log (the second one being more verbose) related to the DBA-initiated test. Other various info: - The same machine acts as BE Media Server and Oracle DB Server. It's _not_ in a Microsoft A/D domain. - The backup targes a Backup-to-Disk folder. - There's no NIC teaming involved. - "Simple" file backups work fine. - The Backup Exec Agent Browser can't be gracefully stopped, we have to manually kill "benetns.exe". - We're running BE 11, rev. 7170 with Service Pack 1 - Example of an RMAN run C:\Documents and Settings\Administrator>rman target / nocatalog Recovery Manager: Release 10.2.0.3.0 - Production on Thu Dec 13 16:38:59 2007 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: QMS (DBID=1494649833) using target database control file instead of recovery catalog RMAN> RUN { 2> ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE'; 3> SEND 'BSA_SERVICE_HOST=QMS,NBBSA_TOTAL_STREAMS=1'; 4> BACKUP TABLESPACE 'PRESET_TBS'; 5> } allocated channel: ch0 channel ch0: sid=87 devtype=SBT_TAPE channel ch0: Symantec/BackupExec/1.1.0 sent command to channel: ch0 Starting backup at 13-DEC-07 channel ch0: starting full datafile backupset channel ch0: specifying datafile(s) in backupset input datafile fno=00043 name=Y:\ORACLE\ORADATA\QMS\PRESET_TBS.DBF channel ch0: starting piece 1 at 13-DEC-07 released channel: ch0 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ch0 channel at 12/13/2007 16:39:39 ORA-19506: failed to create sequential file, name="1mj3gtd8_1_1", parms="" ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: BEError(0xe000fe30) A communications failure has occurred. - The only things communication related that I can find in the logs are: [6024] 12/13/07 16:57:36 ndmp_writeit: NDMP Socket Error when trying to write message. Socket 0x588 len 0x20 [6024] 12/13/07 16:57:36 ndmp_writeit: ErrorCode :: 10054 : An existing connection was forcibly closed by the remote host. [1924] 12/13/07 16:56:52 BETCPConnection::LoopThroughListAndConnect: Could not connect to remote address "10.2.208.61" Error:10061. thanks for your help, -- Maurizio QMS-bengine00.log [6024] 12/13/07 16:57:36 ndmpCreateConnection [6024] 12/13/07 16:57:36 ndmpConnectEx: 'QMS' resolves to the local machine itself. So, we will try and connect to a loopback address ... [6024] 12/13/07 16:57:36 ndmpConnectEx : Control Connection information: A connection was established between end-points 0.0.0.0:2455 and 127.0.0.1:1026. [6024] 12/13/07 16:57:36 ndmpSendRequest: message:0x900 [6024] 12/13/07 16:57:36 ndmp_writeit: len:32 [6024] 12/13/07 16:57:36 ndmp_writeit: NDMP Socket Error when trying to write message. Socket 0x588 len 0x20 [6024] 12/13/07 16:57:36 ndmp_writeit: ErrorCode :: 10054 : An existing connection was forcibly closed by the remote host. [6024] 12/13/07 16:57:36 sent seq#: 1 msg: 0x900 [6024] 12/13/07 16:57:36 ndmp_process_messages: reply_expected:TRUE [6024] 12/13/07 16:57:36 ndmp_recv_msg [6024] 12/13/07 16:57:36 ndmp_readit: len:4000 [6024] 12/13/07 16:57:36 ndmp_readit: Caught message on closed connection. Socket 0x588 len 0xffffffff [6024] 12/13/07 16:57:36 ndmp_readit: ErrorCode :: 10054 : An existing connection was forcibly closed by the remote host. [6024] 12/13/07 16:57:36 ndmp_process_messages: detected eof [6024] 12/13/07 16:57:36 ERROR: ndmpcSendRequest->connection error [6024] 12/13/07 16:57:36 ERROR: ndmpSendRequest failed: [6024] 12/13/07 16:57:36 ndmpFreeMessage: message:0x0 [6024] 12/13/07 16:57:36 NDMPAgentConnector::SetupConnection: connectOpen failed on server QMS. [6024] 12/13/07 16:57:36 ndmpClose [6024] 12/13/07 16:57:36 @@@@@@@MyCloseSocket called with sockfd = 1416(0x588)retval = 0 [6024] 12/13/07 16:57:36 ndmpDestroyConnection [6024] 12/13/07 16:57:36 @@@@@@@MyCloseSocket called with sockfd = -1(0xffffffff)retval = -1 [6024] 12/13/07 16:57:36 NDMPVxBSAHostBackupEngine:ConnectToDataServer() failed for machine QMS. QMS-beremote00.log [5316] 12/13/07 16:56:41 NDMP Daemon Running.. [5316] 12/13/07 16:56:41 Could not create an IPv6 socket at this time, reason:An error occurred during a socket creation operation: Error Code: 10047, System Error Message: An address incompatible with the requested protocol was used. [5316] 12/13/07 16:56:41 @@@@@@@MyCloseSocket called with sockfd = 708(0x2c4)retval = 0 [5316] 12/13/07 16:56:41 SocketService::IsSystemDualIP: No support found for IPv6 currently [5316] 12/13/07 16:56:41 Started NDMP Listener on port 10000 [1108] 12/13/07 16:56:42 Running... 'Q' to stop [1924] 12/13/07 16:56:51 NrdsAdvertiserThread: advertisement cycle started. [1924] 12/13/07 16:56:51 Informational: Restrict Anonymous Support is enabled [1924] 12/13/07 16:56:51 creating DLE for local machine [1924] 12/13/07 16:56:51 BENetConfigEx: Successfully refreshed adapter information. [1924] 12/13/07 16:56:51 EnumClusterDLEs: Could not opening cluster : The system could not find the environment option that was entered. [1924] 12/13/07 16:56:51 NrdsAdvertiserThread: EnumSelfDLE for file system 7 returned 0(0x0) and 1 DLEs [1924] 12/13/07 16:56:51 NrdsAdvertiserThread: Nrds Message Len : 107. [1924] 12/13/07 16:56:51 RMAN_EnumSelfDLE: Checking if DBName QMS is part of RAC. [1924] 12/13/07 16:56:51 NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs [1924] 12/13/07 16:56:51 ConnectToServerEndPoint: dest=QMS, service=6101 [1924] 12/13/07 16:56:52 BETCPConnection::LoopThroughListAndConnect: Could not connect to remote address "10.2.208.61" Error:10061. [1924] 12/13/07 16:56:52 @@@@@@@MyCloseSocket called with sockfd = 856(0x358)retval = 0 [1924] 12/13/07 16:56:52 BETCPConnection::CreateConnectionFromHostAndPort: Remote Host: "QMS": There were no addresses returned, belonging to family: IPv6 [1924] 12/13/07 16:56:52 BETCPConnection::CreateConnectionFromHostAndPort: Could not create a connection to "QMS" because attempts with both IPv4 and IPv6 protocols failed [1924] 12/13/07 16:56:52 Could not create a BETCPConnection object from address: QMS error=An error occurred during a socket connect operation: Error Code: 10061, System Error Message: No connection could be made because the target machine actively refused it. [1924] 12/13/07 16:56:52 NrdsAdvertiserThread: connect to target=QMS port=6101 failed [1924] 12/13/07 16:56:52 NrdsAdvertiserThread: Retrying in 60 seconds [4456] 12/13/07 16:56:56 NrdsAdvertiserThread: negative (purge) advertisement cycle started. [4456] 12/13/07 16:56:56 NrdsAdvertiserThread: no purge is pending. [4456] 12/13/07 16:56:56 NrdsAdvertiserThread: negative (purge) advertisement cycle complete. Waiting 240 minutes before advertising again. [1924] 12/13/07 16:57:52 ConnectToServerEndPoint: dest=QMS, service=6101 [1924] 12/13/07 16:57:52 CreateConnection type=0 on socket 860 via BESocket OK [1924] 12/13/07 16:57:52 NrdsAdvertiserThread: send of qms type 7 subtype 2 to target=QMS port=6101 succeeded [1924] 12/13/07 16:57:52 @@@@@@@MyCloseSocket called with sockfd = 860(0x35c)retval = 0 [1924] 12/13/07 16:57:52 NrdsAdvertiserThread: advertisement cycle complete. Waiting 240 minutes before advertising again. [5316] 12/13/07 17:00:56 @@@@@@@MyCloseSocket called with sockfd = 688(0x2b0)retval = 0
Maurizio_2
17 years ago Place Backup Exec
4.3KViews
0likes
4Comments
Restore SQL to file?
is it possible to restore a database out in a file, instead of direct to another Sql server?
Solved
Emort
12 years ago Place Backup Exec
4.3KViews
3likes
2Comments
Backup Exec 2010 server service crashing after daily SQL BKUPEXEC database backup runs
Every day at 4am, immediately after the local Backup Exec database backup completes, the backup exec server process crashes with the following event in the application event log: Event ID: 1000 Faulting application beserver.exe, version 13.0.2896.0, time stamp 0x4b173f02, faulting module MSVCP80.dll, version 8.0.50727.4053, time stamp 0x4a5938bd, exception code 0xc0000005, fault offset 0x000000000002ba5c, process id 0x%9, application start time 0x%10. Operating System is Windows Server 2008 64bit.
Jon_Hicks
15 years ago Place Backup Exec
3.6KViews
0likes
29Comments
Moving BEXEC DB from one SQL server to another
Hey folks, I am trying to migrate our BEXEC SQL server to a stand alone SQL server. I am following the following article: http://www.symantec.com/business/support/index?page=content&id=TECH37752 The source DB is the default SQL server express instance that gets loaded by default when you install BEXEC. SQL Express 2005 Trying to move it to a SQL 2008 Enterprise box. When I kick off the the BEUTILITY to migrate the DB it fails saying: Failed to access the registry keys of selected server XXXX to get the Backup Exec version numbers. Failed to access the registry keys of the select server XXXX to get the SQL Server version number. Operation to change the location of Backup Exec database to SQL server instance XXXX ended with errors. Both machines are Windows Server 2008 x64 Remote registry is up and running on both machines. Using a domain admin account. Nothing in the event logs on either machine Help!!
Cyberfed27
13 years ago Place Backup Exec
3.2KViews
1like
8Comments
Symantec Backup Exec 2010 Remote Agent Utility Authentication Error
Dear Sir, While creating Oracle Database Backup job, Testing is successful, but when the actual backup process starts it gives the authentication error. "The logon account specified in the remoate agent utility cannot be authenticated. Update the entry in the list of authentication credentials in the media server" Our Backup Server IP : 10.36.65.11 (W2k3 STD R2 32 Bit) Our Database Server IP : 10.46.65.2 (W2k3 STD R2 64 Bit) Through Firewall, nating of Ip series has been configured & backup Ports are also opened. Also we were getting Backup Agent Utility Version error, "Make sure the correct version of remote agent is installed and running on the target computer. If the server or resource is no longer exists, remove it from the selection list ....." we did an unstallation from the Database server. Initially from RAWS64 the agent utility had been installed. But after we noticedthis versionerror duing uninstallation with suggestion to install from BEX64. We install from BEX64. Even after that also we are getting the same authentication errors. Event the authentication has been created in the authentication list. Our SAN : XG8T0MEXP & 6ND6LFEXP. We created MysymAccount (bala.it@ppcoimbatore.com), but could not include the SAN -XG8T0MEXP details. Pls. include the same also. Pls. give us backup remote agent authentication solution. How do we check the communication between remote agent and backup or media server (in our case both are same).
Balakrishnan
13 years ago Place Backup Exec
2.8KViews
0likes
25Comments
e0000340 - V-79-57344-832 – backups database
When we try to backup the database error e0000340 - V-79-57344-832 appears . The log refer to the Database output section but the log don’t have this section. We are using oracle 10G, backup exec 12 and windows 2003 server.
nsilva
16 years ago Place Backup Exec
2.4KViews
0likes
5Comments
Job hangs at "Snapshot Processing"; is the Database Corrupted?
I have a server that doesn't start its backup jobs, they get stuck on "Snapshot Processing" forever. My guess is that the backup Exec database is corrupt. I cannot just reinstall the program because it's linked to a (CASO) Central Server, and this could potentially fuck up every database linked (around 15-20), is this right? What would you recommend to reinstall this thing? I already tried beutility.exe to Repair said with no luck, and I'm not confident about doing the Dump/Recover thing. All servers are running v12.0 of Backup Exec. I cannot reboot the server either, because people are and will be using it all weekend long... this increases the hazard of not running backups during this time!
Javier_Aparicio
16 years ago Place Backup Exec
2.4KViews
0likes
9Comments