+ - VSS. Shall I write "Include Writer 'WMI Writer", "MSDEWriter"
+ Let me explain this: An windows application can (no must)
+ register as VSS writer. This means that the applications opts to
+ be notified if a backup (or restore) occurs. If it then gets
+ this message, it will immediately store a consistent state to
+ disk. Examples for these writers are "MSDE" (Microsoft database
+ engine), "Event Log Writer", "Registry Writer" plus 3rd
+ party-writers. If you have a non-vss aware application (e.g.
+ SQL Anywhere or probably MySQL), a shadow copy is still generated
+ and the open files can be backed up, but there is no guarantee
+ that the file is consistent.
+
+ At least the Microsoft example makes a significant effort to
+ determine which writers may be involved when a drive or file is
+ to be shadow copied. Of course, every single writer may fail....
+ So they offer a user interface to explicitly include or exclude a
+ writer when creating a VSS shadow copy. I personally would not
+ like to bother the user with this - at least not right now
+ (efforts for exchanging lists between fd and director + efforts
+ for selecting, etc.).
+
+ But I personally would like to have an information message about
+ the individual writers involved in the backup-process ("vssadmin
+ list writers" produced 4 entries on my xp-client and 7 on my w2k3
+ server, please try this on your machine to understand the system
+ a little bit better).
+
+ - Multiple drive autochanger support
+ - Support for ANSI/IBM labels.
+ - Seven new options keywords in a FileSet resource:
+ ignorecase, fstype, hfsplussupport, wilddir, wildfile, regexdir,
+ and regexfile thanks to Pruben Guldberg). See below for details.
+ - Restore of all files for a Job or set of jobs even if the file
+ records have been removed from the catalog.
+ - Restore of a directory (non-recursive, i.e. only one level).
+ - Support for TLS (ssl) between all the daemon connections thanks
+ to Landon Fuller.
+ - Any Volume in the Pool named Scratch may be reassigned to any
+ other Pool when a new Volume is needed.
+ - Unicode filename support for Win32 (thanks to Thorsten Engel)
+ - Volume Shadow Copy support for Win32 thus the capability to
+ backup exclusively opened files (thanks to Thorsten Engel).
+ A VSS enabled Win32 FD is available. You must explicitly
+ turn on VSS with "Enable VSS = yes" in your FileSet resource.
+ - SQLite3 support, but it seems to run at 1/2 to 1/4 the speed of
+ SQLite2.
+ - 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:
+ - 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.
+
+ - "python restart" restarts the Python interpreter. Rather brutal, make
+ sure no Python scripts are running. This permits you to change
+ a Python script and ge
+ - With Python 2.3, there are a few compiler warnings.
+ - You must add --with-openssl to the configure command line if
+ you want TLS communications encryption support.
projects / bacula / bacula / blobdiff