Re: access to raid
nope not using xinetd "John R. Jackson" wrote: > >groups = yes is nowhere as far as I know, doing a grep search through > >man amanda, amdump, amanda.conf shows no such line > > It's an xinetd parameter. You need to look in that config file, if > you're using xinetd. > > >I assume therefore the default is group = no.? > > That's my understanding. > > >Steven > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: access to raid
I run amcheck before amdump via crontab -u backup -e 45 15 * * 1-6 /usr/sbin/amcheck -m DailySet1 00 19 * * 1-6 /usr/sbin/amdump DailySet1 if there are any errors it emails me Yes its a debian sid linux client box its running kernel 2.4.2. groups = yes is nowhere as far as I know, doing a grep search through man amanda, amdump, amanda.conf shows no such line I assume therefore the default is group = no.? Ive got round it by specifying the share/mount point instead Steven "John R. Jackson" wrote: > >/dev/md0's group is disk, backup is in /etc/group under disk... > > What does amcheck say? Is this a Linux box? Are you running xinetd > to start amandad? Do you have "groups = yes"? > > >Steven > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: access to raid
/dev/md0's group is disk, backup is in /etc/group under disk..permissions are rw-rw---as per normal partitions. Steven Jason Shupe wrote: > I backup md devices on multiple linux boxen... > > what about permissions? does the amanda user have group read permission? > > On Wed, Apr 25, 2001 at 03:30:01PM +1200, thing wrote: > > These dumps were to tape kaitlin01. > > Tonight's dumps should go onto 1 tape: a new tape. > > > > FAILURE AND STRANGE DUMP SUMMARY: > > kaitlin/dev/md0 lev 0 FAILED [disk /dev/md0 offline on kaitlin?] > > localhost /root lev 0 STRANGE > > localhost sdb1 lev 0 STRANGE > > > > 8>< > > > > kaitlin /dev/hda6 0 10 32 320.00:00 485.50:00 7281.8 > > > > kaitlin /dev/hdd2 0 146470 126112 86.12:20 902.91:41 1255.1 > > > > kaitlin /dev/md0 0 FAILED > > > > localhost /bin 0 2000 960 48.00:01 882.70:00 2484.8 > > > > localhost /boot 0 920 768 83.50:01 1395.30:00 2574.4 > > > > the raid device isnt off line its working fineis /dev/md0 a > > non-acceptable device in amanda? > > > > Steven
Re:access to raid
These dumps were to tape kaitlin01. Tonight's dumps should go onto 1 tape: a new tape. FAILURE AND STRANGE DUMP SUMMARY: kaitlin/dev/md0 lev 0 FAILED [disk /dev/md0 offline on kaitlin?] localhost /root lev 0 STRANGE localhost sdb1 lev 0 STRANGE 8>< kaitlin /dev/hda6 0 10 32 320.00:00 485.50:00 7281.8 kaitlin /dev/hdd2 0 146470 126112 86.12:20 902.91:41 1255.1 kaitlin /dev/md0 0 FAILED localhost /bin 0 2000 960 48.00:01 882.70:00 2484.8 localhost /boot 0 920 768 83.50:01 1395.30:00 2574.4 the raid device isnt off line its working fineis /dev/md0 a non-acceptable device in amanda? Steven
Re: access to amrecover
"John R. Jackson" wrote: > >Futher problem, Im trying to recover off a remote host, I'm getting, > > > >>amrecover > >AMRECOVER ...Contacting server on localhost ... > >amrecover: error conecting to server: Connection refused > > What version of Amanda are you using? 2.4.2p1 (and maybe 2.4.2, I forget) > had a problem with Linux. It's fixed with 2.4.2p2. 2.4.1p1, guess I need to find a new deb.bugger > >Am I supposed to be contacting the localhost or the remote tapeserver? > > You should have configured amindexd and amidxtaped on the tape server > machine in inetd.conf (or with xinetd), and that's the machine you need > to contact. > > Are those services running on your tape server? yes, netstat -ta shows them running. > >I'm also almost ready to put this into production, are there any files i > >can delete/reset so I can start "clean" ... > > I think there is an FAQ item about this (www.amanda.org). thanks Steven
Re: access to amrecover
So why is default no? ;-^) Futher problem, Im trying to recover off a remote host, I'm getting, >amrecover AMRECOVER ...Contacting server on localhost ... amrecover: error conecting to server: Connection refused so I try, amrecover -t kascha AMRECOVER ...Contacting server on localhost ... amrecover: error conecting to server: Connection refused so I try, amrecover -t kascha.thing.dyndns.org AMRECOVER ...Contacting server on localhost ... amrecover: error conecting to server: Connection refused I have 2 lines in .amandahost kascha.thing.dyndns.org backup kascha.thing.dyndns.org root anything else i need? Am I supposed to be contacting the localhost or the remote tapeserver? I'm also almost ready to put this into production, are there any files i can delete/reset so I can start "clean" I now have 3 extra tapes so I want to add these to the pool, ive edited amanda.conf. Are there any other files i need to edit to get a "clean" start? thanks, Steven "John R. Jackson" wrote: > >... do i really need an index? > > Yes, if you want to use amrecover. > > >Steven > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: access to amrecover
No I didnt, seeing the default is no, do i really need an index?
thanks,
Steven
Alexandre Oliva wrote
> Did you have `index yes' in the corresponding dumptype at backup time?
>
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist*Please* write to mailing lists, not to me
Re: access to amrecover
Thanks, I now have 2 lines in .amandahosts, localhost backup kascha root is this correct? Im getting this error, "501 No index records for host: kascha. Invalid? Trying kascha... "501 No index records for host: kascha. Invalid? Trying kascha.thing.dyndns.org... 501 No index records for host:kascha.thing.dyndns.org. Invalid? amrecover>" Then Im "in" Thanks, Thing "John R. Jackson" wrote: > >Hi Im on the tape server trying to recover some files locally so i start > >amrecover as root and get > > > >8><"500 Access not allowed: [access as backup not allowed from root@kascha] > > You need: > > kascharoot > > in your ~AMANDA/.amandahosts (where "AMANDA" is your Amanda user) on > the tape server machine. > > >Thing > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: access to amrecover
Hi Im on the tape server trying to recover some files locally so i start amrecover as root and get 8><"500 Access not allowed: [access as backup not allowed from root@kascha] so i try su - backup then /usr/sbin/amrecover and get, amrecover: amrecover must be run by root so im in catch22 help pls :) Thing
Re: Holding Disk Question
raid 0 them? Steven Gerhard den Hollander wrote: > Im currently using a single (big) holding disk. > I have 2 smaller disks, that I'd like to use as holding disks. > > But the samller disks will not be able to hold the big 0 dumps. > > According to the docs, the holding disks are used in a round-robin way > (dump 1 to HD1, dump 2 -> HD 2, dump3 -> HD3, dump4 -> HD1 &c &c ) > > What happens if my dump is supposed to go to HD1, but is way too big for > HD1, but would easily fit on HD3 ? > > Will amanda use the big Holding disk ? > > Currently listening to: Flying Frog Brigade - Here's to the Man (August 29 - New >York City) > > Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == > -- >__O Some say the end is near. > =`\<, Some say we'll see armageddon soon > (=)/(=) I certainly hope we will > I could use a vacation
disk offline
amanda email output,
FAILURE AND STRANGE DUMP SUMMARY:
kascha sdb2 lev 0 FAILED [disk sdb2 offline on kascha?]
kascha sdb1 lev 0 FAILED [disk sdb1 offline on kascha?]
kascha sda1 lev 0 FAILED [disk sda1 offline on kascha?]
Since these are my boot disk and /usr disk they arnt off
line.
:}
Im using GNUTAR (or tryng to) using the options below,
tar version is 1.13.17-2 (latest Debian 2.2r2+)
amanda.conf8><
org "DailySet1" # your organization name for reports
mailto "[EMAIL PROTECTED]" # space separated list of mail ssj
#12
dumpuser "backup" # the user to run dumps under
dumpcycle 1 #ssj added
#tapedev /dev/nst0 #ssj added disabled as per man page
inparallel 4# maximum dumpers that will run in parallel
netusage 6000 # maximum net bandwidth for Amanda, in KB persec
# a filesystem is due for a full backup once every days
#ssj dumpcycle 4 weeks # the number of days in the normal dump cycle
tapecycle 8 tapes # the number of tapes in rotation
#25
bumpsize 20 MB # minimum savings (threshold) to bump level 1 ->
2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * (level-1)**bumpmult
#runtapes 9 # explained in WHATS.NEW
#tpchanger "no-changer" # the tape-changer glue script, see
TAPE.CHANGERS
tapedev "/dev/nst0" # Linux @ tuck, important: norewinding
# tapedev "/dev/nrst8" # or use the (no-rewind!) tape device directly
tapetype DEC-DAT# ssj what kind of tape it is
(seetapetypesbelow) dec-tk88
labelstr "^kaitlin[0-9][0-9]*$" # label constraint regex: all tapes
diskdir "/home/amanda" # where the holding disk is (dev/sdc1)
disksize 3000 MB# how much space can we use on
8><
define tapetype DEC-DAT {
comment "DAT tape drives"
length 25000 mbytes # these numbers are not accurate
filemark 100 kbytes # but you get the idea
speed 500 kbytes
}
-8><
}
#ssj my option for linux boxes
define dumptype gnutar-full {
comment "Full dump of this filesystem always"
options compress-fast
priority high
dumpcycle 0
maxcycle 0
}
disklist8><
#start with kascha
kascha sda1 gnutar-full
kascha sdb1 gnutar-full
kascha sdb2 gnutar-full
last log file
amdump: start at Tue Mar 27 07:58:01 NZST 2001
planner: pid 537 executable /usr/lib/amanda/planner version 2.4.1p1
planner: build: VERSION="Amanda-2.4.1p1"
planner:BUILT_DATE="Mon Jun 12 23:14:52 MDT 2000"
planner:BUILT_MACH="Linux rover 2.2.15pre15 #1 Thu Mar 23
02:22:27 MST 2000 i686 unknown"
planner:CC="gcc"
planner: paths: bindir="/usr/sbin" sbindir="/usr/sbin"
planner:libexecdir="/usr/lib/amanda" mandir="/usr/share/man"
planner:CONFIG_DIR="/etc/amanda" DEV_PREFIX="/dev/"
planner:RDEV_PREFIX="/dev/" DUMP="/sbin/dump"
planner:RESTORE="/sbin/restore"
SAMBA_CLIENT="/usr/bin/smbclient"
planner:GNUTAR="/bin/tar" COMPRESS_PATH="/bin/gzip"
planner:UNCOMPRESS_PATH="/bin/gzip" MAILER="/usr/bin/Mail"
planner:listed_incr_dir="/var/lib/amanda/gnutar-lists"
planner: defs: DEFAULT_SERVER="localhost" DEFAULT_CONFIG="DailySet1"
planner:DEFAULT_TAPE_SERVER="localhost"
planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM
planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY
planner:USE_AMANDAHOSTS CLIENT_LOGIN="backup" FORCE_USERID
HAVE_GZIP
planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast"
planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc"
READING CONF FILES...
driver: pid 538 executable /usr/lib/amanda/driver version 2.4.1p1
driver: send-cmd time 0.003 to taper: START-TAPER 20010327
startup took 0.005 secs
SETTING UP FOR ESTIMATES...
setting up estimates for kascha:sda1
kascha:sda1 overdue 11408 days for level 0
setup_estimate: kascha:sda1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb1
kascha:sdb1 overdue 11408 days for level 0
setup_estimate: kascha:sdb1: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates for kascha:sdb2
kascha:sdb2 overdue 11408 days for level 0
setup_estimate: kascha:sdb2: command 0, options:
last_level -1 next_level0 -11408 level_days 0
getting estimates 0 (0) -1 (-1) -1 (-1)
setting up estimates took 0.000 secs
GETTING ESTIMATES...
driver: started dumper0 pid 540
driver: started dumper1 pid 541
driver: started dumper2 pid 542
driver: started dumper3 pid 543
taper: pid 539 executable taper version 2.4.1p1
dumper: pid 540 executable dumper version 2.4.1p1, using port 540
dumper: pid 541 executable dumper version 2.4.1p1, using port 541
dumper: pid 542 executable dumper version 2.4.1p1, using port 542
dumper: pid 543 e
Re: amanda backup setup failing
"John R. Jackson" wrote: > >/var/backups/.amandahosts has, > > > >localhost backup > > Is /var/backups the home directory for "backup"? yes under /etc/passwords the permissions of the dir and .amandahosts are backup:backup > > > Note the message you got: > > access as backup not allowed from backup@kascha > > So this says you need this line in .amandahosts: > > kascha backup doh.. The debian maintainer has put, "localhost backup", changing to "kascha backup" has got through that "stage" i have 2 other errors now :} will work through them and see what I can find, thanks for your time, Thing
Re: amanda backup setup failing
"backup" is in /etc/group under the group disks. disk:x:6:backup and under /dev/ sd??'s are group disk /var/backups/.amandahosts has, localhost backup the holding disk is set to backup:backup but I dont think its getting that far. I fogot to mention this is a Debian 2.2r2 machine and im backing up the server itself Thing [EMAIL PROTECTED] wrote: > hope this helps: > > Have a look at the group which owns the device files in /dev/... you want > to > backup. > > The backup user must belong to this group to have access to the devices. > > bye Mike
amanda backup setup failing
anybody have any idea why?
I get the email below, it runs from cron as "backup"
I suspect permissions on the partitions, however I cannot find anything
in the docs or web site to give me a clue, so im almost ending up making
the user backup the same group as root to allow access, this seems
excessive. Any ideas please?
Thing
These dumps were to tape kaitlin02.
Tonight's dumps should go onto 1 tape: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
kascha /dev/sdb2 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]
kascha /dev/sdb1 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]
kascha /dev/sda1 lev 0 FAILED [kascha: [access as backup not
allowed from backup@kascha]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:00 0:00 0:00 (0:00 start,
0:00 idle)
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Tape Used (%) 0.00.00.0
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk kascha:/dev/sda1.
planner: Adding new disk kascha:/dev/sdb1.
planner: Adding new disk kascha:/dev/sdb2.
driver: WARNING: got empty schedule from planner
taper: tape kaitlin02 kb 0 fm 0 [OK]
