| |
|---|
| | |
|---|
| | The files and/or contents of ``/root``, ``/home``, and ``/usr/home`` |
|---|
| | would be written to a tarball in the backup directory (default: |
|---|
| | ``/bku/``). By default, the resulting tarball's name has a long |
|---|
| | string of text that includes the machine name, system type, OS type, |
|---|
| | date, *and* the so-called *set name*. The "set name" is nothing |
|---|
| | string of text that includes the date, machine name, system type, OS type, |
|---|
| | *and* the so-called *set name*. The "set name" is nothing |
|---|
| | more than the suffix of the name of the fileset used to produce the |
|---|
| | tarball, in this case, ``homedirs``. |
|---|
| | |
|---|
| | Additionally, you'll also find a log of the backup and "dot files" |
|---|
| | that tell you when the backup began and when it ended. Here's part |
|---|
| | of what you might see if you did an ``ls -a /bku``:: |
|---|
| | |
|---|
| | .mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-20080319-begin |
|---|
| | .mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-20080319-end |
|---|
| | mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-20080319.tar.gz |
|---|
| | mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-20080319.log |
|---|
| | .20080319-mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-begin |
|---|
| | .20080319-mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs-end |
|---|
| | 20080319-mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs.tar.gz |
|---|
| | 20080319-mach.fake.org-FreeBSD-6.3-STABLE-i386-homedirs.log |
|---|
| | |
|---|
| | The "dot files" don't actually contain any information, but their |
|---|
| | date/time stamps (you can see this with ``ls -al /bku``) will tell |
|---|
| | you when the backup began and ended. |
|---|
| |
|---|
| | |
|---|
| | **Autodeletion Of Old Backups** |
|---|
| | |
|---|
| | As shipped, ``tbku`` uniquely identifies each backup set based on |
|---|
| | machine name, OS, CPU architecture, set name, and, most importantly, |
|---|
| | date. If you've set it up to run as a cron job, over time you'll |
|---|
| | accumulate lots of older copies of backups. That's because each new |
|---|
| | day, the backup file name will change (since it includes the date). |
|---|
| | machine date, name, OS, CPU architecture, and set name. If you've |
|---|
| | set it up to run as a cron job, over time you'll accumulate lots of |
|---|
| | older copies of backups. That's because each new day, the backup |
|---|
| | file name will change (since it includes the date). |
|---|
| | |
|---|
| | If you don't like this default behavior, change the ``TBKUDEL`` |
|---|
| | environment variable to be "YES". It must be *exactly* this string, |
|---|
| | all in upper case. Anything else will cause ``tbku`` to *not* |
|---|
| |
|---|
| | |
|---|
| | |
|---|
| | **COPYRIGHT & LICENSING** |
|---|
| | |
|---|
| | ``tbku`` is Copyright (c) 2004-2008, TundraWare Inc., Des Plaines, IL, USA |
|---|
| | ``tbku`` is Copyright (c) 2004-2014, TundraWare Inc., Des Plaines, IL, USA |
|---|
| | |
|---|
| | There is no fee for using ``tbku`` either personally or commercially |
|---|
| | *so long as the terms of the tbku license are met*. Please read the |
|---|
| | ``tbku-license.txt`` file for a full explanation of the licensing |
|---|
| |
|---|
| | information, see: |
|---|
| | |
|---|
| | http://docutils.sourceforge.net/rst.html |
|---|
| | |
|---|
| | ``$Id: tbku.rst,v 1.1 2012/06/09 18:02:57 tundra Exp $`` |
|---|
| | |
|---|
| | ``$Id: tbku.rst,v 1.2 2014/10/22 22:22:23 tundra Exp $`` |
|---|
| | |
|---|
| | |
tundra
authored
on 22 Oct 2014