Thanks Joshua,
I have make sure that the files are in one file-system and readible by
amanda.

since my /usr/lib are in the / file system, I only backup the /
filesystem,it should include /usr/lib/*

Below is my disk usage for local disk:

Filesystem Mbyte used availcapacity Mounted 
/dev/dsk/c0t0d0s0 28281 12566 15432 45% / 
/proc 0 0 0 0% /proc 
fd 0 0 0 0%
/dev/fd mnttab 0 0 0 0%
/etc/mnttab swap 1605 0 1605 1% 
/var/run swap 1606 1 1605 1% /tmp
/dev/dsk/c1t1d0s7 170504130857 37942 78% /cbic1 
/dev/dsk/c1t8d0s7 68937 63315 4933 93% /cbic3 
/dev/dsk/c1t2d0s7 170504106734 62065 64% /cbic2
/dev/dsk/c1t3d0s7 68937 46017 22231 68% /export/home1 
/dev/dsk/c0t0d0s1 4922 3744 1129 77% /export/user_storage


when I backup /, /usr/lib/* is not backuped.

Any suggestions? Thanks


On Fri, 26 Oct 2001, Joshua Baker-LePain wrote:

> On Fri, 26 Oct 2001 at 11:26am, Dengfeng Liu wrote
> 
> > I use amanda server on a solaris 8, when I backup the local machine,
> > but I noticed that the full backup do not include the /usr/lib/ and
> > some other file. 
> > 
> > My configuration file is:
> > 
> > machineName / machineName-comp-root-tar -1 local 
> > 
> amanda calls tar with the --one-file-system flag, so that tar behaves 
> like a "normal" *nix dump program and stays within a partition.  Look at 
> the output of 'df -k', e.g.:
> 
> [jlb@chaos jlb]$ df -k
> Filesystem           1k-blocks      Used Available Use% Mounted on
> /dev/sda1               248895    137984     98061  59% /
> /dev/sdb1              8262036   7256560    585780  93% /home
> /dev/sda5             12460452   3310400   8517096  28% /scratch
> /dev/sdb2              9384708   8177820    730160  92% /spare
> /dev/sda10              101089     13193     82677  14% /tmp
> /dev/sda6              1770920   1201892    479068  72% /usr
> /dev/sda7              1770920   1442912    238048  86% /usr/local
> /dev/sda9               101089     35099     60771  37% /var
> 
> Using your disklist entry, I'd only backup the first 250MB partition.
> 
> If this isn't the issue, then it's probably permissions.  Make sure that 
> you did 'make install' as root, as some binaries need to be setuid.
> 
> -- 
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University
> 

Reply via email to