Director Recovery

If your configuration and binaries are saved on an other backup server (such as a Storage Daemon, or the Catalog server) as advised, you should be able to recover your Director with the following actions:

• Adjust the new binary path in either the bacula-dir.service unit file or the bacula-ctl-dir` startup script if needed. Usually they are locate in the /opt/bacula/bin directory and the binary path doesn’t require any change

• Comment all Job Schedule directives in bacula-dir.conf

• Affect the Director IP address to your temporary server

• Ensure that your temporary Director can connect to the Catalog (in pg_hba.conf or in mysql database).

• Start the temporary Director Daemon

• Start the Bare Metal or Standard Recovery procedure on your Director

• Stop the temporary Director and un-configure the Director IP address

• Reboot to the fresh Director

• Test your Director by doing one backup and restore of files per Storage Daemon

If your Director and your Catalog are on the same host, you need to restore the Catalog first or use a Bootstrap file as explained here.

See also

Go back to:

• System Recovery Preparation

• General GNU/Linux System Recovery

• GNU/Linux Bare Metal Recovery

• Windows Bare Metal Recovery

• Bacula Configuration Recovery

Go to:

• Storage Daemon Recovery

• Catalog Recovery

Go back to the Standard Recovery Solution chapter.

Go back to the Disaster Recovery chapter.

Go back to the main Bacula Infrastructure Recovery page.