-New Directives:
-- New Job directive 'Prefer Mounted Volumes = yes|no' causes the
- SD to select either an Autochanger or a drive with a valid
- Volume already mounted in preference. If none is available,
- it will select the first available drive.
-- New Run directive in Job resource of DIR. It permits
- cloning of jobs. To clone a copy of the current job, use
- Run = 'job-name level=%l since=\'%s\''
- Note, job-name is normally the same name as the job that
- is running but there is no restriction on what you put. If you
- want to start the job by hand and use job overrides such as
- storage=xxx, realize that the job will be started with the
- default storage values not the overrides. The level=%l guarantees
- that the chosen level of the job is the same, and the since=...
- ensures that the job uses *exactly* the same time/date for incremental
- and differential jobs. The since=... is ignored when level=Full.
- A cloned job will not start additional clones, so it is not possible
- to recurse.
-- New Options keywords in a FileSet directive (backported to 1.36.3):
- - WildDir xxx
- Will do a wild card match against directories (files will not
- be matched).
- - WildFile xxx
- Will do a wild card match against files (directories will not
- be matched).
- - RegexDir xxx
- Will do a regular expression match against directories (files
- will not be matched).
- - RegexFile xxx
- Will do a regular expression match against files( directories
- will not be matched).
- - IgnoreCase = yes | no
- Will ignore case in wild card and regular expression matches.
- This is handy for Windows where filename case is not significant.
- - FsType = string
- where string is a filesystem type: ext2, jfs, ntfs, proc,
- reiserfs, xfs, usbdevfs, sysfs, smbfs, iso9660. For ext3
- systems, use ext2. You may have multiple fstype directives
- and thus permit multiple filesystem types. If the type
- specified on the fstype directive does not match the
- filesystem for a particular directive, that directory will
- not be backed up. This directive can be used to prevent
- backing up non-local filesystems.
- - HFS Plus Support = yes | no
- If set, Mac OS X resource forks will be saved and restored.
-- Label Type = ANSI | IBM | Bacula
- Implemented in Director Pool resource and in SD Device resource.
- If it is specified in the SD Device resource, it will take
- precedence over the value passed from the Director to the SD.
-- Check Labels = yes | no
- Implemented in the SD Device resource. If you intend to read
- ANSI or IBM labels, this *must* be set. Even if the volume
- is not ANSI labeled, you can set this to yes, and Bacula will
- check the label type.
-- Scripts Directory = <directory> name. Defines the directory from
- which Bacula scripts will be called for events. In fact, Bacula
- appends this name to the standard Python list of search directories,
- so the script could also be in any of the Python system directories.
-- In FileSet, you can exclude backing up of hardlinks (if you have
- a lot, it can be very expensive), by using:
- HardLinks = no
- in the Options section. Patch supplied by David R Bosso. Thanks.
-- MaximumPartSize = bytes (SD, Device resource)
- Defines the maximum part size.
-- Requires Mount = Yes/No (SD, Device resource)
- Defines if the device require to be mounted to be read, and if it
- must be written in a special way. If it set, the following directives
- must be defined in the same Device resource:
- + Mount Point = directory
- Directory where the device must be mounted.
- + Mount Command = name-string
- Command that must be executed to mount the device. Before the command
- is executed, %a is replaced with the Archive Device, and %m with the
- Mount Point.
- + Unmount Command = name-string
- Command that must be executed to unmount the device. Before the
- command is executed, %a is replaced with the Archive Device, and
- %m with the Mount Point.
- + Write Part Command = name-string
- Command that must be executed to write a part to the device. Before
- the command is executed, %a is replaced with the Archive Device, %m
- with the Mount Point, %n with the current part number (0-based),
- and %v with the current part filename.
- + Free Space Command = name-string
- Command that must be executed to check how much free space is left
- on the device. Before the command is executed, %a is replaced with
- the Archive Device, %m with the Mount Point, %n with the current part
- number (0-based), and %v with the current part filename.
-- Write Part After Job = Yes/No (DIR, Job Resource, and Schedule Resource)
- If this directive is set to yes (default no), a new part file will be
- created after the job is finished.
-- A pile of new Directives to support TLS. Please see the TLS chapter
- of the manual.
-
-New Commands:
-- 'python restart' restarts the Python interpreter. Rather brutal, make
- sure no Python scripts are running. This permits you to change
- a Python script and get Bacula to use the new script.
-
-New configure options:
-- --with-libintl-prefix for defining alternate locations for
- the NLS internationalization libraries. Not normally required.
-- --datadir for defining where the language files will be installed
- required only if you do not want the default /usr/share.
-
-Items to note!!!
-- The Storage daemon now keeps track of what tapes it is using
- (was not the case in 1.36.x). This means that you must be much
- more careful when removing tapes and putting up a new one. In
- general, you should always do a 'unmount' prior to removing a
- tape, and a 'mount' after putting a new one into the drive.
-- If you use an Autochanger, you MUST update your SD conf file
- to use the new Autochanger resource. Otherwise, certain commands
- such as 'update slots' may not work.
-- You must add --with-python=[DIR] to the configure command line
- if you want Python support. Python 2.2, 2.3 and 2.4 should be
- automatically detected if in the standard place.
-- When linking with --with-python, there are a few warnings that
- can be ignored.
-- You must either create a new catalog database or upgrade your
- old database. After installation, run from your scripts
- directory:
-
- ./upgrade_bacula_tables
-
- You can also find this script in the <bacula-source>/src/cats
- directory.
-- The Director, Storage daemon, and File daemons are
- Deamons are not compatible with prior versions.
- All FDs must be upgraded at the same time.
-- You must add --with-openssl to the configure command line if
- you want TLS communications encryption support.
-- Disk seeking during restores does not yet work correctly in
- all cases, so it is turned off.
-- Note, with gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) on an
- AMD64 CPU running 64 bit CentOS4, there is a compiler bug that
- generates bad code that causes Bacula to segment fault.
- Typically you will see this in the Storage daemon first. The
- solution is to compile Bacula ensuring that no optimization is
- turned on (normally it is -O2).
- This same compiler bug has been reported and confirmed with
- gcc (GCC) 4.0.2 20050901 (prerelease) (SUSE Linux) running on
- an AMD64 CPU. This for the moment, I would recommend that all
- users of GCC 4.0.1 or greater turn off all optimization when
- compiling.
-
-
-Other Items Fixed:
-- Security fixes for temp files created in mtx-changer, during
- ./configure, and during making of Rescue disk.
-- A new script, dvd-handler, in the scripts directory,
- which is designed to be used as parameters to Write Part Command and
- Free Space Command. They need the dvd+rw-tools to be installed
- (http://fy.chalmers.se/~appro/linux/DVD+RW/) AND, the growisofs
- program must be patched using the
- <bacula-source>/patches/dvd+rw-tools-5.21.4.10.8.bacula.patch
- You must have Python installed to run the scripts.
-- Part files support: File volumes can now be split into multiple
- files, called 'parts'.
-- For the details of the Python scripting support, please see the new
- Python Scripting chapter in the manual.
-- The default user/group for the Director and Storage daemon installed
- by rpms is bacula/bacula, thus you may need to add additional permissions
- to your database, or modify the permissions of the tape drive. If
- all else fails, change to using user=root. However, it is more secure
- to use user=bacula.