Re: Amanda users does not get full access to files
Does bin have read access on the raw devices /dev/rdsk (or /dev/vx/)?? Toomas Aas wrote: Hi David! On 8 Apr 02 at 10:57 you 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. I don't know about Solaris but in FreeBSD the user that Amanda runs as needs to have read access to disk devices (in my casem, a subset of /dev/da0s* and /dev/da1s*) -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * No problem is so big that it can't be run away from.
Re: Amanda users does not get full access to files
To confirm bin does have read access I did a dd if=/dev/rdsk/c0t0d0s0 of=/tmp/foobar bs=512 count=1 as bin and it did not complain as it would if bin did not have read access. On 8 Apr 2002, at 9:08, Don Potter wrote: Does bin have read access on the raw devices /dev/rdsk (or /dev/vx/)?? Toomas Aas wrote: Hi David! On 8 Apr 02 at 10:57 you 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. I don't know about Solaris but in FreeBSD the user that Amanda runs as needs to have read access to disk devices (in my casem, a subset of /dev/da0s* and /dev/da1s*) -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * No problem is so big that it can't be run away from. - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: Amanda users does not get full access to files
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. Please post what df -k /export/home/staff says. I'm guessing it's not a real file system but a subdirectory (or some goofy automounter thing) and dump isn't doing what you think it is. David Flood John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Amanda users does not get full access to files
David Flood [mailto:[EMAIL PROTECTED]] 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. Can you find out what the data that the amanda user isn't seeing is? Ricky
RE: --with-group?
No -- this is the group that the files/amanda user belong to. The idea is that disk devices (and files such as /etc/dumpdates) are owned by root, but the group disk (on my linux box), or operator (on my freebsd one), or sys (I think, on the solaris machines) has read and write access. This means that the amanda user, who is a member of the group that you specified, can access the devices through the group membership, rather than forcing the devices to be owned by Amanda... HTH, Ricky -Original Message- From: David Flood [mailto:[EMAIL PROTECTED]] Sent: Monday 08 April 2002 9:04 AM To: [EMAIL PROTECTED] Subject: --with-group? What is the significance of the group when configuring i.e. --with- group. Does it mean whoever is in this group can run the amanda utils as well as the amanda user? - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: Amanda users does not get full access to files
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
Should I upgrade to 2.4.3b3?
Hello all. I am currently using Amanda version 2.4.2p2 without any problems. Are there any compelling reasons that I should upgrade to 2.4.3b3 since everything is working now? Thanks! Anthony
Re: Amanda users does not get full access to files
I did this already in reply to either Toomas or Don's reply but I think I only sent it to them instead of the list - Doh. Here goes: I'll use c0t0d0s0 in this example but all slices on all disk are the same in terms of ownership and permissions. ls -la /dev/dsk/c0t0d0s0 lrwxrwxrwx 1 root root 41 Apr 9 1999 /dev/dsk/c0t0d0s0 -> ../../devices/pci@1f,4000/scsi@3/sd@0,0:a ls -la /devices/pci@1f,4000/scsi@3/sd@0,0:a brw-r- 1 root sys 32, 0 Apr 9 1999 /devices/pci@1f,4000/scsi@3/sd@0,0:a Doing the same inspection for rdsk instead of dsk gives the same result except for the c instead of a b as you would expect. if I do a 'groups bin': bin sys uucp On 8 Apr 2002, at 12:15, Martin Hepworth wrote: > 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 > > > > > > > > > > > - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: Only 3 tapes in 7 tape changer gets scaned twice
It appears that the offline_before_unload switch/feature does not work in this script! Am i :-/ /gat John R. Jackson wrote: I think the following patch fixes that version. Also, there is a new copy of the whole thing at: ftp://gandalf.cc.purdue.edu/pub/amanda/chg-zd-mtx.sh.in-243 Also, could you send your chg-zd-mtx config file? I think I understand
Re: Only 3 tapes in 7 tape changer gets scaned twice
It appears that the offline_before_unload switch/feature does not work in this script! ... Insufficient details, so you get a million questions in response: Did you drop this file in place of your existing chg-zd-mtx.sh.in file (saving the original in case there is a problem)? Did you rerun ./configure, then make then make install? What did you put in your changer config file? What is in the changer log file? Why do you think it's not working? /gat John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Only 3 tapes in 7 tape changer gets scaned twice
This is far short of a million, even if its binary, questions! actually plugged it in, and linked it to ...sh.in rebuilt it ( make, not configure ) , but no install. Just cp'd the chg-zd-mtx to /usr/local/libexec. I know its there bec the old version is ~17k, and newer one is ~37k it does not work bec it does not (apparently) do a mt rewoffl before changing to the next tape. I can manually do a mt rewoffl, and then amtape confname slot 2 will work. firstslot=1 lastslot=7 cleanslot=9 havereader=0 offlinestatus=1 AUTOCLEAN=0 autocleancount=0 offline_before_unload=1 John R. Jackson wrote: It appears that the offline_before_unload switch/feature does not work in this script! ... Insufficient details, so you get a million questions in response: Did you drop this file in place of your existing chg-zd-mtx.sh.in file (saving the original in case there is a problem)? Did you rerun ./configure, then make then make install? What did you put in your changer config file? What is in the changer log file? Why do you think it's not working? /gat John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Amanda users does not get full access to files
I have not run a restore to check but last time when the symptoms were identical it was mostly directory structure taht was backed up and any files bin had access to. To try and explain that a bit more let say I had a user named bob: /export/home/staff/bob the backup tape would contain the directory structure /export/home/staff/bob/any/sub/dirs The only files it would backup would be files the user bin had access to which in staff's home areas is not a lot. On 8 Apr 2002, at 12:03, Morse, Richard E. wrote: David Flood [mailto:[EMAIL PROTECTED]] 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. Can you find out what the data that the amanda user isn't seeing is? Ricky - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: Should I upgrade to 2.4.3b3?
On 7 Apr 2002 at 8:41am, Anthony Valentine wrote I am currently using Amanda version 2.4.2p2 without any problems. Are there any compelling reasons that I should upgrade to 2.4.3b3 since everything is working now? Given that 'b' means beta... probably not. ;) Even when 2.4.3 proper comes out, there's really no compelling reason to upgrade *unless* you need any of the new features. If it ain't broke... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Only 3 tapes in 7 tape changer gets scaned twice
Interesting, the log file shows that offline_before_unload is set to 0
:-{
Storage Element 5:Full
Storage Element 6:Empty
Storage Element 7:Full
12:18:14 SLOTLIST - firstslot set to 1
12:18:14 SLOTLIST - lastslot set to 7
12:18:14 SLOTLIST - 1 2 3 4 5 6 7
12:18:15 Config info:
firstslot = 1
lastslot = 7
cleanslot = -1
cleancycle = -1
offline_before_unload = 0
unloadpause = 0
autoclean = 0
autocleancount = 99
havereader = 0
driveslot = 0
poll_drive_ready = 3
max_drive_wait = 120
John R. Jackson wrote:
It appears that the offline_before_unload switch/feature does not work
in this script! ...
What is in the changer log file?
Applying Ditial Unix advfs patch issues
I've created a file called duampatch with vi, copied the patch from the web page http://www.amanda.org/patches/2.4.2p2/advfs.diff, and pasted it into the file. When I issue: patch -p1 duampatch from the top level of the amamanda-2.4.2 tree, it just says, Hmm... I can't seem to find a patch in there anywhere. Same thing if I do a: patch -p1 -i duampatch In this case ignorance is NOT bliss. What should I be doing? Thanks, EZ
Re: Amanda users does not get full access to files
OK thanks John that's explained a lot but how would you explain (messed up index file or no) how it worked with bin as the user under 2.4.1p1? Was there something changed between 2.4.1p1 and 2.4.2p2 that would affect this? I don't want to appear to be nagging on but backups is one of the most important tasks if not the most important task a sys admin does so I'm quite keen to understand why things in amanda happen and work the way they do. On 8 Apr 2002, at 11:52, John R. Jackson wrote: The backups worked fine as bin when we were using amanda 2.4.1p1 ... You just think it was. This cannot ever have been working 100% properly. I think I maybe slipped up before when I said I'm using dump I should have said I'm using ufsdump. Same difference. I know with dump(through reading this list) it can only do 'whole' volumes but is this the case with ufsdump? Pretty much. Many dump programs will flat out refuse to do subdirectories. Some (like ufsdump) switch over to doing a different kind of backup. In the case of ufsdump, it no longer uses the raw disk device but goes through the normal file system, exactly like GNU tar. So it has the same issues of needing to be run as root. But there's more. I happen to know from helping someone else with a similar problem that the index files are not generated properly in this case, so amrecover is not going to work. So the general rule still applies -- don't use dump on anything other than a complete file system. ... it does not explain why this exact same setup works as root and worked as bin pre 2.4.2p2. It explains why it works as root (ufsdump has the permissions it needs to wander around in the directory tree). Something else had to have been going on for it to work (if it really was) earlier. However, even if you got it to back everything up, amrecover is still not going to work (if that's a problem for you). David Flood JJ - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 The Robert Gordon University School of Computing St. Andrews Street Aberdeen -
Re: Only 3 tapes in 7 tape changer gets scaned twice
This is far short of a million, even if its binary, questions! It was base 1.30766 :-). actually plugged it in, and linked it to ...sh.in rebuilt it ( make, not configure ) , but no install. Just cp'd the chg-zd-mtx to /usr/local/libexec. ... You have to run ./configure to convert chg-zd-mtx.sh.in to chg-zd-mtx.sh, then the make would create chg-zd-mtx from chg-zd-mtx.sh. Doing the install by hand (assuming you made sure it ended up +x) is fine. firstslot=1 lastslot=7 cleanslot=9 havereader=0 offlinestatus=1 AUTOCLEAN=0 autocleancount=0 offline_before_unload=1 ... Interesting, the log file shows that offline_before_unload is set to 0 I'm pretty sure it's not even processing your config file. Note that it also says cleanslot is -1, among other mismatches. I put a new version in the same place that will test to make sure the config file is available, and updated one of the messages to show which file is being processed. You can either get a new copy or I've appended the patch. /gat BTW, thanks for helping test this. I don't run mtx here (it's a long story), and testing this script has been a real adventure. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] chg-zd-mtx-configfile.diff Description: chg-zd-mtx-configfile.diff
Re: Only 3 tapes in 7 tape changer gets scaned twice
There are still some bug-a-boo's. non-amanda tape in slot 5, and loaded in tape drive. no tape in slot 6. There is an amanda tape in slot 7 issue an amcheck confname get -- [Amanda@kodak Amanda]$ amtape confname slot 5 amtape: changed to slot 5 on /dev/nst0 [Amanda@kodak Amanda]$ amcheck confname Amanda Tape Server Host Check - ERROR: holding disk /mnt/hdd4/amanda: statfs: No such file or directory ERROR: holding disk /mnt/sda1/amanda: statfs: No such file or directory amcheck-server: slot 5: not an amanda tape amcheck-server: fatal slot 6: source Element Address 8 is Empty ERROR: label AmandaFullBackup22 or new tape not found in rack (expecting tape AmandaFullBackup22 or a new tape) NOTE: skipping tape-writable test Server check took 31.128 seconds Amanda Backup Client Hosts Check WARNING: lx: selfcheck request timed out. Host down? Client check: 1 host checked in 30.002 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) [Amanda@kodak Amanda]$ -- It does not check tape 7, nor tape 1 or tape 2. If tape 7 is loaded ( AmandaFullBackup22 ), then amcheck is happy. I suppose one can mix match, but i suppose in a BIG tape changer there may be a few empty slots, and a few full ( and even some with the tapes you want to use as the backup media ). ALSO openening the changer door resets the changers idea of whats loaded in each slot. The first time i run amcheck, i get a tape error. The changer does not move. But his test would ruin one nights backup attempt! A second amcheck gets it going. [Amanda@kodak Amanda]$ amcheck confname Amanda Tape Server Host Check - ERROR: holding disk /mnt/hdd4/amanda: statfs: No such file or directory ERROR: holding disk /mnt/sda1/amanda: statfs: No such file or directory amcheck-server: could not get changer info: no slots available John R. Jackson wrote: This is far short of a million, even if its binary, questions!
Re: Amanda users does not get full access to files
... how would you explain (messed up index file or no) how it worked with bin as the user under 2.4.1p1? ... I don't think it was. I don't see any way it could have been working unless you were running it as root. Well, actually, you might have been able to configure Amanda using --with-rundump. Do you recall doing that? Was there something changed between 2.4.1p1 and 2.4.2p2 that would affect this? No. I don't want to appear to be nagging ... No problem. I'd be curious how you had it working, too. David Flood John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with index files
Problem solved, as determined by one dump having the client disks indexed so far. The issue appeared to be that the client had two IP addresses (because of a solution to another, temporary problem). Getting back to one IP address returned the indexing. Thanks for all the help, and I'll still try using that re-indexing script soon to recover the missing indices. -Adam
Re: Applying Ditial Unix advfs patch issues
I've created a file called duampatch with vi, copied the patch from the web page http://www.amanda.org/patches/2.4.2p2/advfs.diff, and pasted it into the file. ... Bad idea. Never try to copy/paste patches. There is practically zero chance it won't get messed up along the way (tabs = blanks, for instance). Use whatever your browser provides to do a save as (e.g. for Netscape on Unix it's Shift-Button1) to get the file. If that's a problem, let me know and I'll drop a copy in my ftp area. EZ John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Newbie question: amcheck - unary operator expected
Hello all,
I'm a brand new if about amanda and mtx so please don't laugh too hard at
me. I'm trying to use our old, retired HP C1553A (it was running under Novell
with Arcserve as a backup software for a few years without any major
problems) under Linux and Amanda. I have my homework done before posting to
the list - I've read a lot, I've tried a lot of different configurations but
somehow I'm missing something and can't get amanda working for me. Any
advice, suggestions would be greatly appreciated. It's not a Houston, we
have a problem situation - I just hate something lying around and doing
nothing.
Sorry for the long post and many thanks in advance.
Greg Wardawy
OK, first some infos:
OS - Redhat 7.2 with 2.4.7-10smp kernel,
Amanda 2.4.2p2-4,
mtx 1.2.13-1
and some entries from my amanda.conf file:
##
#amanda.conf
org DailySet1 # your organization name for reports
mailto amanda wardawyg# space separated list of operators at your
site
dumpuser amanda # the user to run dumps under
inparallel 4# maximum dumpers that will run in parallel
netusage 600 Kbps # maximum net bandwidth for Amanda, in KB per sec
dumpcycle 4 weeks # the number of days in the normal dump cycle
runspercycle 4 weeks# the number of amdump runs in dumpcycle days
tapecycle 25 tapes # the number of tapes in rotation
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for estimates.
runtapes 1
tpchanger chg-zd-mtx
tapedev /dev/sga
changerfile /etc/amanda/mtx-changer
changerdev /dev/sga
tapetype DAT-120m
labelstr ^DailySet1[0-9][0-9]*$
holdingdisk hd1 {
comment main holding disk
directory /var/tmp# where the holding disk is
use 290 Mb # how much space can we use on it
# a negative value mean:
#use all space except that value
#chunksize 2 Gb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split disks in chunks of size N
# 0 split disks in INT_MAX/1024 Kb chunks
# -N Kb/Mb/Gb dont split, dump larger
# filesystems directly to tape
# (example: -2 Gb)
}
infofile /var/lib/amanda/DailySet1/curinfo# database filename
logdir /var/lib/amanda/DailySet1# log directory
indexdir /var/lib/amanda/DailySet1/index # index directory
tapelist /var/lib/amanda/DailySet1/tapelist # list of used tapes
define tapetype DAT-120m {
comment DAT tape (120m tapes)
length 4000 mbytes
filemark 250 kbytes # this is an estimate
speed 512 kbytes
}
##cut#
in the mtx-changer.conf file I have:
firstslot 1
lastslot 6
gravity 0
needeject 0
multieject 0
ejectdelay 0
statefile /var/lib/amanda/DailySet1/curinfo/localhost/_etc/state
slot 1 /dev/sga
slot 2 /dev/sga
slot 3 /dev/sga
slot 4 /dev/sga
slot 5 /dev/sga
slot 6 /dev/sga
and here goes what I'm getting during the tests:
1. [root@linver wardawyg]# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: HP Model: C1553A Rev: 9608
Type: Sequential-AccessANSI SCSI revision: 02
2. [root@linver wardawyg]# mtx inquiry
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'C1553A '
Revision: '9608'
Attached Changer: No
3. [root@linver wardawyg]# mtx status
Storage Changer /dev/sga:1 Drives, 6 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 1 Loaded)
Storage Element 1:Empty
Storage Element 2:Full
Storage Element 3:Full
Storage Element 4:Full
Storage Element 5:Full
Storage Element 6:Full
4. [root@linver sbin]# ./tapeinfo -f /dev/sga
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'C1553A '
Revision: '9608'
Attached Changer: No
MinBlock:1
MaxBlock:16777215
SCSI ID: 1
SCSI LUN: 0
Ready: yes
BufferedMode: yes
Medium Type: Not Loaded
Density Code: 0x24
BlockSize: 0
DataCompEnabled: yes
DataCompCapable: yes
DataDeCompEnabled: yes
CompType: 0x20
DeCompType: 0x0
BOP: yes
Block Position: 0
5. [root@linver sbin]# ./loaderinfo -f /dev/sga
Product Type: Tape Drive
Vendor ID: 'HP '
Product ID: 'C1553A '
Revision: '9608'
Attached Changer: No
Bar Code Reader: No
EAAP: Yes
Number of Medium Transport Elements: 0
Number of Storage Elements: 6
Number of Import/Export Element Elements: 0
Number of Data Transfer Elements: 1
Transport Geometry Descriptor Page: No
Device Configuration Page: Yes
Can Transfer: No
Re: Only 3 tapes in 7 tape changer gets scaned twice
Started debugging the script ... Which version? seems like its reading the file changer.conf.conf ( non-existent file ) and reading the options from there, rather than from just changer.conf. It takes changerfile from amanda.conf (amgetconf config changerfile) and tacks on .conf to make the config file name (it even says this in the comments in the file). The changerfile value is a base name used for several files. There are still some bug-a-boo's. I need the changer debug files. However ... ... I suppose one can mix match, but i suppose in a BIG tape changer there may be a few empty slots, and a few full ( and even some with the tapes you want to use as the backup media ). One of the rules this particular changer lives by is (from the comments): # You do not have to allocate all of the slots for Amanda use, # but whatever slots you use must be contiguous (i.e. 4 through 9 # in the above would be OK but 1, 2, 5, 6, 9 would not). The one # exception to this is that if one of the slots contains a cleaning # cartridge, it may be in any slot (Amanda will just skip over it if # it is between firstslot and lastslot). Amanda expects everything between firstslot and lastslot to belong to it. In theory, it should handle empty slots, but not ones with junk (from Amanda's point of view :-). ALSO openening the changer door resets the changers idea of whats loaded in each slot. The first time i run amcheck, i get a tape error. ... Again, I need the debug files to see what the script did. /gat John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: Newbie question: amcheck - unary operator expected
Greg Wardawy [mailto:[EMAIL PROTECTED]] wrote: Amanda Backup Client Hosts Check ERROR: localhost: [access as amanda not allowed from amanda@linver] amandahostsauth failed Client check: 1 host checked in 0.020 seconds, 1 problem found Hmmm... I can't help you with the others, but here's how to check what's up with this one: # cat /etc/passwd | grep amanda-user-name here this will give you back a line, one item of which will be the home directory of the amanda user. cd to that directory. make sure that the '.amandahosts' file exists in this directory. It should be owned by your amanda user, and have at least the line: linver amanda in it.. HTH, Ricky
Re: Newbie question: amcheck - unary operator expected
I'm a brand new if about amanda and mtx so please don't laugh too hard at me. ... We never laugh at new users!!! :-) Welcome! in the mtx-changer.conf file I have: ... statefile /var/lib/amanda/DailySet1/curinfo/localhost/_etc/state slot 1 /dev/sga slot 2 /dev/sga ... Where did you get the idea behind this file? It doesn't match what chg-zd-mtx is going to want. It looks like what you might set up for chg-multi, not chg-zd-mtx. amcheck-server: could not get changer info: badly formed result from changer: /usr/lib/amanda/chg-zd-mtx: [: -eq: This came up a while back but I can't find it in my archives. This script has had a major overhaul for the next release. Would you mind trying it instead? You can get it at: ftp://gandalf.cc.purdue.edu/pub/amanda/chg-zd-mtx.sh.in-243 To install it: cd changer-src Save your current chg-zd-mtx.sh.in Copy the new file in as chg-zd-mtx.sh.in cd .. ./configure ... make cd changer-src make install You might want to take a look at the script itself. It starts out with a lengthy set of comments about how to set it up. What am I missing here? I'm sure it's something about your config file and a variable in the (old) script that's not set where it should be. If you don't want to try the new version (which is fine), I think the following might be better: firstslot=1 lastslot=6 Even in the old script there is a block of comments about the format of the config file. Just make sure you throw away all the lines you don't need (it doesn't handle comments) and put keyword=value entries in exactly like it says (the new version tries to be a bit more tolerant). Greg John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
sanity check, please
I've got a server farm of about 30 machines, most on various RedHat distributions, a few AIX. I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes. I have 10 physical backup tapes available for each drive. The tape drives are attached to 3 linux computers, Columbia, Frith Coffee, respectively, which have Amanda 2.4.1p1 servers. All the clients are running either 2.4.1p1 or 2.4.2p2 . I have created a configuration directory for each server in /var/lib/amanda and a disklist which has the clients and partitions for each item to be backed up by the respective server. When I analyze the existing space used by the clients, I find that each server is subscribed for between 100 and 180% of the capacity of an individual tape. Questions: - is this a sane configuration? - is this a better configuration than throwing 3 tape drives on 1 amanda server? - is this a better configuration than just using 1 tape drive on 1 amanda server (the 40, obviously) and using more tapes? - what would you recommend for the way to ease into backing up this lot? i.e. uncomment 1/2 of the disklist descriptions the first night, 1/2 the second, or 1/4 the first, for 4 days... or ??? -- John Rodkey, Information Technology, Westmont College [EMAIL PROTECTED]
Re: sanity check, please
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote: I've got a server farm of about 30 machines, most on various RedHat distributions, a few AIX. I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes. I have 10 physical backup tapes available for each drive. The tape drives are attached to 3 linux computers, Columbia, Frith Coffee, respectively, which have Amanda 2.4.1p1 servers. All the clients are running either 2.4.1p1 or 2.4.2p2 . I have created a configuration directory for each server in /var/lib/amanda and a disklist which has the clients and partitions for each item to be backed up by the respective server. When I analyze the existing space used by the clients, I find that each server is subscribed for between 100 and 180% of the capacity of an individual tape. Questions: - is this a sane configuration? - is this a better configuration than throwing 3 tape drives on 1 amanda server? - is this a better configuration than just using 1 tape drive on 1 amanda server (the 40, obviously) and using more tapes? - what would you recommend for the way to ease into backing up this lot? i.e. uncomment 1/2 of the disklist descriptions the first night, 1/2 the second, or 1/4 the first, for 4 days... or ??? You didn't specify why you might want to be using the 2 smaller tape drives -- other than the drives are there and feel guilty about them gathering dust ;) However, if you can get more 40Gb tapes, using a single drive would probably be the easiest route for you to go. As for the distlist, you can do that or just let a few fail for the first few days while Amanda adjusts to it's schedule. Sane? I wouldn't make a judgement on what is and isn't sane. You might as well ask about vi vs emacs, bash vs tcsh ~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~
Re: sanity check, please
On Mon, 8 Apr 2002, Doug Silver wrote: On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote: I've got a server farm of about 30 machines, most on various RedHat distributions, a few AIX. I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes. I have 10 physical backup tapes available for each drive. The tape drives are attached to 3 linux computers, Columbia, Frith Coffee, respectively, which have Amanda 2.4.1p1 servers. All the clients are running either 2.4.1p1 or 2.4.2p2 . Questions: - is this a sane configuration? - is this a better configuration than throwing 3 tape drives on 1 amanda server? - is this a better configuration than just using 1 tape drive on 1 amanda server (the 40, obviously) and using more tapes? - what would you recommend for the way to ease into backing up this lot? i.e. uncomment 1/2 of the disklist descriptions the first night, 1/2 the second, or 1/4 the first, for 4 days... or ??? You didn't specify why you might want to be using the 2 smaller tape drives -- other than the drives are there and feel guilty about them gathering dust ;) Ah, guilt has something to do with it, but another factor is bandwidth and spreading out the load... And I was thinking, Let's put all the technical configuration data like /etc, /boot, and so on to be backed up by one server, and the mail to another, and users' files to a third... so it wouldn't be difficult to figure out which server to go to for a restore. Plus, we already have the tapes for the other drives... vs. buying new tapes for the 40Gb at $20 a pop. We have been having problems because the users' files and the mail files exceed the capacity of a single 40 Gig tape, so we can't seem to get it to do an initial backup of those filesystems to complete. One or the other, but not both. However, if you can get more 40Gb tapes, using a single drive would probably be the easiest route for you to go. As for the distlist, you can do that or just let a few fail for the first few days while Amanda adjusts to it's schedule. Sane? I wouldn't make a judgement on what is and isn't sane. You might as well ask about vi vs emacs, bash vs tcsh Right... maybe I should have said Do you think this is a workable idea? and then, How do you rate it compared to a single host backup? My sanity is often called into question... John ~~ Doug Silver Network Manager Urchin Corporationhttp://www.urchin.com ~~ -- John Rodkey, Information Technology, Westmont College [EMAIL PROTECTED]
Re: sanity check, please
On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote: On Mon, 8 Apr 2002, Doug Silver wrote: On Mon, 8 Apr 2002 [EMAIL PROTECTED] wrote: I've got a server farm of about 30 machines, most on various RedHat distributions, a few AIX. I have 3 tape drives, an 8, a 24 and a 40Gig, all HP DAT tapes. I have 10 physical backup tapes available for each drive. The tape drives are attached to 3 linux computers, Columbia, Frith Coffee, respectively, which have Amanda 2.4.1p1 servers. All the clients are running either 2.4.1p1 or 2.4.2p2 . Questions: - is this a sane configuration? - is this a better configuration than throwing 3 tape drives on 1 amanda server? - is this a better configuration than just using 1 tape drive on 1 amanda server (the 40, obviously) and using more tapes? - what would you recommend for the way to ease into backing up this lot? i.e. uncomment 1/2 of the disklist descriptions the first night, 1/2 the second, or 1/4 the first, for 4 days... or ??? You didn't specify why you might want to be using the 2 smaller tape drives -- other than the drives are there and feel guilty about them gathering dust ;) Ah, guilt has something to do with it, but another factor is bandwidth and spreading out the load... And I was thinking, Let's put all the technical configuration data like /etc, /boot, and so on to be backed up by one server, and the mail to another, and users' files to a third... so it wouldn't be difficult to figure out which server to go to for a restore. Plus, we already have the tapes for the other drives... vs. buying new tapes for the 40Gb at $20 a pop. We have been having problems because the users' files and the mail files exceed the capacity of a single 40 Gig tape, so we can't seem to get it to do an initial backup of those filesystems to complete. One or the other, but not both. That makes sense, though if you're already breaking up partitions with gtar, that might allow you some flexibility with the user/mail files. You could make an exclude list and have two mail and two user partitions. You could set it up this way with the intention of moving everything towards the 40Gb drive in the future once money becomes a bit easier to justify. With ~30 clients, you'll have to figure out the total capacity it would take if you wanted to back everything up and how many tapes that would take on your dumpcycle. Right... maybe I should have said Do you think this is a workable idea? and then, How do you rate it compared to a single host backup? My sanity is often called into question... John It seems reasonable that you're going to have to go this route based on your current resources. While I'd love to have the latest AIT or tape jukebox, DDS4 is working just fine and I have no choice (or desire) to change in the near future. Good luck! -- ~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~
Re: sanity check, please
In addition to the comments Doug made, I just want to remind you that a given Amanda client can only be in one configuration at a time. For instance, you will not be able to put clientA:/etc in the configuration run by the small tape drive machine and clientA:/home in the large tape drive machine. At some point both will try to contact the client, one will win and the other will not be happy. There is a way around this (alternate Amanda port numbers). If you really need to do it this way, let me know and I'll make the patch available. - is this a sane configuration? Other than the above, and given your comments about spreading the load, I don't see anything wrong with it. - what would you recommend for the way to ease into backing up this lot? You could either comment out some of the entries, as you said, and add them in a few at a time. Or you could just turn it all loose and let Amanda sort it all out, which will take a few runs, but it's going to take a few runs anyway. John Rodkey John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: GFS-rotation scheme with amanda
There are 4 day-tapes day1-day4 which are used every week from Monday to Thursday in rotation, so only the tape with the oldest data is overwritten. It would be a good idea to get out of the habit of associating specific tapes with specific days. Amanda will always use the oldest tape. If you miss a day, or have to use two tapes in a day (e.g. a flush and a normal run), it's still using the oldest tape, which is what you really want anyway. My idea was to create 3 amanda tape sets: day: dumpcycle 0, runspercycle 1 day ???, tapecycle 4 tapes week: dumpcycle 0, runspercycle 1 day ???, tapecycle 5 tapes month: dumpcycle 0,runspercycle 1 day ???, tapecycle 999 tapes Leave runspercycle alone. Doing full dumps all the time means you don't need it. In addition to dumpcycle 0, you should also set: strategy noinc skip-incr yes This will be even more emphatic to Amanda that you only want to do full dumps, and will also reduce the time it takes to do estimates. Would this configuration work as I described above? As far as you've described, it seems OK. Another problems could be public holidays. Would it be save to just not call amdump at this days? ... Yes. Would amanda be upset and confuse the rotation-cycle(not overwrite the oldest tape)? No. It will always use the oldest tape. BTW, is it possible to browse through all index databases on the server with amrecover or is it mandantory to specify exactly one? Not sure what you mean. There are amrecover commands to change the host (client) and disk as well as the date, so I would think those would let you move around pretty much wherever you wanted to go. Georg John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: vmlinux in boot does not restore
The file vmlinuz-2.4.2 in the boot directory does not seem to be backed up correctly. If I use dump on the partition and then restore I get 'end-of-input encounted while extracting ./vmlinuz-2.4.2-2' I assume what you mean is you told Amanda to use dump, right? Amanda pretty much just manages whatever image the dump program (be it dump or GNU tar) gives it. It would be next to impossible for Amanda to cause a particular file to misbehave (unless it happens to be at the same place in the dump image). The first thing I'd do is see if one of the dump programs is having trouble before throwing Amanda into the mix. Do a dump (or GNU tar) of the boot directory to a temp area, then cd someplace and do the restore and see what you get back. In the case of dump, the appropriate (what Amanda does) command would be something like this: dump 0f - /boot | cat /some/temp/area/boot.d GNU tar is a bit more complicated, but this should be close enough for a first test: cp /dev/null /tmp/xxx gtar --create --file - --directory /boot --one-file-system \ --listed-incremental /tmp/xxx \ --sparse --ignore-failed-read --totals . | cat /some/temp/area/boot.d Yes, I really mean that silly cat step :-). It more closely mimics how the command is run in the Amanda pipeline. Warrren John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Newbie question: amcheck - unary operator expected
On Monday 08 April 2002 16:46, you wrote: I'm a brand new if about amanda and mtx so please don't laugh too hard at me. ... We never laugh at new users!!! :-) That's what I was thinking but, actually, I don't mind if somebody wants to laugh at me if at the same time I can learn something. in the mtx-changer.conf file I have: ... statefile /var/lib/amanda/DailySet1/curinfo/localhost/_etc/state slot 1 /dev/sga slot 2 /dev/sga ... Where did you get the idea behind this file? It doesn't match what chg-zd-mtx is going to want. It looks like what you might set up for chg-multi, not chg-zd-mtx. Well, I found it somewhere on the Net, can't recall where and that was before I found the information about mtx. It looked right to me so I placed everything from my old changer.conf into the mtx-changer.conf having no idea what I should have in my changer config file. You can get it at: ftp://gandalf.cc.purdue.edu/pub/amanda/chg-zd-mtx.sh.in-243 To install it: cd changer-src Save your current chg-zd-mtx.sh.in Copy the new file in as chg-zd-mtx.sh.in cd .. ./configure ... make cd changer-src make install I got it. Thanks a lot. I'll install it first thing tomorrow morning. You might want to take a look at the script itself. It starts out with a lengthy set of comments about how to set it up. Wow! This script is great! What a gold mine! Even in the old script there is a block of comments about the format of the config file. Just make sure you throw away all the lines you don't need (it doesn't handle comments) and put keyword=value entries in exactly like it says (the new version tries to be a bit more tolerant). I'm sorry I'm a bit confused here. Do I need to remove all unnecessary lines from the chg-zd-mtx.sh file or from the mtx-changer.conf file? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks a lot again, I really appreciate your help. Greg
