On Sun, Apr 23, 2006 at 08:38:09PM -0400, stan wrote:
> I'm trying to finish up a configuration that normally backus up
> to a RAIT of one vtape, and one real tape. The backup side of
> this is working.
> 
> I wnat to have a disk_only (and perhaps a tape_only) config, that
> will only be used to restor things. I've set up a common amanda
> confi file  in ../amanda.conf.main, and all 3 configs amanda.conf
> file include it. In it I have:
> 
> nfofile "/opt/amanda/var/DailyDump/curinfo"    # database DIRECTORY
> logdir   "/opt/amanda/var/DailyDump"            # log directory
> indexdir "/opt/amanda/var/DailyDump/index"      # index directory
> 
> DailyDump is the "prime" configuration.
> 
> DailyDump's amanda.conf file looks like this:
> 
> ncludefile "/opt/amanda/etc/amanda.conf.main"
> tpchanger "chg-multi"
> changerfile "/opt/amanda/etc/DailyDump/chg-multi.conf"
> tapetype RAIT
> 
> That's everyhting that is in it.
> 
> disk_only's amanda.conf looks like this:
> 
> includefile "/opt/amanda/etc/amanda.conf.main"
> tpchanger "chg-multi"
> changerfile "/opt/amanda/etc/disk_only/chg-multi.conf"
> tapetype HARD-DISK
> 
> But look at this:
> 
> root@amanda:/tmp# /opt/ama*/sbin/amrecover DailyDump
> AMRECOVER Version 2.5.0. Contacting server on amanda.meadwestvaco.com ...
> 220 amanda AMANDA index server (2.5.0) ready.
> 200 Access OK
> Setting restore date to today (2006-04-23)
> 200 Working date set to 2006-04-23.
> Warning: no log files found for tape DailyDump17 written 2006-04-23
> Scanning /dumpdisk...
> 20060423120823: found Amanda directory.
> 200 Config set to DailyDump.
> 501 Host amanda.meadwestvaco.com is not in your disklist.
> Trying host amanda.meadwestvaco.com ...
> 501 Host amanda.meadwestvaco.com is not in your disklist.
> Trying host amanda ...
> 200 Dump host set to amanda.
> Trying disk / ...
> $CWD '/tmp' is on disk '/' mounted at '/'.
> 200 Disk set to /.
> /tmp
> WARNING: not on root of selected filesystem, check man-page!
> 
> So far, so good right? But then:
> 
> root@amanda:/tmp# /opt/ama*/sbin/amrecover disk_only
> AMRECOVER Version 2.5.0. Contacting server on amanda.meadwestvaco.com ...
> 220 amanda AMANDA index server (2.5.0) ready.
> 200 Access OK
> Setting restore date to today (2006-04-23)
> 200 Working date set to 2006-04-23.
> Scanning /dumpdisk...
> 20060423120823: found Amanda directory.
> 200 Config set to disk_only.
> 501 Host amanda.meadwestvaco.com is not in your disklist.
> Trying host amanda.meadwestvaco.com ...
> 501 Host amanda.meadwestvaco.com is not in your disklist.
> Trying host amanda ...
> 200 Dump host set to amanda.
> Trying disk / ...
> $CWD '/tmp' is on disk '/' mounted at '/'.
> 200 Disk set to /.
> No index records for disk for specified date
> If date correct, notify system administrator
> Invalid directory - /tmp
> 
> Can't sem to find the index records, right? But it _should_ be able to
> as they are configured in the common amanda config file. Or do the
> index records somehow reference teh configuration? If so, can I
> overide this somehow?

The only similar thing I've done was the opposite of your
arrangement.  You have one combined config that does the
actual dumps and two "pseudo" configs for restore.  I had
two configs doing the dumps (archive_system and archive_users)
and one config that never dumped (archive) but was used
for recovery.  Been a while, but it worked.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)