User Tools

Site Tools


freebsd_disaster_preparedness_planning

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
freebsd_disaster_preparedness_planning [2009/03/10 17:43]
dsampson created
freebsd_disaster_preparedness_planning [2010/01/14 12:29] (current)
deadeyes
Line 1: Line 1:
 ====== FreeBSD Bacula Disaster Preparedness & Planning ====== ====== FreeBSD Bacula Disaster Preparedness & Planning ======
  
-===== Create Static Bacula FD =====+===== Create Static Bacula FD (<​bacula-3.x.x) ​=====
  
 The Bacula FD daemon in the FreeBSD port is compiled dynamically-- not statically. This means that during a restore of a client, the FD daemon may be missing several libraries or may fail due to incompatible versions of libraries. To check for dependency on libraries, one needs to run the '​ldd'​ command followed by the name of the file. Thus checking for libraries needed by /​usr/​local/​sbin/​bacula-fd would be as follows: The Bacula FD daemon in the FreeBSD port is compiled dynamically-- not statically. This means that during a restore of a client, the FD daemon may be missing several libraries or may fail due to incompatible versions of libraries. To check for dependency on libraries, one needs to run the '​ldd'​ command followed by the name of the file. Thus checking for libraries needed by /​usr/​local/​sbin/​bacula-fd would be as follows:
Line 58: Line 58:
  
 One should copy these files to a safe and secure place-- preferably off-site. Or into a backup bag that is taken off-site during non-business hours. All of the files and system configuration information should be copied to a ftp server prior to the restore process. One should copy these files to a safe and secure place-- preferably off-site. Or into a backup bag that is taken off-site during non-business hours. All of the files and system configuration information should be copied to a ftp server prior to the restore process.
 +
 +===== Create Static Bacula FD (Bacula 3.x.x) =====
 +
 +For bacula 3.x.x the procedure for building a static bacula file daemon is slightly different.
 +
 +First edit /​etc/​make.conf and add the following(--disable-libtool is now needed to compile a static binary):
 +   .if $(.CURDIR:​M*/​sysutils/​bacula-client) || \
 +      $(.CURDIR:​M*/​sysutils/​bacula-client)
 +   ​CONFIGURE_ARGS+=--disable-libtool
 +   ​.endif
 +
 +Now configure and compile:
 +   cd /​usr/​ports/​sysutils/​bacula-client
 +   make config
 + (In make config you select the SFDAEMON.)
 +   make
 +
 +In /​usr/​ports/​sysutils/​bacula-client/​work/​bacula-3.x.x/​src/​filed you will find static-bacula-fd.
 +
 +To check if you correctly compiled the binary execute this command:
 +   file static-bacula-fd
 +In the output you should find "​statically linked":​
 +   ​static-bacula-fd:​ ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), for FreeBSD 7.2, statically linked, FreeBSD-style,​ stripped
 +
  
 ===== System Configuration Information ===== ===== System Configuration Information =====
Line 125: Line 149:
  
 Finally, if there has been any changes made to the system configurations-- i.e. adding an additional hard disk or swapping out a NIC for a newer NIC, be sure to update the system configuration information! Also if the port version of the Bacula client has changed, to copy again the static-bacula-fd and it's libraries to the off-site location. Finally, if there has been any changes made to the system configurations-- i.e. adding an additional hard disk or swapping out a NIC for a newer NIC, be sure to update the system configuration information! Also if the port version of the Bacula client has changed, to copy again the static-bacula-fd and it's libraries to the off-site location.
 +
 + --- //​[[dougs@dawnsign.com|Doug Sampson]] 2009/03/10 13:44//
  
freebsd_disaster_preparedness_planning.1236707000.txt.gz ยท Last modified: 2009/03/10 17:43 by dsampson