>I'm trying to backup /export/home/staff on the backup server ... Is /export/home/staff local to the server, i.e. it is not NFS mounted?
Is this the real disk name or is it a synonym of some other name? Here's an example: $ df -k | grep /home/jumpgate/a /export/home/a 480815 207822 224912 49% /home/jumpgate/a Note that /home/jumpgate/a is mounted from /export/home/a (automounter magic). Using /home/jumpgate/a as a disklist entry may or may not be a bad thing (depends on the OS). It could easily decide that's not a real disk and flip back to using tar as a "favor". >... the disklist line looks like this: > >localhost /export/home/staff It doesn't matter for this problem, but don't use "localhost". If you ever change Amanda servers things are going to get real confusing. Always use the fully qualified host name. Also, I assume there really was one more column on the line telling Amanda what dumptype to use? >if I do a du -sk /export/home/staff it reports the 250MB so it >suddenly struck me that it's only backing up 250MB because that's >all the bin user has access to. Might be. I assume you ran "du -sk" as user "bin"? Didn't it report any errors? What does "df -k /export/home/staff" say? >This assumption may be wrong but if it's not how do I give bin >access to these areas. You shouldn't need to. If you're really using dump to back it up, the raw disk is used and ownership does not matter. If you use GNU tar, Amanda will run it under a setuid-root program it provides. >David Flood John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
