Restore Parameters

Bacula Enterprise Only

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

OpenStack Restore Parameters
Parameter	Values	Default	Description
proxy_server	`<String>`		UUID or name of the proxy server used to run the Bacula File Daemon with the OpenStack Plugin.
abort_on_error	`[= <0 or 1>]`	`0`	Specifies whether the plugin should abort on fatal errors during backup or restore. This parameter is optional.
OS_USERNAME	`<String>`		Specifies the username to access the OpenStack API.
OS_PASSWORD	`<String>`		Specifies the password to access the OpenStack API
OS_AUTH_URL	`<String>`		Specifies the endpoint to access the OpenStack API
OS_USER_DOMAIN_NAME	`<String>`		Specifies the domain that accesses the OpenStack API
OS_PROJECT_NAME	`<String>`		Specifies the project that accesses the OpenStack API
openrc	`<String>`	`/opt/bacula/etc/openstack.conf`	Specifies the path to an OpenStack rc file to automatically gather connection information.
server_restore_name	`<String>`		Name to attribute to the restored server.
server_restore_prefix	`<String>`		Prefix to prepend to all restored server name.
server_restore_network	`[= yes or no or auto>]`	`no`	If set to `no` the plugin will create a bogus network to attach to restore server. If `yes`, the plugin will try to find a network matching the server’s original network. If `auto`, the plugin will let OpenStack system try to assign a network to restored server.
verbose	`[= <0 or 1>]`	`0`	This parameter activate verbose output in Bacula joblog.
debug	`[0 - 9]`	`0`	Specifies the debug level. `0` is no debug, `9` is the highest level. Warnings and errors are always sent to the joblog.
server_restore_volume_metadata	`[= <0 or 1>]`	`0`	If set to `1`, the plugin attempts to restore volume image metadata for restored volume that were originally attached to a Nova instance.
server_restore_volume_custom_metadata	`<String>`		Path to a file where each line is a `key=value` tuple. Each entry represents a custom volume image metadata entry to add to restored volume originally attached to a Nova instance.
server_restore_volume_metadata_method	`[= regular or external]`	`regular`	If any volume image metadata restore is attempted via `server_restore_volume_metadata` or `server_restore_volume_custom_metadata`, this parameter chooses which method is used for the restore. External delegates a bigger part of the metadata restore process to OpenStack internal tools.
server_cross_restore_mode	`[= try or id or name or none]`	`try`	Decides which method to use in case of cross-project server restore. `try` attempts to find the original project by ID and then by name, `id` searches only by ID, `name` searches only by name, and `none` restores all servers on the same project as the proxy server.

Important Notes

At restore time, if server_restore_name is not set, the plugin will use the original Nova server name.

If a Nova server with the same name already exists, the plugin will append the -<index> to the restored Nova server name, and it will not replace the existent Nova server.