RE: amlabel
Hi, I get error with rpm version of amanda (2.4.2P2-9). I compile version 2.4.4 of amanda and all working fine thanks. -- Alexandre FOUREY Consultant Architecture de Systèmes T-Systems Soleri Groupe Deutsche Telekom Notre métier : la convergence informatique et télécoms Convergence is our Business - tél. : +33 (0)4 37 65 24 34 fax : +33 (0)4 37 65 24 24 mob : +33 (0)6 61 92 43 00 - www.t-systems.fr Hi, Which release of amanda? What's in amanda.conf What's in your changer conf file? Jean-Louis On Tue, Mar 11, 2003 at 10:01:00AM +0100, afourey wrote: I would like to create virtual tape on hard disk. mkdir -p /data/backups/tape01/data chown -R amanda.disk /data/backups chmod -R 770 /data/backups amlabel -f DailySet1 DailySet101 I get the following error : amlabel: could not load slot current: file:/data/backups/tape01: not a device file Please help
Re: raw device ownership permissions on SGI machine
On Tue, Mar 11, 2003 at 03:35:44PM -0800, Stephen D. Lane wrote: Greetings. I am using amanda to back up several clients, one of which is an SGI Origin workstation. This client was recently rebuilt from scratch to IRIX 6.5.19m (yesterday, as a matter of fact :), and I don't know if the following problem was present prior to the rebuild (it was at 6.5.18m, after having been upgraded from 6.5.3m). I do know that amanda was working fine. After I rebuilt the client, it had the following: 0 crw---1 root sys 0,125 Mar 11 15:26 /hw/rdisk/root As this is the device amcheck complains about when I tell it I want to back up the root partition, I made the following changes: 0 crw-rw1 amanda disk0,125 Mar 11 15:26 /hw/rdisk/root This is how it was configured before the rebuild, and amcheck is perfectly happy with this. If I reboot the machine, however, the device goes back to: 0 crw---1 root sys 0,125 Mar 11 15:26 /hw/rdisk/root Is anyone familiar with this behavior in IRIX? I am seriously contemplating a root cronjob... I believe the /hw filesystem is created on the fly like /proc or a devfs. Actually.. [EMAIL PROTECTED] uname IRIX64 [EMAIL PROTECTED] mount | grep hw /hw on /hw type hwgfs (rw) [EMAIL PROTECTED] man -k hwgfs hwgraph, hwgfs, hw (4) - hardware graph and hardware graph file system And from there, I find: Since hwgfs is a pseudo-filesystem whose files don't actually use any disk space, there is no persistent information associated with files under /hw. In particular, file attributes (mode, owner, group) are not stored across reboots under hwgfs. Rather, reasonable default are used for all hwgfs special files. These defaults can be changed in the normal ways (i.e. with chmod(1), chown(1), chgrp(1)), but the changes only last until the next time the system is rebooted. In order to supply the appearance of special file attributes that are persistent across reboots, hwgfs uses the ioconfig(1m) utility, controlled by the contents of the file /etc/ioperms. Nice to know this. I have not used amanda and dump on Irix so I haven't come across this. -- I suggest that you refrain from posting in a forum such as this one, in which you are clearly intellectually overmatched. Perhaps you should find a debating companion that more closely reflects your natural abilities, such as a rock. -- Jake, in the Monastery
Re: drive compression discovery
Gene Heskett [EMAIL PROTECTED] writes: To get around this, one would assume that amcheck has already been run, and that the correct tape for tonights session is indeed loaded into the drive, This doesn't work when you have to write to more than one tape. Sometimes you do not even know in advance how many tapes will be needed. a: rewind tape b: dd tape label to scratch file, don't forget the 'bs=32k' c: rewind tape d: turn compression off by whatever method e: dd 10 megs or more worth of /dev/zero to the drive, causing it to flush its buffers. This will cause that compression flag to be reset permanently on this tape. Using bs=32k of course f: rewind tape g: dd the scratch file back to the tape to restore the proper label. For my DLT drives writing 32k is sufficient. The taper rewrites the label anyway, so the only additional step is to have the taper do the mt call before writing the label back. Two options: - do the ioctl internally. This might be machine-specific ... - call external mt. This means taper has to close the tape fd, call the external program and the reopen the tape. This is against taper's race-avoiding principles. But when you handcraft this by any workaround like you proposed, there are even more races possible. (Like something migt change the tape beetween your amcheck and yout script-erasing.) So I see these two options which both have their drawbacks. Sven
Who uses amanda?
Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I don't work in computer support but are aware there is a talk of buying a Veritas backup package at academic discount (around 800 UK pounds or $1300). I wanted to know if amanda would be a viable option. I guess there are going to be issues bought up about support, stability, the importance of backups etc. I'd like to know of big organistations using the software and if they have compared it to Veritas. I looked at using amanda once for my home computer (Sun Ultra 80, about 200 Gb of disk space over 4/5 drives, 40 Gb tape drive), but decided that for such a small system, a couple of unix shell scripts run by cron was all I needed, so never bothered using amanda. I know shell scripts are currently used here but we intend expanding the disk space by quite a lot. So basically: a) I know little about amanda b) Have no intention of using it myself for my home computer, but wonder if its a variable option in a university department (~100 staff). Dr. David Kirkby PhD, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail [EMAIL PROTECTED] Web page: http://www.medphys.ucl.ac.uk/~davek
Re: Who uses amanda?
On Wed, Mar 12, 2003 at 11:59:45AM +, Dr. David Kirkby enlightened us: Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). David, We used amanda at my previous job in a small department at Ohio State University (Linguistics). We had about 20 faculty and 80 grad students. Amanda was used to backup the 2 servers, 20 or so Sun workstations, and a handful of faculty PCs running windows. I can't remember exactly how much data we backed up, but I believe it was about 80-90GB for a full dump of all the DLEs which we archived after every academic quarter. I am presently in the process of setting up amanda in a slightly larger department at Ohio University (Mathematics). I expect the numbers to be about the same, and may look into backing up all of our faculty computers. I also use amanda at home, and would trust it with the most critical of data. The big selling point there is that you don't need amanda to recover data from a tape...just dd, tar, and dump. Hope that helps, Matt -- Matt Hyclak Department of Mathematics Ohio University (740) 593-1263 pgp0.pgp Description: PGP signature
Re: Who uses amanda?
For your home machine, amanda still makes sense. It can schedule full dumps of partitions over multiple nights, etc. and do the bookkeeping of what is on what tape. I know several people that run amanda at home. My department has ~30 employees. We run 2 amanda setups onto DDS3 and 1 onto DDS2, and back up around 130 GB total (one has 93 GB of that). They are not separate because one couldn't handle it, but for administrative reasons I don't want to go into. Absent the administrative reasons, we'd probably have everything on one setup and I'm confident it would work fine. The servers are desktop PCs running NetBSD with SCSI cards and DDS3 tape drives. A no longer loved sparc 20 with NetBSD is a decent choice for smaller setups; there is one such setup at MIT backing up about 6 machines. For 100 people you probably want DLT, and maybe a changer. (Assume 400 GB, divide by perhaps 10 for a tape cycle with 30 tapes and full dumps every 10 runs, and an 80 GB native tape should be fine for a while. Remember that you need to buy 2 to have a backup...) I've seen what commercial backup support is like, and the free support or some sysadmin time in your organization is probably as good a bet. My experience is that support people learn amanda faster than commercial backups, and between self help and mailinglist both have fewer problems and solve them faster than commercial backup software. Many others on the list run bigger setups, including with tape changers. Your size of 100 users is not 'large' in terms of existing amanda practice. Points to consider when choosing a backup system: Amanda puts backups on tape in a way that can be read with standard tools (dd, gunzip, restore, tar) by anybody with basic sysadmin clue. You do not need amanda or proprietary tools. Ask how bits can be gotten back with any prospective system. Ask if there is license managment software that must work to get bits back. Amanda self-schedules full dumps to fit. The administrative burden is _very_ low. I am a researcher not a sysadmin, and run a 36 GB total setup. Most days I spend 1 minute glancing at the report, typing 'mt offline' and putting in the next tape. Even with this, I am confident that all the bits are on tape if the report has no exception items. I have seen a commercial system for MS Windows completely fail to achieve its mission when indices were only on RAID sets and not on tape (multiple disk failures occurred). Amanda puts the bits on tape, and you can read them back with any other computer and a tape drive, even if you don't have the indices. You may have to scan 20 tapes, but that's a good situation to be in after a catastrophic failure, really. The importance of backups should lead to a regular program of randomly selected test restores to do QA. We have had a 100% success rate for getting bits back when we needed them (several times since 1995 or so, both disk failure and mistaken rm). Our real only issue was a tape drive that wrote bits wrong, and we read the entire tape back once a week with amverify to ensure that the tape drive works. I consider amanda as reliable as anything commercial, and really even more so. to be fair: Amanda's big weakness is in making multiple tapes for offsite storage. This can be done by various ways discussed on the list, none of which are particularly pretty. One is just to do a tape-tape copy after the dump, and ship one of them offsite. I gather than some commercial programs have explicit support for this. The other downside is that amanda doesn't have integrated Oracle support, etc. If you have postgres and do pg_dump to a file, that seems to work fine. Amanda security is a bit weak. Kerberos is not really supported, even though the code is sort of there. The 'bsd style' authentication is bogus (IP address check). But although I say this, every commercial package I've examined in detail has been worse. Good questions to ask are whether there is strong authentication and confidentiality of the data stream, both authenticating the server to the client to authorize the request to send the bits (most important), and the client to the server to ensure that the right bits are on tape. And, the bits should be encrypted in transit. Amanda/kerberos can do this, and I'm running it, but it's not trivial. One could use IPsec, too, although that may require minor wizardry. Greg Troxel [EMAIL PROTECTED]
Re: dump largee than tape
Hi! Here are the debugs of one run. amandad: debug 1 pid 1888 ruid 501 euid 501: start at Wed Mar 12 09:13:11 2003 amandad: version 2.4.4 amandad: build: VERSION=Amanda-2.4.4 amandad:BUILT_DATE=Mon Mar 3 09:53:03 CET 2003 amandad:BUILT_MACH=Linux corellia 2.4.18-3 #1 Thu Apr 18 07:32:41 EDT 2002 i686 unknown amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=amanda' '--with-group=amanda' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore GNUTAR=/bin/gtar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=corellia DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=corellia amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.000: got packet: Amanda 2.4 REQ HANDLE 000-00560508 SEQ 1047460425 SECURITY USER amanda SERVICE noop OPTIONS features=feff9ffe0f; amandad: time 0.000: sending ack: Amanda 2.4 ACK HANDLE 000-00560508 SEQ 1047460425 amandad: time 0.000: bsd security: remote host altair user amanda local user amanda amandad: time 0.001: amandahosts security check passed amandad: time 0.001: running service noop amandad: time 0.001: sending REP packet: Amanda 2.4 REP HANDLE 000-00560508 SEQ 1047460425 OPTIONS features=feff9ffe0f; amandad: time 0.001: got packet: Amanda 2.4 ACK HANDLE 000-00560508 SEQ 1047460425 amandad: time 0.001: pid 1888 finish time Wed Mar 12 09:13:11 2003 killpgrp: debug 1 pid 1893 ruid 501 euid 0: start at Wed Mar 12 09:13:11 2003 /usr/local/libexec/killpgrp: version 2.4.4 sending SIGTERM to process group 1893 child process exited with status 0 selfcheck: debug 1 pid 1886 ruid 501 euid 501: start at Wed Mar 12 09:11:53 2003 /usr/local/libexec/selfcheck: version 2.4.4 selfcheck: time 0.000: checking disk /export selfcheck: time 0.011: device /dev/sda3 selfcheck: time 0.011: disk /export OK selfcheck: time 0.011: amdevice /export OK selfcheck: time 0.011: device /dev/sda3 OK selfcheck: time 0.011: pid 1886 finish time Wed Mar 12 09:11:53 2003 sendsize: debug 1 pid 1890 ruid 501 euid 501: start at Wed Mar 12 09:13:11 2003 sendsize: version 2.4.4 sendsize[1890]: time 0.023: waiting for any estimate child sendsize[1892]: time 0.024: calculating for amname '/export', dirname '/export', spindle -1 sendsize[1892]: time 0.024: getting size via dump for /export level 0 sendsize[1892]: time 0.025: calculating for device '/dev/sda3' with 'ext2' sendsize[1892]: time 0.025: running /sbin/dump 0Ssf 1048576 - /dev/sda3 sendsize[1892]: time 0.025: running /usr/local/libexec/killpgrp sendsize[1892]: time 0.168: DUMP: Warning: unable to translate LABEL=/ sendsize[1892]: time 0.169: DUMP: Warning: unable to translate LABEL=/boot sendsize[1892]: time 0.170: DUMP: Warning: unable to translate LABEL=/var sendsize[1892]: time 0.171: DUMP: Added inode 7 to exclude list (resize inode) sendsize[1892]: time 5.212: 133587968 sendsize[1892]: time 5.236: . sendsize[1892]: estimate time for /export level 0: 5.211 sendsize[1892]: estimate size for /export level 0: 130457 KB sendsize[1892]: time 5.236: asking killpgrp to terminate sendsize[1892]: time 6.238: getting size via dump for /export level 1 sendsize[1892]: time 6.239: calculating for device '/dev/sda3' with 'ext2' sendsize[1892]: time 6.239: running /sbin/dump 1Ssf 1048576 - /dev/sda3 sendsize[1892]: time 6.240: running /usr/local/libexec/killpgrp sendsize[1892]: time 6.249: DUMP: Warning: unable to translate LABEL=/ sendsize[1892]: time 6.250: DUMP: Warning: unable to translate LABEL=/boot sendsize[1892]: time 6.251: DUMP: Warning: unable to translate LABEL=/var sendsize[1892]: time 6.259: DUMP: SIGSEGV: ABORTING! sendsize[1892]: time 6.260: . sendsize[1892]: estimate time for /export level 1: 0.020 sendsize[1892]: no size line match in /sbin/dump output for /export sendsize[1892]: . sendsize[1892]: estimate size for /export level 1: -1 KB sendsize[1892]: time 6.260: asking killpgrp to terminate sendsize[1892]: time 7.268: done with amname '/export', dirname '/export', spindle -1 sendsize[1890]: time 7.269: child 1892 terminated normally sendsize: time 7.269: pid 1890 finish time Wed Mar 12 09:13:18 2003
Re: drive compression discovery
Sven Rudolph wrote: But when you handcraft this by any workaround like you proposed, there are even more races possible. (Like something migt change the tape beetween your amcheck and yout script-erasing.) But you only have to do this once for each tape! There is no need to put this in the taper program. Just like you have to label each tape once manually too. Just consider this as if you had labeled your tapes bad, and you have to do it again (actually, this is indeed what happened!). While using the mentioned extended relabeling procedure to avoid the compression on your tape, you are watching who inserts the tape yourself, no race condition, unless your shadow is faster than you. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Flushing interrupted backups
Last night, my amdump was interrupted, and there is data left in my holding disk. I'd like to use amflush to dump them onto the tape I was using for last night's backup, but it insists that I use a new tape for the flush. Is there any way to convince Amanda to use last night's tape? Alex -- Mail: Alex Page [EMAIL PROTECTED] Real: Systems/Network Assistant, Epidemiology Unit, Oxford Tel: 01865 302 223 (external) / 223 (internal) PGP: 8868 21D7 3D35 DD77 9D06 BF0A 0746 2DE6 55EA 367E pgp0.pgp Description: PGP signature
a bit off topic but ...
I was wondering how amanda estimates the backup size ? is there a switch to tar to estimate the archive size without generating the file ? / Lars Segerlund.
Re: Who uses amanda?
On Wed, 12 Mar 2003 at 11:59am, Dr. David Kirkby wrote Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I'm the sysadmin for two research groups here (total of about 30 or so faculty/staff/grad students), both with large data storage needs. I use two amanda configs. The first backs up the 30 or so desktops etc to a 7GB native exabyte drive. Total amount of data is about 50GB. The second backs up the 3 RAIDs in use for the groups (.5TB, 1TB, 2TB) to an Overland AIT3 changer (1 drive, 19 tapes). There's currently about 2TB worth of data spread over the 3 arrays. If you search the archives, you can find more threads like this, and more answers. There are some folks running very large installs (both in terms of numbers of clients and in terms of amount of data. Good luck. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: drive compression discovery
On Wed March 12 2003 06:46, Sven Rudolph wrote: Gene Heskett [EMAIL PROTECTED] writes: To get around this, one would assume that amcheck has already been run, and that the correct tape for tonights session is indeed loaded into the drive, This doesn't work when you have to write to more than one tape. Sometimes you do not even know in advance how many tapes will be needed. This is true, and I don't have a good fix for that other than to treat them all by hand after loading them into the magazine, doing it each time any untreated tapes have been loaded. a: rewind tape b: dd tape label to scratch file, don't forget the 'bs=32k' c: rewind tape d: turn compression off by whatever method e: dd 10 megs or more worth of /dev/zero to the drive, causing it to flush its buffers. This will cause that compression flag to be reset permanently on this tape. Using bs=32k of course f: rewind tape g: dd the scratch file back to the tape to restore the proper label. For my DLT drives writing 32k is sufficient. On thinking this over, it may be true for any useage of the rewinding device, because the close and rewind would force the buffer flush. Good point, and a time saver too. The taper rewrites the label anyway, so the only additional step is to have the taper do the mt call before writing the label back. Also true, but I'll leave that to the folks who walk around in that code in their sleep. :) Two options: - do the ioctl internally. This might be machine-specific ... Is that not something that a good configure.in writer couldn't ascertain somehow? I mean I've seen configure ask the darndest questions at times. - call external mt. This means taper has to close the tape fd, call the external program and the reopen the tape. This is against taper's race-avoiding principles. But doable if the non-rewinding device is used. We're talking about maybe a 3 second exposure here, maximum, unless the machine is a certified, can't hunt anymore, dawg. But when you handcraft this by any workaround like you proposed, there are even more races possible. (Like something migt change the tape beetween your amcheck and yout script-erasing.) Yup, cause amcheck emailed them that the wrong tape(s) are in the magazine. In a home situation such as mine, thats not a concern as the missus stays as fur from this thing as she can. She did successfully do the tape changing while I was out of town for 2 weeks last fall, but it was against her better judgement, and she told me so. ;-) So I see these two options which both have their drawbacks. Acceptable risks. Yes they do need evaluated, particularly in a commercial environment, but in the huge majority of the cases I can envision, it doesn't seem to be a showstopper. We're sitting here, beating this subject to death, when it really is something that should be addressed (IMO) at some point by someone with authority over the code like JRJ. It is a nearly constant gotcha for the noobie trying to get his system running as efficiently as his hardware will allow... It seems to me that a simple ./configure --nocompression argument could be used to have taper (or whatever by breaking that ioctl out into a seperate function included by any util that needs it, and have that function do it as soon as the rewind is complete if that option was set at compile time. That would make sure its off before writing the first byte to any rewound tape. Food for thought anyway. -- Cheers Sven, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
Re: drive compression discovery
On Tue, 2003-03-11 at 14:39, Gene Heskett wrote: Two other points come up here, Eric. 1. When a tape is inserted in most modern drives, the tape recognition cycle will discover that this tape has been compressed previously, and will turn the compression back on regardless of your wishes. Sounds good, so if I insert a tape that I *suspect* was written compressed, but I check tapeinfo and it says the drive is still in uncompressed mode, then I know that tape is OK, right? 2: Jon's name isn't John. :-) Whoops! My bad. I have a friend by the same name, and he is famous for saying J-O-N. I'm not a commode. ;-P Sorry Jon! Eric
Re: drive compression discovery
On Wed March 12 2003 09:16, Eric Sproul wrote: On Tue, 2003-03-11 at 14:39, Gene Heskett wrote: Two other points come up here, Eric. 1. When a tape is inserted in most modern drives, the tape recognition cycle will discover that this tape has been compressed previously, and will turn the compression back on regardless of your wishes. Sounds good, so if I insert a tape that I *suspect* was written compressed, but I check tapeinfo and it says the drive is still in uncompressed mode, then I know that tape is OK, right? I'd have a strong tendency to believe that report until proven otherwise. And if thats the case, we would like to know about it pronto so we can advise the next user of that gotcha. 2: Jon's name isn't John. :-) Whoops! My bad. I have a friend by the same name, and he is famous for saying J-O-N. I'm not a commode. ;-P Chuckle, thats a good one. I suspect even Jon is chuckling as he reads this. Sorry Jon! Eric -- Cheers Eric, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Who uses amanda?
* Greg Troxel [EMAIL PROTECTED] (Wed, Mar 12, 2003 at 08:22:34AM -0500) On the same lines, we use amanda at a couple of sites (Middle east, UK and the netherlands) handling somewhere between 1 and 2 Tb of data in total, and we're looking to expand the setup to include another Tb of data to be backed up. The big beneifts of amanda: - reliable - works with standard unix tools (mt, dd and tar/gzip (or (ufs)restore) ) are all you need to get data of a backup tape if you really have to - great support (this list) - minimal overhead - it prints it's own tapelabels (you don;t know how handy it is until you have to restore the disk which had all that information on it ;) ) - it can be setup to email when the wrong tape is in the drive a few hours before the backup starts (amcheck -m) Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global IT Support manager Direct:+31-10.280.1539 Jason Geosystems BV Fax :+31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: dump largee than tape
On Wed March 12 2003 07:25, Konrad Dienst wrote: Hi! Here are the debugs of one run. Thats something that amanda cannot do, is span a single dump across more than one tape. The normal fix is to use tar, and break the disklist entries up into subdirs that are small enough to fit. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Who uses amanda?
On Wed March 12 2003 06:59, Dr. David Kirkby wrote: Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I don't work in computer support but are aware there is a talk of buying a Veritas backup package at academic discount (around 800 UK pounds or $1300). I wanted to know if amanda would be a viable option. I guess there are going to be issues bought up about support, stability, the importance of backups etc. I'd like to know of big organistations using the software and if they have compared it to Veritas. You obviously have, in such a situation, a need for a library, and one with multimegabyte a second drives in it. This will be far more important in terms of getting the backups done in a timely manner in the wee hours than the software you use to accomplish that. Also far more costly than the software even if it was arkeia or veritas. But since amanda is a client/server setup, and the client can be told to do the compression, the next consideration would be the occupied network bandwidth while the backup is running. Using client compression can make night and day differences in the network loading and its general useability while the backup is in progress. You'll need at least 100baseT if its going to get well into the 10's of gigabytes per session. IMO amanda is a viable option, here's why: Support: I'd be willing to bet you'll get help here at least as fast as you'll get it from veritas, we're (some of us) awake all around the world on a 24/7/365 basis. Veritas keep office hours. Stability: I've been running the latest snapshots, and have yet to feel the need to come back to this list and report that snapshot-version-date so-and-so was busted for my little 2 machine home system. And we have been told that the United States Dept. of Agriculture has been using amanda for quite some time, and I believe that would qualify as a large organization. However, I'd expect that, except for the Washington DC offices, is a distributed in little autonomous pieces setup. I looked at using amanda once for my home computer (Sun Ultra 80, about 200 Gb of disk space over 4/5 drives, 40 Gb tape drive), but decided that for such a small system, a couple of unix shell scripts run by cron was all I needed, so never bothered using amanda. I know shell scripts are currently used here but we intend expanding the disk space by quite a lot. So basically: a) I know little about amanda We were all there once :) b) Have no intention of using it myself for my home computer, but wonder if its a variable option in a university department (~100 staff). Why not? For a home system, its a piece of cake. I have a 4 tape magazine drive, so I don't have the daily chore of remembering to change the tapes. Amcheck emails me to remind me it couldn't find the next tape it needs, half a day before its actually needed, so the responsibility of seeing to it the proper tapes are loaded is mine. Not too bad on an every 4th day schedule. Other than that, once up and running, that is the sum total of human intervention required to run amanda. If I had a 30 tape library, I could close the door and lock it, but then I do a 5 day cycle to get everything in a full, and have 28 tapes in the pool, so I have over 4 full fulls on hand at any one time. Paranoid maybe... Besides, doing it on your home system will automaticly make you an expert when the university deploys it. Dr. David Kirkby PhD, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail [EMAIL PROTECTED] Web page: http://www.medphys.ucl.ac.uk/~davek -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
problem with amrestore / tar permissions
Hi, when I run the command amrestore -p /dev/rmt/1n scuba /boot | tar -pxv on the tape server itself, I manage to restore the files however the files are restored in a new directory structure. A number of new directories are created and also the files loose permissions. any idea how this can be solved? regards, liam
Re: Flushing interrupted backups
On Wed, 12 Mar 2003 at 2:00pm, Alex Page wrote Last night, my amdump was interrupted, and there is data left in my holding disk. I'd like to use amflush to dump them onto the tape I was using for last night's backup, but it insists that I use a new tape for the flush. Is there any way to convince Amanda to use last night's tape? No. Amanda doesn't append, and that's a safety feature. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: a bit off topic but ...
On Wed, 12 Mar 2003 at 2:47pm, Lars Segerlund wrote I was wondering how amanda estimates the backup size ? is there a switch to tar to estimate the archive size without generating the file ? You can see the exact command in /tmp/amanda/sendsize*debug. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Who uses amanda?
Dr. Kirkby -- I support about thirty or so UNIX servers (Solaris, AIX, Linux) that represent the development, testing, and production environments for the electronic resources of the University of Wisconsin at Madison Libraries. I started using Amanda 2.4.x about two years ago to do backups on these systems, originally using a collection of miscellaneous resources (hosts, holding disks, and tape drives) left over from previous backup strategies. We're just now finishing a re-implementation of the whole system that will give us 1 TB of capacity on our primary (and now, finally, dedicated) Amanda host. We use a modestly-priced Linux host, coupled with 500 GB of IDE-to-SCSI holding disk, and five Overland LibraryPro AIT-3 autoloaders. We configure for at least fourteen days of mixed full and incremental backups (level zeroes every three days), plus at least six weeks of level zero offsites. Cost of the entire system, including tape media and three years of onsite next-day support for all hardware, was $60k. Doing it again, shaving support costs and with recent pricing changes, I think I could probably do it for $50k even. By comparison, I did a three-year cost workup for buying backups on our central storage solution (Tivoli-based). Even assuming low initial capacity, ramping up gradually to 1 TB across the three years, the cost was easily $200k+, for a system that (in my opinion) would be almost useless to us in a true disaster-recovery scenario, as opposed to occasional file restores when someone fumble-fingers an rm -rf. I have been told that I didn't allow for the cost of my time to implement and babysit our system; but from watching one of my colleagues struggle with our Tivoli implementation, I'm not sure it makes that much of a difference. And that same colleague has now approached me about buying some of the excess time and capacity on our Amanda system, so we'll do some cost-recovery there as well. -mgs
Re: Flushing interrupted backups
Alex Page wrote: Last night, my amdump was interrupted, and there is data left in my holding disk. I'd like to use amflush to dump them onto the tape I was using for last night's backup, but it insists that I use a new tape for the flush. Is there any way to convince Amanda to use last night's tape? Alex Hi Alex not really, if you force the flush to tape it will overwrite the stuff already there. Prob best to not put in a tape tonight. This will force the backups to the holding area, then flush everything to tape tomorrow when you get in. -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: a bit off topic but ...
On Wed, 12 Mar 2003 at 2:47pm, Lars Segerlund wrote I was wondering how amanda estimates the backup size ? is there a switch to tar to estimate the archive size without generating the file ? What actually happens: - gnu tar knows that if its output is to /dev/null, it doesn't actually have to read the file contents. - dump estimates dump size before it begins dumping.
tapes are doomed
I am observing that high capacity tapes continue to be expensive, while high capacity disk drives continue to fall in price at an astrounding rate. Non-tape writable media are also cheap and falling, though they tend to be lower capacity. When some of these price/capacity curves cross, something has to change. Maybe it's just that the price premium on tapes follows the competition down, in a race to the marginal cost bottom. Maybe we stop buying tapes and (1) start feeding writable optical media into writers, or (2) tapes are replaced by black box cartridges which standardize interfaces and physical shape but not media. The standardized black box has long-term advantages over other media: no worries about alignment. no barriers to deploying new materials or other technological innovations. (It's why sealed Winchester disks wiped out removable disk drives.) It looks to me like the tape industry is falling behind its competitors, and unless something (like O-Mass) causes a big improvements in both capacity and price/capacity, the reasons for buying tapes may disappear. If I'm buying my next archive medium in about 12 months, there's a good chance that my disposable tapes will be hot-plug FireWire drives and my drive will just be a FireWire hub. OR I'll buy a DVD writer (red or blue laser) with robotic feeder. One interesting question is where compression fits into this picture. An interesting variation would be a manufacturer producing a tape drive emulator whose sole functions are compression, serial interface to the random access device (throw in an AIT-like random access component), and physical interface to the cartridge. In any event, it would be a good idea for Amanda to be ready to support direct access devices as an output medium one of these days. (The changes won't be hard.) a prediction from: Liudvikas Bukys [EMAIL PROTECTED]
RE: Who uses amanda?
We use amanda at the CSREES agency of U.S. Dept of Agriculture. We use it on our Linux and unix servers. We back up approximately 30 Gigs of data with it. Michael Martinez CSREES/ISTM/USDA -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 9:34 AM To: Dr. David Kirkby; Amanda Users Subject: Re: Who uses amanda? On Wed March 12 2003 06:59, Dr. David Kirkby wrote: Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I don't work in computer support but are aware there is a talk of buying a Veritas backup package at academic discount (around 800 UK pounds or $1300). I wanted to know if amanda would be a viable option. I guess there are going to be issues bought up about support, stability, the importance of backups etc. I'd like to know of big organistations using the software and if they have compared it to Veritas. You obviously have, in such a situation, a need for a library, and one with multimegabyte a second drives in it. This will be far more important in terms of getting the backups done in a timely manner in the wee hours than the software you use to accomplish that. Also far more costly than the software even if it was arkeia or veritas. But since amanda is a client/server setup, and the client can be told to do the compression, the next consideration would be the occupied network bandwidth while the backup is running. Using client compression can make night and day differences in the network loading and its general useability while the backup is in progress. You'll need at least 100baseT if its going to get well into the 10's of gigabytes per session. IMO amanda is a viable option, here's why: Support: I'd be willing to bet you'll get help here at least as fast as you'll get it from veritas, we're (some of us) awake all around the world on a 24/7/365 basis. Veritas keep office hours. Stability: I've been running the latest snapshots, and have yet to feel the need to come back to this list and report that snapshot-version-date so-and-so was busted for my little 2 machine home system. And we have been told that the United States Dept. of Agriculture has been using amanda for quite some time, and I believe that would qualify as a large organization. However, I'd expect that, except for the Washington DC offices, is a distributed in little autonomous pieces setup. I looked at using amanda once for my home computer (Sun Ultra 80, about 200 Gb of disk space over 4/5 drives, 40 Gb tape drive), but decided that for such a small system, a couple of unix shell scripts run by cron was all I needed, so never bothered using amanda. I know shell scripts are currently used here but we intend expanding the disk space by quite a lot. So basically: a) I know little about amanda We were all there once :) b) Have no intention of using it myself for my home computer, but wonder if its a variable option in a university department (~100 staff). Why not? For a home system, its a piece of cake. I have a 4 tape magazine drive, so I don't have the daily chore of remembering to change the tapes. Amcheck emails me to remind me it couldn't find the next tape it needs, half a day before its actually needed, so the responsibility of seeing to it the proper tapes are loaded is mine. Not too bad on an every 4th day schedule. Other than that, once up and running, that is the sum total of human intervention required to run amanda. If I had a 30 tape library, I could close the door and lock it, but then I do a 5 day cycle to get everything in a full, and have 28 tapes in the pool, so I have over 4 full fulls on hand at any one time. Paranoid maybe... Besides, doing it on your home system will automaticly make you an expert when the university deploys it. Dr. David Kirkby PhD, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail [EMAIL PROTECTED] Web page: http://www.medphys.ucl.ac.uk/~davek -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Who uses amanda? -- RFC
This regular query never made it to the FAQ-O-Matic I see. A proposal, I'll put together a survey form (sample follows) and ask the list for submissions. After a period I'll summarize the data, hopefully in a table of some form and submit it to the F-O-M. So, two questions: 1. Is the survey desired or frowned upon? 2. Is the data asked for, and the wording of the form suitable? On or Off-list opinions gratefully accepted. Jon, [[ proposed survey form ]] PLEASE DO NOT RESPOND TO THIS SURVEY, IT IS NOT FINALIZED! -- RESPONDER INFORMATION Name .. : Organization .. : Email Address : Date Submitted : Note, responder information is requested for confirmation and clarification purposes only. It will not be included in any published compendium of the information. -- ORGANIZATION USING AMANDA INFORMATION Name . : Department ... : Extent of Amanda Usage ... : (entire organization, department, subnet, ...) Date of First Amanda Usage : (/mm) Note, if you prefer the organization remain anonymous, please provide descriptive information (eg. Fortune 100 insurance company, German computer manufacturer, eastern state university, independent consultant home office, ...) -- DESCRIPTION OF AMANDA INSTALLATION Dumpcycle .. : Frequency of Backups : (daily, weekly, 5/week, ...) Number of Client Hosts Backed up by Amanda : Total Disk Capacity of Client Hosts .. : Total Data on Client Host Disks .. : Average Size of Data Backed Up Per Backup : (pre-compression) Amanda Server Host(s) Amanda Version(s) : Operating System(s) : Amanda Client Host(s) Amanda Version(s) : Operating System(s) : Note, if you are running multiple configurations please try to give pooled values; alternatively, repeat parts of the survey as necessary. -- [[ end of proposed survey form ]] -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: raw device ownership permissions on SGI machine
On Wed, 2003-03-12 at 03:02, Harri Haataja wrote: I believe the /hw filesystem is created on the fly like /proc or a devfs. Nice to know this. I have not used amanda and dump on Irix so I haven't come across this. I use amanda to back up Irix clients (Onyx racks). However, I have chosen to back up filesystems, not devices: b52 /data/cvsroot/ nocomp-user eth0 b52 /etc/ nocomp-user eth0 b52 /usr/people/nocomp-user eth0 It works fine, although I couldn't get the SGI freeware working right, so I compiled from source. -Gord -- Gordon Pritchard, P.Eng. | Institute of Electrical and Research Labs Manager| Electronics Engineers Simon Fraser University, Surrey | Quarter Century Wireless Ass'n [EMAIL PROTECTED] | Telephone Pioneers of America phone: 604.586.6186
Re: drive compression discovery
Gene Heskett wrote: On Wed March 12 2003 09:16, Eric Sproul wrote: On Tue, 2003-03-11 at 14:39, Gene Heskett wrote: Two other points come up here, Eric. 1. When a tape is inserted in most modern drives, the tape recognition cycle will discover that this tape has been compressed previously, and will turn the compression back on regardless of your wishes. Sounds good, so if I insert a tape that I *suspect* was written compressed, but I check tapeinfo and it says the drive is still in uncompressed mode, then I know that tape is OK, right? You have to read something on it first to be really sure that the drive did a recognition cycle. Something like: dd ibs=256K if=/dev/your/tapedev of=/dev/null count=1 (blocksize equal to or larger than the first block on tape is fine) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Check length/capacity of tape?
My first successful backup withe the DLT7000 loader seems to have run out of tape at about 20GB. I'm *almost* certain that all of the tapes I was using with the DLT4000 were new, and therefore should be capable of holding the 35GB. There isn't any definitive markings on any of the tapes. They all say DLT IV but nothing more. Is there any way, short of running tapetype on every tape, to know for certain its' capacity? -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Who uses amanda?
Gene Heskett wrote:
But since amanda is a client/server setup, and the client can be
told to do the compression, the next consideration would be the
occupied network bandwidth while the backup is running. Using
client compression can make night and day differences in the
network loading and its general useability while the backup is in
progress. You'll need at least 100baseT if its going to get well
into the 10's of gigabytes per session.
The gain with the parallelisation of Amanda can be amazing!
Here is a snippet of my archive run last weekend:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:13
Run Time (hrs:min) 8:12
Dump Time (hrs:min) 42:57 42:57 0:00
Output Size (meg) 70427.970427.90.0
Original Size (meg)149337.0 149337.00.0
Avg Compressed Size (%)47.2 47.2--
Filesystems Dumped 114114 0
Avg Dump Rate (k/s) 466.3 466.3--
It means that it did a full backup in 8 hours 12 minutes,
that would take almost 43 hours when run sequentially (what
many simple backup scripts actually do!).
We have a mix of fast and old slow machines (Sun Sparc IPX,
Intel Pentium 150Mhz with 32 MByte RAM etc); also a mix of
100baseT and 10baseT network cards. Amanda does them all
(do there still exist veritas clients for SunOS 4.1.4?).
For curiosity, here is my Daily config statistics section:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:28
Run Time (hrs:min) 2:52
Dump Time (hrs:min) 11:40 8:45 2:55
Output Size (meg) 16658.415116.6 1541.8
Original Size (meg) 42697.537183.0 5514.5
Avg Compressed Size (%)39.0 40.7 28.0
Filesystems Dumped 116 22 94 (1:89 2:5)
Avg Dump Rate (k/s) 406.4 491.5 150.7
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: a bit off topic but ...
Lars Segerlund wrote: I was wondering how amanda estimates the backup size ? is there a switch to tar to estimate the archive size without generating the file ? For the estimate phase Amanda uses the --file /dev/null option of gnutar, and gnutar has a special optimisation that if it detects output to /dev/null, it will actually not read any bytes of files, but just make statistics. For samba clients it uses the builtin du command of smbclient (if your smbclient version is recent enough). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: problem with amrestore / tar permissions
liam pace wrote: Hi, when I run the command amrestore -p /dev/rmt/1n scuba /boot | tar -pxv on the tape server itself, I manage to restore the files however the files are restored in a new directory structure. A number of new directories are created and also the files loose permissions. any idea how this can be solved? If you run tar -px... as root, then the permissions are correct. Tar also extracts files into the current directory (not bad if you first want to check if what you have on tape is better than what is on disk). If it is not these two problems, then you need to give more information. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Who uses amanda?
On Wed March 12 2003 12:45, Paul Bijnens wrote:
Gene Heskett wrote:
But since amanda is a client/server setup, and the client can be
told to do the compression, the next consideration would be the
occupied network bandwidth while the backup is running. Using
client compression can make night and day differences in the
network loading and its general useability while the backup is
in progress. You'll need at least 100baseT if its going to get
well into the 10's of gigabytes per session.
The gain with the parallelisation of Amanda can be amazing!
Thats what I was trying to say Paul, but not all that well said.
Data like this is very convincing. And, here, I couldn't show that
since the other machine is actually backed up by rsyncing it, and
the rsync'd mirror then gets backed up here. This gets rid of the
smb and its bogus file dates gotchas, but doesn't allow for the
paralleling of jobs out on the client... Someday...
These are great figures in fact, thats a time shrinkage to 19% of
what it would have taken if serialized.
Now the 64k question is, can veritas, arkeia, tivoli, or bru top
that? I have VERY serious doubts about that personally.
Here is a snippet of my archive run last weekend:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:13
Run Time (hrs:min) 8:12
Dump Time (hrs:min) 42:57 42:57 0:00
Output Size (meg) 70427.970427.90.0
Original Size (meg)149337.0 149337.00.0
Avg Compressed Size (%)47.2 47.2--
Filesystems Dumped 114114 0
Avg Dump Rate (k/s) 466.3 466.3--
It means that it did a full backup in 8 hours 12 minutes,
that would take almost 43 hours when run sequentially (what
many simple backup scripts actually do!).
We have a mix of fast and old slow machines (Sun Sparc IPX,
Intel Pentium 150Mhz with 32 MByte RAM etc); also a mix of
100baseT and 10baseT network cards. Amanda does them all
(do there still exist veritas clients for SunOS 4.1.4?).
For curiosity, here is my Daily config statistics section:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:28
Run Time (hrs:min) 2:52
Dump Time (hrs:min) 11:40 8:45 2:55
Output Size (meg) 16658.415116.6 1541.8
Original Size (meg) 42697.537183.0 5514.5
Avg Compressed Size (%)39.0 40.7 28.0
Filesystems Dumped 116 22 94 (1:89 2:5)
Avg Dump Rate (k/s) 406.4 491.5 150.7
And this is a 75% reduction here.
You are doing about 20x the data I am, in about the same time. But
my drive is a DDS2, so one normally calls a surveyer to set stakes
in order to measure its throughput anyway. :-(
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.24% setiathome rank, not too shabby for a WV hillbilly
Re: tapes are doomed
On Wed, 12 Mar 2003 at 11:31am, [EMAIL PROTECTED] wrote I am observing that high capacity tapes continue to be expensive, while high capacity disk drives continue to fall in price at an astrounding rate. Non-tape writable media are also cheap and falling, though they tend to be lower capacity. *snip* This is a *very* common discussion -- see the archives of this list or google in comp.arch.storage. Tape still has a lot of advantages, especially when it comes to archiving. In any event, it would be a good idea for Amanda to be ready to support direct access devices as an output medium one of these days. Amanda already support backup directly to files on disk. It's trivial to then move those to your output medium of choice. (The changes won't be hard.) Patches accepted, as they say. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Who uses amanda?
Dr. Kirby, We have used amanda for backup of about 65 workstations and servers for going on five years now here at corporate research for Goodyear. Currently, we backup about 700GB. We use amanda at the CSREES agency of U.S. Dept of Agriculture. We use it on our Linux and unix servers. We back up approximately 30 Gigs of data with it. Michael Martinez CSREES/ISTM/USDA -Original Message- From: Gene Heskett [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2003 9:34 AM To: Dr. David Kirkby; Amanda Users Subject: Re: Who uses amanda? On Wed March 12 2003 06:59, Dr. David Kirkby wrote: Can anyone tell me if they use amanda and are a large commercial company ( 250 employees), a hospital or a university and if so how much it's used (whole institution, small department, single server etc). How many Gb do you back up (don't answer that if you feel its confidential, or you don't know). I don't work in computer support but are aware there is a talk of buying a Veritas backup package at academic discount (around 800 UK pounds or $1300). I wanted to know if amanda would be a viable option. I guess there are going to be issues bought up about support, stability, the importance of backups etc. I'd like to know of big organistations using the software and if they have compared it to Veritas. You obviously have, in such a situation, a need for a library, and one with multimegabyte a second drives in it. This will be far more important in terms of getting the backups done in a timely manner in the wee hours than the software you use to accomplish that. Also far more costly than the software even if it was arkeia or veritas. But since amanda is a client/server setup, and the client can be told to do the compression, the next consideration would be the occupied network bandwidth while the backup is running. Using client compression can make night and day differences in the network loading and its general useability while the backup is in progress. You'll need at least 100baseT if its going to get well into the 10's of gigabytes per session. IMO amanda is a viable option, here's why: Support: I'd be willing to bet you'll get help here at least as fast as you'll get it from veritas, we're (some of us) awake all around the world on a 24/7/365 basis. Veritas keep office hours. Stability: I've been running the latest snapshots, and have yet to feel the need to come back to this list and report that snapshot-version-date so-and-so was busted for my little 2 machine home system. And we have been told that the United States Dept. of Agriculture has been using amanda for quite some time, and I believe that would qualify as a large organization. However, I'd expect that, except for the Washington DC offices, is a distributed in little autonomous pieces setup. I looked at using amanda once for my home computer (Sun Ultra 80, about 200 Gb of disk space over 4/5 drives, 40 Gb tape drive), but decided that for such a small system, a couple of unix shell scripts run by cron was all I needed, so never bothered using amanda. I know shell scripts are currently used here but we intend expanding the disk space by quite a lot. So basically: a) I know little about amanda We were all there once :) b) Have no intention of using it myself for my home computer, but wonder if its a variable option in a university department (~100 staff). Why not? For a home system, its a piece of cake. I have a 4 tape magazine drive, so I don't have the daily chore of remembering to change the tapes. Amcheck emails me to remind me it couldn't find the next tape it needs, half a day before its actually needed, so the responsibility of seeing to it the proper tapes are loaded is mine. Not too bad on an every 4th day schedule. Other than that, once up and running, that is the sum total of human intervention required to run amanda. If I had a 30 tape library, I could close the door and lock it, but then I do a 5 day cycle to get everything in a full, and have 28 tapes in the pool, so I have over 4 full fulls on hand at any one time. Paranoid maybe... Besides, doing it on your home system will automaticly make you an expert when the university deploys it. Dr. David Kirkby PhD, Senior Research Fellow, Department of Medical Physics, University College London, 11-20 Capper St, London, WC1E 6JA. Tel: 020 7679 6408 Fax: 020 7679 6269 Internal telephone: ext 46408 e-mail [EMAIL PROTECTED] Web page: http://www.medphys.ucl.ac.uk/~davek -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly --- Wayne Richards Phone: 330 796-4462 Goodyear
Re: drive compression discovery
I realize this isn't the correct forum, but as long as your are already on the subject I'm hoping you will not mind too much. I have one system, just one, that I do not run amanda on but perform backups of. Its a Redhat Linux rel 7.2, code name Inigma, kernel 2.4.9.3-1, with a DLT 8000 drive. We are running out of tape during our nightly dump and can't seem to figure out the correct drive parameters to either use better blocking or turn on compression. Yes, I've been following this discussion but we haven't been successful. Current command is # dump 0udsf 49125 67854 /dev/nst0 /iarcvol (I'm not primary on that system, I'm not really sure where these values originated but have been involved in testing tweeking them). Only about 18 of the 25 gig make it to tape and a DLT8000 should have sufficient capacity to dump all the date with room to spare. thanks, Brian Gene Heskett wrote: On Wed March 12 2003 09:16, Eric Sproul wrote: On Tue, 2003-03-11 at 14:39, Gene Heskett wrote: Two other points come up here, Eric. 1. When a tape is inserted in most modern drives, the tape recognition cycle will discover that this tape has been compressed previously, and will turn the compression back on regardless of your wishes. Sounds good, so if I insert a tape that I *suspect* was written compressed, but I check tapeinfo and it says the drive is still in uncompressed mode, then I know that tape is OK, right? You have to read something on it first to be really sure that the drive did a recognition cycle. Something like: dd ibs=256K if=/dev/your/tapedev of=/dev/null count=1 (blocksize equal to or larger than the first block on tape is fine) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: drive compression discovery
On Wed March 12 2003 14:12, Brian Cuttler wrote: I realize this isn't the correct forum, but as long as your are already on the subject I'm hoping you will not mind too much. I'd guess thats since it has to do with tape, it should come under our umbrella. I have one system, just one, that I do not run amanda on but perform backups of. Its a Redhat Linux rel 7.2, code name Inigma, kernel 2.4.9.3-1, with a DLT 8000 drive. We are running out of tape during our nightly dump and can't seem to figure out the correct drive parameters to either use better blocking or turn on compression. Yes, I've been following this discussion but we haven't been successful. Current command is # dump 0udsf 49125 67854 /dev/nst0 /iarcvol (I'm not primary on that system, I'm not really sure where these values originated but have been involved in testing tweeking them). Hoo boy, a dump user. Ok all you dump experts, jump right in. :-) Me, I'm a tar user, so I have no idea what all those options might mean. Only about 18 of the 25 gig make it to tape and a DLT8000 should have sufficient capacity to dump all the date with room to spare. thanks, Brian Gene Heskett wrote: [and snipped] -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Who uses amanda?
I have been told that I didn't allow for the cost of my time to implement and babysit our system; but from watching one of my colleagues struggle with our Tivoli implementation, I'm not sure it makes that much of a difference. Hrm. In a past life, I implemented Amanda in a company that backed up about 100GB of small Sybase dumps, a few web servers, a few app servers, and a couple of user workstations to some fairly nice tape drive. The company went out of business, but it was a dotcom, and they wanted to maintain a presence as though they were still in business (to try to sell the company, you see). They left all the servers in colo but there was no-one to administer them. I continued to get daily emails from Amanda for months afterward as it kept doing its best to spread backups across holding disks and the single tape that never got changed out. I knew when they finally pulled the plug on the Amanda machine, because that's when I stopped getting emails. I recall Amanda needing VERY LITTLE BABYSITTING whatsoever, and seemed to make it very clear exactly what I needed to do to remedy whatever problems it was having (someone change the damn tape, please!). It was very clear Amanda was well-written to deal with edge cases and abnormal circumstances. It is this experience that has me currently implementing Amanda in a 3-office ~100-employee ~60 workstation mixed Unix/Windows environment. I don't feel a single twinge of concern about whether or not Amanda is up to the task, and quite frankly, I WOULD FEEL CONCERN about implementing some commercial backup system, because the ones I've seen in operation are buggy, annoying, and time-consuming. -- pv
The amflush that wouldn't flush
I seem to have some sort of database anomaly in my AMANDA system.
I am looking for references to previous articles about this topic...
or maybe some guidance as to what I should be examining or evaluating...
##
I have sent the amflush command for the only degraded backup remaining.
It always comes back indicating there is nothing to write to tape.
I read the archives and found a thread where John R. Jackson advises
users not to muck with the database manually, to let the Amanda system
handle it...
Well, it appears degraded mode entry is stale.
Any ideas?
Thanks!
DK
#
Subject: DailySet1 AMFLUSH MAIL REPORT FOR March 12, 2003
The dumps were flushed to tape DailySet1-14.
The next tape Amanda expects to use is: DailySet1-16.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
DailySet1-14 0:00 0.00.0 0
NOTES:
amflush: legless._usr_local__legless_mysql_var.1: disk
legless:/usr/local_legless/mysql/var not in database, skipping it.
amflush: legless._usr_local__legless_mysql_var.2: disk
legless:/usr/local_legless/mysql/var not in database, skipping it.
taper: tape DailySet1-14 kb 0 fm 0 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER STATS
HOSTNAME DISKLORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS KB/s
- -
anaconda /etc NO FILE TO FLUSH
--
anaconda /net/anaconda/scratch1NO FILE TO FLUSH
--
boa/etc NO FILE TO FLUSH
--
boa/net/boa/srv NO FILE TO FLUSH
--
boa/var/yp NO FILE TO FLUSH
--
legless/etc NO FILE TO FLUSH
--
legless/usr/local_legless/mysql/data NO FILE TO FLUSH
--
phenix /etc NO FILE TO FLUSH
--
phenix /home/phenix NO FILE TO FLUSH
--
phenix /usr/localNO FILE TO FLUSH
--
redbelly /etc NO FILE TO FLUSH
--
redbelly /net/adder/scratch1 NO FILE TO FLUSH
--
redbelly /net/adder/scratch2 NO FILE TO FLUSH
--
redbelly /net/redbelly/home1 NO FILE TO FLUSH
--
redbelly /net/redbelly/lanl1 NO FILE TO FLUSH
--
redbelly /net/redbelly/lbnl1 NO FILE TO FLUSH
--
redbelly /usr/local_redbelly/etc NO FILE TO FLUSH
--
redbelly /var/amanda NO FILE TO FLUSH
--
ringneck /etc NO FILE TO FLUSH
--
ringneck /net/ringneck/camb1 NO FILE TO FLUSH
--
ringneck /net/ringneck/scratch1NO FILE TO FLUSH
--
ringneck /net/ringneck/scratch2NO FILE TO FLUSH
--
ringneck /net/ringneck/tamu1 NO FILE TO FLUSH
--
(brought to you by Amanda version 2.4.4)
drive compression discovery - I like dump :)
On Wed, Mar 12, 2003 at 02:34:13PM -0500, Gene Heskett wrote: ---cut--- Current command is # dump 0udsf 49125 67854 /dev/nst0 /iarcvol (I'm not primary on that system, I'm not really sure where these values originated but have been involved in testing tweeking them). Hoo boy, a dump user. Ok all you dump experts, jump right in. :-) Me, I'm a tar user, so I have no idea what all those options might mean. There's a very good discussion of dump options in W. Curtis Preston's book (here's his example): dump Ounbdsf 128 1 11500 /dev/rmt/0cbn /home 0-9 dump level u update the dumpdates file n notify the members of the operator group when dump is completed b blocking factor ds tape size info (see below) f device specification The example above uses b a blocking factor of 128 d a density factor of 1 s a size factor of 11500 density refers to how much data will fit on one inch of tape sizerefers to the tape size in feet. In actual practice these options are very difficult to use and yeild very little value. YMMV. Good luck! --Steve Lane /\ Doudna Lab \ / ASCII Ribbon Campaign U. C. BerkeleyX Against HTML Email / \
Re: level 0 of huge filesystem not working (tar returned 2, and thebackup fails)
On Wed, 12 Mar 2003 at 3:54pm, wab wrote One filesystem I'm trying to back up with AMANDA is really huge and I'm encountering errors: This filesystem is so huge, a level 0 is taking longer than 24 hours. Any ideas on what could be going wrong? My best guesses: 1. The filesystem is just too big for TAR. 2. The filesystem is so big, its contents are changing during the tar process and confusing it or amanda. I backup several DLEs with tar that are rather large -- I think the biggest one is nearly 80GB. That one takes about 3 hours (no compression). Of course, that Linux server is rather fast. /-- server /usr lev 0 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [server:/usr level 0] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end ? gtar: Read error at byte 53808128, reading 10240 bytes, in file ./archive/www/access.0203.gz: I/O error An I/O error is bad. Look in your system logs for more info on that. ./opt/freeware/apache/share/htdocs/Library/easmenu.lbi.LCK: No such file or directory The rest of the stuff, yes, has to do with tarring an active filesystem. Any ideas as to what might be causing this? Look into that I/O error. Also, is this Solaris? For whatever reason, tar seems rather slow on Solaris (at least a lot of questions on this list seem to point that way). If that's a filesystem, could you try dump? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: level 0 of huge filesystem not working (tar returned 2, and the backup fails)
On Wed, Mar 12, 2003 at 03:54:09PM -0500, wab wrote: One filesystem I'm trying to back up with AMANDA is really huge and I'm encountering errors: This filesystem is so huge, a level 0 is taking longer than 24 hours. Any ideas on what could be going wrong? My best guesses: 1. The filesystem is just too big for TAR. 2. The filesystem is so big, its contents are changing during the tar process and confusing it or amanda. No I don't think this is the situation. /-- server /usr lev 0 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [server:/usr level 0] sendbackup: info BACKUP=/usr/local/bin/tar [[ snip ]] | Total bytes written: 30747043840 ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] My past reading of tar source showed this error when one or several files could not be backed up but most of the backup was ok. You had several individual file errors. Go to your config/config.h file and add a line #define IGNORE_TAR_ERRORS and recompile. It will then continue after this and several other specific errors. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Gene Heskett's amanda build script
On Sun February 23 2003 08:23, Carsten Rezny wrote: Thanks for your reply, Jay. On Sat, 2003-02-22 at 21:57, Jay Lessert wrote: [Posted and Cc'ed] On Sat, Feb 22, 2003 at 08:09:16PM +0100, Carsten Rezny wrote: I have installed Amanda 2.4.2p2 on a SuSE 8.0 box. The machine is server and client. When I run amcheck I get the following result ERROR: /dev/nst0: no tape online (expecting tape maphy-d05 or a new tape) I assume you understand this and will fix it, right? Right, that's not the problem. WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.006 seconds, 1 problem found You always hate to see localhost here, so many ways that can go wrong. Change the DLE (disklist entry) from localhost to the true hostname, double check ~amanda/.amandahosts according to docs/INSTALL, and try again. OK, I replaced localhost with the real hostname, checked ~amanda/.amandahosts and still get the same result. Here is what I think is the problem: [amandad debug file] got packet: Amanda 2.4 REQ HANDLE 000-20B90708 SEQ 1046003786 SECURITY USER amanda SERVICE selfcheck OPTIONS ; GNUTAR /mirror 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; GNUTAR /home 0 OPTIONS |;bsd-auth;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; sending ack: Amanda 2.4 ACK HANDLE 000-20B90708 SEQ 1046003786 amandad: dgram_send_addr: sendto(0.0.0.0.875) failed: Invalid argument ^ amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-20B90708 SEQ 1046003786 ERROR [addr 0.0.0.0: hostname lookup failed] ^^^ It looks like amandad doesn't know the server's IP address. Both client and server run on the same machine and the machine knows its hostname. Any more ideas? Thanks, Carsten First off, 2.4.2p2 is pretty ancient these days. Second, this looks as if it wasn't told the host machines address when it was configured. There have been some changes since 2.4.2p2, most notably in how excludes are handled, and in the support for backups to disk, but you should probably goto the amanda.org site, and down near the bottom of the page you'll see a link to snapshots, follow it and get 2.4.4b1-20030220. Then follow the build it directions. They are basicly, become the user amanda after making amanda a member of the group disk(or some other equally high ranking group), unpack it in /home/amanda (makes perms easier to track), cd into the resultant directory and configure and make it. Then become root, and install it. As one needs an anchor point so that a newer version can be built to the same configuration as the older one, thereby maintaining continuity of its characteristics, I've been using a script to do that configuration, one that gets copied to each new incarnation of amanda as I unpack it. At risk of boring the rest of the list, here it is again, modify to suit where needed of course but read the docs for the details, always a good idea. gh.cf, run as ./gh.cf after setting execute perms--- #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi 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 -- By using this script, I have built and used with only a couple of problems, nearly every snapshot released since 2.4.2p2, probably close to 40 snapshots since I started using amanda. If you installed from rpm's, remove all traces of the rpm's first before installing the tarball built version. I'd found that when using RH's up2date, if it thought there was a fingerprint of amanda installed, it would cheerfully proceed to update it, thoroughly mucking up your carefully crafted local install. I'd expect something similar might occur with Suse's update tool if given half a chance. Does your distribution use inetd, or xinetd? HTH -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.23% setiathome rank, not too shabby for a WV hillbilly --- Deb Baddorf [EMAIL PROTECTED] 840-2289 You can't help getting older, but you don't have to get old. - George Burns IXOYE
amrecover file based backup and rewind
Im trying to recover some file from file based backup. Im using the changer for rotating backup folders. The problem is that amrecover wants to rewind the tape, but it tries to rewind the file:/data/Daily instead of file:/data/Daily/backup/Daily03 which is the real file backup tape. If I rewind it manually it still tries to do it and amrecover fail. Regards, Gregor
Re: amrecover file based backup and rewind
Hi Gregor, You can set your tape drive to 'file:/data/Daily/backup/Daily03' in amrecover. amrecover will not be able to use your changer if you use chg-multi, this bug was fixed a few days after 2.4.4 was release. You can a try a snapshot from http://www.iro.umontreal.ca/~martinea/amanda Jean-Louis On Thu, Mar 13, 2003 at 01:59:18AM +0100, Gregor Ibic wrote: Im trying to recover some file from file based backup. Im using the changer for rotating backup folders. The problem is that amrecover wants to rewind the tape, but it tries to rewind the file:/data/Daily instead of file:/data/Daily/backup/Daily03 which is the real file backup tape. If I rewind it manually it still tries to do it and amrecover fail. Regards, Gregor -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: Xinetd not starting amanda
On Mon, Mar 10, 2003 at 12:10:47PM -0600, Rebecca Pakish Crum said:
I am having some similar problems relating to this thread, in regards to
loading the three services below, and running 'amcheck config' on FreeBSD
5.0. I have installed both amanda-client-2.4.3, and amanda-server-2.4.3.
Can you do a chkconfig --list and see the amanda services listed under xinetd based
services and are they turned on? Do you have amanda, amandaidx and amidxtape files
in your xinetd.d directory, and do they all look something like this (respectively):
In regards to xinetd, I have not had any experience. I looked at the
xinetd.conf man page, and it said the configs outlined below need to be in
the /usr/local/etc/xinetd.conf file. If they are specified in that file,
xinetd can see them, because when any of the services are broken (ie an
invalid option specified) xinetd spits out errors.
My services are specified exactly as below, except the group is different
and the option 'disable = no' exists for all three.
xinetd appears to load without errors, and I can not see any amanda
processes loaded (but this appears to be the nature of Xinetd.) I tried to
telnet to my amanda server on ports 10080, 10082 and 10083, but only ports
10082 and 10083 responded (amandaidx and amidxtape.) Is this the correct
behaviour? Amandad does not seem to work correctly (unless it's not
supposed to load.)
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
These are the results I now get from running amcheck:
[EMAIL PROTECTED] /data/amanda]$ amcheck normal
Amanda Tape Server Host Check
-
Holding disk /data/amanda/holdingdisk: 44031578 KB disk space available, that's plenty
amcheck-server: slot 1: date Xlabel tape00 (first labelstr match)
NOTE: skipping tape-writable test
Tape tape00 label ok
NOTE: info dir /data/amanda/normal/curinfo/testies.sageautomation.com: does not exist
NOTE: info dir /data/amanda/normal/curinfo/megatron.sageautomation.com: does not exist
Server check took 0.147 seconds
Amanda Backup Client Hosts Check
ERROR: testies.sageautomation.com: [addr 192.168.8.50: hostname lookup failed]
WARNING: megatron.sageautomation.com: selfcheck request timed out. Host down?
Client check: 2 hosts checked in 30.053 seconds, 2 problems found
(brought to you by Amanda 2.4.3)
The host 'testies.sageautomation.com' exists, and is resolvable (internally.)
The host 'megatron.sageautomation.com' exists and resolves internally,
but it has no amanda services loaded on it, so its error messages are
correct.
Why am I getting a hostname lookup error for a host that exists when the
host is resolvable?
Thanks for your help.
Regards,
--
Adam Smith
Information Technology Officer
SAGE Automation Ltd.
[EMAIL PROTECTED]
http://www.sageautomation.com
Re: ACLs
On Mon, Mar 10, 2003 at 11:30:14AM -0500, Mitch Collinsworth said: On Mon, 10 Mar 2003, Adam Smith wrote: On FreeBSD 5.0 with UFS2 + ACLs, what is my best method for backing up my ACLs along with my files? I am only experimenting with Amanda at this point, but it seems to use the native tar utility, however tar does not support the backing up of ACLs. Can anyone show me what I need to do? I don't have a 5.0 system to look at, but looking briefly at the CVS tree, it appears their ACL system is designed to not require special consideration. There seems to be more explanation of the UFS1 implementation, which requires more manual setup, than the UFS2 implementation, which is natively available. Do your filesystems have a special directory at their root? Possibly .attribute ? No, with UFS2 the ACLs just 'exist' as part of the filesystem, yet I am not sure how to export them out. -- Adam Smith Information Technology Officer SAGE Automation Ltd. [EMAIL PROTECTED] http://www.sageautomation.com
Re: Xinetd not starting amanda
On Wed March 12 2003 22:01, Adam Smith wrote:
On Mon, Mar 10, 2003 at 12:10:47PM -0600, Rebecca Pakish Crum
said:
I am having some similar problems relating to this thread, in
regards to loading the three services below, and running 'amcheck
config' on FreeBSD 5.0. I have installed both
amanda-client-2.4.3, and amanda-server-2.4.3.
Can you do a chkconfig --list and see the amanda services listed
under xinetd based services and are they turned on? Do you have
amanda, amandaidx and amidxtape files in your xinetd.d
directory, and do they all look something like this
(respectively):
In regards to xinetd, I have not had any experience. I looked at
the xinetd.conf man page, and it said the configs outlined below
need to be in the /usr/local/etc/xinetd.conf file. If they are
specified in that file, xinetd can see them, because when any of
the services are broken (ie an invalid option specified) xinetd
spits out errors.
My services are specified exactly as below, except the group is
different and the option 'disable = no' exists for all three.
xinetd appears to load without errors, and I can not see any
amanda processes loaded (but this appears to be the nature of
Xinetd.) I tried to telnet to my amanda server on ports 10080,
10082 and 10083, but only ports 10082 and 10083 responded
(amandaidx and amidxtape.) Is this the correct behaviour?
Amandad does not seem to work correctly (unless it's not supposed
to load.)
service amanda
{
protocol= udp
socket_type = dgram
wait= yes
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
protocol= tcp
socket_type = stream
wait= no
user= amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
These are the results I now get from running amcheck:
[EMAIL PROTECTED] /data/amanda]$ amcheck normal
Amanda Tape Server Host Check
-
Holding disk /data/amanda/holdingdisk: 44031578 KB disk space
available, that's plenty amcheck-server: slot 1: date X
label tape00 (first labelstr match) NOTE: skipping tape-writable
test
Tape tape00 label ok
NOTE: info dir
/data/amanda/normal/curinfo/testies.sageautomation.com: does not
exist NOTE: info dir
/data/amanda/normal/curinfo/megatron.sageautomation.com: does not
exist Server check took 0.147 seconds
Amanda Backup Client Hosts Check
ERROR: testies.sageautomation.com: [addr 192.168.8.50: hostname
lookup failed] WARNING: megatron.sageautomation.com: selfcheck
request timed out. Host down? Client check: 2 hosts checked in
30.053 seconds, 2 problems found
(brought to you by Amanda 2.4.3)
It appears you have everything covered with the possible exception
of the .amandahosts file. If you configured with it, then the
allowable hosts must be listed in this file. Its discussed in the
docs. Also, make sure that the reverse lookup is correct using
dig -x 192.168.8.50. If that fails, you'll need to fix your
named records for that domain.
You should get something like this for that command:
---
[EMAIL PROTECTED] root]# dig -x 192.168.1.3
; DiG 9.2.1 -x 192.168.1.3
;; global options: printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 36320
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1,
ADDITIONAL: 1
;; QUESTION SECTION:
;3.1.168.192.in-addr.arpa. IN PTR
;; ANSWER SECTION:
3.1.168.192.in-addr.arpa. 86400 IN PTR coyote.coyote.den.
;; AUTHORITY SECTION:
1.168.192.in-addr.arpa. 86400 IN NS gene.coyote.den.
;; ADDITIONAL SECTION:
gene.coyote.den.86400 IN A 192.168.1.1
;; Query time: 18 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Mar 12 23:00:36 2003
;; MSG SIZE rcvd: 108
---
The host 'testies.sageautomation.com' exists, and is resolvable
(internally.) The host 'megatron.sageautomation.com' exists and
resolves internally, but it has no amanda services loaded on it,
so its error messages are correct.
Why am I getting a hostname lookup error for a host that exists
when the host is resolvable?
Thanks for your help.
Regards,
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.24% setiathome rank, not too shabby for a WV hillbilly
Re: Xinetd not starting amanda
On Wed, Mar 12, 2003 at 11:02:15PM -0500, Gene Heskett said: It appears you have everything covered with the possible exception of the .amandahosts file. If you configured with it, then the allowable hosts must be listed in this file. Its discussed in the docs. Also, make sure that the reverse lookup is correct using dig -x 192.168.8.50. If that fails, you'll need to fix your named records for that domain. It was both of those problems. I had only whacked in a DNS entry because of the error that was being generated, and hadn't thought about reverse DNS at the time. After running amcheck again, I got the error about the .amandahosts file, created it, and it all seems to be fine. All I need to do now is run a test backup sequence and everything should be good :-) Thanks. -- Adam Smith Information Technology Officer SAGE Automation Ltd. [EMAIL PROTECTED] http://www.sageautomation.com
