I am having problems using amrecover. I can only see limited number of
indexes and then follow them down to a file level. Most indexes do not 
seem to be there. When I do a 'ls' command I only see the 'opt/' 
directory or entry from the index files. 


amrecover> setdisk /hostserver0/root
Scanning /var/holddisk/amanda1...
  20030627: found Amanda directory.
Scanning /var/holddisk/amanda0...
  20030627: found Amanda directory.
200 Disk set to /hostserver0/root.
amrecover> ls
2003-07-01 opt/

>>From the index file 20030701_0: I see serveral entries for /opt...

/opt/SUNWexplo/output/explorer.hostserver0-2003.06.28.07.00/disks/vxvm/disk_groups/vxdg-g_free=r
ootdg.out

And I also see the following entries in the same index file:
...
07665067355/./etc/lu/optfs
07665067356/./etc/vx/vras/.rdg
07665067403/./opt/SUNWstade/System/NETCONNECT
...
07665067405/./opt/SUNWstade/lib/auto/XML/LibXML/LibXML.bs
07665067405/./opt/SUNWstade/lib/auto/XML/Parser/Expat/Expat.bs
07665067412/./.dt/.Printers/CSD-HP5_Print
07665067412/./.dt/.Printers/_default_Print
07665067412/./.dt/.Printers/hplj5si_Print
...

When I do a 'ls' command in amrecover, I only see the 'opt/' directories
and files and none of the other enteries that start with a number followed by
a '/./'. 

My dumptype looks like:

define dumptype global {
    comment "Global definitions"
    holdingdisk no
    compress none
}

define dumptype root-tar {
    global
    program "GNUTAR"
    comment "root partitions dumped with tar"
    index yes
    priority high
    dumpcycle 0
}

My disklist looks like:

hostserver0 / root-tar 1 local

Also, I am running Amanda 2.4.4 on a Sun Solaris 9 box. Has anyone seen 
any problems like this? Any ideas? Thanks in advance.

Bob...



--
Robert Zahn     UNIX Systems Administrator
Oklahoma City Community College
7777 S. May Avenue
Oklahoma City, Ok 73159
bzahn AT zeus.okccc DOT edu    bzahn AT okccc DOT edu
--