# Config file for Backups Blow by Brandon Low # Supplemental binary path # PATH=/usr/local/bin # Configure replacement binary names for programs # PROGRAM_tar=/usr/local/bin/gtar # The log4perl configuration file # LOGCONF=/etc/backupsblow/backupsblow.log4perl # The path to which backups are saved. This path is used as a unix style path # for local, SSH or FTP backups and as a bucket name for s3 backups and must # exist prior to the first running of Backups Blow BACKUP_DIR=/backups/ # Comma separated list of directories to backup. If your directory names have # commas in them, too bad. Use fully qualified directories or bad might # happen. DIRS=/home,/etc,/var # Comma separated list of excludes. If your excludes have commas in them, too # bad. These are used in 'tar --exclude' so use the same pattern rules that # tar expects. It is reasonable to include the Backups Blow data directory # here. EXCLUDES=.ccache,/var/lib/backupsblow,/var/tmp,/tmp # This is where to store the incremental tar data DATA=/var/lib/backupsblow # Compression options # Compression program to use, must default to pipe-in,pipe-out operation # Defaults to gzip COMPRESSION_PROGRAM=bzip2 # Suffix for compressed files, defaults to gz to match the gzip default COMPRESSION_SUFFIX=bz2 # What day to do a full backup on, all other days of the week will be # incremental to this. This must match the day name in the unix date command's # %a format. FULL_BACKUP_DAY=Sat # Set to true to remove old backups RM_OLD=true # How many sets of old backups to keep (default=1) A set is defined as a full # backup and all of the incrementals after it before the next full backup BACKUP_SETS=1 # Comma separated list of mount points to eject -t before and eject after a # backup is performed # EJECTS=/dev/tape,/dev/cdrom # Comma separated list of mount points to mount before and unmount after a # backup is performed these might be a filesystem you want to include in the # backup or a device that you want to backup to. # MOUNTS=/boot,/mnt/tape,/mnt/cdrom # What transport to backup over # Valid options are: local, s3, ssh or ftp TRANSPORT=local # The host to save the backup to (ssh or ftp only) HOSTNAME=someserver # The username on the remote machine (s3, ssh or ftp only) USERNAME=someuser # The password on the remote machine (s3 or ftp only) PASSWORD=somepass # S3 specific options # How large should each S3 object be, in bytes? Defaults to 100000000. S3_OBJECT_SIZE=100000000 # How many digits should be used to identify each S3 object in a backup? # Defaults to 5 digits, allowing 10^12 total bytes with a 10^7 object size. S3_OBJECT_SUFFIX_DIGITS=5 # How many tries should we give each S3 operation? Defaults to 3 S3_TRIES=3 # Do we want to backup some mysql databases as well? SQL=true # The MYSQL host to backup from. SQLHOST=localhost # The MYSQL username. This should be a user with _read only_ permission to all # databases. SQLUSER=someuser # The MYSQL password SQLPASS=somepass # This is the file to which the sql will be written. If you do not include # the COMPRESSION_SUFFIX in this name, it will be added as the file is # compressed. In most cases, this file should be in a subdirectory of one of # the directories specified in DIRS above (if not, the sql backup will never # end up in the final backup location). SQLFILE=/var/lib/mysql/backup.sql
"Sell not virtue to purchase wealth, nor liberty to purchase power." --Fortune Cookie