Bernhard,
We had successful backup of all systems except the 2.6 box
last night, it was a file protection problem on the /usr/local/libexec
directory (yassp over-tighened security for us).
The 2.6 box no longer mounts the 2.8 system's /usr/local and instead
has an installation of the previously built (and fortunately archived)
2.4.1p1 which did return proper results when checked by the 2.8 box's
2.4.2p2 amanda server. Tonight will tell us if dumps will actually
run correctly.
Thanks for your help, at this point it looks like we're back in business.
thanks,
Brian
> > I've run the amandad on the command line and from the errors I'm
> > seeing believe the current problem stems from running a client
> > built under 2.8 on a 2.6 system.
>
> I'm no Solaris expert but my feeling is this _will_ cause problems.
>
> [...]
> > Don't have a functioning gcc under any of my 2.6 system, do you
> > think my previously built 2.4.1p1 client will run correctly with
> > my 2.4.2p2 server ?
>
> I don't think so. At least in theory it should run flawlessly. I
> remember some weird problems when I upgraded some servers or clients
> from 2.4.1p1 to 2.4.2 and clients or servers were left on 2.4.1p1 but I
> can't you tell any details at the moment. Just try it. To know if it
> runs or not takes less time than getting gcc for 2.6. If it doesn't run,
> try something like http://gcc.gnu.org/, then click somewhere on
> "binaries".
