How to generate debug logs and where to locate them in Backup Exec 9.1/9.2 for NetWare Servers

Article:TECH27890  |  Created: 2005-01-08  |  Updated: 2005-01-08  |  Article URL http://www.symantec.com/docs/TECH27890
Article Type
Technical Solution

Environment

Issue



How to generate debug logs and where to locate them in Backup Exec 9.1/9.2 for NetWare Servers

Solution



In all instructions and statements below, <VOLUME> should be substituted with the actual volume where Backup Exec (tm) 9.1 for NetWare Servers is installed to. In all cases, be sure to remove the debug switches after testing, as the debug logs can grow very large over time.

1. Media Server debug logs

To generate debug information on the media server, perform the following:

a. Exit Backup Exec by typing BESTOP at the server console prompt, and then pressing <Enter>

b. At the server console prompt, type BESTART -ZL at the server console prompt, and then press <Enter> to enable debug mode on the server

c. When testing is complete, type BESTOP at the server console prompt and then press <Enter> to shut down Backup Exec

Note: If Backup Exec is installed to a clustered volume, BESTART and BESTOP become BESTARTC and BESTOPC respectively.

The following logs will be generated:

In <VOLUME>:\BKUPEXEC\LOG

BEDBG.LOG
BEPSVR.LOG
BESVRDBG.LOG
NDMPC.LOG
NDMPD.LOG


In <VOLUME>:\BKUPEXEC

BKUPEXEC.LOG
BESTOP.LOG

Media Server - Workstation Agent debug information
If the problem being worked on is related to the access of a Backup Exec workstation agent, the debug output of NRLTLI.NLM may be useful. This log provides insight into the advertising from, and connections to, the Generic Remote File System (GRFS) agents. The GRFS style agents in Backup Exec 9.1 are used for Windows 95, 98, Me Agents, Macintosh Agent, and the Linux/UNIX agent. This component is not used with any of the accelerated Network Data Management Protocol (NDMP) based Remote Agents for NetWare and Windows NT/2000/2003/XP.

To enable the NRLTLI.NLM debug output on the media server, perform the following:

a. Exit Backup Exec by typing BESTOP at the server console prompt, and then pressing <Enter>

b. Edit the BESTART.NCF file. Add the command LOAD SYS:\BKUPEXEC\NLMS\NRLTLI -z just before the LOAD SYS:\BKUPEXEC\NLMS\BKUPEXEC.NLM line. This option causes NRLTLI to send debug output to the console (or logger screen in NetWare 6.x).

c. In order to send in the console log, the console logger needs to be stopped with the UNLOAD CONLOG.NLM command. The resulting file is named SYS:\ETC\CONSOLE.LOG. Copy this file and then restart the console logger with the LOAD CONLOG.NLM command. To save the information from the logger screen in NetWare 6.x, please refer to  http://support.novell.com (at the time of writing this TechNote, TID #10072682 contained these instructions).

2. Remote Server debug logs

To generate debug information for a remote server, perform the following:

a. At the remote server console prompt, type BESTART -ZL at the server console prompt, and then press <Enter>

b. When testing is complete, type BESTOP at the server console prompt, and then press <Enter>

Note: If Backup Exec is installed to a clustered volume, then BESTART and BESTOP become BESTARTC and BESTOPC respectively.

The following debug reports will be generated:

In <VOLUME>:\BKUPEXEC\LOG:

NDMPD.LOG


In <VOLUME>:\BKUPEXEC

BKUPEXEC.LOG
BESTOP.LOG


3. Media Server JAVA debug logs

a. To generate debug information for the Java Application Server, edit the file <VOLUME>:\BKUPEXEC\NLMS\BESTARTJ.NCF

The last line of the file looks like this:
----------------------------------------------------
JAVA -nsac -sn"Backup Exec Java Application Server" -Djava.security.policy=
\\bkupexec\java\bkupexec.policy vrts.hro.net.rmi.server.ServerMain -P 10002
-Language eng -Path <VOLUME>:\BKUPEXEC\LOG\
----------------------------------------------------

Change it to read (the change is bolded):

----------------------------------------------------
JAVA -nsac -sn"Backup Exec Java Application Server" -Djava.security.policy=
\\bkupexec\java\bkupexec.policy vrts.hro.net.rmi.server.ServerMain -P 10002
-Language eng -Path <VOLUME>:\BKUPEXEC\LOG\ -debuglog
-----------------------------------------------------

This will enable debug in the Java engine whenever Backup Exec is started. To disable debug, remove the -debuglog switch from the last line of the file. The debug report BEDebugLog_JavaServer.txt is generated in <VOLUME>:\BKUPEXEC\LOG.

b. To generate debug information for the server-based Java Administration console, edit the file SYS:\SYSTEM\BESTARTJC.NCF

The last line of the file looks like this:
-----------------------------------------------------
JAVA -nsac -sn"Backup Exec Java Administration Console" -Xms64M
-Xmx256M vrts.hro.UserInterface.console.BEAdminConsole -Path
SYS:\BKUPEXEC\JAVA\CLIENT\BATCH -Language eng
-----------------------------------------------------

Change it to read (the change is emphasized):

-----------------------------------------------------
JAVA -nsac -sn"Backup Exec Java Administration Console" -Xms64M
-Xmx256M vrts.hro.UserInterface.console.BEAdminConsole -Path
SYS:\BKUPEXEC\JAVA\CLIENT\BATCH -Language eng -debuglog
-----------------------------------------------------

This will enable debug whenever the JAVA Administration console is started on the server. To disable debug, remove the -debuglog switch from the last line of the file. The debug report BEDebugLog_JavaClient.txt is generated in <VOLUME>:\BKUPEXEC\JAVA\CLIENT\BATCH.


4. Workstation Java debug logs (where the Windows-based Java Administration console is running)

To generate Java debug information on the workstation running the Administration console, start the console by executing RUN.BAT instead of using a shortcut (in a default installation, the RUN.BAT file is installed in C:\Program Files\Veritas\Backup Exec for NetWare\Batch). The debug report BEDebugLog_JavaClient.txt will be generated in the C:\Program Files\Veritas\Backup Exec for NetWare\Batch directory.


5. Installation debug logs (when installing Backup Exec 9.1 for NetWare Servers from a workstation)

To generate debug logs for the installation process on the workstation, run SETUP.EXE with the --Debug=On switch. Note the two dashes. This will create the file DEBUG.LOG in the root of the Windows drive. Note that this is generally in C:\DEBUG.LOG, but if Windows was installed on a different drive, it could be at the root of another volume (such as D:\DEBUG.LOG).

When installing from a Backup Exec 9.1 for NetWare Servers installation CD, do the following:

a. Click Start | Run

b. Type D:\NETWARE\INSTALL\SETUP.EXE --DEBUG=ON (where D: is the drive letter for the CD-ROM drive), and then click OK


When installing Backup Exec 9.1 for NetWare Servers from a downloaded copy of the install, do the following:

a. Click Start | Run

b. Type <path>\SETUP.EXE --DEBUG=ON (where <path> is the directory where the download package was extracted. For example,  C:\DOWNLOADS\BENW\SETUP.EXE --DEBUG=ON)

c. Click OK

Please see  http://support.veritas.com/docs/272988 for details on the Remote Agent for Linux and Unix Servers debug logs.



Legacy ID



262008


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


Terms of use for this information are found in Legal Notices