Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have inherited a bunch of old backup tapes that contain some data that needs to be recovered. The problem is that the amanda implementation used to create these backups has since been obliterated.

I am very new to amanda, but was under the impression that the config files are required to recover backed up data.

Is there any easy way to get this data off? If not, what steps should I take?

share|improve this question

You will have to read all the tapes until you find the configuration data.

Install Amanda and use this to recover the configuration :

The Amanda Wiki is a good place to start looking, there are many howto's describing the steps to take to recover your data.

Good luck.

share|improve this answer

(I realize this is a rather old question but there are other options.)

To be pedantic, it is not necessary to have Amanda even installed to read backups off those tapes. Having Amanda just makes it a lot easier. I just recently experienced this sort of failure and didn't find the information I needed from the current Zmanda wiki, but I did find it in their deprecated section with Google. (See below.)

The front of each tape will have a 32k header block containing plain text, and that text contains instructions how you can recover the backup files off that tape using normal *nix commands. So, to read that header, all you need to do is:

dd if=/your/tape/device bs=32k count=1

and that will dump the text header to stdout. To read the tape's contents

If you're using physical tapes, each 'record' on the tape contains the backup of a single filesystem, or DLE, and each one will have a 32K header on it with instructions and metadata specific to that client. The content of each block after the first is whatever your Amanda was configured to create, which can be gnutar, star, cpio. or something custom, and all can be compressed or not compressed. As these can vary by client, each record on the tape can be a different format, but all of them will have that 32K header block with instructions.

If your tapes are virtual tapes using the dsk-changer driver, then each DLE is written to its own file, and finding what you want is a lot easier because the host and disk are part of the filename.

This old web page at may be deprecated, but it still was very useful to me just two weeks ago, when there were "interesting times" in our data center and my Amanda server's VM rolled back about six weeks (because the VM is hosted in windows and windows crashed, taking my Amanda VM with it.) I had the Amanda binaries, but the tape databases were all older than my existing tape library, so I couldn't use Amanda's smarts to read anything off my virtual tapes. Yeah, today I'm building a new bare-metal box to be our Amanda server, so windows won't destroy me again.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.