Preparing Recovery Environment

Bacula Enterprise Only

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

Preparing BMR Restore

To make the BMR configuration complete, a Rescue Client resource that will be used during restore needs to be defined:

Client {
  Name = rescue-fd                 # Use your rescue client name
  Address = 0.0.0.0                # Will be set automatically by LinuxBMR
  Password = bacularescue          # USE YOUR OWN PASSWORD
  Catalog = MyCatalog
}

During a LinuxBMR restore session, the LinuxBMR system needs to contact the Director. To do so a Console is required in the Director’s configuration. For security reasons a named Console is used, which may be configured with restricted permissions. A Console resource for use with the LinuxBMR toolkit could be set up as follows:

Console {
  Name = rescue-fd                # MUST HAVE same name as Client resource
  Password = bacularescue         # USE YOUR OWN!
  CommandACL = *all*
  ClientACL = *all*
  CatalogACL = *all*
  JobACL = *all*
  StorageACL = *all*
  ScheduleACL = *all*
  PoolACL = *all*
  FilesetACL = *all*
  WhereACL = *all*
  # The next two ACLs are required when using
  # Bacula Enterprise 8.8.0 and above
  UserIdACL = *all*
  DirectoryACL = *all*
  # This last ACL is available when using
  # Bacula Enterprise 8.8.0 and above but is not required
  RestoreClientACL = *all*
}

Finally a restore job resource which does not have any run scripts is needed by the LinuxBMR restore process.

Creating LinuxBMR Rescue Media

The LinuxBMR recovery image may be downloaded from your download area. This ISO image may be written to a CD, a DVD, or a USB key. It is also possible to customize the image with some information related to your infrastructure.

LinuxBMR-rescue-amd64-<version_number>.iso

The size of the image can vary from version to version. The latest version is currently too big to fit on a CD media, but that may change for future releases, as we do our best to keep the size as small as possible. The ISO image file may be used directly on VMware or VirtualBox to boot a Virtual Machine.

On , tools like Win32DiskImager are available to write the image to a USB stick. This tool may be downloaded from https://sourceforge.net/projects/win32diskimager/

Warning

Attention!

On Linux, the cp or dd commands can be used to do the job. This needs to be done carefully, as the procedures described in this section will destroy anything already on the target! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on your hard disk is lost.

With current systems, a USB stick should be automatically recognized when inserted. If it is not, you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a block storage device named /dev/sdX, where the “X” usually is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command dmesg after inserting it.

To write to your stick, you may have to turn off its write protection switch.

root# cp LinuxBMR-rescue-amd64-2.0.0.iso /dev/sdX
root# sync

Make sure to use /dev/sdX and not /dev/sdX1. This is a very common error.