- Release Notes for Bacula 1.34.3
-
- Bacula code: Total files = 364 Total lines = 102,925 (*.h *.c *.in)
-
-Changes for 1.34.3:
-Major Features:
-- Implemented and documented the first cut of the new FileSet directives.
- The first cut permits using wild-card matches for including files in
- addition to excluding files.
-- The Windows rescue procedure is confirmed for WinXP/2K (probably not NT).
-- Modification of the PostgreSQL database creation scripts to improve
- performance by removing foreign keys.
-- Use trasactions on PostgreSQL to improve performance.
-- Restore jobs will now not start until they can get exclusive use
- of the Storage daemon Device previously they erred.
-- Permit execution of more kinds of Win32 files with ClientRunxxxJob.
- If an absolute path is specified, the filename must contain the correct
- extention.
-
-Items to note!!!!
-- If you are upgrading from 1.32, please be sure to see the database
- upgrade procedure under the 1.34.0 notes.
-- Although the daemons are compatible for all 1.34.2 features,
- the new FileSet directives are not compatible with 1.34.2 daemons.
-- Fixed several query.sql bugs.
-- The behavior of the hourly, daily, weekly, and monthly keywords in
- the Run directive have been changed to be more logical -- they only
- affect the one item mentioned rather than all items.
-
-Other items:
-- The wx-console has had significant improvements.
-- Upgraded to latest autoconf files.
-- Added BaculaRoadmap_v1.1.pdf in doc directory
-- Fixed a crash in the btape "fill" command.
-- Added a new alpha directory to platforms -- first cut.
-- The mtx-changer script was broken in 1.34.2 -- it is now fixed.
-- Pass all arguments on database creation scripts.
-- I finally found and fixed the bug that in some cases required a double
- mount to get Bacula to look at the tape again.
-- Thanks to user input corrected (I think) the negative values that
- sometimes occurred in the spooling statistics.
-- Fixed several bsmpt bugs thanks to user input.
-- Added user supplied code to read the Directors's conf file in dbcheck so
- that remote databases could be contacted as well as the working directory
- and other catalog parameters obtained.
-- Fixed changing a Volume from one Pool to another in "update volumes".
-
-
+ Release Notes for Bacula 1.37.12
+
+ Bacula code: Total files = 419 Total lines = 124,877 (*.h *.c *.in)
+
+Note! The DB has been upgraded from version 8 to 9 and requres
+a DB upgrade.
+
+Major Changes:
+- The Python interface has been updated to be object oriented.
+- This version has a new DIR <--> SD protocol. Both must be
+ upgraded at the same time.
+- 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 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:
+ - 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.