more than one Tapes?
Hi! I have installed Amanda on a SUSE Linux with a Tapechanger. So far so good. It works fine, but since Monday Amanda means that one tape is not enough. OK, one Tape can save 40GB native Data, and i must save ca. 50GB. In Amanda.conf i give Amanda one tape runtapes 1 #number of tapes to be used in a single run of amdump After changing runtapes 1 to runtapes 2, Amanda will not make backups I became the following Mail from Amanda: --begin from: Amanda Admin <[EMAIL PROTECTED]> to: [EMAIL PROTECTED]:; Datum: Wed, 24 Jan 2001 07:46:45 +0100 These dumps were to tape Daily09. Tonight's dumps should go onto 2 tapes: Daily00, Daily06. FAILURE AND STRANGE DUMP SUMMARY: fileserver sdd1 lev 0 FAILED [fileserver NAK: amandad busy] fileserver sdc1 lev 0 FAILED [fileserver NAK: amandad busy] fileserver sdb1 lev 0 FAILED [fileserver NAK: amandad busy] STATISTICS: Total Full Daily Estimate Time (hrs:min) 0:00 Run Time (hrs:min) 0:06 Dump Time (hrs:min) 0:00 0:00 0:00 Output Size (meg) 0.0 0.0 0.0 Original Size (meg) 0.0 0.0 0.0 Avg Compressed Size (%) -- -- -- Filesystems Dumped 0 0 0 Avg Dump Rate (k/s) -- -- -- Tape Time (hrs:min) 0:00 0:00 0:00 Tape Size (meg) 0.0 0.0 0.0 Tape Used (%) 0.0 0.0 0.0 Filesystems Taped 0 0 0 Avg Tp Write Rate (k/s) -- -- -- NOTES: driver: WARNING: got empty schedule from planner taper: tape Daily09 kb 0 fm 0 [OK] DUMP SUMMARY: DUMPER STATS TAPER STATS HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - fileserver sdb1 0 FAILED --- fileserver sdc1 0 FAILED --- fileserver sdd1 0 FAILED --- (brought to you by Amanda version 2.4.2-19991216-beta1) -End What is the mistake? Who can help me? Thanks Juergen -- This is a Microsoft free Mail! Have Fun!
Re: Q: tape drives beyond DLT or SLR
Hi! > > > Work on multitapebackup is (apparently) underway for Amanda NG > > > > _This_ is good news indeed. So one possible solution would be > > to go for a library instead of an autoloader, start with 1 tape > > of 50 or 100 GB capacity now - and hope AmandaNG will be available > > when we need it ;-)) > > What is "Amanda NG"? Amanda Next Generation? That's what I implied. Besides that I don't know more. I couldn't find anything on Amanda NG on www.amanda.org neither on egroups. Can someone of the people who seem to know about it give us a clue? Regards, Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- -- Patrick M. Hausen - Technical Director - [EMAIL PROTECTED] --- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
re: self check request timed out
Well I thought all was well I noticed that smbclient was missing from my config, after I added some samba shares to my disklist(my fault). I went ahead and did a 'make distclean', ran configure, make && make install. Only change, well wasn't really a change was my $PATH - added /usr/local/samba/bin/. I re-ran amcheck as user amanda and was presented with my original error message (WARNING: atsun01: selfcheck request timed out. Host down?) that started this whole thread :( I decided to start with the troubleshooting tips you supplied earlier in emails, but before I did go through the steps I thought I'd take a look at the system log. grep 'amanda' /var/adm/messages Jan 23 21:48:58 atsun01 inetd[142]: /usr/local/libexec/amandad: Segmentation Fault Jan 23 21:49:00 atsun01 last message repeated 2 times Jan 23 21:49:37 atsun01 last message repeated 35 times Jan 23 21:49:38 atsun01 inetd[142]: amanda/udp server failing (looping), service terminated This is the first time I've seen the system whining about amanda. Argh...so close . Thanks, -Ben
Re: Amanda/Sol8 + Exabyte X80 + HIARCjb
Check the december archives. I know someone who put in the tapetype of the
Mammoth 2 drive.
I know this is redundant but this is what was given:
define tapetype M2-AME225 {
comment "Mammoth2 with AME225"
length 57487 mbytes
filemark 0 kbytes
speed 11765 kbytes
}
As a rule of thumb, if you got a question, its most likely been
asked. =) I know, I had that same question.
I give thatnks to those who have spent the time finding these things
out for us.
Tanniel Simonian
UC Riverside Libraries
On Tue, 23 Jan 2001, Richard Michael wrote:
> Hello,
>
> I've researched a new backup config that I need to build and would like
> to solicit comments from people who have been using Amanda for awhile
> (this is my first config).
>
> Does someone have tapetype entries for mammoth2 media? (I'd like to avoid
> running the media through once wit tapetype. Though, if I run tapetype,
> I'll post :)
>
> Running on Solaris, what are the issues I should be aware of when
> considering gnutar versus ufsrestore? (other than the xtr bug in Sol8's
> ufsrestore from awhile back).
>
> Can someone please email Josh Huston's perl script for the
> HIARCjb driver to me? The eGroups archiver does a nice job of mutiliating
> the text in the body.
>
> Josh -> Thanks for the work, your script will help me along immensely.
>
> Thanks for any comments/advice.
>
> Regards,
> Richard
>
Re: Strange processes that wont die
>... I still have leftover amandad processes lingering on the >client and server, only a couple on the client, but TONS on the >server, what could be causing this, or is this normal? Thanks What version of Amanda? Where did you get it and how did you build it? The server does not use amandad except when it treating itself as a client, so I doubt it being the server is explicitly an issue. Can you attach a debugger to one of the amandad's and get a stack traceback? What's in /tmp/amanda/amandad*debug? >Phil John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: self check request timed out
Okay, A reboot seemed to fix things - weird. I enabled the original amadad entry in /etc/inetd.conf and restarted. Went ahead and ran amcheck atlab as user amanda and it is now creating amandad.debug && selfcheck.debug in /tmp/amanda. Ahhh.. now this is much better :) cat /tmp/amanda/selfcheck.debug selfcheck: debug 1 pid 323 ruid 101 euid 101 start time Tue Jan 23 18:15:41 2001 /usr/local/libexec/selfcheck: version 2.4.1p1 checking disk /apps: device /dev/md/rdsk/d0: OK checking disk /opt: device /dev/rdsk/c0t1d0s1: OK checking disk /export/home: device /dev/rdsk/c0t0d0s3: OK checking disk /usr: device /dev/rdsk/c0t1d0s3: OK checking disk /: device /dev/rdsk/c0t0d0s0: OK Thanks for your help troubleshooting this John. Regards, -Ben
Strange processes that wont die
Hi all, I have a strange issue. I have setup a new server and am migrating to it, and all seems well, backups are happening et al, but, I do have one really strange side effect. When I run an amcheck or amdump, after it finishes supposedly just fine, I still have leftover amandad processes lingering on the client and server, only a couple on the client, but TONS on the server, what could be causing this, or is this normal? Thanks Phil -- Phillip Davis, MIS Department 415.354.4238 tel or x4238 @ 415.354.4878 [EMAIL PROTECTED], http://www.linuxcare.com/ Linuxcare. Support for the Revolution.
Re: self check request timed out
>Removed the directory, re-ran amcheck... nothing. "nothing" as in the directory was not re-created, or "nothing" as in it was created but no files were in it? >This is where I'm really getting confused. There is no /tmp/run-amandad.out >being created Then inetd is not running amandad for some reason. I know you did the "netstat" thing before, but maybe you should do it again? And take a look at the system log files to see if it's whining about anything. Are you sure the "amanda" service is registered properly (in particular, the same port number) on both server and client? There's a little test program at: ftp://gandalf.cc.purdue.edu/pub/amanda/getservbyname.c If none of **that** gets you anywhere :-), try running truss against inetd while you run amcheck: truss -f -w 2 -p >Running the script manually in /tmp works fine. Good. Go ahead and blow away /tmp/amanda again, just so we're starting at a clean point each time. >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: self check request timed out
>I removed everything from the /tmp/amanda dir and re-ran amcheck. >Nothing, absolutely nothing shows up in the /tmp/amanda dir - it's mode 0775 >amanda:sys I don't think it matters, but that's not how Amanda would create the directory. Try removing the directory itself and running amcheck again. Did the directory get recreated? >> Is /usr/local/libexec/amandad the exact same thing you have in inetd.conf? > >Here's the line for amandad in my /etc/inetd.conf >amanda dgram udp waitamanda /usr/local/libexec/amandad amandad OK. Just checking one more thing off the list. Here's the next thing to try (if the above doesn't help). Duplicate your current inetd.conf line, comment out the original and change the duplicate to something like this: amanda dgram udp waitamanda /tmp/run-amandad amandad Then in /tmp/run-amandad put this (fix the path to "truss"): #!/bin/sh exec > /tmp/run-amandad.out 2>&1 echo "Starting amandad: `date`" /path/to/truss -f -w 2 /usr/local/libexec/amandad status=$? echo "Ending amandad: status: $status: `date`" exit $status Then chmod +x /tmp/run-amandad, send a HUP to inetd and try amcheck again. The idea is to run amandad under truss to see all the system calls. Hopefully one of them will show that the log files are going someplace else, or that there is some other kind of error. Obviously this is just for debugging and we'll put it back when the problem is determined. >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: self check request timed out
> I'd suggest blowing away /tmp/amanda, doing the amcheck, and then seeing > what's in there. There should be an amandad*debug and selfcheck*debug, > both recently updated (as of the time of the amcheck). Take a look at > the first few lines of each (assuming they are both there) and an "ls -l" > to verify they are brand new. I removed everything from the /tmp/amanda dir and re-ran amcheck. Nothing, absolutely nothing shows up in the /tmp/amanda dir - it's mode 0775 amanda:sys > Is /usr/local/libexec/amandad the exact same thing you have in inetd.conf? Here's the line for amandad in my /etc/inetd.conf amanda dgram udp waitamanda /usr/local/libexec/amandad amandad > Let's keep tracking this for the moment. Okay > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -Ben
Re: self check request timed out
>> What's in the matching amandad*debug file? > >It's not being updated by amcheck :( Whoa, there. If amandad*debug is not being updated, neither should selfcheck*debug. They log to the same directory. I'd suggest blowing away /tmp/amanda, doing the amcheck, and then seeing what's in there. There should be an amandad*debug and selfcheck*debug, both recently updated (as of the time of the amcheck). Take a look at the first few lines of each (assuming they are both there) and an "ls -l" to verify they are brand new. >When run manually as user amanda /usr/local/libexec/./amandad I get the >following in /tmp/amanda/amandad.debug That's correct. Is /usr/local/libexec/amandad the exact same thing you have in inetd.conf? >Would it be worth a try to configure/install the new version 2.4.2? Let's keep tracking this for the moment. >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: self check request timed out
> What's in the matching amandad*debug file? It's not being updated by amcheck :( When run manually as user amanda /usr/local/libexec/./amandad I get the following in /tmp/amanda/amandad.debug amandad: debug 1 pid 11289 ruid 101 euid 101 start time Tue Jan 23 13:58:41 2001 ./amandad: version 2.4.1p1 ./amandad: build: VERSION="Amanda-2.4.1p1" ./amandad:BUILT_DATE="Mon Jan 22 16:32:45 PST 2001" ./amandad:BUILT_MACH="SunOS atsun01 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-4" ./amandad:CC="gcc" ./amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" ./amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" ./amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" ./amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" ./amandad:RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/tar" ./amandad:COMPRESS_PATH="/usr/local/bin/gzip" ./amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" ./amandad:MAILER="/usr/ucb/Mail" ./amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" ./amandad: defs: DEFAULT_SERVER="atsun01" DEFAULT_CONFIG="atlab" ./amandad:DEFAULT_TAPE_SERVER="atsun01" ./amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0hn" HAVE_MMAP HAVE_SYSVSHM ./amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY ./amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP ./amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" ./amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: error receiving message: timeout Would it be worth a try to configure/install the new version 2.4.2? > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -Ben
Re: Diagnosing client-side errors
> LABEL=/ / ext2defaults1 1 >... >The first two line were created automatically during RedHat 7 installation. >The third line was created by hand. I guess the LABEL= notation is to allow >moving disks or filesystems around and still have them found and mounted at >boottime. I have a patch for this (compliments of testing by Ben Elliston) that I'll get into 2.4.2p1, which should be out in a day or two. Note that it contains a bit of a hack (the #define of HAVE_SETMNTENT) because it is too hard to send out ./configure patches. The real release will do the right thing. >Ron John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] getfsent.diff
Re: self check request timed out
>REQ packet is bogus? Well, that's a new one. What's in the matching amandad*debug file? >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: self check request timed out
> OK, that's all normal. But I asked what was in selfcheck*debug, not > amandad*debug. Ugh, sorry about that. * I ran this manually as user amanda - it does not get updated on amcheck * selfcheck: debug 1 pid 11368 ruid 101 euid 101 start time Tue Jan 23 14:15:54 2001 ./selfcheck: version 2.4.1p1 REQ packet is bogus selfcheck: pid 11368 finish time Tue Jan 23 14:16:25 2001 REQ packet is bogus? grep 'amanda' /etc/inetd.conf # Advanced Maryland Automatic Network Disk Archiver amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped amanda dgram udp waitamanda /usr/local/libexec/amandad amandad grep 'amanda' /etc/services # Advanced Maryland Automatic Network Disk Archiver amanda 10080/udp # Amanda backup server amandaidx 10082/tcp # Amanda backup server amidxtape 10083/tcp # Amanda backup server > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks, -Ben
Re: Diagnosing client-side errors
On Tue, 16 Jan 2001, Ben Elliston wrote: > I am trying to back up a single partition having just installed Amanda. I > thought I'd try with this in my `disklist': > > scooby sda8 always-full > > I get the following error, but can't work out what I'm doing wrong. Any > tips? In general, how can I diagnose client-side problems? > > Thanks, B. > > > Amanda Backup Client Hosts Check > > ERROR: scooby: [can not access sda8 (sda8): No such file or directory] > Client check: 1 host checked in 0.014 seconds, 1 problem found > > (brought to you by Amanda 2.4.2) I just ran into this with RedHat 7. amanda found two out of three filesystems. The fstab contains LABEL=/ / ext2defaults1 1 LABEL=/boot /boot ext2defaults1 2 /dev/sdb1 /home ext2defaults2 2 The first two line were created automatically during RedHat 7 installation. The third line was created by hand. I guess the LABEL= notation is to allow moving disks or filesystems around and still have them found and mounted at boottime. Ron [EMAIL PROTECTED]
Re: amtape update command fails to read tapes on chacking changer
>1. tape device or changer issue? ... I'd strongly suspect a problem with the changer code rather than with the drive. >At the end of this I'll place the amanda.conf and changer.conf files... I suspect we also need to see /tmp/amanda/changer*debug. That's where all the good stuff is :-). >2. Timing issue? Is there a parameter in the changer.conf that could be >set to eliminate this? An edit that could be made in the source code? Yes. Let us know when you find it :-). >I've also had the changer hang hard when an amanda job failed and aborted >because of a config file error. ... Posting the matching /tmp/amanda/changer*debug file that matches is probably the best way to proceed. >--doug John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: self check request timed out
>> Is /tmp/amanda/selfcheck*debug getting updated on atsun01? What's in it? >amandad: error receiving message: timeout OK, that's all normal. But I asked what was in selfcheck*debug, not amandad*debug. >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: self check request timed out
> OK, but I have to ask a few questions anyway to make sure something > wasn't lost in translation. Sure > Is /tmp/amanda/amandad*debug getting updated on atsun01? Yes, ls -lu /tmp/amanda/amandad.debug confirms this. > What happens if you run .../amandad by hand **as the Amanda user** > (the one listed in inetd.conf)? It should sit for 30 seconds and then > terminate, but /tmp/amanda/amandad*debug will be updated. /tmp/amanda/amandad.debug gets updated as you say. > Is /tmp/amanda/selfcheck*debug getting updated on atsun01? What's in it? amandad: debug 1 pid 11289 ruid 101 euid 101 start time Tue Jan 23 13:58:41 2001 ./amandad: version 2.4.1p1 ./amandad: build: VERSION="Amanda-2.4.1p1" ./amandad:BUILT_DATE="Mon Jan 22 16:32:45 PST 2001" ./amandad:BUILT_MACH="SunOS atsun01 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-4" ./amandad:CC="gcc" ./amandad: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" ./amandad:libexecdir="/usr/local/libexec" mandir="/usr/local/man" ./amandad:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/dsk/" ./amandad:RDEV_PREFIX="/dev/rdsk/" DUMP="/usr/sbin/ufsdump" ./amandad:RESTORE="/usr/sbin/ufsrestore" GNUTAR="/usr/local/bin/tar" ./amandad:COMPRESS_PATH="/usr/local/bin/gzip" ./amandad:UNCOMPRESS_PATH="/usr/local/bin/gzip" ./amandad:MAILER="/usr/ucb/Mail" ./amandad:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" ./amandad: defs: DEFAULT_SERVER="atsun01" DEFAULT_CONFIG="atlab" ./amandad:DEFAULT_TAPE_SERVER="atsun01" ./amandad:DEFAULT_TAPE_DEVICE="/dev/rmt/0hn" HAVE_MMAP HAVE_SYSVSHM ./amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY ./amandad:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP ./amandad:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" ./amandad:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" amandad: error receiving message: timeout > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Thanks, -Ben
Re: self check request timed out
Ben Hyatt wrote: > > Hello, > > amcheck returns the following on my tape server host (atsun01) e450 2.7 > solaris: > > (*insecure*)amanda@atsun01:/usr/local/etc/amanda/atlab$ amcheck atlab > Amanda Tape Server Host Check > - > /apps/backup/amanda: 9710434 KB disk space available, using 9505634 KB. > NOTE: skipping tape-writable test. > Tape atlab01 label ok. > Server check took 5.630 seconds. > > Amanda Backup Client Hosts Check > > WARNING: atsun01: selfcheck request timed out. Host down? > Client check: 7 hosts checked in 30.191 seconds, 1 problem found. > > (brought to you by Amanda 2.4.1p1) > > First, let me start by saying I've checked the faq o'matic and > verified the steps people suggested. > > netstat -an |grep 10080 reports that amanda is indeed listening. > *.10080 *.*0 0 0 0 LISTEN Does amandad really get spawned? Look at the access time (ls -lu) of /usr/local/libexec/wherever/amandad. What's in /tmp/amanda/selfcheck.debug?
Re: Q: tape drives beyond DLT or SLR
> > Work on multitapebackup is (apparently) underway for Amanda NG > > _This_ is good news indeed. So one possible solution would be > to go for a library instead of an autoloader, start with 1 tape > of 50 or 100 GB capacity now - and hope AmandaNG will be available > when we need it ;-)) What is "Amanda NG"? Amanda Next Generation?
Re: self check request timed out
>WARNING: atsun01: selfcheck request timed out. Host down? >... >First, let me start by saying I've checked the faq o'matic and >verified the steps people suggested. OK, but I have to ask a few questions anyway to make sure something wasn't lost in translation. Is /tmp/amanda/amandad*debug getting updated on atsun01? What happens if you run .../amandad by hand **as the Amanda user** (the one listed in inetd.conf)? It should sit for 30 seconds and then terminate, but /tmp/amanda/amandad*debug will be updated. Is /tmp/amanda/selfcheck*debug getting updated on atsun01? What's in it? >-Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: FAILURE AND STRANGE DUMP SUMMARY
We had a similar problem (well, the exact same problem) but ended up getting the computer in question to backup to a share, and getting amanda to backup the share which contained 1 big file because I was getting annoyed with it. Only problem is, that smbclient doesn't know how to read files > 2G or thereabouts, which means it returns a file size of -197M to the planner. Obviously, the planner feels this is an unusual state of affairs, not being versed with an imagination, and refuses to try and backup -197M. Apparently it's a samba problem; unfortunately not one we've worked out - if you do suss it then please let me know! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mitch Collinsworth Sent: Wednesday, 24 January 2001 02:14 To: Gerald T. Freymann Cc: [EMAIL PROTECTED] Subject: Re: FAILURE AND STRANGE DUMP SUMMARY On Tue, 23 Jan 2001, Gerald T. Freymann wrote: > FAILURE AND STRANGE DUMP SUMMARY: > amanda file://xxx/PAP2 lev 0 STRANGE > > And then what follows is a line by line blow of each and every file that > got backed up. > > How do you make Amanda think these PC shares are no longer "Strange?" You didn't say what versions of amanda and samba you're using. I used to see this with old versions when I had samba configured with too high a logging level. It's been so long since I've looked at this I don't now remember what the correct level is, but this is where I'd suggest looking first. -Mitch P.S. You have a very catchy name. Well to me anyhow, since I have an uncle named Jerry Freyman. :-)
Re: Estimates
"John R. Jackson" <[EMAIL PROTECTED]> writes: > >When amstatus reports on estimates, are these supposed to be the estimates > >for the volume of data dumped at the specified dump level? ... > > Yes. They are the estimates for the level Amanda picked to be done. That depends on when you look at the estimates. As long as estimating is still running on at least one client, the reported estimates are all level 0 dump estimates. As soon as the dumping begins, it shows the estimates for the dump levels picked. > >Ben > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] Jens Bech Madsen -- Jens Bech Madsen The Stibo Group, Denmark
self check request timed out
Hello, amcheck returns the following on my tape server host (atsun01) e450 2.7 solaris: (*insecure*)amanda@atsun01:/usr/local/etc/amanda/atlab$ amcheck atlab Amanda Tape Server Host Check - /apps/backup/amanda: 9710434 KB disk space available, using 9505634 KB. NOTE: skipping tape-writable test. Tape atlab01 label ok. Server check took 5.630 seconds. Amanda Backup Client Hosts Check WARNING: atsun01: selfcheck request timed out. Host down? Client check: 7 hosts checked in 30.191 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) First, let me start by saying I've checked the faq o'matic and verified the steps people suggested. netstat -an |grep 10080 reports that amanda is indeed listening. *.10080 *.*0 0 0 0 LISTEN Any ideas? Thanks, -Ben
Amanda/Sol8 + Exabyte X80 + HIARCjb
Hello, I've researched a new backup config that I need to build and would like to solicit comments from people who have been using Amanda for awhile (this is my first config). Does someone have tapetype entries for mammoth2 media? (I'd like to avoid running the media through once wit tapetype. Though, if I run tapetype, I'll post :) Running on Solaris, what are the issues I should be aware of when considering gnutar versus ufsrestore? (other than the xtr bug in Sol8's ufsrestore from awhile back). Can someone please email Josh Huston's perl script for the HIARCjb driver to me? The eGroups archiver does a nice job of mutiliating the text in the body. Josh -> Thanks for the work, your script will help me along immensely. Thanks for any comments/advice. Regards, Richard
Re: barcode reader update to labelfile?
I think I found my own answer to this question. I found that the labelfile will be created by amlabel as each tape is labeled... --doug At 01:42 PM 1/23/2001 -0500, you wrote: >An additional question - >the Ecrix VXA autopak has a bar code reader which amanda initially used >and set up /usr/local/etc/amanda/daily/labelfile with tape labels and >barcodes - > >Can I force amanda to re-examine this library and re-write the labelfile? >Which command? >Or just wipe out the existing file? > >--doug > > > > > >Doug Munsinger > >egenera, Inc. >[EMAIL PROTECTED] >563 Main Street, Bolton, MA 01740 >Tel: 508-786-9444 ext. 2612 >OR 508-481-5493 >fax: 978 779-9730 Doug Munsinger egenera, Inc. [EMAIL PROTECTED] 563 Main Street, Bolton, MA 01740 Tel: 508-786-9444 ext. 2612 OR 508-481-5493 fax: 978 779-9730
Re: temporary skip a tape
> Alexandre> Reduce tapecycle by one, so that Amanda will accept > Alexandre> daily-1. You may also want to mark daily-0 as no reuse > Alexandre> with amadmin. > >Thanks ok, but what do I do when I have access to the tape skipped >again and want to include it in the cycle again (with the same name)? Crank tapecycle back up by one and use amadmin to mark the tape "reuse". As it's probably the oldest tape in the tapelist file, it will be the next one requested. You can check that with "amadmin tape". > / Erik John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Estimates
>When amstatus reports on estimates, are these supposed to be the estimates >for the volume of data dumped at the specified dump level? ... Yes. They are the estimates for the level Amanda picked to be done. >Every day when >Amanda runs, I see the same huge estimates for disks that, once backed up, >only had a few hundred KB of incrementals to do. You might poke through the amdump. files. The first part is the estimating phase and it's not too hard to see the results coming back. If those are really wrong, the next place I'd look is a typical /tmp/amanda/sendsize*debug file on a client and see what's going on in there. You really don't want those estimates to be way off. It can severely confuse Amanda. Not to the point of doing something terribly wrong, but easily to the point of doing more work than it should. >Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amdump failed: missing estimate
>... when I try to run amdump, >it's done within less than a second, and exits' because it doesn't get >any estimates. What's in /tmp/amanda/sendsize*debug on the client? >Marion John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: avoiding level 0 dumps
>I back up a partition on a remote machine, connected by a 28.8k modem. Ick. :-) >After only two days, Amanda has decided to do a level 0 backup of this >partition, which seems strange, if not wrong. It's probably trying to balance the load. It takes a couple of cycles after changing your configuration (e.g. adding/removing clients or disks) to get things ordered properly again. But once it does, it will probably settle down to only doing this one once per cycle. >Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
barcode reader update to labelfile?
An additional question - the Ecrix VXA autopak has a bar code reader which amanda initially used and set up /usr/local/etc/amanda/daily/labelfile with tape labels and barcodes - Can I force amanda to re-examine this library and re-write the labelfile? Which command? Or just wipe out the existing file? --doug Doug Munsinger egenera, Inc. [EMAIL PROTECTED] 563 Main Street, Bolton, MA 01740 Tel: 508-786-9444 ext. 2612 OR 508-481-5493 fax: 978 779-9730
amtape update command fails to read tapes on chacking changer
I am running amanda 2.4.2 compiled from source on RedHat 6.2 running
2.2.16-3 RedHat kernel.
I have successfully set up and run amdump configurations for daily, full
and offsite backups.
I have verified SOME (still testing this) restores using amrestore with
good results.
My tape library is a Ecrix VXA autopak with a single VXA drive.
All tapes are Ecrix VXA 17.
The scsi card is an adaptec 29160.
The computer is a dell optiplex GX110 with 2 30 GB and one 45 GB ide drive
(testing machine).
When running /usr/local/sbin/amtape daily update I consistently get the
following result:
amtape: scanning all 15 slots in tape-changer rack:
slot 8: rewinding tape: Input/output error
slot 9: rewinding tape: Input/output error
IF a tape is already loaded, then I will get a result for that first tape,
then a repeat of the input/output error...
But I can run the simpler amtape commands one at a time and work around the
errors.
[amanda@ford daily]$ /usr/local/sbin/amtape daily slot 1
amtape: changed to slot 1 on /dev/nst0
[amanda@ford daily]$ mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 1024 bytes. Density code 0x80 (unknown to this mt).
Soft error count since last status=0
General status bits on (4101):
BOT ONLINE IM_REP_EN
[amanda@ford daily]$ mt -f /dev/nst0 rewind
[amanda@ford daily]$ mt -f /dev/nst0 rewind
[amanda@ford daily]$ ls
amanda.conf changer.conf-access changer.conf-slot labelfile tapelist
tapelist.yesterday
changer.conf changer.conf-clean disklist tape0-slot
tapelist.amlabel tapestatus
[amanda@ford daily]$ /usr/local/sbin/amtape daily update
amtape: scanning all 15 slots in tape-changer rack:
slot 1: date 20010116 label Daily-Set1-03
slot 2: rewinding tape: Input/output error
I wrote a perl hack to label tapes and adapted it to run a check on all
slots in the changer:
#! /usr/local/bin/perl
use strict;
use Carp;
#path to the amtape binary
my $AMTAPE = "/usr/local/sbin/amtape";
#path to amlabel binary
my $AMLABEL = "/usr/local/sbin/amlabel";
#comand to use for rewinding the tape drive
my $rewind = "/bin/mt -f /dev/nst0 rewind";
# this will be either "daily" or "archive"
#my $type = "archive";
my $type = "daily";
# skipping slot 0 which is a cleaning tape
my @slots = qw(1 2 3 4 5 6 7 8 9 10 11 12 13 14);
#these are the result codes for the checking commands
#the linux OS indicates success with "0" so these are set to something else
to start
my $eject_result = 1;
my $load_result = 1;
my $rew_result = 1;
my $curr_result = 1;
#start a log file...
`date > /tmp/amanda_changer_tapes`;
`echo "" >> /tmp/amanda_changer_tapes`;
foreach (@slots) {
#eject the tape
print ("ejecting current tape...\n");
while ($eject_result != 0) {
$eject_result = system("$AMTAPE $type eject");
print ("eject result: $eject_result\n");
}
$eject_result = 1; # reset for the next loop...
#load the tape
print ("loading proper tape in slot $_...\n");
while ($load_result != 0) {
$load_result = system("$AMTAPE $type slot $_");
print ("load result: $load_result\n");
}
$load_result = 1; # reset for the next loop...
#rewind the tape - note the sleep commands let the tape settle in
the drive...
while ($rew_result != 0) {
`sleep 20`;
print ("rewinding tape...\n");
$rew_result = system("$rewind");
print ("rewind result: $rew_result\n");
}
$rew_result = 1; # reset for the next loop...
while ($curr_result != 0) {
print ("$AMTAPE $type current\n");
$curr_result = system("$AMTAPE $type current >>
/tmp/amanda_changer_tapes 2>&1");
print ("amtape program has written tape data to
/tmp/amanda_changer_tapes file\n");
print ("current result: $curr_result\n");
}
$curr_result = 1; #reset for the next loop...
`sleep 15`;
}
...and the result is:
Tue Jan 23 11:47:37 EST 2001
amtape: scanning current slot in tape-changer rack:
slot 1: date 20010116 label Daily-Set1-03
amtape: scanning current slot in tape-changer rack:
slot 2: date Xlabel Daily-Set1-04
amtape: scanning current slot in tape-changer rack:
slot 3: date Xlabel Daily-Set1-05
amtape: scanning current slot in tape-changer rack:
slot 4: date Xlabel Daily-Set1-06
amtape: scanning current slot in tape-changer rack:
slot 5: date Xlabel Daily-Set1-07
This script made it to about tape number 11 (an unlabeled tape, slot 12)
out of 15 slots before crapping out.
Questions I hope for help with:
1. tape device or changer issue? I have mostly discarded this since the
amtape program will issue commands to the changer and get a response most
of the time. I haven't entirely discarded this because someti
Re: FAILURE AND STRANGE DUMP SUMMARY
Gerald T. Freymann <[EMAIL PROTECTED]> wrote: > I'm using Amanda 2.4.1p1 and Samba 2.0.7 You should apply the patch http://www.amanda.org/patches/2.4.1p1/samba2-2418.diff or upgrade to amanda-2.4.2 HTH, Lipo -- Roland E. Lipovits Vienna, Austria
Re: Reiser
> Sure, if you think 50GB and 100GB are "larger" :) I have to split them
> up according to directory structure, though, due to the nature of the
> data on them {O(4) files in a directory takes (g)tar a relatively long
> time} and the size of the tapes I'm using (Ecrix VXA V17 - 33/66GB). I
> also backup similarly-sized ext2 FS's with large file support.
Thanks for the advice. I don't consider 50-100 being all that large, but on
a workstation with an IDE bus, it gets to be a bit of a drag pulling all that
data off it.
--
Joshua Warchol
UNIX Systems Administrator
DSL.net
RE: RedHat 7.0
On Tue, 16 Jan 2001, Chris Herrmann wrote: > RH7 will use xinet.d. here's one i prepared before... you'll need to check > the directories etc though I found I had to add group = disk to the amanda service, otherwise I got ERROR: spitfire: [can not access /dev/sdb3 (sdb3): Permission denied] ERROR: spitfire: [can not access /dev/sda1 (sda1): Permission denied] ERROR: spitfire: [can not read/write /etc/dumpdates: Permission denied] even though amanda's passwd entry specified the disk group. Ron Stanonik [EMAIL PROTECTED]
Re: avoiding level 0 dumps
On Wed, Jan 24, 2001 at 12:06:38AM +1100, Ben Elliston wrote: > I back up a partition on a remote machine, connected by a 28.8k modem. > After only two days, Amanda has decided to do a level 0 backup of this > partition, which seems strange, if not wrong. > > How can I discourage her from doing level 0s until the end of the dumpcycle? > Almost nothing is as bad as doing a level 0 over this link. Consider maintaining a local image of anything at the far end of such a slow link. "rsync -avx -e ssh" can be used. The advantage of this is you do the level 0, effectively, only once over the slow link. The rsync program transfers only incremental changes after that. I run amanda from a shell script invoked over cron. This script does any necessary preparation, including rsync of remote sites, database dumps, and so on, runs the amanda backups, then ejects the tape. -- - Dan Wilder <[EMAIL PROTECTED]> Technical Manager & Correspondent SSC, Inc. P.O. Box 55549 Phone: 206-782-7733 x123 Seattle, WA 98155-0549 URLhttp://www.linuxjournal.com/ -
Re: Using LTO drives with amanda? (oops, lto.ps)
* Chris Stoddart <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 03:55:46PM +) Oops. I noticed the lto.ps has a logo included with it, you proabbly don't want the logo in there if you use it , so you have to hack it out of the postscript again ;) Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Some say the end is near. =`\<, Some say we'll see armageddon soon (=)/(=) I certainly hope we will I could use a vacation
Using LTO drives with amanda?
Guys, I'm in the rather happy position of being able to start replacing my ageing DAT drives with a bigger, faster setup. Apart from considering the obvious DLT drives I have been looking at the new LTO drives. Has anyone managed to use an LTO Ultrium drive with amanda? Care to share a 'Tapetype' section of amanda.conf for a HPC7369? Any gotchas that should steer me towards DLT instead? Thanks in advance for any advice/experience. Chris -- Dr Chris Stoddart: Unix SysAdmin, Department of Computer Science, Sheffield University, U.K.
Re: FAILURE AND STRANGE DUMP SUMMARY
> You didn't say what versions of amanda and samba you're using. I > used to see this with old versions when I had samba configured with > too high a logging level. I'm using Amanda 2.4.1p1 and Samba 2.0.7 > P.S. You have a very catchy name. Well to me anyhow, since I > have an uncle named Jerry Freyman. :-) Oh? We're from Lithuanian (sp?) originally... Grandma landed in Toronto, Ontario, Canada many moons ago. Grandfather was left behind as a POW. -Gerry
Re: FAILURE AND STRANGE DUMP SUMMARY
On Tue, 23 Jan 2001, Gerald T. Freymann wrote: > FAILURE AND STRANGE DUMP SUMMARY: > amanda file://xxx/PAP2 lev 0 STRANGE > > And then what follows is a line by line blow of each and every file that > got backed up. > > How do you make Amanda think these PC shares are no longer "Strange?" You didn't say what versions of amanda and samba you're using. I used to see this with old versions when I had samba configured with too high a logging level. It's been so long since I've looked at this I don't now remember what the correct level is, but this is where I'd suggest looking first. -Mitch P.S. You have a very catchy name. Well to me anyhow, since I have an uncle named Jerry Freyman. :-)
Re: Reiser
Joshua E Warchol wrote:
>
> Has anyone successfully backed up larger reiserfs partitions? One of my co-
> workers has setup a new Linux workstation with reiserfs for everything but
> /boot. Boy, am I glad he did that :-(
Sure, if you think 50GB and 100GB are "larger" :) I have to split them
up according to directory structure, though, due to the nature of the
data on them {O(4) files in a directory takes (g)tar a relatively long
time} and the size of the tapes I'm using (Ecrix VXA V17 - 33/66GB). I
also backup similarly-sized ext2 FS's with large file support.
reiserfs has not given me any trouble at all w.r.t. backups. I don't
think there is a stable 'dump' for reiserfs yet, so you'll have to stick
with GNU tar.
Michael
Re: Reiser
* Joshua E Warchol <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 09:02:36AM -0500) > Has anyone successfully backed up larger reiserfs partitions? One of my co- Depending on what you mean by larger ... My own linux box has 2 reiser partitions, the OS (which doesn't get backed up) and my personal data (which does ;) [~ 8G ]). And we've got a number crucnher that has 2 reiser partitions (6 and 18G) and they back up just fine. Of course, you have to use tar to make a backup, since there is no dump for reiser. ^^ > workers has setup a new Linux workstation with reiserfs for everything but > /boot. Boy, am I glad he did that :-( Well, I for one am very happy with it. 1) it actually *is* fatser than ext2 2) never having to fsck an 18G partition after a hard crash (and yes, I know, linux boxes shouldn';t hard crash, but then, you shouldn't be playing with alpha and beta level kernel drivers ;) ) Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\<, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
amdump failed: missing estimate
Hi, I'm trying to set uo amanda for backing up just one computer. Amcheck runs fine, doesn't detect any problems, but when I try to run amdump, it's done within less than a second, and exits' because it doesn't get any estimates. Here's what amanda tells me about the dump: amdump: start at Fri Jan 19 15:28:43 CET 2001 driver: pid 16634 executable /usr/local/libexec/driver version 2.4.2 driver: send-cmd time 0.003 to taper: START-TAPER 20010119 planner: pid 16633 executable /usr/local/libexec/planner version 2.4.2 planner: build: VERSION="Amanda-2.4.2" planner:BUILT_DATE="Fri Jan 12 17:59:02 CET 2001" planner:BUILT_MACH="Linux maulaf.isd.uni-stuttgart.de 2.2.17 #3 Thu Oct 26 21:09:13 CEST2000 i686 unknown" planner:CC="gcc" planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" planner:libexecdir="/usr/local/libexec" mandir="/usr/local/man" planner:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" planner:CONFIG_DIR="/usr/local/etc/amanda" DEV_PREFIX="/dev/" planner:RDEV_PREFIX="/dev/" DUMP="/sbin/dump" planner:RESTORE="/sbin/restore" planner:GNUTAR="/usr/local/etc/amanda/tar/bin/tar" planner:COMPRESS_PATH="/usr/bin/gzip" planner:UNCOMPRESS_PATH="/usr/bin/gzip" MAILER="/usr/bin/Mail" planner:listed_incr_dir="/usr/local/var/amanda/gnutar-lists" planner: defs: DEFAULT_SERVER="maulaf.isd.uni-stuttgart.de" planner:DEFAULT_CONFIG="weekly" planner:DEFAULT_TAPE_SERVER="maulaf.isd.uni-stuttgart.de" planner:DEFAULT_TAPE_DEVICE="/dev/null" HAVE_MMAP HAVE_SYSVSHM planner:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE BSD_SECURITY planner:USE_AMANDAHOSTS CLIENT_LOGIN="amanda" FORCE_USERID HAVE_GZIP planner:COMPRESS_SUFFIX=".gz" COMPRESS_FAST_OPT="--fast" planner:COMPRESS_BEST_OPT="--best" UNCOMPRESS_OPT="-dc" READING CONF FILES... startup took 0.028 secs SETTING UP FOR ESTIMATES... setting up estimates for maulaf:/disk2/home/mack driver: started dumper0 pid 16636 driver: started dumper1 pid 16637 driver: started dumper2 pid 16638 driver: started dumper3 pid 16639 taper: pid 16635 executable taper version 2.4.2 maulaf:/disk2/home/mack overdue 11342 days for level 0 setup_estimate: maulaf:/disk2/home/mack: command 0, options: last_level -1 next_level0 -11342 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates for maulaf:/disk2/home/trittler dumper: pid 16636 executable dumper version 2.4.2, using port 536 dumper: pid 16637 executable dumper version 2.4.2, using port 537 dumper: pid 16639 executable dumper version 2.4.2, using port 539 dumper: pid 16638 executable dumper version 2.4.2, using port 538 taper: read label `/dev/null' date `X' taper: wrote label `/dev/null' date `20010119' maulaf:/disk2/home/trittler overdue 11342 days for level 0 setup_estimate: maulaf:/disk2/home/trittler: command 0, options: last_level -1 next_level0 -11342 level_days 0 getting estimates 0 (0) -1 (-1) -1 (-1) setting up estimates took 0.172 secs GETTING ESTIMATES... error result for host maulaf disk /disk2/home/trittler: missing estimate error result for host maulaf disk /disk2/home/mack: missing estimate getting estimates took 0.149 secs FAILED QUEUE: 0: maulaf /disk2/home/trittler 1: maulaf /disk2/home/mack DONE QUEUE: empty ANALYZING ESTIMATES... planner: FAILED maulaf /disk2/home/trittler 0 [missing result for /disk2/home/trittler in maulaf response] planner: FAILED maulaf /disk2/home/mack 0 [missing result for /disk2/home/mack in maulaf response] INITIAL SCHEDULE (size 64): DELAYING DUMPS IF NEEDED, total_size 64, tape length 12582912 mark 0 delay: Total size now 64. PROMOTING DUMPS IF NEEDED, total_lev0 0, balanced_size 0... analysis took 0.026 secs GENERATING SCHEDULE: reserving 0 out of 0 for degraded-mode dumps driver: start time 0.393 inparallel 4 bandwidth 2000 diskspace 0 dir OBSOLETE datestamp 20010119 driver: drain-ends tapeq LFFO big-dumpers 1 driver: result time 0.393 from taper: TAPER-OK driver: state time 0.393 free kps: 2000 space: 0 taper: idle idle-dumpers: 4 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state time 0.393 if : free 600 if LE0: free 400 if LOCAL: free 1000 driver: hdisk-state time 0.393 driver: QUITTING time 0.393 telling children to quit driver: send-cmd time 0.393 to dumper0: QUIT driver: send-cmd time 0.393 to dumper1: QUIT driver: send-cmd time 0.393 to dumper2: QUIT driver: send-cmd time 0.393 to dumper3: QUIT driver: send-cmd time 0.393 to taper: QUIT taper: DONE [idle wait: 0.188 secs] taper: writing end marker. [/dev/null OK kb 0 fm 0] driver: FINISHED time 0.396 amdump: end at Fri Jan 19 15:28:44 CET 2001 Here's what my .amandahosts looks like: maulaf.isd.uni-stuttgart.de amanda maulaf.isd.uni-stuttgart.de root So I think amnda should not have any problems connecting, I just can't seem to find what I did
FAILURE AND STRANGE DUMP SUMMARY
Now that I finally have my rebuilt Amanda server working again, there is one item that I'd like to check in on. When it backs up the PC shares on our Win2K, WinNT and Win95 boxes, I get this: FAILURE AND STRANGE DUMP SUMMARY: amanda file://xxx/PAP2 lev 0 STRANGE amanda file://xxx/EAGLE lev 0 STRANGE amanda file://xxx/OUTLOOK lev 0 STRANGE amanda file://xx3/d lev 0 STRANGE amanda file://xx2/d lev 0 STRANGE amanda file://x/d lev 0 STRANGE And then what follows is a line by line blow of each and every file that got backed up. The email message we get sent to us can be up to 6 megabytes in size, and is darn right painful to even attempt to view and has been know to crash Outlook 2000/Express when received. How do you make Amanda think these PC shares are no longer "Strange?" -Gerry
Re: Solaris: suid root stuff
Hello John, You put your finger right on the solution! The former admin put a"nosuid" mount on the partition that had Amanda installed! I removed it and it corrected the problem. Thanks! Luc Lalonde "John R. Jackson" wrote: > >I can't seem to figure this one out. I've got my Linux host running > >Amanda-2.4.2 and all the Linux clients working allright but not my > >Ultra10's running Solaris 2.7. > >... > >Is there a Solaris patch I should know about? > > I don't think so. I have several Solaris 2.7 machines, both Sparc and > Ultra, and they are working fine. > > >Here's a listing of runtar: > >-rwsr-x--- 1 root backup 216808 Jan 20 21:19 runtar > > > >And here's the error I get in /tmp/amanda/sendsize.debug: > >runtar: error [must be setuid root] > > I assume the "ls -l" and sendsize*debug came from the same client host? > > Is there any NFS going on, like is runtar being served from some other > machine? If so, you'll need to change the client mount command (or > automount, etc) and possibly the server (e.g. dfstab) to allow setuid > across the NFS mount. See "man mount_nfs" and "man dfstab_nfs". > > Here's a small patch to log what effective UID runtar thinks it is, > which might shed some more light on things. > > >Luc. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] > > > Name: runtar.diff >runtar.diff Type: unspecified type (application/octet-stream) > Description: runtar.diff -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: [EMAIL PROTECTED] begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;; version:2.1 email;internet:[EMAIL PROTECTED] title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard
Reiser
Has anyone successfully backed up larger reiserfs partitions? One of my co- workers has setup a new Linux workstation with reiserfs for everything but /boot. Boy, am I glad he did that :-( Look forward to any advice the list may have. -- Joshua Warchol UNIX Systems Administrator DSL.net
avoiding level 0 dumps
I back up a partition on a remote machine, connected by a 28.8k modem. After only two days, Amanda has decided to do a level 0 backup of this partition, which seems strange, if not wrong. How can I discourage her from doing level 0s until the end of the dumpcycle? Almost nothing is as bad as doing a level 0 over this link. Ben
Estimates
When amstatus reports on estimates, are these supposed to be the estimates for the volume of data dumped at the specified dump level? Every day when Amanda runs, I see the same huge estimates for disks that, once backed up, only had a few hundred KB of incrementals to do. It's a bit confusing! Ben
Re: temporary skip a tape
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes: > I have six tapes in my tape cycle and according to amanda, tonight's > dumps should go to the tape "daily-0". However, exactly that tape > isn't available at the moment, and I don't want to wait with the > backup until I have access to that particular tape again. Can I > somehow tell amanda to skip that tape and use "daily-1" just for > this time instead? Is this a faq? Alexandre> Reduce tapecycle by one, so that Amanda will accept Alexandre> daily-1. You may also want to mark daily-0 as no reuse Alexandre> with amadmin. Thanks ok, but what do I do when I have access to the tape skipped again and want to include it in the cycle again (with the same name)? / Erik -- erik eriksson; [EMAIL PROTECTED]; +4613203202(work); +46705228912(cell)
Re: Q: tape drives beyond DLT or SLR
Hi! Mitch wrote: > On Tue, 23 Jan 2001, Patrick M. Hausen wrote: > > > Unfortunately our customer with the highes capacity needs stores > > precompressed data of several GB per month and wants them all > > available on disk. So we need to plan for full dumps of 100 GB > > and maybe even more. That's why I'd prefer a tape solution that > > gets 200 GB of data on a tape. > > > > For the curious: webserver logfiles - they want at least one > > year's worth of that available online for analysis ... marketing types ;-) > > You _might_ want to consider modifying your strategy here. What > you're describing is really an archive of static data. Why beat > your backup hardware/software up over it when it's static logs? Absolutely correct ... but ... > How about something like this. At end of each month, move current > month's logs into your online archive and cut a tape, perhaps with > duplicates if you prefer the extra security, of just the new bits. > Add tape to your tape archive. Don't bother making periodic backups > of data in the archive, since you've already got it on both disk and > tape, and it's not changing anyway. This means a separate tape drive and/or manual intevention. All servers are located in a remote data center - that's why we want a "change cartridges once a week and forget about the rest" solution ... If the customer is willing to buy a separate autoloader instead of using our standard "data center backup service", we can implement your suggestion. And ... the customers wants _yesterday's_ logs available for analysis today. Together with all accumulated data over the last year up to and including yesterday. They're using Webtrends Enterprise Reporting - this software just can't analyze seperate months separately and give out reports containing the entire period. Still they insist on using it - it generates "prettier" reports than, say, NetTracker, and has a "nicer" UI. There are quite a few other quirks with this product. If you analyze a year's worth of compressed logfiles, WT insist on decompressing _everything_ to temporary storage, then analyzing, then remove the temporary files. It starts one thread per ip address to reverse-lookup ... Need I say more? Sun, IBM, Compaq sure like it a lot ;-))) The customer asks - we suggest and offer - they buy - or don't. I don't have a problem with that, I'm providing _services_. But now I'm definitely getting off topic. > Alternatively, if the above just won't cut it for whatever reason, > and you want to/have to keep this archival data in your regular > backup cycle, this seems like one time when the current amanda > workaround for filesystems too large for one tape will work quite > well. This being the "use tar and make separate entries in disklist > for each top-level directory" approach. Right. Something along this line probably will do the trick. Getting the biggest tape drive available with current technology won't hurt, either. ;-) Thanks, Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- -- Patrick M. Hausen - Technical Director - [EMAIL PROTECTED] --- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
Re: Q: tape drives beyond DLT or SLR
On Tue, 23 Jan 2001, Patrick M. Hausen wrote: > Unfortunately our customer with the highes capacity needs stores > precompressed data of several GB per month and wants them all > available on disk. So we need to plan for full dumps of 100 GB > and maybe even more. That's why I'd prefer a tape solution that > gets 200 GB of data on a tape. > > For the curious: webserver logfiles - they want at least one > year's worth of that available online for analysis ... marketing types ;-) You _might_ want to consider modifying your strategy here. What you're describing is really an archive of static data. Why beat your backup hardware/software up over it when it's static logs? How about something like this. At end of each month, move current month's logs into your online archive and cut a tape, perhaps with duplicates if you prefer the extra security, of just the new bits. Add tape to your tape archive. Don't bother making periodic backups of data in the archive, since you've already got it on both disk and tape, and it's not changing anyway. Alternatively, if the above just won't cut it for whatever reason, and you want to/have to keep this archival data in your regular backup cycle, this seems like one time when the current amanda workaround for filesystems too large for one tape will work quite well. This being the "use tar and make separate entries in disklist for each top-level directory" approach. -Mitch
Re: Q: tape drives beyond DLT or SLR
* Patrick M. Hausen <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 10:42:33AM +0100) > I just compared uncompressed capacity. Tandberg's SLR100 gives 50 GB > uncompressed, IBM's Ultrium 100 GB uncompressed. > Unfortunately our customer with the highes capacity needs stores > precompressed data of several GB per month and wants them all > available on disk. So we need to plan for full dumps of 100 GB > and maybe even more. That's why I'd prefer a tape solution that > gets 200 GB of data on a tape. Either that, or partition your disks in 100G partitions, and spread his data over multiple partitions, with symlinks he won't even know it. BTW, note that HP also sells ultrium tapes, which are exactly the same (except the tape box sais HP iso IBM) b8ut sell at 10-20% cheaper than the IBM tapes .. go figure ... > "Quantum Super DLT 220N" with a quoted capacity of 220 GB (that's almost > certainly compressed, so it may have 110 GB uncompressed). > Unfortunately the link to Quantum's website doesn't reveal _any_ > information on that product. Is it vaporware? Well, with LTO being 100 DLT has to beat that .. It's probably going to be there ``soon'' > "Ampex DST 312" with a quoted capacity of 330 GB - anyone used > these? They're helical scan technology which makes me feel a > lot less comfortable than with Tandberg or IBM ... Never heard of those . Of course, wait another year and you can buy Super DLT tapes that store 500G uncompressed and 1 T compressed ... Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\<, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Re: Q: tape drives beyond DLT or SLR
Hi all! Gerhard den Hollander wrote: > * Patrick M. Hausen <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 09:11:36AM +0100) > > > What options do I have for higher capacity drives? > > Amanda still requires the largest dump to fit on a single tape. > > With filesystems routinely approaching a couple of hundreds of gigs > > these days there seems to be a huge gap ... > > > I found IBM Ultrium technology. Has someone used these successfully? > Yup. > > > OTOH they are 100 GB uncompressed - not a _real_ order of magnitude. > > No, > amanda with compressuion should get you to 200G depending on the type of > data) I just compared uncompressed capacity. Tandberg's SLR100 gives 50 GB uncompressed, IBM's Ultrium 100 GB uncompressed. Unfortunately our customer with the highes capacity needs stores precompressed data of several GB per month and wants them all available on disk. So we need to plan for full dumps of 100 GB and maybe even more. That's why I'd prefer a tape solution that gets 200 GB of data on a tape. For the curious: webserver logfiles - they want at least one year's worth of that available online for analysis ... marketing types ;-) > Different backup software that allows dumps to span multiple tapes, in > combination with stackers or taperobots. That's what I figured ... > Work on multitapebackup is (apparently) underway for Amanda NG _This_ is good news indeed. So one possible solution would be to go for a library instead of an autoloader, start with 1 tape of 50 or 100 GB capacity now - and hope AmandaNG will be available when we need it ;-)) We certainly would be willing to help with beta testing, but don't have spare time for development. 2 more options I found on www.backupcentral.com: "Quantum Super DLT 220N" with a quoted capacity of 220 GB (that's almost certainly compressed, so it may have 110 GB uncompressed). Unfortunately the link to Quantum's website doesn't reveal _any_ information on that product. Is it vaporware? "Ampex DST 312" with a quoted capacity of 330 GB - anyone used these? They're helical scan technology which makes me feel a lot less comfortable than with Tandberg or IBM ... Thanks, Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- -- Patrick M. Hausen - Technical Director - [EMAIL PROTECTED] --- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
Re: Q: tape drives beyond DLT or SLR
* Patrick M. Hausen <[EMAIL PROTECTED]> (Tue, Jan 23, 2001 at 09:11:36AM +0100) > What options do I have for higher capacity drives? > Amanda still requires the largest dump to fit on a single tape. > With filesystems routinely approaching a couple of hundreds of gigs > these days there seems to be a huge gap ... > I found IBM Ultrium technology. Has someone used these successfully? Yup. > OTOH they are 100 GB uncompressed - not a _real_ order of magnitude. No, amanda with compressuion should get you to 200G depending on the type of data) > What _do_ multi-terabyte datacenters use for backup, anyway? Different backup software that allows dumps to span multiple tapes, in combination with stackers or taperobots. Work on multitapebackup is (apparently) underway for Amanda NG Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support 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.
Q: tape drives beyond DLT or SLR
Hi fellow Amanda users! We use Amanda for networked backup. Currently we rely on Tandberg SLR tape drives exclusively. These drives are available at a maximum capacity of 50 GB w/o compression. And they're robust, reliable and _reasonably_ fast and cheap. DLT drives max out at 40 GB w/o compression. What options do I have for higher capacity drives? Amanda still requires the largest dump to fit on a single tape. With filesystems routinely approaching a couple of hundreds of gigs these days there seems to be a huge gap ... I found IBM Ultrium technology. Has someone used these successfully? OTOH they are 100 GB uncompressed - not a _real_ order of magnitude. What _do_ multi-terabyte datacenters use for backup, anyway? I know, if I find something to backup 200 or 300 GB on a single tape, that I will face another limit - the speed of my 100 MBit/s Ethernet network. We already have a separate VLAN for backup only. A rough calculation shows a _theoretical_ bandwidth of ~47 GB per hour without counting packet overhead. And if I fix that by going to Gigabit Ethernet for the biggest servers, I'll hit the SCSI-bus and tape bandwidth barrier ... ;-) Operating systems we use are FreeBSD and Solaris, so we are familiar with i386 and Sparc architecture and technology. Thanks in advance for any comments/hints, Patrick -- --- WEB ISS GmbH - Scheffelstr. 17a - 76135 Karlsruhe - 0721/9109-0 --- -- Patrick M. Hausen - Technical Director - [EMAIL PROTECTED] --- "Contrary to popular belief, penguins are not the salvation of modern technology. Neither do they throw parties for the urban proletariat."
