Using Backup Exec's BEDBG tool to create crash dumps for Backup Exec processes
Further details may be found in the Administrator's Guide.
Generates a user dump of a process that shuts down unexpectedly.
bedbg Starts bedbg in console mode
bedbg --sc+ Creates bedbg service
bedbg --sc- Deletes bedbg service
bedbg --I Registers bedbg as a post-event debug tool
bedbg --UI Unregisters post-event debugger
BE 2010, 2010 R2, 2010 R3 - Captures memory dump of a running process
bedbg --pid BE 2012 and higher - Captures memory dump of a running process
Enables local archiving of WER collected dumps
bedbg --wer- Disables WER local archiving
bedbg --? Displays bedbg usage information
bedbg --?? Displays bedbg help
--max # Maximum number of dump files in a folder (def: 10)
--type # Memory dump type: 0 - custom (def), 1 - mini, 2- full.
--path arg The path where the dump files are to be stored.
1. For BE 2010 attach BEDBG to a running process (for BE 2010 R2 and later versions just follow this for a process crash not creating a dmp output automatically)
To perform this, you first need to determine the processes PID. This can be determined using Window's Task Manager.
Launch Task Manager and go to View > Select Columns (FIGURE 1):
Select PID (Process Identifier) from the list (FIGURE 2):
Now Task Manager will show you the PID for all processes (FIGURE 3):
Running the following will allow you to attach to just a single process (FIGURE 4):
NOTE: The command window must be left open in order for BEDBG to stay running and capture the crash. Closing the command prompt window or logging off of the server will cause BEDBG to close.
C:\Program Files\Veritas\Backup Exec>bedbg --I --type 2
In case dump is not created in Backup Exec 2012 and later versions, bedbg needs to be attached to a crashing process (similarly to the step 1) with the following command:
C:\Program Files\Veritas\Backup Exec>bedbg --pid <PID>
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):