On Saturday 02 March 2002 02:43 pm, [EMAIL PROTECTED] wrote: >I had the same problem when I upgraded from amanda 2.4.1p1 to >2.4.2p2. In both versions the user was bin, but when I tried to >retrieve data with the new version I found the directory > structure but no files. I discovered amanda was just backing up > only a fraction of what it was supposed to. For example instead > of backing up a partition which was several gig it only backed > up 250mb of the partition. I then noticed that when doing a du > -sk on that partition as the user bin it reported 250mb. So I > concluded amanda was only backing up what the user bin had > permission to read and hence the directory structure being > backed up with no files. So in short I don't think it's tar > that's causing your problem I think it is a permission problem. > Is the machine your trying to back up a new one? If so check > your amandahosts/rhosts file set up properly. I did not > understand this problem when I come up against it as I had only > installed a more recent version of amanda which was configured > using the exact same options. In the end I had to reinstall > amanda using the user root which solved the problem but this is > not recomended for security reasons. > >If anyone reading this knows why this permissions problem >occured I would be grateful if you could let me know.
This often occurs when doing an upgrade, things get intalled with the wrong permissions. Here, I try to preclude such goings on by su'ing to the user amanda to do *every step* of the build, only exiting to root to do the make install, which seems to alleviate all the perms problems that can otherwise plague one. ISTR its in the README someplace, but easliy forgotten, at least by me. What I need here is the ability to read the prompt so I don't forget who I am, that still bites me occasionally. :-) [snip] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.6+% setiathome rank, not too shabby for a hillbilly
