advertisement
Chapter 31
Autochanger Support
Bacula provides autochanger support for reading and writing tapes. In order to work with an autochanger,
Bacula requires a number of things, each of which is explained in more detail after this list:
• A script that actually controls the autochanger according to commands sent by Bacula. We furnish such a script that works with mtx found in the depkgs distribution.
• That each Volume (tape) to be used must be defined in the Catalog and have a Slot number assigned to it so that Bacula knows where the Volume is in the autochanger. This is generally done with the label command, but can also done after the tape is labeled using the update slots command. See below for more details. You must pre-label the tapes manually before using them.
• Modifications to your Storage daemon’s Device configuration resource to identify that the device is a changer, as well as a few other parameters.
• You should also modify your Storage resource definition in the Director’s configuration file so that you are automatically prompted for the Slot when labeling a Volume.
• You need to ensure that your Storage daemon (if not running as root) has access permissions to both the tape drive and the control device.
• You need to have Autochanger = yes in your Storage resource in your bacula-dir.conf file so that you will be prompted for the slot number when you label Volumes.
thus creating a multi-drive autochanger. If you have an autochanger, you must use this new resource.
Bacula uses its own mtx-changer script to interface with a program that actually does the tape changing.
Thus in principle, mtx-changer can be adapted to function with any autochanger program, or you can call any other script or program. The current version of mtx-changer works with the mtx program. However,
FreeBSD users have provided a script in the examples/autochangers directory that allows Bacula to use the chio program.
Bacula also supports autochangers with barcode readers. This support includes two Console commands: label barcodes and update slots. For more details on these commands, see the ”Barcode Support” section below.
Current Bacula autochanger support does not include cleaning, stackers, or silos. Stackers and silos are not supported because Bacula expects to be able to access the Slots randomly. However, if you are very careful to setup Bacula to access the Volumes in the autochanger sequentially, you may be able to make Bacula work with stackers (gravity feed and such).
resource is also recommended for single drive autochangers.
267
268 Bacula Version 5.0.3
In principle, if mtx will operate your changer correctly, then it is just a question of adapting the mtxchanger script (or selecting one already adapted) for proper interfacing. You can find a list of autochangers supported by mtx at the following link: http://mtx.opensource-sw.net/compatibility.php. The home page for the mtx project can be found at: http://mtx.opensource-sw.net/.
Note, we have feedback from some users that there are certain incompatibilities between the Linux kernel and mtx. For example between kernel 2.6.18-8.1.8.el5 of CentOS and RedHat and version 1.3.10 and 1.3.11
of mtx. This was fixed by upgrading to a version 2.6.22 kernel.
In addition, apparently certain versions of mtx, for example, version 1.3.11 limit the number of slots to a maximum of 64. The solution was to use version 1.3.10.
If you are having troubles, please use the auto command in the btape program to test the functioning of your autochanger with Bacula. When Bacula is running, please remember that for many distributions (e.g.
FreeBSD, Debian, ...) the Storage daemon runs as bacula.tape rather than root.root, so you will need to ensure that the Storage daemon has sufficient permissions to access the autochanger.
Some users have reported that the the Storage daemon blocks under certain circumstances in trying to mount a volume on a drive that has a different volume loaded. As best we can determine, this is simply a matter of waiting a bit. The drive was previously in use writing a Volume, and sometimes the drive will remain
BLOCKED for a good deal of time (up to 7 minutes on a slow drive) waiting for the cassette to rewind and to unload before the drive can be used with a different Volume.
31.1
Knowing What SCSI Devices You Have
Under Linux, you can cat /proc/scsi/scsi to see what SCSI devices you have available. You can also: cat /proc/scsi/sg/device_hdr /proc/scsi/sg/devices to find out how to specify their control address (/dev/sg0 for the first, /dev/sg1 for the second, ...) on the Changer Device = Bacula directive.
You can also use the excellent lsscsi tool.
$ lsscsi -g
[1:0:2:0] tape SEAGATE ULTRIUM06242-XXX 1619 /dev/st0 /dev/sg9
[1:0:14:0] mediumx STK L180 0315 /dev/sch0 /dev/sg10
[2:0:3:0]
[3:0:0:0]
[3:0:1:0] tape disk
HP enclosu HP
Ultrium 3-SCSI
A6255A
HP 36.4G ST336753FC
G24S
HP04
HP00
/dev/st1
-
/dev/sdd
/dev/sg11
/dev/sg3
/dev/sg4
For more detailed information on what SCSI devices you have please see the Linux SCSI Tricks section of the Tape Testing chapter of this manual.
Under FreeBSD, you can use: camcontrol devlist
To list the SCSI devices as well as the /dev/passn that you will use on the Bacula Changer Device = directive.
Please check that your Storage daemon has permission to access this device.
Bacula Version 5.0.3
269
The following tip for FreeBSD users comes from Danny Butroyd: on reboot Bacula will NOT have permission to control the device /dev/pass0 (assuming this is your changer device). To get around this just edit the
/etc/devfs.conf file and add the following to the bottom: own perm own perm pass0 root:bacula pass0 0666 nsa0.0
root:bacula nsa0.0
0666
This gives the bacula group permission to write to the nsa0.0 device too just to be on the safe side. To bring these changes into effect just run:-
/etc/rc.d/devfs restart
Basically this will stop you having to manually change permissions on these devices to make Bacula work when operating the AutoChanger after a reboot.
31.2
Example Scripts
Please read the sections below so that you understand how autochangers work with Bacula. Although we supply a default mtx-changer script, your autochanger may require some additional changes. If you want to see examples of configuration files and scripts, please look in the <bacula-src>/examples/devices directory where you will find an example HP-autoloader.conf Bacula Device resource, and several mtxchanger scripts that have been modified to work with different autochangers.
31.3
Slots
To properly address autochangers, Bacula must know which Volume is in each slot of the autochanger. Slots are where the changer cartridges reside when not loaded into the drive. Bacula numbers these slots from one to the number of cartridges contained in the autochanger.
Bacula will not automatically use a Volume in your autochanger unless it is labeled and the slot number is stored in the catalog and the Volume is marked as InChanger. This is because it must know where each volume is (slot) to be able to load the volume. For each Volume in your changer, you will, using the Console program, assign a slot. This information is kept in Bacula’s catalog database along with the other data for the volume. If no slot is given, or the slot is set to zero, Bacula will not attempt to use the autochanger even if all the necessary configuration records are present. When doing a mount command on an autochanger, you must specify which slot you want mounted. If the drive is loaded with a tape from another slot, it will unload it and load the correct tape, but normally, no tape will be loaded because an unmount command causes Bacula to unload the tape in the drive.
You can check if the Slot number and InChanger flag are set by doing a: list Volumes in the Console program.
31.4
Multiple Devices
in version 1.37 permits you to group Device resources, where each device represents a drive. The Director may still reference the Devices (drives) directly, but doing so, bypasses the proper functioning of the drives together. Instead, the Director (in the Storage resource) should reference the Autochanger resource name.
270 Bacula Version 5.0.3
Doing so permits the Storage daemon to ensure that only one drive uses the mtx-changer script at a time, and also that two drives don’t reference the same Volume.
Multi-drive requires the use of the Drive Index directive in the Device resource of the Storage daemon’s configuration file. Drive numbers or the Device Index are numbered beginning at zero, which is the default.
To use the second Drive in an autochanger, you need to define a second Device resource and set the Drive
Index to 1 for that device. In general, the second device will have the same Changer Device (control channel) as the first drive, but a different Archive Device.
As a default, Bacula jobs will prefer to write to a Volume that is already mounted. If you have a multiple drive autochanger and you want Bacula to write to more than one Volume in the same Pool at the same
Storage daemon to maximize the use of drives.
31.5
Device Configuration Records
Configuration of autochangers within Bacula is done in the Device resource of the Storage daemon. Four records: Autochanger, Changer Device, Changer Command, and Maximum Changer Wait control how Bacula uses the autochanger.
These four records, permitted in Device resources, are described in detail below. Note, however, that the
Changer Device and the Changer Command directives are not needed in the Device resource if they are present in the Autochanger resource.
Autochanger = Yes—No The Autochanger record specifies that the current device is or is not an autochanger. The default is no.
Changer Device = <device-name> In addition to the Archive Device name, you must specify a
Changer Device name. This is because most autochangers are controlled through a different device than is used for reading and writing the cartridges. For example, on Linux, one normally uses the generic SCSI interface for controlling the autochanger, but the standard SCSI interface for reading and writing the tapes. On Linux, for the Archive Device = /dev/nst0, you would typically have Changer Device = /dev/sg0. Note, some of the more advanced autochangers will locate the changer device on /dev/sg1. Such devices typically have several drives and a large number of tapes.
On FreeBSD systems, the changer device will typically be on /dev/pass0 through /dev/passn.
On Solaris, the changer device will typically be some file under /dev/rdsk.
Please ensure that your Storage daemon has permission to access this device.
Changer Command = <command> This record is used to specify the external program to call and what arguments to pass to it. The command is assumed to be a standard program or shell script that can be executed by the operating system. This command is invoked each time that Bacula wishes to manipulate the autochanger. The following substitutions are made in the command before it is sent to the operating system for execution:
%% = %
%a = archive device name
%c = changer device name
%d = changer drive index base 0
%f = Client’s name
%j = Job name
%o = command (loaded, load, or unload)
%s = Slot base 0
%S = Slot base 1
%v = Volume name
An actual example for using mtx with the mtx-changer script (part of the Bacula distribution) is:
Changer Command = "/etc/bacula/mtx-changer %c %o %S %a %d"
Bacula Version 5.0.3
271
Where you will need to adapt the /etc/bacula to be the actual path on your system where the mtxchanger script resides. Details of the three commands currently used by Bacula (loaded, load, unload) as well as the output expected by Bacula are give in the Bacula Autochanger Interface section below.
Maximum Changer Wait = <time> This record is used to define the maximum amount of time that
Bacula will wait for an autoloader to respond to a command (e.g. load). The default is set to 120 seconds. If you have a slow autoloader you may want to set it longer.
If the autoloader program fails to respond in this time, it will be killed and Bacula will request operator intervention.
Drive Index = <number> This record allows you to tell Bacula to use the second or subsequent drive in an autochanger with multiple drives. Since the drives are numbered from zero, the second drive is defined by
Device Index = 1
To use the second drive, you need a second Device resource definition in the Bacula configuration file.
See the Multiple Drive section above in this chapter for more information.
In addition, for proper functioning of the Autochanger, you must define an Autochanger resource.
272 Bacula Version 5.0.3
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
advertisement
Table of contents
- 18 What is Bacula?
- 18 Who Needs Bacula?
- 18 Bacula Components or Services
- 21 Bacula Configuration
- 21 Conventions Used in this Document
- 22 Quick Start
- 22 Terminology
- 24 What Bacula is Not
- 24 Interactions Between the Bacula Services
- 26 Release Version 5.0.2 and 5.0.3
- 28 New Features in 5.0.1
- 28 Truncate Volume after Purge
- 29 Allow Higher Duplicates
- 29 Cancel Lower Level Duplicates
- 30 New Features in 5.0.0
- 30 Maximum Concurrent Jobs for Devices
- 30 Restore from Multiple Storage Daemons
- 30 File Deduplication using Base Jobs
- 31 AllowCompression = <yes|no>
- 31 Accurate Fileset Options
- 32 Tab-completion for Bconsole
- 32 Pool File and Job retention
- 32 Read-only File Daemon using capabilities
- 33 Bvfs API
- 33 Testing your Tape Drive
- 34 New Block Checksum Device Directive
- 34 New Bat Features
- 34 Media List View
- 34 Media Information View
- 34 Job Information View
- 36 Autochanger Content View
- 37 Bat on Windows
- 37 New Win32 Installer
- 37 Win64 Installer
- 37 Linux Bare Metal Recovery USB Key
- 37 bconsole Timeout Option
- 37 Important Changes
- 38 Custom Catalog queries
- 38 Deprecated parts
- 38 Misc Changes
- 40 Released Version 3.0.3 and 3.0.3a
- 42 New Features in Released Version 3.0.2
- 42 Full Restore from a Given JobId
- 43 Source Address
- 43 Show volume availability when doing restore
- 43 Accurate estimate command
- 46 New Features in 3.0.0
- 46 Accurate Backup
- 46 Accurate = <yes|no>
- 46 Copy Jobs
- 49 ACL Updates
- 50 Extended Attributes
- 51 Shared objects
- 51 Building Static versions of Bacula
- 51 Virtual Backup (Vbackup)
- 53 Catalog Format
- 53 64 bit Windows Client
- 54 Duplicate Job Control
- 54 Allow Duplicate Jobs = <yes|no>
- 54 Allow Higher Duplicates = <yes|no>
- 54 Cancel Running Duplicates = <yes|no>
- 55 Cancel Queued Duplicates = <yes|no>
- 55 TLS Authentication
- 55 TLS Authenticate = yes
- 55 bextract non-portable Win32 data
- 55 State File updated at Job Termination
- 55 MaxFullInterval = <time-interval>
- 56 MaxDiffInterval = <time-interval>
- 56 Honor No Dump Flag = <yes|no>
- 56 Exclude Dir Containing = <filename-string>
- 57 Bacula Plugins
- 57 Plugin Directory
- 57 Plugin Options
- 57 Plugin Options ACL
- 57 Plugin = <plugin-command-string>
- 58 The bpipe Plugin
- 59 Microsoft Exchange Server 2003/2007 Plugin
- 59 Background
- 59 Concepts
- 59 Installing
- 60 Backing Up
- 60 Restoring
- 61 Restoring to the Recovery Storage Group
- 61 Restoring on Microsoft Server 2007
- 61 Caveats
- 62 libdbi Framework
- 63 Console Command Additions and Enhancements
- 63 Display Autochanger Content
- 63 list joblog job=xxx or jobid=nnn
- 63 Use separator for multiple commands
- 63 Deleting Volumes
- 64 Bare Metal Recovery
- 64 Miscellaneous
- 64 Allow Mixed Priority = <yes|no>
- 65 Bootstrap File Directive – FileRegex
- 65 Bootstrap File Optimization Changes
- 65 Solaris ZFS/NFSv4 ACLs
- 65 Virtual Tape Emulation
- 66 Bat Enhancements
- 66 RunScript Enhancements
- 66 Status Enhancements
- 66 Connect Timeout
- 66 ftruncate for NFS Volumes
- 66 Support for Ubuntu
- 67 Recycle Pool = <pool-name>
- 67 FD Version
- 67 Max Run Sched Time = <time-period-in-seconds>
- 67 Max Wait Time = <time-period-in-seconds>
- 67 Incremental|Differential Max Wait Time = <time-period-in-seconds>
- 67 Max Run Time directives
- 67 Statistics Enhancements
- 68 ScratchPool = <pool-resource-name>
- 69 Enhanced Attribute Despooling
- 69 SpoolSize = <size-specification-in-bytes>
- 69 MaximumConsoleConnections = <number>
- 69 VerId = <string>
- 69 dbcheck enhancements
- 69 --docdir configure option
- 70 --htmldir configure option
- 70 --with-plugindir configure option
- 72 The Current State of Bacula
- 72 What is Implemented
- 74 Advantages Over Other Backup Programs
- 74 Current Implementation Restrictions
- 75 Design Limitations or Restrictions
- 75 Items to Note
- 76 System Requirements
- 78 Supported Operating Systems
- 80 Supported Tape Drives
- 81 Unsupported Tape Drives
- 81 FreeBSD Users Be Aware!!!
- 81 Supported Autochangers
- 81 Tape Specifications
- 84 Getting Started with Bacula
- 84 Understanding Jobs and Schedules
- 84 Understanding Pools, Volumes and Labels
- 85 Setting Up Bacula Configuration Files
- 85 Configuring the Console Program
- 86 Configuring the Monitor Program
- 86 Configuring the File daemon
- 87 Configuring the Director
- 87 Configuring the Storage daemon
- 88 Testing your Configuration Files
- 88 Testing Compatibility with Your Tape Drive
- 88 Get Rid of the /lib/tls Directory
- 88 Running Bacula
- 89 Log Rotation
- 89 Log Watch
- 89 Disaster Recovery
- 90 Installing Bacula
- 90 Source Release Files
- 91 Upgrading Bacula
- 92 Releases Numbering
- 93 Dependency Packages
- 94 Supported Operating Systems
- 94 Building Bacula from Source
- 97 What Database to Use?
- 97 Quick Start
- 98 Configure Options
- 103 Recommended Options for Most Systems
- 103 Red Hat
- 104 Solaris
- 105 FreeBSD
- 105 Win32
- 105 One File Configure Script
- 106 Installing Bacula
- 106 Building a File Daemon or Client
- 106 Auto Starting the Daemons
- 107 Other Make Notes
- 108 Installing Tray Monitor
- 108 GNOME
- 109 KDE
- 109 Other window managers
- 109 Modifying the Bacula Configuration Files
- 110 Critical Items to Implement Before Production
- 110 Critical Items
- 111 Recommended Items
- 112 A Brief Tutorial
- 112 Before Running Bacula
- 113 Starting the Database
- 113 Starting the Daemons
- 113 Using the Director to Query and Start Jobs
- 115 Running a Job
- 119 Restoring Your Files
- 121 Quitting the Console Program
- 121 Adding a Second Client
- 122 When The Tape Fills
- 124 Other Useful Console Commands
- 124 Debug Daemon Output
- 125 Patience When Starting Daemons or Mounting Blank Tapes
- 125 Difficulties Connecting from the FD to the SD
- 125 Daemon Command Line Options
- 126 Creating a Pool
- 126 Labeling Your Volumes
- 127 Labeling Volumes with the Console Program
- 130 Customizing the Configuration Files
- 131 Character Sets
- 132 Resource Directive Format
- 132 Comments
- 132 Upper and Lower Case and Spaces
- 132 Including other Configuration Files
- 133 Recognized Primitive Data Types
- 134 Resource Types
- 134 Names, Passwords and Authorization
- 135 Detailed Information for each Daemon
- 136 Configuring the Director
- 136 Director Resource Types
- 137 The Director Resource
- 139 The Job Resource
- 154 The JobDefs Resource
- 154 The Schedule Resource
- 157 Technical Notes on Schedules
- 157 The FileSet Resource
- 168 FileSet Examples
- 173 Backing up Raw Partitions
- 173 Excluding Files and Directories
- 173 Windows FileSets
- 175 Testing Your FileSet
- 176 The Client Resource
- 177 The Storage Resource
- 179 The Pool Resource
- 185 The Scratch Pool
- 185 The Catalog Resource
- 186 The Messages Resource
- 187 The Console Resource
- 188 The Counter Resource
- 189 Example Director Configuration File
- 192 Client/File daemon Configuration
- 192 The Client Resource
- 194 The Director Resource
- 195 The Message Resource
- 195 Example Client Configuration File
- 196 Storage Daemon Configuration
- 196 Storage Resource
- 198 Director Resource
- 198 Device Resource
- 206 Edit Codes for Mount and Unmount Directives
- 206 Devices that require a mount (DVD)
- 208 Autochanger Resource
- 209 Capabilities
- 209 Messages Resource
- 209 Sample Storage Daemon Configuration File
- 212 Messages Resource
- 216 Console Configuration
- 216 General
- 216 The Director Resource
- 217 The ConsoleFont Resource
- 217 The Console Resource
- 219 Console Commands
- 219 Sample Console Configuration File
- 220 Monitor Configuration
- 220 The Monitor Resource
- 220 The Director Resource
- 221 The Client Resource
- 221 The Storage Resource
- 222 Tray Monitor Security
- 222 Sample Tray Monitor configuration
- 223 Sample File daemon's Director record.
- 223 Sample Storage daemon's Director record.
- 223 Sample Director's Console record.
- 224 The Restore Command
- 224 General
- 224 The Restore Command
- 229 Restore a pruned job using a pattern
- 229 Selecting Files by Filename
- 230 Replace Options
- 231 Command Line Arguments
- 232 Using File Relocation
- 232 Introduction
- 232 RegexWhere Format
- 233 Restoring Directory Attributes
- 233 Restoring on Windows
- 234 Restoring Files Can Be Slow
- 234 Problems Restoring Files
- 235 Restore Errors
- 235 Example Restore Job Resource
- 235 File Selection Commands
- 237 Restoring When Things Go Wrong
- 242 Automatic Volume Recycling
- 243 Automatic Pruning
- 243 Pruning Directives
- 245 Recycling Algorithm
- 246 Recycle Status
- 247 Making Bacula Use a Single Tape
- 247 Daily, Weekly, Monthly Tape Usage Example
- 249 Automatic Pruning and Recycling Example
- 250 Manually Recycling Volumes
- 252 Basic Volume Management
- 252 Key Concepts and Resource Records
- 253 Pool Options to Limit the Volume Usage
- 254 Automatic Volume Labeling
- 254 Restricting the Number of Volumes and Recycling
- 255 Concurrent Disk Jobs
- 256 An Example
- 258 Backing up to Multiple Disks
- 259 Considerations for Multiple Clients
- 264 Automated Disk Backup
- 264 The Problem
- 264 The Solution
- 265 Overall Design
- 265 Full Pool
- 266 Differential Pool
- 266 Incremental Pool
- 266 The Actual Conf Files
- 270 Migration and Copy
- 271 Migration and Copy Job Resource Directives
- 273 Migration Pool Resource Directives
- 273 Important Migration Considerations
- 274 Example Migration Jobs
- 276 File Deduplication using Base Jobs
- 278 Backup Strategies
- 278 Simple One Tape Backup
- 278 Advantages
- 278 Disadvantages
- 278 Practical Details
- 279 Manually Changing Tapes
- 279 Daily Tape Rotation
- 279 Advantages
- 280 Disadvantages
- 280 Practical Details
- 284 Autochanger Support
- 285 Knowing What SCSI Devices You Have
- 286 Example Scripts
- 286 Slots
- 286 Multiple Devices
- 287 Device Configuration Records
- 290 Autochanger Resource
- 291 An Example Configuration File
- 291 A Multi-drive Example Configuration File
- 292 Specifying Slots When Labeling
- 293 Changing Cartridges
- 293 Dealing with Multiple Magazines
- 294 Simulating Barcodes in your Autochanger
- 294 The Full Form of the Update Slots Command
- 295 FreeBSD Issues
- 295 Testing Autochanger and Adapting mtx-changer script
- 296 Using the Autochanger
- 297 Barcode Support
- 298 Use bconsole to display Autochanger content
- 298 Bacula Autochanger Interface
- 300 Supported Autochangers
- 304 Data Spooling
- 304 Data Spooling Directives
- 305 !!! MAJOR WARNING !!!
- 305 Other Points
- 306 Using Bacula catalog to grab information
- 306 Job statistics
- 308 ANSI and IBM Tape Labels
- 308 Director Pool Directive
- 308 Storage Daemon Device Directives
- 310 The Windows Version of Bacula
- 310 Win32 Installation
- 314 Post Win32 Installation
- 314 Uninstalling Bacula on Win32
- 314 Dealing with Win32 Problems
- 316 Windows Compatibility Considerations
- 317 Volume Shadow Copy Service
- 318 VSS Problems
- 319 Windows Firewalls
- 319 Windows Port Usage
- 319 Windows Disaster Recovery
- 319 Windows Restore Problems
- 320 Windows Ownership and Permissions Problems
- 320 Manually resetting the Permissions
- 322 Backing Up the WinNT/XP/2K System State
- 323 Considerations for Filename Specifications
- 323 Win32 Specific File daemon Command Line
- 324 Shutting down Windows Systems
- 326 Disaster Recovery Using Bacula
- 326 General
- 326 Important Considerations
- 326 Steps to Take Before Disaster Strikes
- 327 Bare Metal Recovery on Linux with a Rescue CD
- 327 Requirements
- 327 Restoring a Client System
- 328 Boot with your Rescue CDROM
- 330 Restoring a Server
- 331 Linux Problems or Bugs
- 331 Bare Metal Recovery using a LiveCD
- 332 FreeBSD Bare Metal Recovery
- 333 Solaris Bare Metal Recovery
- 333 Preparing Solaris Before a Disaster
- 334 Bugs and Other Considerations
- 334 Disaster Recovery of Win32 Systems
- 334 Ownership and Permissions on Win32 Systems
- 335 Alternate Disaster Recovery Suggestion for Win32 Systems
- 335 Restoring to a Running System
- 336 Additional Resources
- 338 Bacula TLS – Communications Encryption
- 338 TLS Configuration Directives
- 339 Creating a Self-signed Certificate
- 340 Getting a CA Signed Certificate
- 340 Example TLS Configuration Files
- 344 Data Encryption
- 345 Building Bacula with Encryption Support
- 345 Encryption Technical Details
- 345 Decrypting with a Master Key
- 346 Generating Private/Public Encryption Keys
- 346 Example Data Encryption Configuration
- 348 Using Bacula to Improve Computer Security
- 348 The Details
- 349 Running the Verify
- 350 What To Do When Differences Are Found
- 351 A Verify Configuration Example
- 354 Installing and Configuring MySQL
- 354 Installing and Configuring MySQL – Phase I
- 355 Installing and Configuring MySQL – Phase II
- 356 Re-initializing the Catalog Database
- 356 Linking Bacula with MySQL
- 357 Installing MySQL from RPMs
- 357 Upgrading MySQL
- 358 Installing and Configuring PostgreSQL
- 358 Installing PostgreSQL
- 359 Configuring PostgreSQL
- 361 Re-initializing the Catalog Database
- 361 Installing PostgreSQL from RPMs
- 362 Converting from MySQL to PostgreSQL
- 363 Upgrading PostgreSQL
- 364 Tuning PostgreSQL
- 364 Credits
- 366 Installing and Configuring SQLite
- 366 Installing and Configuring SQLite – Phase I
- 367 Installing and Configuring SQLite – Phase II
- 367 Linking Bacula with SQLite
- 367 Testing SQLite
- 368 Re-initializing the Catalog Database
- 370 Catalog Maintenance
- 370 Setting Retention Periods
- 371 Compacting Your MySQL Database
- 372 Repairing Your MySQL Database
- 372 MySQL Table is Full
- 373 MySQL Server Has Gone Away
- 373 MySQL Temporary Tables
- 373 Repairing Your PostgreSQL Database
- 373 Database Performance Issues
- 374 Performance Issues Indexes
- 374 PostgreSQL Indexes
- 374 MySQL Indexes
- 375 SQLite Indexes
- 375 Compacting Your PostgreSQL Database
- 376 Compacting Your SQLite Database
- 376 Migrating from SQLite to MySQL or PostgreSQL
- 376 Backing Up Your Bacula Database
- 377 Security considerations
- 378 Backing Up Third Party Databases
- 378 Database Size
- 380 Bacula Security Issues
- 381 Backward Compatibility
- 381 Configuring and Testing TCP Wrappers
- 383 Running as non-root
- 384 The Bootstrap File
- 384 Bootstrap File Format
- 387 Automatic Generation of Bootstrap Files
- 388 Bootstrap for bscan
- 388 A Final Bootstrap Example
- 390 Bacula Copyright, Trademark, and Licenses
- 390 FDL
- 390 GPL
- 390 LGPL
- 390 Public Domain
- 391 Trademark
- 391 Fiduciary License Agreement
- 391 Disclaimer
- 392 GNU Free Documentation License
- 398 Table of Contents
- 398 GNU GENERAL PUBLIC LICENSE
- 398 Preamble
- 399 TERMS AND CONDITIONS
- 402 How to Apply These Terms to Your New Programs
- 403 Table of Contents
- 403 GNU LESSER GENERAL PUBLIC LICENSE
- 403 Preamble
- 404 TERMS AND CONDITIONS
- 409 How to Apply These Terms to Your New Libraries
- 410 Thanks
- 412 Bacula Bugs