Ok,
I decided to try a recover before I NEEDED to do one. I just did an
"amoverview"
and it showed a level 0 on my dumpserver last thurs, and level 1 on
friday. I
followed with this:
{0}:powderday:/>amrecover
AMRECOVER Version 2.4.1p1. Contacting server on
powderday.vail.agency.com ...
220 powderday AMANDA index server (2.4.1p1) ready.
200 Access OK
Setting restore date to today (2000-11-13)
200 Working date set to 2000-11-13.
200 Config set to DailySet1.
501 No index records for host: powderday.vail.agency.com. Invalid?
Trying powderday.vail.agency.com ...
501 No index records for host: powderday.vail.agency.com. Invalid?
Trying powderday.eriver.com ...
501 No index records for host: powderday.eriver.com. Invalid?
Trying powderday ...
501 No index records for host: powderday. Invalid?
Trying loghost ...
501 No index records for host: loghost. Invalid?
amrecover> quit
I have this in my disk list:
powderday c0t0d0s0 generic-cb # /
powderday c0t0d0s3 generic-cb # /var
powderday c0t0d0s4 generic-cb # /opt
powderday c0t0d0s6 generic-cb # /usr
powderday c0t1d0s6 generic-cb #
/export/home
Thoughts?
I put "powderday.vail.agency.com root" in my .amandahosts because
it complained I wasn't allowed to connect. That error went away.
Robert
--
:wq!
---------------------------------------------------------------------------
Robert L. Harris | Micros~1 :
Unix System Administrator | For when quality, reliability
at Agency.com | and security just aren't
\_ that important!
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
