← Back to all articles

Overview

Debug mode writes everything the backup software does to a log file. We can use this log to find the cause of a backup problem. You need to be signed in to Windows as an administrator.

Turn on debug mode

  1. Right-click Notepad and click Run as administrator.
  2. In Notepad, click File → Open. Change the file type from Text documents (*.txt) to All files, otherwise the file won’t be listed. Then open:
    • Server software: C:\Program Files\serverbackup\bin\RunCB.bat
    • Desktop software: C:\Program Files\desktopbackup\bin\RunCB.bat
  3. Find this line:
    SET DEBUG_MODE=" "
    and change it to:
    SET DEBUG_MODE="--debug "
    Type it exactly as shown: two hyphens before debug, with no space between them.
  4. Save the file.

Run the backup in debug mode

  1. Make sure the folder C:\temp exists. The log is saved there, but you can use any folder you can write to.
  2. Type cmd in the Start menu search, right-click Command Prompt and click Run as administrator. If you use a normal Command Prompt, the software still runs but the log won’t be complete.

    Command Prompt with Run as administrator selected

  3. Go to the software’s folder:
    • Server software: cd "C:\Program Files\serverbackup\bin"
    • Desktop software: cd "C:\Program Files\desktopbackup\bin"
  4. Start the software with logging turned on:
    RunCB.bat > C:\temp\backupdebug.log
  5. The backup software opens. Run the backup that has the problem and wait for it to finish or fail.
  6. Close the backup software.

Send us the log and turn debug mode off

  1. Attach C:\temp\backupdebug.log to a support ticket.
  2. Open RunCB.bat in Notepad as administrator again, change the line back to SET DEBUG_MODE=" " and save the file.