HP SureStore DLT80 tapetype
It just completed:
define tapetype HP-DLT-80 {
comment "HP SureStore DLT 80, with DLT IV tape"
length 37970 mbytes
filemark 5 kbytes
speed 2068 kps
}
Re: calcsize not accounting for compression? (was: Re: [dumps too big, but cannot incremental dump new disk])
* John E Hein <[EMAIL PROTECTED]> (Wed, Sep 19, 2001 at 09:39:23AM -0600) >>> Hmmm... it also seems to not take compression into account (we use gnu >>> tar with client side compression). The estimated size is much larger >>> than the actual size. amstatus gives: >> No, it doesn;'t take compression into account , neither does ufsdump or >> gnutar .. at least the way I have it setup. > okay... I'll buy that for the moment. [8<] >>> So for our 12 GB DDS-3 drive, we're getting a lot of 'full dump delayed' >>> messages because of this issue. >> If you know this, you can specify the tapesize to be 24G (iso 12G) and you >> should get the dumps you think you were getting. > I suppose, but why do we need to do that now where we didn't before (when > we were using gnu tar for estimates)? I don't know. > Last night things got even worse. It only used 1.8 GB of the tape and > we got 24 'full dump delayed' messages (the night before was 13 such > messages and it used 5 GB). Are you by any chance using exclusion lists in tar ? calcsize does not (yet) support exclusion lists . It's something I was going to do in my spare time (fixing calcsize to handle exclusion lists), but between work, family and sheer exhaustion I haven't had much spare time in the last 2 months ;( .. At any rate, Im gonna have a look at my own tests on calcsize, I had figured out a way to run the various estimate programs (ufsdump, gnutar and calcsize) from the command line and could compare the results. If you happen to have a debug file lying around from the previous runs (the tar iso calcsize extimates) you can find the exact tar command in there. Could you do me a favor and run the tar - estimate commands by hand, as well as the calcsize estimates and let me know the results. Gerhard, <@jasongeo.com> == The Acoustic Motorbiker == -- __O With judicious application of shaving foam & water =`\<, and scraping with a razor of it's prickly hind quarters (=)/(=) Whether it wriggles like fury, or curls up in a ball That blasted hedgepod can be buggered for sure.
Re: amrecover: Unexpected server end of file
On October 1 2001, Jason Joines wrote: > My amindexed debug file gives this information: > "more amindexd.20010927121349.debug > amindexd: debug 1 pid 15662 ruid 37 euid 37 start time Thu Sep 27 > 12:13:49 2001 > amindexd: version 2.4.2p2 > could not open conf file "/usr/local/etc/amanda/amidxtape/amanda.conf": > No such file or directory > amindexd: pid 15662 finish time Thu Sep 27 12:13:49 2001" Aha! I'll bet this is a problem with your inetd.conf file on the Amanda server. If there are "too many" arguments on the amandaidx line, some may be passed to amindexd as arguments, which it will interpret as config names, etc. I was able to reproduce what you saw by changing my inetd.conf file to have a line like this: amandaidx stream tcp nowait operator /amanda/libexec/amindexd amindexd amidxtape The last bit (amidxtape) should not be there. I'm almost certain that you have two lines merged together, since the "amidxtape ..." line usually follows the amandaidx line in the examples. I hope this helps, -Ben -- Benjamin LewisThank goodness modern convenience is a Database Analyst/Programmer thing of the remote future. Purdue University Computing Center -- Pogo, by Walt Kelly [EMAIL PROTECTED]
Amanda client side error
Hello ppl, I have a little problem with amanda...I have configured it for tapeless backup and when I do amcheck all is ok on the server side but on the client side I recive a very strange error: "ERROR: nil NAK: service selfcheck unavailable" I will provide you with all my config files ...maybe you can figure this out.I have Suse 7.2 distribution and "nil" is the computer who runs the backups and also witch is going to be backed up.Also I have edited inetd.conf and services for amanda. I will appreciate any kind of help, Andrei -- Andrei Neagoe mailto:[EMAIL PROTECTED] ___ SecureNet S.R.L. Intranet und Internet Solutions Tel: +40 94/283968 Strada Brestei 3a General office: +40 51/410555 1100 Craiova, Romania http://www.secure-net.de
Re: level 2 and 3
* Ron Stanonik <[EMAIL PROTECTED]> (Mon, Oct 01, 2001 at 08:45:15AM -0700) > Can amanda be configured to limit the incremental level? > I almost always have a few level 2's and often a level 3. > I'd like to never see anything higher than level 1. Why? > Restoring is simpler. > > My previous configuration was > > dumpcycle7 days > runspercycle 5 > typecycle 30 tapes > > Which produced level 0 and 1, and an occasional level 2. > As the number of systems increased, amanda began having > problems fitting everything, so, I lengthened the cycle > > dumpcycle 12 days > runspercycle 8 > typecycle 30 tapes > > Which produces level 0 and 1, almost always some level 2, > and often a level 3. > > So, too short a cycle and amanda can't fit everything, > but too long a cycle and amanda produces level 2 and 3? check out the following variables in amanda.conf bumpsize 5000 Mb# minimum savings (threshold) to bump level 1 -> 2 bumpdays 2 # minimum days at each level bumpmult 4 # threshold = bumpsize * bumpmult^(level-1) setting bumpdays to 99 should only give you 0's and 1's > Currently listening to: the hum of my computer 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: amrecover: Unexpected server end of file
On Friday 28 September 2001 07:39 am, you wrote: > On September 27 2001, Jason Joines wrote: > > I just tried to use amrecover for the first time. It yields > > this error, "amrecover: Unexpected server end of file". Checking > > the debug file gives this information, > > "amrecover: debug 1 pid 15661 ruid 0 euid 0 start time Thu Sep 27 > > 12:13:49 2001 > > amrecover: stream_client: connected to 139.78.89.34.10082 > > amrecover: stream_client: our side is 0.0.0.0.890" > > Any idea what this means? > > It probably means that the default configuration (often "Dailyset1") > compiled into amrecover isn't the same as the name of the > configuration you actually use. You'll want to look in > /tmp/amanda/amindexed*debug on the Amanda server to check that. > > You'll either need to recompile Amanda on the client after re-running > configure with the "--with-config=xxx" option or just make sure you > use the correct configuration name when you run amrecover. For > example, on my system the configuration name is "DLT", the tape/index > server is "iori", and the tape drive (on iori) is "/dev/nsa0", so > here's how I run amrecover: > > amrecover -C DLT -s iori -t iori -d /dev/nsa0 > > More information is in the amrecover man page and in "The Chapter" at > > http://www.backupcentral.com/amanda-23.html > > I hope this helps, > > -Ben My amindexed debug file gives this information: "more amindexd.20010927121349.debug amindexd: debug 1 pid 15662 ruid 37 euid 37 start time Thu Sep 27 12:13:49 2001 amindexd: version 2.4.2p2 could not open conf file "/usr/local/etc/amanda/amidxtape/amanda.conf": No such file or directory amindexd: pid 15662 finish time Thu Sep 27 12:13:49 2001" I'm not sure why it is looking for that file. My configuration name is daily and the configuration file is in /usr/local/etc/amanda/daily/amanda.conf. I execute "amrecover -C daily" and get the same results: "/usr/local/sbin/amrecover -C daily AMRECOVER Version 2.4.2p2. Contacting server on darkangel ... amrecover: Unexpected server end of file" The compiled default is DailySet1 but using -C is supposed to let you specify another configuration. All the other compiled defaults for amrecover seem to match my setup. Jason ---
UPDATE -- Re: PROBLEM: Dump is agonizingly slow on one host
I have an update: I have traced the problem to the indeces. If I turn
indexing off, my test backup completes in the expected timespan. If I turn
indexing on, it takes forever.
A little information first:
/etc/amanda/test/ contains amanda.conf and disklist.
/var/amanda/test/ contains amdump files, log files, curinfo database, and
index database.
I have deleted everything in /var/amanda/test/, /var/amanda/test/curinfo/, and
/var/amanda/test/index/. When I run the test backup without indexing all goes
well. When I repeat this setup (i.e. deleting all the aforementioned files)
and re-run the backup with indexing turned on, amanda creates the file
/var/amanda/test/index/alnus/_/*_0.gz.tmp, but it stays at a size of 0 bytes.
I have verrified that the hard drive on the index server is not full. I can
see ufsrestore running on alnus, and I can see gzip running on the server, but
I don't know how to verrify whether or not the data is actually getting from
the client to the server at all.
Here's what the process tree looks like from alnus (the client):
14091 /usr/libexec/sendbackup
14092 /usr/libexec/sendbackup
14093 sh -c /usr/sbin/ufsrestore -tvf - 2>&1 | sed -e ' s/^leaf[
14095 sed -e s/^leaf[ ]*[0-9]*[ ]*\.// t /^dir[ ]/ { s/^dir[
14096 /usr/sbin/ufsrestore -tvf -
14094 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
14097 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
14101 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
14098 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
14100 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
14099 dump 0sf 1048576 - /dev/rdsk/c0t0d0s0
Here's what the process tree looks like from the server:
21080 /bin/sh /usr/sbin/amdump test
21086 /usr/libexec/driver test
21087
21090 dumper test
21113 /usr/local/bin/gzip --best
21088 taper test
21089 taper test
And just for good measure, here's what amstatus is reporting:
Using /var/adm/amanda/test/amdump from Mon Oct 1 12:52:57 EDT 2001
alnus:/ 0 723445k dumping 96k ( 0.01%) (12:53:05)
SUMMARY part real estimated
size size
partition : 1
estimated : 1 723445k
failed : 0 0k ( 0.00%)
wait for dumping: 0 0k ( 0.00%)
dumping to tape : 0 0k ( 0.00%)
dumping : 1 96k 723445k ( 0.01%) ( 0.01%)
dumped : 00k0k ( 0.00%) ( 0.00%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 00k0k ( 0.00%) ( 0.00%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 00k0k ( 0.00%) ( 0.00%)
all dumpers active
taper idle
network free kps:11970
holding space : 2912170k ( 80.10%)
(It's only 0.01% complete, but it should have been done by now.)
Any more ideas anyone?
Michael
>
> Hello all,
>
> I've been using amanda for, well, years now, and I have never run accross this
> problem before. I have one brand new host that is taking *WAY* too long to
> back up. Here's the skinny:
>
> It's a Sun SPARC Ultra-5 running Solaris-2.7 with amanda 2.4.2p2. There are a
> total of six machines that I installed, all on the same day, one of which has a
> nearly identical hardware setup. (The only difference is that this particular
> host has two hard drives instead of one.) All the other new machines send
> backups in reasonable ammounts of time -- only this one seems to be affected.
> (And, of course, over 20 old hosts running identical versions of the same
> software work just fine. :)
>
> I started a test run of amdump at 3 pm (15:00) yesterday:
>
> | $ amdump tiem
>
> According to amstatus, amanda happily started processing and began to dump this
> particular computer, named alnus, at 15:08:57. At 09:47:30 this morning
> amstatus reports that it has only gotten 1.24% through with 705 megs of data!
>
> I sat down and did some figuring. Dump has been running on this host for
> 18:21:27, and has only gotten 1.24% completed by sending 8992k of the dump back
> to the tape host. According to a little math, I figure that it's moving about
> 139 bytes/sec, and has about 61 days 16:26:36 left until it completes!
>
> To say that this is unacceptable is a minor understatement. I've been
> struggling with this problem for four days now, and all I can do is scratch my
> head and wonder.
>
> The next thing I did was run the dump by hand according to the command listed
> in alnus:/tmp/amanda/sendbackup.*.debug file:
>
> | $ time /bin/sh -c "ssh alnus '/usr/sbin/ufsdump 0sf 1048576 - \
> | /dev/ds
Re: level 2 and 3
> Can amanda be configured to limit the incremental level? > I almost always have a few level 2's and often a level 3. > I'd like to never see anything higher than level 1. Why? > Restoring is simpler. man amanda: bumpsize int Default: 10 Mbytes. The minimum savings required to trigger an automatic bump from one incremental level to the next. If Amanda determines that the next higher backup level will be this much smaller than the current level, it will do the next level. See also the bumpmult option. bumpmult float Default: 1.5. The bump size multiplier. Amanda multiplies bumpsize by this factor for each level. This prevents active filesystems from bumping too much by making it harder to bump to the next level. For example, with the default bumpsize and bumpmult set to 2.0, the bump threshold will be 10 Mbytes for level one, 20 Mbytes for level two, 40 Mbytes for level three, and so on. bumpdays int Default: 2. To insure redundancy in the dumps, Amanda keeps filesystems at the same incremental level for at least bumpdays days, even if the other bump threshold criteria are met.
level 2 and 3
Can amanda be configured to limit the incremental level? I almost always have a few level 2's and often a level 3. I'd like to never see anything higher than level 1. Why? Restoring is simpler. My previous configuration was dumpcycle7 days runspercycle 5 typecycle 30 tapes Which produced level 0 and 1, and an occasional level 2. As the number of systems increased, amanda began having problems fitting everything, so, I lengthened the cycle dumpcycle 12 days runspercycle 8 typecycle 30 tapes Which produces level 0 and 1, almost always some level 2, and often a level 3. So, too short a cycle and amanda can't fit everything, but too long a cycle and amanda produces level 2 and 3? I'm running 2.4.1p1. Thanks, Ron Stanonik [EMAIL PROTECTED]
Re: Tape stuck
Hi to all! Thank you for the answers and help. Unfortunatelly, only a reboot helped but now machine is up and running, so all ok. Thank you again for help. Radu On Thu, 20 Sep 2001 [EMAIL PROTECTED] wrote: > > Actually, Amanda can't use tapes that hasn't been previously labeled by > amlabel. > > As for me, for ejecting the tape, I use to issue "mt offline -f /dev/nst0" > > > > En réponse à Tom Schutter <[EMAIL PROTECTED]>: > > > I have a ADR30 and have similar problems. > > > > The "Input/output" errors seemed to go away for me once I used amlabel > > to label the tape. In other words, it seemed to give the errors only > > when the tape had never been written to. > > > > As for ejecting the tape, my solution has been to try multiple > > "mt rewind" commands. When I press the eject button, the light flashes > > but then nothing happens. But if I do a few "mt rewind" commands, then > > the eject button works. > > > > Radu Filip wrote: > > > > > > Hi! > > > > > > By two days I've got "Input/output" error everytime amanda tries to > > backup > > > or just check if proper tape is inserted. The same errors occurs if I > > try > > > to manually rewind or retension the tape. > > > > > > I'm located in Romania and my server is in US, so I cannot figure out > > > what's happens. But a guy from copmany that colocate the server told > > me > > > the he was not able to eject the tape! So how to proceed in this > > > situation? > > > > > > I know it's not directly related to Amanda, but I don't know anyother > > > place where to ask and I assume that there are peoples here that could > > > have an advice for me. > > > > > > Thank you in advance, > > > Radu Filip > > > > > > -- Forwarded message -- > > > Date: Tue, 18 Sep 2001 14:22:59 -0400 > > > From: [EMAIL PROTECTED] > > > To: radu Filip <[EMAIL PROTECTED]> > > > Subject: Re: Please check the tape > > > > > > Radu, > > > > > > he tape is not ejecting at all. I have tried to eject the tape two > > times > > > and it still has not ejected. > > > > > > How would you like us to proceed from here?? > > > > -- > > Tom Schutter (mailto:[EMAIL PROTECTED]) > > Platte River Associates, Inc. (http://www.platte.com) > > > -- Radu Filip Network Administrator @ Technical University of Iasi [EMAIL PROTECTED] Information Technology and Communication Center http://socrate.tuiasi.ro/ [EMAIL PROTECTED] | http://ccti.tuiasi.ro/
interactive backup
hallo Is there a possibility to make backup interativetly on tapes and with different cofigs. For example: client1 on client1-tape1-2 client2 on client2-tape1-2 client3 on client3-tape1-2 thanks nezir
