Section 1 - Help Centre

This section provides useful help and tips over and above the formal support manual sections 2 through 18.




1.5 How to start OBM / ACB in debug mode?


    Product Version: ACB / OBM: All

    Operating System: All platforms

    Description: How to start OBM / ACB in debug mode?

    Steps:
    This document contains the information of how to start OBM / ACB in debug mode.


    Table of Contents:



    1. Instruction for ACB:


    2. Instruction for OBM:

    Note:
    Debug mode is only available for ACB version after 5.5.1.0.




    For ACB / OBM version 6.7.0.0 or above - Windows / Mac OS X:

    Back to top

    You can start the client agent in debug mode by editing the RunOBC batch / script file and afc.opt files, located in the installation home and installation home bin folder -

    ${Install-Home}\bin\RunOBC.bat       or        ${Install-Home}/bin/RunOBC.sh
    ${Install-Home}\afc.opt



    1. Open the RunOBC.bat / RunOBC.sh file with a text editor:

      2. RunOBC:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Enable/Disable debug mode
       e.g. SET DEBUG_MODE="--debug"
         or  SET DEBUG_MODE=""
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      SET DEBUG_MODE=""


    2. Edit the 'DEBUG_MODE' parameter by adding the option '--debug', similar to the example as follows:

      RunOBC (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Enable/Disable debug mode
       e.g. SET DEBUG_MODE="--debug"
         or  SET DEBUG_MODE=""
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      SET DEBUG_MODE="--debug"

    3. Save all changes afterward.
    4. Execute the RunOBC.bat / RunOBC.sh file in command prompt or terminal.

    For ACB / OBM version 5.5.1.0 - 6.5.x.x - Windows / Mac OS X:

    Back to top

    You can start the client agent in debug mode by editing the RunOBC batch or script file, located in the installation home bin folder -

    ${Install-Home}\bin\RunOBC.bat       or        ${Install-Home}/bin/RunOBC.sh



    1. Open the RunOBC.bat / RunOBC.sh file with a text editor:

      RunOBC.bat or RunOBC.sh:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Enable/Disable debug mode
       e.g. SET DEBUG_MODE="--debug"
         or  SET DEBUG_MODE=""
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      SET DEBUG_MODE=""

    2. Edit the 'DEBUG_MODE' parameter by adding the option '--debug', similar to the example as follows:

      RunOBC.bat or RunOBC.sh (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Enable/Disable debug mode
       e.g. SET DEBUG_MODE="--debug"
         or  SET DEBUG_MODE=""
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
       SET DEBUG_MODE="--debug"

    3. Save the changes afterward.
    4. Execute the RunOBC.bat / RunOBC.sh file in command prompt or terminal.


    For OBM version 6.7.0.0 or above - Linux: Back to top



    You can start the client agent in debug mode by editing the RunBackupSet.sh file and afc.opt files, located in the installation home and installation home bin folder -

    ${Install-Home}/bin/RunBackupSet.sh
    ${Install-Home}/afc.opt

    1. Open the RunBackupSet.sh file with a text editor:

      RunBackupSet.sh:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="NO-DEBUG"

    2. Edit the DEBUG_MODE parameter by changing 'NO-DEBUG' to 'DEBUG', similar to the example as follows:

      RunBackupSet.sh (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="DEBUG"

    3. Save all changes afterward.
    4. Execute the RunOBC.bat / RunOBC.sh file in command prompt or terminal.


    For OBM version 5.5.1.0 - 6.5.x.x - Linux

    Back to top

    You can start the client agent in debug mode by editing the RunBackupSet.sh script file, located in the installation home bin folder -

    ${Install-Home}/bin/RunBackupSet.sh



    1. Open the RunBackupSet.sh file with a text editor:

      RunBackupSet.sh:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="NO-DEBUG"

    2. Edit the DEBUG_MODE parameter by changing 'NO-DEBUG' to 'DEBUG', similar to the example as follows:

      3. RunBackupSet.sh (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="DEBUG"

    3. Save the changes afterward.
    4. Execute the RunBackupSet.sh file in shell.


    For OBM version 5.2.x installation on Windows / Mac OS X:

    Back to top

    You can start the client agent in debug mode by editing the RunOBM batch or script file, located in the installation home bin folder -

    ${Install-Home}\bin\RunOBM.bat       or        ${Install-Home}/bin/RunOBM.sh



    1. Open the RunOBM.bat / RunOBM.sh file with a text editor:

      RunOBM.bat:

       ...
      %JAVA_EXE% %JAVA_LIB_PATH% %CLASSPATH% %JAVA_OPTS% obm %OBM_HOME%
      CONFIG_HOME%
      pause
       ...

      RunOBM.sh:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set the debug mode. Options available: [ --debug | {EMPTY} ]
       e.g. DEBUG_MODE=--debug
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE=

    2. For RunOBM.bat, edit the %JAVA_EXE% parameters similar to the example as follows:

      3. RunOBM.bat (Updated):

       ...
      %JAVA_EXE% %JAVA_LIB_PATH% %CLASSPATH% %JAVA_OPTS% obm --debug %
      OBM_HOME% %CONFIG_HOME% > c:\debug.log
      pause
       ...

    3. For RunOBM.sh, edit the DEBUG_MODE parameter by adding the option '--debug', similar to the example as follows:

      4. RunOBM.sh (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set the debug mode. Options available: [ --debug | {EMPTY} ]
       e.g. DEBUG_MODE=--debug
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE=--debug

    4. Save the changes afterward, then execute the RunOBM.bat / RunOBM.sh file.


    For OBM version 5.2.x installation on Linux:

    Back to top

    You can start the client agent in debug mode by editing the RunBackupSet.sh script file, located in the installation home bin folder -

    ${Install-Home}/bin/RunBackupSet.sh



    1. Open the RunBackupSet.sh file with a text editor:

      2. RunBackupSet.sh:

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="NO-DEBUG"

    2. Please amend the DEBUG_MODE line by changing "NO-DEBUG" to "DEBUG", so the line will appear similar to the example as follows:

      3. RunBackupSet.sh (Updated):

      ------------------------------------------------------------------  DEBUG_MODE  -----------------------------------------------------------------
      Set Debug mode.
      Options available: DEBUG/NO-DEBUG
       e.g. SET DEBUG_MODE="DEBUG"
          or  SET DEBUG_MODE="NO-DEBUG"
      --------------------------------------------------------------------------------------------------------------------------------------------------------------
      DEBUG_MODE="DEBUG"

    3. Save the changes afterward, then execute the RunBackupSet.sh file.

      4. Back to top