David make sure that the 'bin' user has access to the /dev/dsk/c0t0d0s0 (or whatever). It will probably need to be a member of sys on a solaris box, check the file group membership of the actual device.
-- Martin David Flood wrote: > I've just upgraded from 2.4.2p2 to 2.4.3b3, at the same time I've changed my > amanda user from root to bin. I notice when I get the report at the end of a > level 0 backup. It has backed up nowhere near all the data that exists. > > For example: > > /export/home/staff > > has 11.8GB but is only backing up 235MB. Now when I do a du -sk > /export/home/staff as user bin it reports (Guess what) 235MB. > > This happened before when I upgraded to 2.4.2p2 I could not get a solution so I > swapped to user root which solved the problem. Some time after someone on the > list said the solution was to configure and make as the same user your going to > be using then do make install as root(obviously). So because it's not > recommended to have the amanda user as root I thought since I was upgrading > 2.4.3b3 I would kill two birds with one stone and put it back to bin. So again I > find myself in this position. > > To give more detail, I'm using dump as my backup method and my tapeserver is > Solaris 7. At the moment I'm only backing up the tapeserver i.e. localhost. It > is not a tape space problem as I'm using DLT's and the report said the total > original size was only 18GB. > > Does anyone know why this happens and how to fix it? If not what are the > security issues with the amanda user being root? > > Thanks in advance > > > David Flood > Systems Administrator > > > >
