Fix: Can’t remove server from Backup Exec selection list


One of our Backup Exec 11d jobs failed last night with the following error in the Backup Exec job log:

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

This same error was seen in the Windows Application log as Backup Exec Event 34113.

A check of the server listed in the error log showed the Backup Exec Remote Agent service had been stopped and disabled last night.  I checked with the administrator who did this, and she confirmed the server had been decomissioned and was no longer being backed up.  Oddly enough, she said she removed the server from the Backup Exec job’s selection list.

I opened up the selections list for the job in question, and lo and behold, the offending server was still selected.  I deselected the server, applied changes, re-opened the server selections – and the server was still selected.

Initial thought was something was wrong with Backup Exec, so I exited the program, restarted the BE services, went back into the application and went through the exercise of deselecting the decommissioned server and saving changes… but the server was once again selected.

The solution ended up being based on Symantec Document ID 277355.  Rather than unchecking the box next to the server’s name on the “View by Resource” tab, I deleted all of the decommissioned server’s resources on the “View Selection Details” tab.  After saving changes and exiting the application, I saw that the server was no longer showing as selected when viewing the job selections list.

Note:

My instuctions are for Backup Exec 11d. Symantec Document ID 277355 is written for BE 10.0 and 10d.  In version 10 instead of selecting the “View Selection Details” tab, change the view format from Graphical to Text.  Same thing, different terminology and GUI layout.

Enabling Backup Exec remote agent debug logging on Novell Netware


We’ve been experiencing issues with some of our Backup Exec 9 remote agents losing their connections to media server during backup.  The Backup Exec server job logs report the following generic error:

Final error: 0xa000fe30 – A communications failure has occurred.

To help troubleshoot this problem, I decided to enable debugging on the Backup Exec remote agent. To do this, on the Netware server that is running the Backup Exec remote agent:

1.  Make a backup copy of the sys:\system\bestart.ncf file

 2.  Edit the sys:\system\bestart.ncf file
 
3.  The default bestart.ncf should look something like:
 
SEARCH ADD SYS:\BKUPEXEC\NLMS
LOAD BKUPEXEC.NLM -tr
 
4.  Add -zl to line that loads BKUPEXEC.NLM, so it looks like
 
SEARCH ADD SYS:\BKUPEXEC\NLMS
LOAD BKUPEXEC.NLM -tr -zl
 
5. At the server console, stop the Backup Exec remote agent by typing
 
bestop.ncf
 
6.  At the server console, start the Backup Exec remote agent by typing
 
bestart.ncf
 
Remote agent log files will be written to SYS:\BKUPEXEC\LOG\NDMPD.LOG
 
Make sure to disable remote debugging once you are through troubleshooting, or you may fill up your SYS volume.  To do this:
 
1.  Restore the copy of your original bestart.ncf file to sys:\system.
 
2.  On the server console, type bestop.ncf to unload the remote agent.
 
3.  On the server console, type bestart.ncf to load the remote agent with the original settings.
 
 

Howto: Enable debug logging for Backup Exec for Windows Servers


You can temporarily enable Backup Exec debug logging by adding the -debug start parameter to the Backup Exec Remote Agent for Windows Servers service. This is a temporary setting that will be reset when the services are cycled or at the next server reboot.  To enable debug logging permanently, see the second section that details editing the reqistry.

To temporarily enable Backup Exec debug logging on Windows 2000, Windows XP, Windows 2003 and Windows 2008:
 
1. Go to Start > Programs > Administrative Tools > Services

2. Select the Backup Exec Remote Agent for Windows Servers service, and click Stop. When prompted, click Yes to shut down the service.

3. Select and right-click on the Backup Exec Remote Agent for Windows Servers service, and then select Properties

4. In the Startup Parameters box, type debug.  Click Start in the Properties page to start the service. Click OK 

5. Select and right-click the Backup Exec Job Engine service, and then select Properties

6. In the Startup Parameters box, type debug. Click Start in the Properties page. Click OK to close. 
 
To permanently enable Backup Exec debug logging on Windows NT 4.0, Windows 2000, Windows XP, Windows 2003 and Windows 2008:
 
1. Stop all Backup Exec for Windows Servers services

2. Run REGEDIT.EXE

3. a. Backup Exec 10d or below: Browse to HKey_Local_Machine\Software\VERITAS\Backup Exec\Engine\Logging

     b. Backup Exec 11d or above: Browse to HKey_Local_Machine\Software\Symantec\Backup Exec for Windows\Backup Exec\Engine\Logging


4. Change the value of CreateDebugLog to 1 to enable debug logging

5. Quit the registry editor

6. Start the Backup Exec for Windows Servers services

After the Backup Exec Job Engine and Backup Exec Remote Agent for Windows Servers service are started, two log files will be created in the Backup Exec \Logs directory, which is located in one of the following directories:
 
  • Backup Exec 10d or below:  \Program Files\Veritas\Backup Exec\NT\Logs
  • Backup Exec 11d or above:  \Program Files\Symantec\Backup Exec\Logs
The name of the log files will follow the format of <ServerName>-BENGINEXX.Log for the Backup Exec Job Engine service, and <ServerName>-BEREMOTEXX.LOG for the Backup Exec Remote Agent for Windows Servers service. The XX will increment each time the services are started with the -debug option, so that a new log file is created.
 

FIX: Event ID: 57860 “An error occurred while attempting to log in to the following server… SQL error number: “0011” is seen when backing up a server with SQL installed


Exact Error Message

Event ID: 57860 Source: Backup Exec Type: Error Description: An error occurred while attempting to log in to the following server: “SERVERNAME”. SQL error number: “0011”. SQL error message: “[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
 
Details:
 
This error will occur when performing any type of backup on a server running Microsoft SQL Server or Microsoft SQL Server Desktop Engine (MSDE), even if the SQL Agent Backup is not being performed. “bedssql2.dll” will always be initialized and loaded on every server that is running the “Backup Exec Remote Agent Service ” whether the SQL agent and license is installed or not.
 
Cause:
 
One or more SQL Databases are corrupted on the remote machine, or the SQL database no longer exists on the remote machine.

Workaround:

Perform the following to resolve this issue:

1. On the SQL server, stop the Backup Exec Remote Agent Service from Windows Control Panel > Services.

2. If SQL is installed on the media server (i.e. if SQL is on the same machine as Backup Exec), within Windows Explorer browse to the installation directory for Backup Exec, which by default is:

\Program Files\VERITAS\Backup Exec\NT

for Backup Exec version 11d and above, the default location is 

\Program Files\Symantec\Backup Exec\
 
If SQL is installed on a remote server, browse to the installation directory for the Remote Agent:

\Program Files\VERITAS\Backup Exec\RANT

for 11d and above:

\Program Files\Symantec\Backup Exec\RAWS

3. Rename the bedssql2.dll file to bedssql2.old

4. Start the Backup Exec services

If the SQL/MSDE is installed on a Remote Server:

1. Stop Remote Agent service on the remote server.
2. Rename the bedssql2.dll file to bedssql2.old on the remote server.
3. Start the Remote Agent service.
4. Re-Start the Backup Exec services on the media server.
5. Run the Backup job and check the result.

WARNING:  Renaming the bedssql2.dll will effectively disable the SQL agent on the server it is renamed upon.  If the SQL agent is purchased in the future, the issue with the corrupt database(s) must be resolved first, and backup of the SQL servers on which the bedssql2.dll was changed is desired – the bedssql2.old file MUST be renamed back to bedssql2.dll. 

Converting Backup Exec 11d job logs into .txt or .html files


Backup Exec 11d saves it’s jobs logs as .xml files by default. Symantec Document ID 287036 describes how to use the bemcmd.exe program to save the .xml job log as a text or html file.

The default location of bemcmd.exe is the \Program Files\Symantec\Backup Exec directory on the drive the software is installed.

To convert the job log D:\Backup Exec\Data\BEX_BKP2_08574.xml into a .html file named dailydiff.html, run the following from a command prompt where bemcmd.exe is located (type as one line):

bemcmd -o31 -l”dailydiff.html” -s1 -f”D:\Backup Exec\Data\BEX_BKP2_08574.xml”

To save the same BEX_BKP2_08574.xml log file as a text file the command would be (again, typed as a single line):

bemcmd -o31 -l”dailydiff.txt” -s0 -f”D:\Backup Exec\Data\BEX_BKP2_08574.xml”

Howto: Stop Backup Exec from failing entire backup jobs when corrupt files are encountered


Here is the registry entry to stop Backup Exec from failing backup jobs when corrupt files are encountered

[For Backup Exec versions 9x and 10x]
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup

[For Backup Exec versions 11x and 12x]
HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec for Windows\Backup Exec\Engine\Backup

On the menu bar, select Edit | Add Value

In the Value name field, type in Fail Jobs On Corrupt Files

For the Data Type, select REG_DWORD

In the right window, double-click Fail Jobs on Corrupt Files

Change the Value to 0 (zero)

Restart the Backup Exec services or restart the Windows server.