On 15/11/18 00:04, Nathan Stratton Treadway wrote: > On Wed, Nov 14, 2018 at 15:35:50 -0500, Chris Nighswonger wrote: >> Can anyone point me to "good" documentation that describes Amanda's DB? >> Things like schema, field descriptions and/or uses, etc. >> >> It looks like maybe they are located in >> '/var/backups/jobname/index|curinfo' ? So flat files? > > Yes, those are flat files. I haven't run across specific documentation > for them (though I can't say I've looked hard for it). > > The "index" files (up through Amanda 3.3, anyway) are just the plain > file/directory names pulled out of the dump-archives, and they are used > to present you with the list of directories/files that can be recovered > in "amrecover". > > The curinfo files feel like a simple dump-to-text of in-memory data > structures (the datetime stamps are seconds-since-the-unix-epoch, for > example, and spaces are used to separate unlabeled fields on the lines). > > > Two other (interrelated) categories of data that Amanda maintains are > the tapelist file, and the log.DATETIMESTAMP files (in the same > directory as the amdump.DATETIMESTAP files). There is a "tapelist" man > page to describe the former; the latter records the mapping of which > dumps were written to which volume. > >> I notice that the later versions of ZWC use SQL. > > I saw that the Amanda source repository master branch includes the > following commit: > > commit ea4dd29d265b44a914e794d5150e53bce9d9435d > Author: Jean-Louis Martineau <[email protected]> > Date: Thu Jan 4 12:52:28 2018 +0000 > > Use a database (SQLite, MySQL or ProstgreSQL) to replace the tapelist > and log.* file > Read the Amanda-Catalog file > * perl/*, server-src/*, common-src/conffile.c: Major changes > * installcheck/*: Fix tests > * Amanda-Catalog: New documentation document > > Jan 2018 is after Amanda 3.5 was released so this is still > work-in-progress, and I don't know how "mature" this transition got > before Jean-Louis left.... > > Nathan > > ---------------------------------------------------------------------------- > Nathan Stratton Treadway - [email protected] - Mid-Atlantic region > Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 >
On CentOS (and therefore RHEL, Fedora and SL) look in /var/spool/amanda.
There will be a directory for each config name, look in there and
you'll see two directories: curinfo and index. The subdirectories are
named after the host and DLE:
/var/spool/amanda/<config>/{curinfo,index}/<host>/<DLE>/
As Nathan says, the curinfo tree just contains files called info which
are a dump of a few parameters and the history list in reverse date
order. I think the history list's fields are:
history: 0 5103770 5103770 1542234933 721
history: record label
0 level
5103770 bytes (to back up?)
5103770 bytes (backed up?)
1542234933 datestamp
721 unknown, possibly seconds elapsed.
The index tree has two sorts of files, for example 20170928224421_1.gz
and 20170928224421_1.header. The gzipped file is simply a list of the
files that amanda backed up during that run. The header seems to be
fixed and defines information about the DLE and program used to dump.
It ends with instructions as to how to restore the dump.
--
J Martin Rushton MBCS
signature.asc
Description: OpenPGP digital signature
