Refer to http://www.amanda.org/docs/restore.html for the current version of
this document.
-This document describes how to restore files backed up with AMANDA either with
-or without AMANDA tools.
+This document describes how to restore files backed up with Amanda either with
+or without Amanda tools.
All these cases assume you're trying to restore a complete disk, that is,
you've replaced the lost disk with a new one, or created a new filesystem on
it. Tweaking with the arguments to restore (not amrestore), you will be able to
First of all, boot off the CD, and reinstall the system critical
partition, restoring it to vendor supplied state. Then, go through all of
Scenario 1.
- 3. Server machine fails, non-system critical, non-AMANDA disk.
+ 3. Server machine fails, non-system critical, non-Amanda disk.
Proceed just as described in Scenario 1. However, you won't have to go
through the rsh process, because you can just use amrestore to replace the
lost data directly.
- 4. Server machine fails, system critical, non-AMANDA disk.
+ 4. Server machine fails, system critical, non-Amanda disk.
Example: / on Aaron
First of all, boot off the CD, and reinstall the system critical
partition, restoring it to vendor supplied state.
Then, follow steps in Scenario 3.
- 5. Server machine fails, non-system critical, AMANDA disk, with db.
+ 5. Server machine fails, non-system critical, Amanda disk, with db.
Example: /opt on Aaron
- If the disk that contains the AMANDA database is toast, then you need to
+ If the disk that contains the Amanda database is toast, then you need to
rebuild the database. The easiest way to do it is to take the text file
that you had mailed to you via the 'amadmin export' command, and import
via the 'amadmin import' command. Then you should be able to follow the
steps outlined in Scenario 4.
- Note that AMANDA does not mail the exported database automatically; you
+ Note that Amanda does not mail the exported database automatically; you
may add this to the crontab entry that runs amanda.
Maybe it's a good idea to print out the text files as well and store the
last 2 dumpcycles worth of paper (the disc text files might have got
toasted as well). From the paper you still are able to reconstruct where
your discs are.
- 6. Server machine fails, non-system critical, AMANDA disk, with binaries.
+ 6. Server machine fails, non-system critical, Amanda disk, with binaries.
Example: /usr/local on Aaron
This is where things get hairy. If the disk with the amanda binaries on it
is toast, you have three options.
- i. reinstall the AMANDA binaries from another tape, on which you have
+ i. reinstall the Amanda binaries from another tape, on which you have
conveniently backed up the binaries within the last couple of weeks
- (not using AMANDA).
- ii. recompile AMANDA, making sure not to overwrite your db files.
- iii. use dd to read AMANDA formatted tapes. This is the option I am going
+ (not using Amanda).
+ ii. recompile Amanda, making sure not to overwrite your db files.
+ iii. use dd to read Amanda formatted tapes. This is the option I am going
to explore most fully, because this seems the most likely to occur.
- a. Find out the device name used by AMANDA, by looking in
+ a. Find out the device name used by Amanda, by looking in
amanda.conf. Turns out to be /dev/rmt/0cn for this system.
If amanda.conf isn't at hand: this must be a non-rewinding tape
device specifier (which I believe the trailing `n' stands for).
Example output:
- AMANDA: FILE 19971220 uri /root-sun4 lev 1 comp .gz program
+ Amanda: FILE 19971220 uri /root-sun4 lev 1 comp .gz program
DUMP
- AMANDA: FILE 19971220 uri /misc lev 1 comp .gz program DUMP
- AMANDA: FILE 19971220 uri / lev 1 comp .gz program DUMP
+ Amanda: FILE 19971220 uri /misc lev 1 comp .gz program DUMP
+ Amanda: FILE 19971220 uri / lev 1 comp .gz program DUMP
- g. Restore the AMANDA binaries (what else do you need??), and then
+ g. Restore the Amanda binaries (what else do you need??), and then
bail out of ufsrestore. You can use amrestore, as in Scenario 3.
projects / debian / amanda / blobdiff