BaculaFS 0.1.7

Bacula Filesystem in USErspace<br /><br />BaculaFS is a filesystem that exposes the Bacula catalog and storage as a Filesystem in USErspace (FUSE).<br /><br />BaculaFS is a tool, independent of Bacula, that represents the Bacula catalog and backup storage media as a read-only filesystem in userspace.<br /><br />BaculaFS is specifically designed to cater for the following use-cases:<br /><br />* maintaining a remote snapshot of the files in the backup storage using rsync<br />* auditing the contents of backup jobs, without resorting to SQL queries<br />* comparing backup jobs (using several mount points)<br /><br />INSTALLATION:<br /><br />Extract the source code archive to a temporary directory, cd to this directory and run<br /><br />python setup.py install<br /><br />USAGE:<br /><br />baculafs [mountpoint] [options]<br /><br />Options:<br /> --version show program's version number and exit<br /> -h, --help show this help message and exit<br /> -o opt,[opt...] mount options<br /> -o driver=mysql|postgresql|sqlite|sqlite3<br /> database driver [default: sqlite3]<br /> -o host=HOST database server address [default: localhost]<br /> -o port=PORT database server port<br /> -o database=PATH database name [default: bacula]<br /> -o username=USERNAME database user name [default: bacula]<br /> -o password=PASSWORD database password<br /> -o conf=PATH storage daemon configuration file [default:<br /> /etc/bacula/bacula-sd.conf]<br /> -o client=CLIENT file daemon name<br /> -o fileset=FILESET backup fileset<br /> -o device=DEVICE storage device name [default: FileStorage]<br /> -o datetime='YYYY-MM-DD hh:mm:ss'<br /> snapshot date/time [default: now]<br /> -o recent_job select contents of most recent job only [default:<br /> False]<br /> -o joblist='JOBID1 JOBID2 ...'<br /> select contents of specified list of jobs<br /> -o cleanup clean cache directory upon umount [default: False]<br /> -o move_root make absolute path symlinks point to path under<br /> mount point [default: False]<br /> -o prefetch_attrs read and parse attributes for all files upon<br /> filesystem initialization [default: False]<br /> -o prefetch_symlinks extract all symbolic links upon filesystem<br /> initialization (implies prefetch_attrs) [default:<br /> False]<br /> -o prefetch_regex=REGEX<br /> extract all objects that match REGEX upon<br /> filesystem initialization (implies prefetch_attrs)<br /> -o prefetch_recent extract contents of most recent non-full job upon<br /> filesystem initialization (implies<br /> prefetch_symlinks) [default: False]<br /> -o prefetch_diff=PATH extract files that do not match files at PATH<br /> (hint: speeds up rsync; implies prefetch_symlinks)<br /> -o prefetch_everything<br /> extract everything upon filesystem initialization<br /> (complete restore to cache) [default: False]<br /> -o user_cache_path=PATH<br /> user specified cache path (hint: combine this with<br /> one of the prefetch options) [default: none]<br /> -o logging=debug|info|warning|critical|error<br /> logging level [default: warning]<br /> -o syslog log to both syslog and console [default: False]<br /><br />FUSE options:<br /> -d -o debug enable debug output (implies -f)<br /> -f foreground operation<br /> -s disable multi-threaded operation<br /><br /> -o allow_other allow access to other users<br /> -o allow_root allow access to root<br /> -o nonempty allow mounts over non-empty file/dir<br /> -o default_permissions enable permission checking by kernel<br /> -o fsname=NAME set filesystem name<br /> -o subtype=NAME set filesystem type<br /> -o large_read issue large read requests (2.4 only)<br /> -o max_read=N set maximum size of read requests<br /><br /> -o hard_remove immediate removal (don't hide files)<br /> -o use_ino let filesystem set inode numbers<br /> -o readdir_ino try to fill in d_ino in readdir<br /> -o direct_io use direct I/O<br /> -o kernel_cache cache files in kernel<br /> -o [no]auto_cache enable caching based on modification times (off)<br /> -o umask=M set file permissions (octal)<br /> -o uid=N set file owner<br /> -o gid=N set file group<br /> -o entry_timeout=T cache timeout for names (1.0s)<br /> -o negative_timeout=T cache timeout for deleted names (0.0s)<br /> -o attr_timeout=T cache timeout for attributes (1.0s)<br /> -o ac_attr_timeout=T auto cache timeout for attributes (attr_timeout)<br /> -o intr allow requests to be interrupted<br /> -o intr_signal=NUM signal to send on interrupt (10)<br /> -o modules=M1[:M2...] names of modules to push onto filesystem stack<br /><br /> -o max_write=N set maximum size of write requests<br /> -o max_readahead=N set maximum readahead<br /> -o async_read perform reads asynchronously (default)<br /> -o sync_read perform reads synchronously<br /> -o atomic_o_trunc enable atomic open+truncate support<br /> -o big_writes enable larger than 4kB writes<br /> -o no_remote_lock disable remote file locking<br /><br />Module options:<br /><br />[subdir]<br /> -o subdir=DIR prepend this directory to all paths (mandatory)<br /> -o [no]rellinks transform absolute symlinks to relative<br /><br />[iconv]<br /> -o from_code=CHARSET original encoding of file names (default: UTF-8)<br /> -o to_code=CHARSET new encoding of the file names (default: UTF-8)<br /><br />OPERATION<br /><br />INITIALIZATION<br /><br />BaculaFS starts by running several SQL queries against the Bacula catalog. This is done to determine the list of files that belong to the most recent backup for a given client and fileset.<br /><br />BaculaFS can also be told to represent a backup snapshot corresponding to a specified date and time, or a list of backup job ids.<br /><br />Following this, BaculaFS may run bextract once to prefetch and cache symbolic links and actual file contents, depending on user specified command line options.<br /><br />At this point the filesystem is ready.<br /><br />CACHE<br /><br />Opening a file for reading causes BaculaFS to run bextract in order to extract the file from the storage device. If this operation succeeds, the file is cached for subsequent read operations.<br /><br />Bacula storage is not designed for random access file retrieval, so it is important to select a suitable cache prefetch strategy beforehand. Running bextract once, during filesystem initialization, to extract several files, is much more efficient than running it several times to extract each individual file, when accessed at a later stage.<br /><br />For example:<br /><br /> * use -o prefetch_attrs for storage space usage analysis (e.g. with Baobab)<br /> * use -o prefetch_symlinks for any manual filesystem traversal with command line or GUI tools (find, mc, etc.)<br /> * use -o prefetch_diff with rsync<br /><br />The cache may be cleaned up automatically upon un-mounting the filesystem, with -o cleanup. It may also be reused between mount operations with -o user_cache_path.<br /><br />EXTENDED ATTRIBUTES<br /><br />BaculaFS uses extended file attributes to expose Bacula specific information for each file in the filesystem. These extended attributes are all grouped in the user.baculafs namespace:<br /><br />user.baculafs.FileIndex<br />user.baculafs.JobId<br />user.baculafs.LStat<br />user.baculafs.MD5<br /><br />The root directory has several more attributes, that expose filesystem instance-specific information:<br /><br />user.baculafs.cache_prefix<br />user.baculafs.client<br />user.baculafs.datetime<br />user.baculafs.fileset<br />user.baculafs.joblist<br /><br />and several more attributes for monitoring the file extraction process:<br /><br />user.baculafs.bextract.failures<br />user.baculafs.bextract.path<br />user.baculafs.bextract.pending<br />user.baculafs.bextract.retries<br />user.baculafs.bextract.state<br />user.baculafs.bextract.volume<br /><br />MISSING VOLUMES<br /><br />If the storage device is a tape drive then it's possible that BaculaFS will attempt to retrieve a file from a volume that's on an unmounted tape. BaculaFS will then set user.baculafs.bextract.state to *user intervention required*, and will wait for user intervention.<br /><br />The user should then mount the tape containing the missing volume and set the state to run, to make BaculaFS retry the operation:<br /><br />attr -s baculafs.bextract.state -V run < mount-point ><br /><br />Please note that this feature has undergone only rudimentary testing. Expect breakage.<br /><br />Limitations:<br /><br />LOCKING:<br /><br />?*A* Access to the storage device by different instances of BaculaFS is serialized by locking the storage daemon configuration file. This means that you can mount several views of the backup catalog (e.g. accessing backup snapshots of different clients or snapshots from the same client but from different dates).<br /><br />There are at least two issues with this locking mechanism that you should note:<br /><br />?*A* * the lock is advisory, meaning that it does not prevent the Bacula storage daemon itself from accessing the storage device while in use by BaculaFS<br />?*A* * depending on your setup, the lock may not work if the storage daemon configuration file is accessed via NFS<br /><br />WINDOWS FILESETS:<br /><br />?*A* BaculaFS can be used with Windows backup filesets, but it does not reproduce any Windows specific file attributes. This is because bextract does not extract Windows specific file attributes on Linux.<br /><br />#md5=50dcca4d11eeaa98fe0382dfd58243db

Requirements:	No special requirements
Platforms:	*nix, Linux
Keyword:	Attributes,  Backup,  Bacula,  Baculafs,  Cache,  Contents,  Database,  Default,  Device,  Directory,  Enable,  Extract,  False,  Files,  Filesystem,  Initialization,  Mount,  Names,  Storage
Users rating:	0/10