General Plugin Parameters

Enterprise

Bacula Enterprise Only

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

Parameter

Required

Default

Description

Example

server

Yes

DNS name of RHV~Manager (the server parameter requires a domain name, not an URI, nor are IP addresses allowed).

server=rhv.example.com

use_imageio_in_mng_node

No

false

Indicates whether the Manager’s proxy or the host itself will be used to retrieve disk data. This requires that the hosts be network-accessible by the bacula-fd.

use_imageio_in_mng_node=true

truststore_file

Yes

File name of truststore

truststore\_file=/opt/bacula/etc/rhv-trust

truststore_password

No

changeit

Truststore password

truststore\_password=changeit

truststore_hpassword

No

changeit

Obfuscated truststore password, use either the obfuscated or plain password

truststore_hpassword=NTUyOjU0NDpRR1xaR0VJWwA

insecure

No

false

Mode insecure, without truststore. Not recommended in production environment

insecure=yes

user

No

admin

RHV user account to authenticate as

user=bacula

password

Yes

User password

password=rhvpass123

hpassword

Yes

Obfuscated user password

hpassword=NTUyOjU0NDpRR1xaR0VJWwA

auth

No

http

Authentication type, http or oauth

auth=oauth

config_file

No

Path to configuration file

config_file=/opt/bacula/etc/rhv.conf

profile

No

internal

Connection user profile

profile=internal

abort_on_error

No

1

Abort the backup in case of any problem with disks implied or previous backup files (0 or 1)

abort_on_error=0

output

No

json

Helper program output format, one of json, bacula, console

output=console

log

No

./rhv-plugin.log

Log to specified file

log=/tmp/rhvbkup.log

debug

No

0

Enable debug output: 0 (informational), 1 (debug), 2 (deep debug)

debug=1

Note

To create obfuscated passwords, the Bacula administrator should execute the command @encode password in bconsole and copy the result, or execute it directly via the plugin. This application is explained in section Plugin System.

Note

Alternatively to using the user credentials in the plugin line, the plugin parameter config_file allows for the creation of a file which can be used to provide all necessary options. These configuration files are plain text files containing one setting per line where the name of the setting and its value are separated by an equals sign “=”. An example configuration file could look like this:

server=rhv.example.com
user=admin
truststore_file=/opt/bacula/etc/rhvm.truststore
target_datacenters=myDatacenter
operation=backup

If a parameter is mentioned more than once, the last instance is used.

Go back to: Plugin Configuration.