Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 1 Dec 1996 18:56:26 +0200 (IST)
From:      Yuri Gindin <yuri@aebeard.technion.ac.il>
To:        Andreas Klemm <andreas@klemm.gtn.com>
Cc:        Michael Reifenberger <root@totum.plaut.de>, gpalmer@FreeBSD.org, FreeBSD-Ports <freebsd-ports@FreeBSD.org>
Subject:   Re: amanda 2.3.0 anyone under current?
Message-ID:  <Pine.BSI.3.95.961201180221.5754A-100000@aebeard.technion.ac.il>
In-Reply-To: <Pine.BSF.3.95.961201135042.19716A-100000@klemm.gtn.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 1 Dec 1996, Andreas Klemm wrote:

Andreas,
> My $0.02:
> 
> put a "#! /bin/sh" into the first line of the shellscript "amdump" 
> to make sure, that it will be executed by the bourne shell ;-)
> 
> BTW, I'm still in deep trouble here. Don't get amanda working.
> 
> Perhaps one kind soul could look over my configuration ?!
> 
> Here is the mail I get, after starting amdump as user bin from 
Better, use another user or put bin the group operator.
> a shell.
> 
> *** THE DUMPS DID NOT FINISH PROPERLY!
My $0.02
> 
> These dumps were to tape .

Here, I think, you have to label your tape with amlabel.
The tape is not labeled.

> Tonight's dumps should go onto a new tape.
> 
> FAILURE AND STRANGE DUMP SUMMARY:
>   taper: FATAL couldn't write tapelist: Permission denied

Your dumpuser cannot write into your config directory.

>   klemm      sd0a  RESULTS MISSING
>   klemm      sd0s3e  RESULTS MISSING
> 
[Snip]
> (brought to you by Amanda version 2.2.6)
> - -------------------------------------------------------------------------------
Why 2.2.6 ?
> 
> What I did after the make install:
> a) made sure, that proper entries are in /etc/services and /etc/inetd.conf.
> b) created the needed directory for my "akl" configuration
> c) fixed the amdump script by putting #! /bin/sh in front of it
> d) created a /var/log/amanda directory, which is writeable for the bin
>    user.
> e) chmod 666 /dev/*rst*
Why to all, they must be writeable for dumpuser.
> 
> What's this tape list amanda can't write ?! *sigh* ;-)
> 
> Does somebody have a clue ?
> 
> Here my configuration:
> 
> - -----------------------------------------------------------------------------
> 
> #
> # amanda.conf - sample Amanda configuration file.  This is the actual config
> #		file in use at CS.UMD.EDU.
> #
> # If your configuration is called, say, "csd", then this file normally goes
> # in /etc/amanda/csd/amanda.conf.
> #
> 
> org "KLEMM"		# your organization name for reports
> mailto "andreas"	# the mailing list for operators at your site
> dumpuser "bin"		# the user to run dumps under
> 
> inparallel 3		# maximum dumpers that will run in parallel
> netusage  999		# maximum net bandwidth for Amanda, in KB per sec
> 
> dumpcycle 1 weeks	# the number of days in the normal dump cycle
> tapecycle 7 tapes	# the number of tapes in rotation
You must have more tapes then *real* backup days. If you make backup
7 days a week you need at least 8 tapes.
> 
> bumpsize 10 MB		# minimum savings (threshold) to bump level 1 -> 2
> bumpdays     2		# minimum days at each level
> bumpmult     2		# threshold = bumpsize * (level-1)**bumpmult
> 
> #tpchanger "chg-generic"	# the tape-changer glue script
> tapedev "/dev/nrst0"	# or use the (no-rewind!) tape device directly
> 
> tapetype TDC-4222	# what kind of tape it is (see tapetypes below)
> labelstr "^AKL[0-9][0-9]*$"	# label constraint regex: all tapes must match
> 
> #Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> #/dev/sd0s3e     63567     2976    55506     5%    /www
> 
> #diskdir "/www/holding-disk"	# where the holding disk is
> #disksize 30 MB			# how much space can we use on it
Where is your holding disk ? Or otherwise it can make only 1 "parallel" 
backup at a time.Slow :-(
> 
> 
> infofile "/var/log/amanda/curinfo"	# database filename
> logfile	 "/var/log/amanda/log"		# log filename
> 

> 
> define tapetype TDC-4222 {
>     comment "TANDBERG TDC-4222 5GB QIC TAPE"
>     length 5000 mbytes
>     filemark 32 kbytes
>     speed 500 kbytes			
> }
> 
> define dumptype akl-high {
>     comment "high priority"
>     options no-compress
I think better is to use software compression with gzip instead of
hardware compression, but it uses more CPU.
>     priority high
> }
> 
[snip]
> #/dev/sd0s3g    765058   642255    61599    91%    /usr
> #/dev/sd1s1e    197951    93676    88439    51%    /news
> #/dev/sd1s1f   1786531  1010960   632649    62%    /local
Use your /local as a dumpdisk.
It's good for the backup of many hosts from network.
> 
> klemm sd0a   akl-high
> klemm sd0s3e akl-low
> klemm sd0s3f akl-medium
> klemm sd0s3g akl-medium
> klemm sd1s1e akl-low
> klemm sd1s1f akl-high
> 
Use mountpoints instead of disks, it's more readable.

Regards,
--Yuri.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.961201180221.5754A-100000>