- Release Notes for Bacula 1.32
-
- Bacula code: Total files = 259 Total lines = 77,702 (*.h *.c *.in)
-
-Major Changes this Release:
-- Implemented forward space file/block whenever possible
- during restore. Restoring a small number of files is now
- much faster.
-- There is a new option to restore that allows you
- to restore files based on their Filename. You can
- also specify a file to read which contains the list.
-- Added ClientRunBeforeJob and ClientRunAfterJob.
-- Implemented Include | and < in File daemon.
-- Automatic labeling of tape Volumes should work now.
-- Recycling has been completely restructured and should work.
-- Implemented full length time interval qualifiers (e.g
- "5n is now "5 min" or "5 minutes". A modifier is now required!
-- Fixed gnome-console to compile with RH9 (Gnome 2.0)
-- Implemented "list nextvol job=xxx", which displays the
- next volume to be used by job xxx. The Volume name to
- be used is also added to the "status dir" output.
-- Lots of fixes with variable expansion and counter variables
-- Implemented a new Include/Exclude syntax.
-
-
-Other Changes this Release:
-- A warning message is sent when a job starts that will be
- blocked because the user did an "unmount".
-- Block checksum errors if any are printed in the job report.
-- Implemented a single routine to read_records. It also returns
- a different record packet for each session. This means
- that multiple simultaneous jobs should work.
-- Added SDConnectTimeout to FD.
-- Lots of doc enhancements
-- Fixed a PurgeOldestVolume bug (VolStatus not returned)
-- Don't crash if DB address record not specified.
-- Return VolStatus on find_next_volume.
-- Use alist for incexe name_list.
-- Use bget_dirmsg() everywhere possible when talking to FD.
-- Delete old semaphore job and workq job scheduling code.
-- edit_run_codes in one place (/lib) Add Job name
-- Update query.sql to find current backups correctly.
-- Correct ambiguous SQL statement for pruning.
-- Set heartbeat interval to zero by default.
-- Fix a possible race condition in stopping the
- heartbeat thread.
-- Eliminate gnome2-console directory. Everything is in gnome-console
-- Enhanced "packet too big" message to indicate who sent it.
-- Corrected console prompt problem in non-readline versions.
-- Correct a number of variable expansion problems.
-- Added a number of new regression tests.
-- In an attempt to make configuration a bit less confusing, I've changed
- the name of a number of variables. The old ones still work, but will
- be phased out over time. FDAddress, FDPassword, SDAddress SDPassword,
- SDDeviceName, and DBPassword.
-- A possible fix to the very intermittent SD crashes that Alex gets.
-
-
-
-Items to note: !!!!!
-- Modifiers (sec, min, hour, day, ...) are now required on conf file
- time interval specifications.
-- Duplicate names within the same conf resource are prohibited.
-- If you have used a prior BETA version of 1.32, please do
- the following to cleanup any zero length spool files:
-
- cd <working-directory-as-in-Bacula-conf>
- rm -f *.spool.*
-
- Please be sure there are no spaces between the asterisks
- and the periods.
+ Release Notes for Bacula 1.37.3
+
+ Bacula code: Total files = 411 Total lines = 122,189 (*.h *.c *.in)
+
+
+Major Changes:
+- This version has a new database format that is not compatible
+ with previous databases. The upgrade scripts should work, but
+ they are not yet tested.
+- SQLite3 support, but it seems to run at 1/2 to 1/4 the speed of
+ SQLite2.
+- First cut at ANSI labels.
+- New communications protocol between DIR and SD to reserve
+ drives. The DIR and SD are no longer compatible with 1.36 or
+ lower versions.
+- Preliminary Python Event support has been added. See below for
+ configuration and details.
+- DVD writing support, using parts, and a lot of new directives in
+ the Device resource of the Storage configuration file.
+- Seven new options keywords in a FileSet resource:
+ ignorecase, fstype, hfsplussupport, wilddir, wildfile, regexdir,
+ and regexfile. See below for details.
+
+New Directives:
+- New Options keywords in a FileSet directive:
+ - 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.
+ IBM is not yet implemented.
+- 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.
+
+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.
+
+Items to note!!!
+- You must add --with-python=[DIR] to the configure command line
+ if you want Python support. Python 2.2 and 2.3 should be automatically
+ detected if in the standard place.
+- With Python 2.2 version, the link of the Director gets a few linker
+ warnings due to the fact that Python pulls in some old non-secure
+ libraries.
+- With Python 2.3, there are a few compiler warnings.
+- You must either create a new catalog database or upgrade your
+ old database (upgrade scripts not yet tested).
+
+Other Items:
+- 2 new scripts, dvd-writepart and dvd-freespace, in the scripts directory,
+ which are 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/).
+- Part files support: File volumes can now be splitted in multiple
+ files, called "parts".
+- Python scripting support:
+ A Python script will be called at particular points or conditions
+ in Bacula called Events. The currently defined Events are called:
+
+ StartJob, EndJob, NewVolume
+
+ Where StartJob is called before the RunBeforeJob, EndJob is called
+ after RunAfterJob, and NewVolume, is called before all other
+ "methods" of obtaining a new Volume name, when one is needed.
+
+ The Python script of the same name as the Event name (but with a .py)
+ is called from the Scripts Directory (a directive defined in the
+ Director resource). Note, both the Filename, and the name of
+ the function in the file must correspond to the Event name.
+
+ Once the Python script gets control, it can have access to Bacula
+ variables by doing:
+
+ import bacula
+
+ The script is called with one argument, typically called j. This
+ argument *must* be passed unchanged to each bacula function. The
+ format of the call is slightly different for reading Bacula
+ variable and for writing bacula variables. See below.
+
+ Bacula variables can be read with:
+
+ bacula.get(j, "Variable-name")
+
+ where j is the argument passed to the function, and Variable-name
+ is on of the following:
+
+ JobId, Client, Pool, Storage, Catalog, MediaType, NumVols, DirName,
+ Level, Type, Job, JobName, JobStatus
+
+ Bacula varibles can be set using Python keyword arguments:
+
+ bacula.set(jcr=j, VolumeName="xyz")
+
+ The two currently implemented writable "variables" are:
+
+ VolumeName and JobReport
+
+ It is possible to submit a Bacula run command with the following:
+
+ bacula.run(j, "run kernsave client=Matou storage=File")
+
+ this function returns the JobId of the job that was started. If
+ there is an error, the return value is zero.
+
+ Example:
+
+== File EndJob.py ===
+import bacula
+
+def EndJob(j):
+ jobid = bacula.get(j, "JobId")
+ client = bacula.get(j, "Client")
+ bacula.set(jcr=j, JobReport="EndJob output: JobId=%d Client=%s.\n" % (jobid, client))
+ if (jobid < 5) :
+ startid = bacula.run(j, "run kernsave")
+ print "Python started jobid=", startid
+
+ return 1
+====
+
+== File NewVolume.py ===
+import bacula
+
+def NewVolume(j):
+ jobid = bacula.get(j, "JobId")
+ print "JobId=", jobid
+ client = bacula.get(j, "Client")
+ print "Client=" + client
+ numvol = bacula.get(j, "NumVols");
+ print "NumVols=", numvol
+ bacula.set(jcr=j, JobReport="New Volume set for Job.\n")
+ bacula.set(jcr=j, VolumeName="TestA-001")
+ return 1
+====
+
+