vSphere Plugin Logs

Enterprise

Bacula Enterprise Only

This solution is only available for Bacula Enterprise. For upgrade inquiries, please reach out to sales@baculasystems.com.

The vSphere Plugin uses many different technologies and third party libraries. The result is that traces are spread among different directories on the backup server. You will be able to consult the following files:

vSphere plugin traces
File	Component	Note
/opt/bacula//vsphere-ctl-.log	vsphere-ctl	This file is produced by the Java vsphere-ctl program that sends commands to the ESXi/vCenter server.
/opt/bacula/working/vsphere/``/``/`*`.log	vddk	This file is produced by the C++ vddk program that read/write to the VMDK.
/opt/bacula/working/`*`.trace	bacula-fd	This file is produced Bacula File Daemon when activating the debug.

To extract the bvmdk file without converting it with vddk on the fly during a restore, you need to set the File Daemon debug level to 1. Bacula may report a false error during the restore about the file size. This is normal.