Long numbers running together in amanda output
Hi, our dumps are quite big, so I quite often get reports like kanga//brain/sw$ 0 3201994027473728 85.8 356:551282.9 82:075576.2 keaton /home 4 18812151273856 67.7 35:41 595.1 8:442429.1 ^ As you can imagine this is quite difficult to read ;-) Where would I have to patch amanda to produce a better readable output? Has anyone already written a different format line? Thanks, Christopher -- == Dipl.-Ing. Christopher Odenbach HNI Rechnerbetrieb [EMAIL PROTECTED] Tel.: +49 5251 60 6215 ==
Re: problem with ACLs
On Tue, 2 Jul 2002 09:53:54 +0200 Guillaume Roger [EMAIL PROTECTED] wrote: Hi, I have to save Windows (NTFS) files, but it seems that Amanda doesn't keep the ACLs. Does someone know if there is a mean to do that, or is it definitly not possible? thanks Guillaume Hi! Search in Sourceforge for amanda client Win32. It is the Linux client adapted to Windows NT stuff, it can back up Windows files natively, so with the ACLs also! Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Operations phone: (+33)492283200 (standard) Sophia Antipolis, France
Problems with amanda
Hello everybody, i am having problems with amanda. I have installed amanda-2.4.2p2.rpm and amanda-server-2.4.2p2.rpm that came with Red Hat 7.2. I am unable to make this work. When i run amverify command i get this error: bash-2.05$ /usr/sbin/amverify Diaria Tape changer is chg-scsi... 1 slot... System restore program not found: /sbin/restore Verify summary to [EMAIL PROTECTED] Defects file is /tmp/amanda/amverify.17519/defects amverify Diaria vie jun 28 09:43:59 CEST 2002 Loading current slot... ** Error loading slot current amtape: could not load slot chg-scsi:: chg.conf[0] == NULL Advancing past the last tape... ** Error advancing after last slot amtape: could not load slot chg-scsi:: chg.conf[0] == NULL Errors found: amtape: could not load slot chg-scsi:: chg.conf[0] == NULL amtape: could not load slot chg-scsi:: chg.conf[0] == NULL bash-2.05$ rpm -qif amanda error: file amanda: No existe el fichero o el directorio bash-2.05$ exit logout My tape device is a HP-Surestore DDS4 20G, i have already run the tapetype command and i put the values in the amanda.conf file. This device is in /dev/st0, but when i run the amadmin command whith the version option the program says that my DEFAULT_TAPE_DEVICE=/dev/null. Does anybody knows what can I do?, Thanks a lot. Regards. Víctor Guerra. [EMAIL PROTECTED]
Re: amanda 2.5.0 / autoconf
Hi, yes i've seen this message, not with amanda, but with some other package under linux, but i guess you have'nt installed automake, have you? if it is installed, try upgrading it to a newer version. then rerun autoconf and retry. After that the error went away for me. Christoph JC Simonetti wrote: Hi all! I have a pretty tricky issue with autoconf and Amanda 2.5.0 from the Sourceforge CVS. In fact, when I give my configure.in file to autoconf, I have a warning, and when I run my new configure I craches after 5 lines :( This is a paste of my console: # autoconf configure.in:1782: warning: AC_TRY_RUN called without default to allow cross compiling # ./configure loading cache ./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking cached system tuple... ok ./configure: line 786: syntax error near unexpected token `AM_INIT_AUTOMAKE(amanda,' ./configure: line 786: `AM_INIT_AUTOMAKE(amanda, 2.5.0)' Well... I'm not very familiar to autoconf. Has anyone already seen that? Thanks a lot. Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Operations phone: (+33)492283200 (standard) Sophia Antipolis, France
Re: amanda 2.5.0 / autoconf
Yep, you're right. I forgot automake and libtool :( Now it seems better. I learned I had to run aclocal, autoconf, automake. Now it crashes a bit later with: ./configure: line 11816: syntax error near unexpected token `ICE_CHECK_DECL(accept,sys/types.h' ./configure: line 11816: `ICE_CHECK_DECL(accept,sys/types.h sys/socket.h)' Well... Seems I'm not lucky this day :( Thanks! On Tue, 02 Jul 2002 11:33:14 +0200 Christoph Scheeder [EMAIL PROTECTED] wrote: Hi, yes i've seen this message, not with amanda, but with some other package under linux, but i guess you have'nt installed automake, have you? if it is installed, try upgrading it to a newer version. then rerun autoconf and retry. After that the error went away for me. Christoph JC Simonetti wrote: Hi all! I have a pretty tricky issue with autoconf and Amanda 2.5.0 from the Sourceforge CVS. In fact, when I give my configure.in file to autoconf, I have a warning, and when I run my new configure I craches after 5 lines :( This is a paste of my console: # autoconf configure.in:1782: warning: AC_TRY_RUN called without default to allow cross compiling # ./configure loading cache ./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking cached system tuple... ok ./configure: line 786: syntax error near unexpected token `AM_INIT_AUTOMAKE(amanda,' ./configure: line 786: `AM_INIT_AUTOMAKE(amanda, 2.5.0)' Well... I'm not very familiar to autoconf. Has anyone already seen that? Thanks a lot. Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Operations phone: (+33)492283200 (standard) Sophia Antipolis, France
Re: Long numbers running together in amanda output
On Tue, 2 Jul 2002, Christopher Odenbach wrote: our dumps are quite big, so I quite often get reports like kanga//brain/sw$ 0 3201994027473728 85.8 356:551282.9 82:075576.2 keaton /home 4 18812151273856 67.7 35:41 595.1 8:442429.1 See the comments in your amanda.conf. -Mitch
Re: amanda 2.5.0 / autoconf
Hi, seems like one of your auto-tools doesnt't recognise this tocken and doesn't process it correct. i would double chek all these tools are the most recent available. (if necesarry install them from source) if that doesn't help, go to amanda-hackers and ask there for help. Christoph PS: you know you are compiling the bleeding-edge development-version of amanda, which isn't supposed to be stable nor compileable all the time, do you? JC Simonetti wrote: Yep, you're right. I forgot automake and libtool :( Now it seems better. I learned I had to run aclocal, autoconf, automake. Now it crashes a bit later with: ./configure: line 11816: syntax error near unexpected token `ICE_CHECK_DECL(accept,sys/types.h' ./configure: line 11816: `ICE_CHECK_DECL(accept,sys/types.h sys/socket.h)' Well... Seems I'm not lucky this day :( Thanks! On Tue, 02 Jul 2002 11:33:14 +0200 Christoph Scheeder [EMAIL PROTECTED] wrote: Hi, yes i've seen this message, not with amanda, but with some other package under linux, but i guess you have'nt installed automake, have you? if it is installed, try upgrading it to a newer version. then rerun autoconf and retry. After that the error went away for me. Christoph JC Simonetti wrote: Hi all! I have a pretty tricky issue with autoconf and Amanda 2.5.0 from the Sourceforge CVS. In fact, when I give my configure.in file to autoconf, I have a warning, and when I run my new configure I craches after 5 lines :( This is a paste of my console: # autoconf configure.in:1782: warning: AC_TRY_RUN called without default to allow cross compiling # ./configure loading cache ./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking cached system tuple... ok ./configure: line 786: syntax error near unexpected token `AM_INIT_AUTOMAKE(amanda,' ./configure: line 786: `AM_INIT_AUTOMAKE(amanda, 2.5.0)' Well... I'm not very familiar to autoconf. Has anyone already seen that? Thanks a lot. Jean-Christian SIMONETTIemail: [EMAIL PROTECTED] SysAdmin Wanadoo Operations phone: (+33)492283200 (standard) Sophia Antipolis, France
Re: Problems with amanda
On Tuesday 02 July 2002 04:18, Víctor Guerra wrote: Hello everybody, i am having problems with amanda. I have installed amanda-2.4.2p2.rpm and amanda-server-2.4.2p2.rpm that came with Red Hat 7.2. The majority opinion of those on this list is that any rpm's for amanda probably should be subjected to an intentional rm -f, they rarely, very rarely, will fit the individual users individual system, leaving out many vital steps such as adding a user amanda and makeing her a member of group disk for instance. Generally speaking, making an rpm installation work is going to be 10x more difficult than making a home built install work. There isn't enough docs to describe the rpm's default configuration so you can either make your system match the one the rpm was built on, or give up in a morass of error messages. First, as root, if you haven't already done so, use linuxconf to add a user amanda and then make her a member of group disk. You would be far better off to get the latest 2.4.3b3 snapshot, dated June 10th from: http://www.iro.umontreal.ca/~martinea/amanda/ then become root, cd to /home/amanda and unpack it, then do #tar xzvf /path/to/where/you/downloaded/it/amanda-2.4.3b3-20020610 and # chown -R amanda:disk amanda-2.4.3b3-20020610 then become user amanda # su amanda # cd /home/amanda/amanda-2.4.3b3-20020610 and write a script so you can do it exactly the same each time you configure a fresh amanda install. I call mine gh.cf, so the command line then is #./gh.cf and configure will be run. Your script should look *something* like this: -- #!/bin/sh make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld \ --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=192.168.1.3 \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda -- remove the changer-device= line if you aren't using a changer (you aren't), and modify the ip address of the machine which is the tape-server to suit. Now do # make When thats done, exit back to user root and # exit # make install By doing it as user amanda until the install stage, all the permission problems will go away and you are then ready to run, as user amanda, #amcheck /configname/ repeatedly, doing mkdirs to fix missing directories, and touches to make missing files until its happy. First however, you will need to generate a customized amanda.conf in /usr/local/etc/amanda/configname to control some of its options, and generate a disklist in that same directory telling amanda what you want to backup and how you want it backed up. Start out small there because as you get it figured out, then adding the rest of the systems is relatively easy. I'm partial to using tar here as dump doesn't do excludes and I need them, but to use it, a useable tar of version 1.13-19 or higher must be already installed on your system at the time the configure script is run as its path becomes hard coded into amanda at that time. Do NOT use the drives compression as it hides the true capacity of the drive from amanda and leads to more problems than its worth. Besides that, software compression is usually quite a bit better than the drives simple RLL-2-7 method. But do use a compression in the disklist, until you see in the email report sent to the user specified in amanda.conf, a compression rate thats greater than 100% for a given partition. If you see that, re-edit the dumptype for that partitions listing in the disklist file so it will not use a compressed format. Std. Disclaimer: I've no doubt left out something very important. I'm not one of the authors, just a user trying to take on a wee a bit of the qa load. But thats what this list is all about, asking good questions and getting (hopefully) good answers to fill in the blanks. We are all new bees once... Follow the above menu to install it, and come back to this list with the next question(s) after, someone will probably have experience in the area of your question and be able to answer it. Once up and running, amanda is a good, dependable servant-wench. [snip errors, looks like typical rpm bad install] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: permission problem
On Mon, 1 Jul 2002 at 3:31pm, Soo Hom wrote I am getting this error on a new client I added: Amanda Backup Client Hosts Check ERROR: song3: [can not access /dev/rdsk/c0t0d0s7 (c0t0d0s7): Permission denied] You need to make sure that the amanda user has read permissions on those devices (or belongs to a group that does). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: help with tape drive
Also Sprach cwhite: i need a little help with my new tape drive i used to have an internal travan tape drive, scsi, which showed up as /dev/st0, i recently aquired an external dds3 drive, sony sdt-9000, so i took my internal drive out of the system and plugged the dds drive into it when linux boot's there is no problem finding the drive, it show up between my hard drives the first hard drive is id 0, /dev/sda 2nd hard drive is id 2, /dev/sdb 3rd hard drive is id 4, /dev/sdc sony sdt tape drive is id 6, no device is given here 4th hard drive is id 10, /dev/sdd i am running redhat 7.0 with kernel 2.2.16 I'd upgrade the distribution since Redhat 7.0 is notoriously buggy. At the very least make sure your kernel has the patch to fix the POSIX capabilities hole. any help or pointer as to where i can find a solution to my problem would be greatly appreciated thx The SDT9000 is a narrow device, I noticed that you have it on a wide bus. Is it the last device in the chain and are the 18 pins properly terminated? Also check the drive jumpers, sometimes you need to fiddle with them depending on the SCSI bus and OS. C. Chan [EMAIL PROTECTED]GPG Public Key registered at pgp.mit.edu Your Pithy Aphorism Here! Or finger [EMAIL PROTECTED]
Re: help with tape drive
On Tuesday 02 July 2002 09:59, C. Chan wrote: Also Sprach cwhite: i need a little help with my new tape drive i used to have an internal travan tape drive, scsi, which showed up as /dev/st0, i recently aquired an external dds3 drive, sony sdt-9000, so i took my internal drive out of the system and plugged the dds drive into it when linux boot's there is no problem finding the drive, it show up between my hard drives the first hard drive is id 0, /dev/sda 2nd hard drive is id 2, /dev/sdb 3rd hard drive is id 4, /dev/sdc sony sdt tape drive is id 6, no device is given here 4th hard drive is id 10, /dev/sdd i am running redhat 7.0 with kernel 2.2.16 I'd upgrade the distribution since Redhat 7.0 is notoriously buggy. At the very least make sure your kernel has the patch to fix the POSIX capabilities hole. any help or pointer as to where i can find a solution to my problem would be greatly appreciated thx The SDT9000 is a narrow device, I noticed that you have it on a wide bus. Is it the last device in the chain and are the 18 pins properly terminated? Gaaccckk! I missed that id=10 that was the trigger for a wide buss presence. Glad you caught that. In this case it would have to have the top half of the data buss terminated at the adaptor that brings the cable width down to a 50 pin plug or the whole buss may go away in an errant write, possibly taking the drive addressed at the time with it in terms of file system integrity. Some cards are switchable in that regard, so it may be possible to share a rear panel hidens 50 with an internal 68 pin by turning on the internal terms only for the top half of the buss. I'd certainly investigate it in any event as its cheaper than all those terms and adaptors. Also check the drive jumpers, sometimes you need to fiddle with them depending on the SCSI bus and OS. C. Chan [EMAIL PROTECTED]GPG Public Key registered at pgp.mit.edu Your Pithy Aphorism Here! Or finger [EMAIL PROTECTED] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: AGAIN amrecover: file is not on Volume
Is there a /tmp/amanda/amidxtaped.*.debug file with a matching date/time? What does it say? Does /usr/sbin/ufsrestore exist and is executable? On Tue, 2002-07-02 at 00:20, BRINER Cedric wrote: hi, I've tried amrecover without the -d switch without success, I've checked the amrecover file and it looks fine to me: amrecover: debug 1 pid 22930 ruid 0 euid 0 start time Tue Jul 2 09:30:36 2002 amrecover: stream_client: connected to 129.194.65.9.10082 amrecover: stream_client: our side is 0.0.0.0.558 add_dir_list_item: Adding 2002-07-02 1 DailySet36 /. add_dir_list_item: Adding 2002-07-02 1 DailySet36 /TT_DB/ add_dir_list_item: Adding 2002-07-02 1 DailySet36 /bartho/ : add_dir_list_item: Adding 2002-06-27 0 DailySet34 /bartho/system/sysinfo/whichmg add_glob (Disques) - ^Disques$ add_file: Looking for Disques[/]*$ add_file: Converted path=Disques[/]*$ to path_on_disk=\/bartho\/system\/sysinfo/Disques[/]*$ add_file: Pondering ditem-path=/bartho/system/sysinfo/. : add_file: Pondering ditem-path=/bartho/system/sysinfo/Disques add_file: (Successful) Added /bartho/system/sysinfo/Disques add_file: Pondering ditem-path=/bartho/system/sysinfo/Juin2001/ : add_file: Pondering ditem-path=/bartho/system/sysinfo/updatedb add_file: Pondering ditem-path=/bartho/system/sysinfo/whichmg amrecover: stream_client: connected to 129.194.65.9.10083 amrecover: stream_client: our side is 0.0.0.0.603 amrecover: try_socksize: receive buffer size is 65536 Started amidxtaped with arguments 6 -h -p /dev/rmt/0cbn obssb1 ^/export/diskA1$ 20020627 Exec'ing /usr/sbin/ufsrestore with arguments: restore xbf 2 - /bartho/system/sysinfo/Disques amrecover: pid 22930 finish time Tue Jul 2 09:51:04 2002 So.. no special information here !!! Try amrecover without the -d switch. Also, have you looked at your /tmp/amanda/amrecover.*.debug files for clues? Anthony On Mon, 2002-07-01 at 00:19, BRINER Cedric wrote: hi, I'm using amanda for a while (about a year now), and I get this strange output telling me that amrecover cannot retrieve the file on the tape amrecover DailySet -t atalante -s atalante -d /dev/rmt/0cbn : : amrecover ls 2002-06-20 . 2002-06-13 .smhist 2002-06-20 Alarm_T.txt 2002-06-13 All_Ports 2002-06-13 Disques amrecover add Disques Added /bartho/system/sysinfo/Disques amrecover extract Extracting files using tape drive /dev/rmt/0cbn on host atalante. The following tapes are needed: DailySet22 Restoring files into directory /unige/amanda/sbin Continue? [Y/n]: Y Load tape DailySet22 now Continue? [Y/n]: y-this step to here took only about 10 secs !! | V ./bartho/system/sysinfo/Disques is not on volume set owner/mode for '.'? [yn] y Because I was really needing this file, I've started to look how the tape's file are assembled and figured out how to get THE file. Which I firstly not found through amrecover!!! And I finally recover the file manually...so the file that I was looking for was back up onto the tape !! Amrecover should then find it !! I'm quite surprised that amrecover define that the file is not present on the tape after only --10secs-- when usually it took much more time. I've checked more than twice the argument given to amrecover DailySet -t atalante -s atalante -d /dev/rmt/0cbn In addition, I've discovered that amrestore can only work well, if I place the DailySetTape at the right position by repeating this command: mt -f /dev/rmt/0cbn fsf 1; dd bs=32k if=/dev/rmt/0cbn of=/tmp/qq ; head /tmp/qq until I felt on the desired tuple host,disk... So I'm feeling that the problem come from amrestore more than amrecover... any idea of what I'm doing wrong !!! Thanks in advance Briner /tmp/amanda/amidx...debug amidxtaped: debug 1 pid 577 ruid 0 euid 0 start time Thu Jun 27 13:41:22 2002 amidxtaped: version 2.4.2p2 SECURITY USER root bsd security: remote host atalante user root local user root amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/rmt/0cbn obssb1 ^/export/diskA1$ 20020613 Ready to execv amrestore with: path = /unige/amanda/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = /dev/rmt/0cbn argv[4] = obssb1 argv[5] = ^/export/diskA1$ argv[6] = 20020613 amrestore: 0: skipping start of tape: date 20020613 label DailySet22 amrestore: 1: restoring obssb15._export_diskA1.20020613.2 amidxtaped: amrestore terminated normally with status: 0 Rewinding tape: done amidxtaped: pid 577 finish time Thu Jun 27 13:42:10 2002 -- * * * -- **--- * :( BRINER Cédric* o + Observatory of Geneva, Switzerland .:oO0Oo:. cedricîbriner@obsóunigeùch* * o ( ^---
Unable to connect to host
I am in the process of setting up amanda 2.4.3b3 for a tapeless backup on a Redhat 7.2
server. As a test, I am trying to backup the amanda server to itself. Unfortunately,
it is unable to connect. When I configured amanda, I set it up to not use the
.amandahosts file. I am able to rsh to server from the server as the user amanda so
the problem is not .rhosts or hosts.equiv files and it is able to resolve the host
name.
When I run amcheck, here is the error message I receive:
Amanda Backup Client Hosts Check
WARNING: toast.pcf.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
(brought to you by Amanda 2.4.3b3)
I have added a .amandahosts file in case it was trying to use it:
/home/amanda/.amandahosts
toast amanda
localhost amanda
osiris amanda
Here is the relevant file for the xinetd configuration:
/etc/xinetd.d/amanda
service amanda
{
socket_type = dgram
wait = yes
protocol = udp
user = amanda
groups = yes
server = /usr/amanda/backup/libexec/amandad
disable = no
}
Any suggestions would be greatly appreciated.
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
Re: Unable to connect to host
Forget about the .amandahosts file for now, you're not getting that far.
Try restarting xinetd, either a stop/start or kill -USR2. Sending a HUP
just makes xinetd write a state file and doesn't reread its config.
Make sure the amanda line is in /etc/services.
Also check /tmp/amanda/selfcheck.*.debug for errors.
Frank
--On Tuesday, July 02, 2002 09:03:34 -0700 Dean Lambourn [EMAIL PROTECTED] wrote:
I am in the process of setting up amanda 2.4.3b3 for a tapeless backup on a Redhat
7.2 server. As a test, I am trying to backup the amanda server to itself.
Unfortunately, it is unable to connect. When I configured amanda, I set it up to not
use the
.amandahosts file. I am able to rsh to server from the server as the user amanda so
the problem is not .rhosts or hosts.equiv files and it is able to resolve the host
name.
When I run amcheck, here is the error message I receive:
Amanda Backup Client Hosts Check
WARNING: toast.pcf.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
(brought to you by Amanda 2.4.3b3)
I have added a .amandahosts file in case it was trying to use it:
/home/amanda/.amandahosts
toast amanda
localhost amanda
osiris amanda
Here is the relevant file for the xinetd configuration:
/etc/xinetd.d/amanda
service amanda
{
socket_type = dgram
wait = yes
protocol = udp
user = amanda
groups = yes
server = /usr/amanda/backup/libexec/amandad
disable = no
}
Any suggestions would be greatly appreciated.
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
--
Frank Smith[EMAIL PROTECTED]
Systems Administrator Voice: 512-374-4673
Hoover's Online Fax: 512-374-4501
Re: Long numbers running together in amanda output
Joshua - Is this for a particular rev of Amanda, i.e. will this work in 2.4.2p2? Thanks! On Tue, 2 Jul 2002, Joshua Baker-LePain wrote: On Tue, 2 Jul 2002 at 9:07am, Christopher Odenbach wrote kanga//brain/sw$ 0 3201994027473728 85.8 356:551282.9 82:075576.2 keaton /home 4 18812151273856 67.7 35:41 595.1 8:442429.1 ^ As you can imagine this is quite difficult to read ;-) Where would I have to patch amanda to produce a better readable output? You don't need a patch. Has anyone already written a different format line? Look for columnspec in amanda.conf. Here's one I use that stays under 80 columns (it's 79, I think): columnspec OrigKB=1:8,OutKB=1:8,DumpRate=1:7,TapeRate=1:6 -- ~~ Doug Silver Network Manager Urchin Software Corp. http://www.urchin.com ~~
Re: Long numbers running together in amanda output
On Tue, 2 Jul 2002 at 10:23am, Doug Silver wrote Is this for a particular rev of Amanda, i.e. will this work in 2.4.2p2? AFAIK, it should work for all current releases. I'm using 2.4.2p2, fwiw. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Long numbers running together in amanda output
On Tue, Jul 02, 2002 at 10:23:46AM -0700, Doug Silver wrote: Joshua - Is this for a particular rev of Amanda, i.e. will this work in 2.4.2p2? Thanks! Look for columnspec in amanda.conf. Here's one I use that stays under 80 columns (it's 79, I think): Should be pretty easy to look, as suggested, and see if it is in there; possibly commented out. Hint, its in there. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
How to restore unknown tapes
Hello all, I have a complete amanda generated backup consisting of eight daily1-8 tapes (SLR100). Now I need to look into these tapes. How do I do that? Alternatively I could also restore the complete set, I have enough space. I have no idea how to use amanda, all quick attempts ended up in missing log files. I only have the tapes, nothing else. Any help appreciated (I won't dive deep into amanda, I just want to restore the data) Best regards, -Harry
Travan, DAT, Tape Changers?!?!?!?
Michael C. Robinson There are many types of tape drives, how does one sort through all the options available on E-Bay lately ? Which tapes drives are in good condition and which aren't ? What is the quality of the various tape drive technologies ? If I wanted an 8 gig TR-4 for example or better yet a drive that can handle 10-24 gigs on a single tape what is the best way to narrow one down ? Price is a big issue, that's why I am looking at tape drives that can backup the systems I'm running even though they won't have as much capacity as the harddrives those systems are installed to. I have heard that VXA is the ultimate because the tapes can take coffee immersion, is TR-4 still better for backup use than ATA-100? What do TR-4 tapes cost ? For how long will the TR-4 tapes be available since everyone seems to be atempting to get rid of theirs ? What tape drives should be avoided other than the under 8 gig models ? When do you buy bigger tape drives verses partition your harddisks into smaller chunks and back up the data to harddisk(s)/CD=R while the system still goes out to tape ? TR-4 drives seem to be acquirable in the $35-$50 range, has anyone tried to stripe multiple tape drives together, do RAID with tape drives so that five eight gig tapes is presented as say one 40 gig tape to Amanda ? Promise puts out a controller supported from the 2.2.19 kernel on for ATA-100 drives which plugs into a PCI slot and using one IRQ adds two drive channels to the system for around $30. Maybe over time I could acquire a second, third... fifth TR-4 eight or ten gig drive. Five tapes per full backup is still fairly reasonable depending on the tape size. Is it for certain that Amanda doesn't support multiple tape backups where a backup set is say four tapes and the drive can take one at a time ? Can software RAID be accomplished if the tape drives are installed, say five or more total, to two servers ?
RE: Unable to connect to host
Do you have ipv6 enabled on your client? If so, you may want to check the
archives for a resolution I posted recently regarding RH 7.2 w/ipv6 enabled.
Long and short of was that upgrading xinetd to a more recent rpm fixed our
problem.
A symptom of this problem was the message you reported from the amanda
server, but /tmp/amanda/amandad* (on the CLIENT) had lines similar to:
Amanda 2.4 REP HANDLE 008-B0DD0708 SEQ 1025278320
ERROR [addr 0.0.0.0: hostname lookup failed]
-ron
-Original Message-
From: Dean Lambourn [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 9:04 AM
To: amanda
Subject: Unable to connect to host
I am in the process of setting up amanda 2.4.3b3 for a
tapeless backup on a Redhat 7.2 server. As a test, I am
trying to backup the amanda server to itself. Unfortunately,
it is unable to connect. When I configured amanda, I set it
up to not use the .amandahosts file. I am able to rsh to
server from the server as the user amanda so the problem is
not .rhosts or hosts.equiv files and it is able to resolve
the host name.
When I run amcheck, here is the error message I receive:
Amanda Backup Client Hosts Check
WARNING: toast.pcf.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
(brought to you by Amanda 2.4.3b3)
I have added a .amandahosts file in case it was trying to use it:
/home/amanda/.amandahosts
toast amanda
localhost amanda
osiris amanda
Here is the relevant file for the xinetd configuration:
/etc/xinetd.d/amanda
service amanda
{
socket_type = dgram
wait = yes
protocol = udp
user = amanda
groups = yes
server = /usr/amanda/backup/libexec/amandad
disable = no
}
Any suggestions would be greatly appreciated.
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
Re: How to restore unknown tapes
On Tue, Jul 02, 2002 at 08:37:05PM +0200, Harald Schmalzbauer wrote: Hello all, I have a complete amanda generated backup consisting of eight daily1-8 tapes (SLR100). Now I need to look into these tapes. How do I do that? Alternatively I could also restore the complete set, I have enough space. I have no idea how to use amanda, all quick attempts ended up in missing log files. I only have the tapes, nothing else. Any help appreciated (I won't dive deep into amanda, I just want to restore the data) Amanda doesn't have to be present to use the tapes. Each dump (generally a file system) is saved on the tape as a separate file. There is also an administrative file placed at the start of the tape. At the start of each dump file on the tape there is also a 32KB header that says what was dumped and how to recover it. Basically it follows the scheme 1. move the tape to the beginning of the dump file mt device options rewind mt device options fsf some file number 2. use dd to extract the 32KB header dd if=tape device of=any file name bs=32k count=1 reading the header will tell you what file system is in the dump file and what commands can be used to extract it. Repeat step 1 and modify step 2 according to the header Besure you use a no rewinding device in your mt and dd commands. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Taper hangs and my backup fails
On Tue, 2 Jul 2002 at 2:40pm, Cassidy Kern wrote tapedev /dev/nht0 # tapetype section tapetype Seagate_Travan_20 labelstr ^Daily[0-9][0-9]* There has been some discussion of IDE tape drives recently, and the consensus seemed to be to use ide-scsi and use them as SCSI devices. Search the list archives for details, and give that a shot. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
(no subject)
unsubscribe
Re: Travan, DAT, Tape Changers?!?!?!?
On Tue, 2 Jul 2002, Gene Heskett wrote: On Tuesday 02 July 2002 14:36, robinsom wrote: TR-4 drives seem to be acquirable in the $35-$50 range, has anyone tried to stripe multiple tape drives together, do RAID with tape drives so that five eight gig tapes is presented as say one 40 gig tape to Amanda ? Promise puts out a controller supported from the 2.2.19 kernel on for ATA-100 drives which plugs into a PCI slot and using one IRQ adds two drive channels to the system for around $30. Maybe over time I could acquire a second, third... fifth TR-4 eight or ten gig drive. Five tapes per full backup is still fairly reasonable depending on the tape size. AFAIK, the striping only works with hard drives, but amanda can do I believe Mark Mengel already hacked RAIT (i.e. Tape RAID) into amanda. I haven't tried it so I can't personally report on how complete it is or how well it works. ChangeLog says it's in 2.5 and 2.4.2-multitape. -Mitch
Re: Unable to connect to host
Thanks for the reply. Right after I sent this e-mail, I found the
problem, admin stupidity. I don't misspell words consistently.
Frank Smith wrote:
Forget about the .amandahosts file for now, you're not getting that far.
Try restarting xinetd, either a stop/start or kill -USR2. Sending a HUP
just makes xinetd write a state file and doesn't reread its config.
Make sure the amanda line is in /etc/services.
Also check /tmp/amanda/selfcheck.*.debug for errors.
Frank
--On Tuesday, July 02, 2002 09:03:34 -0700 Dean Lambourn
[EMAIL PROTECTED] wrote:
I am in the process of setting up amanda 2.4.3b3 for a tapeless
backup on a Redhat 7.2 server. As a test, I am trying to backup the
amanda server to itself. Unfortunately, it is unable to connect. When
I configured amanda, I set it up to not use the
.amandahosts file. I am able to rsh to server from the server as the
user amanda so the problem is not .rhosts or hosts.equiv files and it
is able to resolve the host name.
When I run amcheck, here is the error message I receive:
Amanda Backup Client Hosts Check
WARNING: toast.pcf.com: selfcheck request timed out. Host down?
Client check: 1 host checked in 30.005 seconds, 1 problem found
(brought to you by Amanda 2.4.3b3)
I have added a .amandahosts file in case it was trying to use it:
/home/amanda/.amandahosts
toast amanda
localhost amanda
osiris amanda
Here is the relevant file for the xinetd configuration:
/etc/xinetd.d/amanda
service amanda
{
socket_type = dgram
wait = yes
protocol = udp
user = amanda
groups = yes
server = /usr/amanda/backup/libexec/amandad
disable = no
}
Any suggestions would be greatly appreciated.
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
--
Frank Smith
[EMAIL PROTECTED]
Systems Administrator Voice:
512-374-4673
Hoover's Online Fax:
512-374-4501
--
Dean Lambourn
Systems Administrator
Pacific Coast Feather Company
[EMAIL PROTECTED]
(206) 336-2332
how to see inside the tape
Hi, I am using AMANDA for a little time, meaning I am a new user. My AMANDA is working fine, but I want to know if there is a way to see what´s in the tape. I want to see the content of the tape, is it possible? or just by logs?
(no subject)
unsubscribe
Re: how to see inside the tape
On Tue, 2 Jul 2002 at 5:14pm, Eduardo Ceva wrote I am using AMANDA for a little time, meaning I am a new user. My AMANDA is working fine, but I want to know if there is a way to see what´s in the tape. I want to see the content of the tape, is it possible? or just by logs? If you have 'index yes' in your dumptype(s), you can use amrecover to browse the contents of your backups. If you just want to know what filesystems and levels are on a tape, the email reports will tell you that. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
index port times out
Hi all, I get intermittent client time-outs when running amdump. Has anyone solved an intermittent timeout? Does anyone know why amanda chooses the communications ports that gets chosen? Clients are OpenBSD, FreeBSD, and a RH Linux 7.2. The server is running amanda 2.4.2p2 on RH linux 7.2. I have upgraded all the Gnu tar to be at least 1.13.19. Each run is level 0. For testing purposes I have clipped all the clients except for a FreeBSD 4.5 client with 4 partitions (none larger than a Gb). This client has ipfw firewall running, but is open for the amanda server. When running amdump I usually get one partition timing out. The partition varies. When dumping all of the partitions, it is a particular partition. When dumping all of the partitions except for the particular partition, it is a different partition, with the same error. I have not yet tried omitting more than one partition. The dump has gone through without a partition timing out, but that is Very rare. amcheck does not show any errors. Looking through the logs, the server tries to contact the client. The first 2 index port sendbackup stream_server gets contacted fine, but the 3rd times out. e.g. (x's inserted and on the server side): dumper: stream_client: connected to 128.x.x.x.10081 dumper: stream_client: our side is 0.0.0.0.10080 dumper: stream_client: connected to 128.x.x.x.10082 dumper: stream_client: our side is 0.0.0.0.10081 dumper: stream_client: connect(3496) failed: Connection timed out driver: result time 826.558 from dumper0: TRY-AGAIN 01-6 [could not connect to index port: Connection timed out] This happens nearly every time in a backup. I have compiled amanda to include a portrange between 10080 and 10085, so I'm not sure why amanda chose port 3496. Usually the timeout involves a port somewhat between 3000 and 6000. The odd thing is that the client debug files indicate that the client is waiting on the same port. e.g. (on client side, x's inserted): sendbackup: stream_server: waiting for connection: 0.0.0.0.10081 sendbackup: stream_server: waiting for connection: 0.0.0.0.10082 sendbackup: stream_server: waiting for connection: 0.0.0.0.3496 waiting for connect on 10081, then 10082, then 3496 sendbackup: stream_accept: connection from 128.x.x.x.10080 sendbackup: stream_accept: connection from 128.x.x.x.10081 sendbackup: stream_accept: timeout after 30 seconds sendbackup: timeout on index port 3496 Normally, I would think that there's some sort of firewall keeping the two from communication on any port other than 10080-10085, but I am certain that the firewall would allow this. There is no router or other such device between the two. The amanda.conf include these timeouts: etimeout 1000 dtimeout 27600 ctimeout 2700 I have plenty of bandwidth, dumpers =10 (for 4 partitions), plenty of room on my holding disk, using gnutar, indexing... So, Does anyone know why amanda would choose such a port as 3496 after being compiled --with-portrange=10080,10085, or how to get rid of this error? -- Lalo Castro Programmer/Analyst McHenry Library (831) 459-5208
Re: Problems with amanda
Gene Heskett wrote: The majority opinion of those on this list is that any rpm's for amanda probably should be subjected to an intentional rm -f, they rarely, very rarely, will fit the individual users individual system, leaving out many vital steps such as adding a user amanda and makeing her a member of group disk for instance. Incorrect. Where did you get that idea? From the amanda specfile for Red Hat 7.3: useradd -M -n -g disk -o -r -d /var/lib/amanda -s /bin/bash \ -c Amanda user -u 33 amanda /dev/null 21 || : A little research does wonders, you'll find. Generally speaking, making an rpm installation work is going to be 10x more difficult than making a home built install work. There isn't enough docs to describe the rpm's default configuration so you can either make your system match the one the rpm was built on, or give up in a morass of error messages. I'd dispute that most strongly. It's all there in the spec file, if you'd care to look. Package management exists for a reason. I've noticed a lot of frankly uninformed criticism of packaged amanda installs, and it's beyond time for that to end. -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Problems with amanda
On Wed, Jul 03, 2002 at 09:43:08AM +1000, Robert Kearey wrote: Gene Heskett wrote: The majority opinion of those on this list is that any rpm's for amanda probably should be subjected to an intentional rm -f, they ... Incorrect. Where did you get that idea? ... A little research does wonders, you'll find. Generally speaking, making an rpm installation work is going to be 10x more difficult than making a home built install work. There I'd dispute that most strongly. It's all there in the spec file, if you'd care to look. ... Sounds like you took it personally. Gene was commenting from a point having viewed many bad packages. Perhaps yours is wonderous. That has not been the general experience of long time contributers to this list. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problems with amanda
Jon LaBadie wrote: Sounds like you took it personally. Possibly - I replied pre-morning coffee. Sorry if my tone was a bit aggressive. Gene was commenting from a point having viewed many bad packages. Perhaps yours is wonderous. It cures all know diseases! It's a floor wax, it's a desert whip! No, honestly! That has not been the general experience of long time contributers to this list. It may then be time to re-evaluate that perception. It's just too simplistic to blow off a packaged amanda, especially when there are possible support issues involved. It's possible that someone following Gene's advice may find that their Red Hat Network setup is compromised, for example. And not everybody *has* the luxury of being able to compile from source. http://people.redhat.com/rkearey/amanda.spec is the current spec file, feel free to have a look. Note: Not speaking for Red Hat here, nor am I the amanda package maintainer - just a satisfied user thereof. -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Problems with amanda
On Tuesday 02 July 2002 21:04, Jon LaBadie wrote: On Wed, Jul 03, 2002 at 09:43:08AM +1000, Robert Kearey wrote: Gene Heskett wrote: The majority opinion of those on this list is that any rpm's for amanda probably should be subjected to an intentional rm -f, they ... Incorrect. Where did you get that idea? ... A little research does wonders, you'll find. Generally speaking, making an rpm installation work is going to be 10x more difficult than making a home built install work. There I'd dispute that most strongly. It's all there in the spec file, if you'd care to look. Robert: It's in the spec file you say. Ok, I might buy that, but where in all that rpm related stuff is a pointer that says for the new bee to read the spec file. I've been under the impression it was strictly for rpms instructional useage when building it all this time. ... Sounds like you took it personally. Which most certainly was not my intention. Gene was commenting from a point having viewed many bad packages. Perhaps yours is wonderous. That has not been the general experience of long time contributers to this list. Amen, with some reservations, to wit: I have begun to appreciate that where system related stuff is concerned, the rpm path is a very good one. It tends to keep dependency wolves at bay. OTOH, if the system stuff is solid, then I'd druther build accessory stuff like amanda, cups, gimp-print, sane, even gimp from scratch because the configure scripts, generally speaking, are very good at sorting out the diffs between RHat and everybody else and giving one good usable code in all situations, something the rpm's can't begin to discuss because they are so system specific. Amanda is intended to run on many different systems and cpu's. No one can build a single rpm, binary or source that can do that. I've tried many times to build from a source rpm, and have in 3 years, succeeded maybe 3 or 4 times. Usually my compiler is the wrong version, or my rpm is the wrong version to even unpack the thing, or any one of 20 other reasons for the compatibility to go out the window. I was rather surprised on building the 20020610 snapshot of 2.4.3b3. I'd installed gcc 3.1, and most of the code you can download today will cause it to puke all over itself, requireing editing of makefiles to convert them to use gcc296. I didn't realise I'd used 3.1 on it till after it was built, installed, and running. Like the tv commercial says, These guys are good! Rant mode on again if the old timers can tolerate me one more time. I've made a living out of chaseing electrons for about 53 years now. I grew up with tubes, then transistors, then integrated circuits that gradually got smarter until they can do what they can do today. My own personal computer expertise if one would call it that, goes back to being pretty intimate with several of the old 8 and 16 bit cpu's and assembly or pure KR C to program them. That includes walking around in their os's fixing bugs, or writing programs that were in constant use for 10+ years. Unforch, that was a decade or more ago and time marches on, in this case at a faster pace than I can now manage at 67 and counting. Linuxwise, I started with RH5.1. I guess what I'm trying to say is that I've lived long enough to get a feel for what works, and what doesn't. For amanda, rpms don't very often, and generate too much help me traffic, all out of proportion to the numbers of rpms actually being used. Its easier to instruct on how to build it right, plus the end user then learns far more about how it works, and is far better equipt mentally to handle things when they go bump in the night, or when he adds another machine or drive to his system. Which eventually they will unless we can finally cuff stuff that Mr. Murphy that wrote all those laws... BTW, my way isn't the only way to do it, far from it. Consistency in how you do it should be your way as long as it works. Thats why I emphasize useing a script to configure the girl. -- Cheers to all, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: Problems with amanda
On Tuesday 02 July 2002 21:22, Robert Kearey wrote: Jon LaBadie wrote: Sounds like you took it personally. Possibly - I replied pre-morning coffee. Sorry if my tone was a bit aggressive. Gene was commenting from a point having viewed many bad packages. Perhaps yours is wonderous. It cures all know diseases! It's a floor wax, it's a desert whip! No, honestly! ROTFLMAO! Shades of Billy May, chuckle. :-) That has not been the general experience of long time contributers to this list. It may then be time to re-evaluate that perception. It's just too simplistic to blow off a packaged amanda, especially when there are possible support issues involved. It's possible that someone following Gene's advice may find that their Red Hat Network setup is compromised, for example. And not everybody *has* the luxury of being able to compile from source. Humm, interesting, citing security concerns from one of my recommendations? Can you supply a situation where that could apply? Or are you more concerned with the fact that its configuation is published at all? Maybe, if they leave their system wide open. But if you aren't using portsentry 1.1 to auto-write rules for iptables, and tcp_wrappers, well... I won't say its bulletproof, but in 3 years of sitting on the network with an outside the firewall address, my old office box hasn't been compromised yet. The /etc/hosts.deny file looks a bit like an LA phone book though. Its around 25k the last time I checked. :-) Heck, here at home on a dialup, hosts.deny is up to 12k since I fired up gene in May '98. http://people.redhat.com/rkearey/amanda.spec is the current spec file, feel free to have a look. Note: Not speaking for Red Hat here, nor am I the amanda package maintainer - just a satisfied user thereof. And thats all I am too really, a satisfied user. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: Problems with amanda
Gene Heskett wrote: It's just too simplistic to blow off a packaged amanda, especially when there are possible support issues involved. It's possible that someone following Gene's advice may find that their Red Hat Network setup is compromised, for example. And not everybody *has* the luxury of being able to compile from source. Humm, interesting, citing security concerns from one of my recommendations? Can you supply a situation where that could apply? Or are you more concerned with the fact that its configuation is published at all? OK, poor choice of words. I meant compromised, not so much in the sense of W3 0wnz y00, but more in the sense that you've changed the state of your system in a way that Red Hat Network (via rpm) won't recognize, and perhaps modify in some undesired way. I can probably best some up by saying that when using a system that relies on package management, it's best to stick using packages. If there's a problem with those packages, then let us know and we can fix them! -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Problems with amanda
On Tuesday 02 July 2002 19:43, Robert Kearey wrote: Gene Heskett wrote: The majority opinion of those on this list is that any rpm's for amanda probably should be subjected to an intentional rm -f, they rarely, very rarely, will fit the individual users individual system, leaving out many vital steps such as adding a user amanda and makeing her a member of group disk for instance. Incorrect. Where did you get that idea? From the amanda specfile for Red Hat 7.3: useradd -M -n -g disk -o -r -d /var/lib/amanda -s /bin/bash \ -c Amanda user -u 33 amanda /dev/null 21 || : A little research does wonders, you'll find. Maybe. OTOH, I don't know enough bash to be able to decode just exactly what that above command line actually does. And many, many new bees are going to be in that exact same situation. Generally speaking, making an rpm installation work is going to be 10x more difficult than making a home built install work. There isn't enough docs to describe the rpm's default configuration so you can either make your system match the one the rpm was built on, or give up in a morass of error messages. I'd dispute that most strongly. It's all there in the spec file, if you'd care to look. Package management exists for a reason. I've noticed a lot of frankly uninformed criticism of packaged amanda installs, and it's beyond time for that to end. Maybe it is, but for that to happen, there have to be people on this list knowledgeable about how the rpm works, who can do the hand-holding required that we, the tar builders often don't know how to. You are one of the few who could volunteer to fill those shoes, and we all know this list could use such knowledge constructively. Feel free to turn green (like kermit the frog) and jump right in! If you do, when rpm questions come up, we can shut up. The idea is to render the help that gets them going, not to argue about packaging systems from a near biblical perspective. This belittles the group in general. Thats not what we're here for. I originally joined this group to figure out how to make amanda work. I have, and have shared my methods thereby saving the authors, who don't number all that many, from some of the grunt detail called support. We can certainly use the help. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.04% setiathome rank, not too shabby for a WV hillbilly
Re: Problems with amanda
Gene Heskett wrote: I have begun to appreciate that where system related stuff is concerned, the rpm path is a very good one. It tends to keep dependency wolves at bay. Indeed. OTOH, if the system stuff is solid, then I'd druther build accessory stuff like amanda, cups, gimp-print, sane, even gimp from scratch because the configure scripts, generally speaking, are very good at sorting out the diffs between RHat and everybody else and giving one good usable code in all situations, something the rpm's can't begin to discuss because they are so system specific. rpm doesn't have to be system specific at all - it can just call ./configure in it's buildroot like anything else, and indeed, this is what most spec files actually do. [interesting points snipped] BTW, my way isn't the only way to do it, far from it. Consistency in how you do it should be your way as long as it works. Thats why I emphasize useing a script to configure the girl. Sure - that's what the spec file essentially is, and why I reccomend using it to maintain a consistent build. Note, I'm not advocating using rpm's on non-Red Hat (or similar) systems! :) -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Problems with amanda
Gene Heskett wrote: From the amanda specfile for Red Hat 7.3: useradd -M -n -g disk -o -r -d /var/lib/amanda -s /bin/bash \ -c Amanda user -u 33 amanda /dev/null 21 || : Maybe. OTOH, I don't know enough bash to be able to decode just exactly what that above command line actually does. And many, many new bees are going to be in that exact same situation. Point taken, though man useradd will give most people the info they need. The redirects c are really there to make things look pretty when it's installed :) You are one of the few who could volunteer to fill those shoes, and we all know this list could use such knowledge constructively. Sure, I'll help where I can, if people promise not to go rpms, yuck, compile frome source! :) -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Re: Problems with amanda
On Wed, 3 Jul 2002, Robert Kearey wrote: That has not been the general experience of long time contributers to this list. It may then be time to re-evaluate that perception. Here are my thoughts on the matter: Package management is invaluable from a system administration standpoint; there's no question about that. However, vendor provided packages are something I deem inappropriate for an application as configuration intensive as amanda. I don't want to install a package and then have to tweak anything post-package install. If I am going to have to do that I might as well just NFS mount the source and run 'make install'. The better solution to managing your amanda install is to create your own packages. It's not terribly difficult to take the existing amanda RPM and convert it to suit your needs. It's also not terribly difficult to create custom apt packages for your Debian systems or create custom inst packages for your SGIs. This is the approach I prefer to take to managing my systems. For instance, we use OpenSSH on our SGIs but the SGI Freeware package for OpenSSH is almost always out of date and rarely do the included configuration files suit our needs. So, I maintain custom inst packages for internal use on our machines. -- Brandon D. Valentine [EMAIL PROTECTED] Computer Geek, Center for Structural Biology This isn't rocket science -- but it _is_ computer science. - Terry Lambert on [EMAIL PROTECTED]
