You're right - it is v14.1. The first trac ticket was created in August 2016, so it's been running for a little while (and it is still running fine - it's just that I'd like to update it, and that's proving difficult).
It appears that TKLBAM isn't backing up the directories - there isn't a /TKLBAM/var directory.
I've enclosed a listing of the /TKLBAM test restore directory, the some of the config files, and the backup output below, (which is quite long, but hopefully has enough detail to be helpful).
root@trac-01 /TKLBAM# ls
backup-conf etc fsdelta fsdelta-olist newpkgs
root@trac-01 /TKLBAM#
Config Files
/etc/tklbam/conf
###############################
# TKLBAM BACKUP CONFIGURATION #
###############################
# volsize: size of backup volumes in MBs
volsize 25
# s3-parallel-uploads: Amazon S3 supports multipart uploads. This
# allows different chunks of a volume to be uploaded in parallel
# which may increase upload speed.
#
# The minimum chunk size is 5MB so the maximum s3-parallel-uploads value
# equals volsize / 5
s3-parallel-uploads 1
# full-backup: time frequency of full backup
# (in between full backups we do incremental backups)
#
# format := <int>[mhDWM]
#
# e.g.,
# 60m - 60 minutes
# 12h - 12 hours
# 3D - three days
# 2W - two weeks
# 1M - one month
full-backup 1M
# Skip backup components?
backup-skip-files False
backup-skip-packages False
backup-skip-database False
# restore-cache-size: the maximum size of the download cache in restore-cache-path
#
# This will come in handy when:
# 1) resuming big restores (already downloaded backup archives don't need to be re-downloaded)
# 2) if you make a mistake and need to rollback the restore and try again
#
# e.g.,
# 1000MB
# 2GB
# 50% - 50% of free space in the restore-cache-path
restore-cache-size 50%
restore-cache-dir /var/cache/tklbam/restore
/etc/tklbam/overides
###########################
# TKLBAM BACKUP OVERRIDES #
###########################
#
# FILESYSTEM OVERRIDES
#
# Override default configurations in /var/lib/tklbam/profile/dirindex.conf
#
# This includes or excludes additional files and directories from being
# backed up if they've changed since installation.
#
# Format
#
# -?/path/to/include/or/exclude
#
# Gotchas
#
# * If you add a directory handled by package management this may break
# package management on the system you restore to.
#
# * Only changes (e.g., new files, edited files, deleted files) from the
# base installation are included in a backup.
#
# Examples
#
# (exclude log files in /var/www)
# -/var/www/*/logs
#
# (ignores changes to webmin configuration)
# -/etc/webmin
#
# (include the contents of an external hard disk...)
# /mnt/images
# DATABASE OVERRIDES
#
# By default ALL databases are backed up. Adding a positive override
# changes the default behavior so that only the database or table
# specified in the override is included in the backup.
#
# You can mix positive overrides with negative overrides.
#
# Format
#
# -?mysql:database[/table]
#
# Examples
#
# (exclude Drupal6 sessions table)
# -mysql:drupal6/sessions
#
# (only include drupal6 database)
# mysql:drupal6
/var/lib/tklbam/profile/dirindex.conf
## This is the base profile which all app-specific profiles inherit from
## See README.rst for details
# data
/opt
/srv
/home
/root
-/root/.cache # duplicity caches by default here
# system minus instance-specific stuff
/usr/local
/etc
-/etc/grub.d
-/etc/debian_version
-/etc/turnkey_version
-/etc/ld.so.cache
-/etc/apt
-/etc/resolv.conf
-/etc/resolvconf
-/etc/network/interfaces
-/etc/passwd*
-/etc/group*
-/etc/hostname
-/etc/fstab
-/etc/mtab
-/etc/udev/rules.d
-/etc/ssh/ssh_host_*
-/etc/mysql/debian.cnf
-/etc/webmin/system-status/history
# ec2 blacklist
-/etc/event.d/console
-/usr/local/bin/ec2metadata
-/usr/local/lib/python2.6/dist-packages/ec2metadata.py*
# vmdk blacklist
-/etc/kernel-img.conf
# /var whitelist
/var/run
-/var/run/*.pid
-/var/run/*/*.pid
/var/www
/var/lib/shellinabox # in case you reconfigure the certificate
/var/spool
-/var/spool/postfix/lib
-/var/spool/postfix/private
-/var/spool/postfix/public
-/var/spool/postfix/pid
-/var/spool/postfix/dev
-/var/spool/tklbam-squid
# trac
/var/local/lib/trac
Jeremy,
Jeremy,
You're right - it is v14.1. The first trac ticket was created in August 2016, so it's been running for a little while (and it is still running fine - it's just that I'd like to update it, and that's proving difficult).
It appears that TKLBAM isn't backing up the directories - there isn't a /TKLBAM/var directory.
I've enclosed a listing of the /TKLBAM test restore directory, the some of the config files, and the backup output below, (which is quite long, but hopefully has enough detail to be helpful).
Thank you for your time helping with this.
Version
TKLBAM Simulate Directory Listing
Config Files
/etc/tklbam/conf
/etc/tklbam/overides
/var/lib/tklbam/profile/dirindex.conf
Backup output