Integration of Amanda with Oracle's Recovery Manager?
Title: Integration of Amanda with Oracle's Recovery Manager? Hi, I am curious whether anyone is working on integrating Amanda with Oracle's RMAN via the Media Management API supplied by Oracle. Cheers, Craig.
amanda article in SysAdmin magazine
New SysAdmin issue has an article titled "Configuring Amanda" by David T. Smith. Article is online at: http://www.samag.com/documents/s=7033/sam0204a/sam0204a.htm -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: General Question
On Thu, 7 Mar 2002, Jeffrey S. Auerbach wrote: > My AMANDA server is on a private network and the AMANDA clients are on a > publicly accessible network. The public servers cannot route to the > private server because of the non-routable IP. Would this prevent my > backups from working? Does the server pull the data off of the clients > or do the clients push the data back to the server. > > Thanks > Jeff > > PS. Please don't flame me for asking. > > > If your server can connect to your clients, then you should be able to configure your firewall/etc to allow them to route their amanda connections back properly. The server tells the client what to send, and the clients open up a reverse connection back to what they perceive as the server (generally this would be the firewall/NAT device). Feel free to ask me offline more specific questions and/or check out the Amanda online FAQ area. -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: Unsubscribe
On Thu, 7 Mar 2002 at 1:49pm, Joe Knapp wrote > How exactly do you go about unsubscribing? > Do the instructions on the amanda page at www.amanda.org work? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Unsubscribe
How exactly do you go about unsubscribing?
General Question
My AMANDA server is on a private network and the AMANDA clients are on a publicly accessible network. The public servers cannot route to the private server because of the non-routable IP. Would this prevent my backups from working? Does the server pull the data off of the clients or do the clients push the data back to the server. Thanks Jeff PS. Please don't flame me for asking.
Re: Spectra Logic 10000 (was treefrog config)
Sorry, that is a SL 1, 40 slots 4 drives, with arm, barcode, and door. using sst. > On Thu, 7 Mar 2002, F.M. Taylor wrote: > > - > - How do I move a tape to the door. Thats the only thing I can't seem to > - figure out. > > -- Mike Taylor Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 053 210 N 7th St. Terre Haute, IN. SANS GSEC http://www.sans.org/
Re: amanda reporting nearly-empty tape as full?
On Thu, 7 Mar 2002 at 3:05pm, Dave Sherohman wrote > > Well, there's either a problem with the tape, the drive, or the system. > > OK, I can accept that. And I suppose that, as a result, amflush, even > if it completes without incident, may well produce an unusable backup. > But, on the off chance that it works, would it be less bad to overwrite > last night's tape (since it appears that no device was fully written, > I would expect everything to still be on the holding disk) or the next > one in the sequence (which would definitely destroy an existing backup > volume, but is what the report said to do)? If *some* stuff got to the tape, then it's an active volume and amanda won't let you over-write it. You'd have to 'amrmtape' it and then re'amlabel' it. This is *exactly* the reason it's good to have your tapecycle > runspercycle. > *sigh* There it is... A dozen lines of complaints from the SCSI driver. > Looks like the drive's been timing out and getting reset. I would guess > that this is a problem with the drive, since it's had trouble with 3 or > 4 different tapes. Thanks. Could be. Or the SCSI adapter. Or the terminater. Or the cables. Also, when was the last time you sacrificed a goat to the chain, and what color was it? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amanda reporting nearly-empty tape as full?
On Thu, Mar 07, 2002 at 03:28:17PM -0500, Joshua Baker-LePain wrote: > On Thu, 7 Mar 2002 at 12:08pm, Dave Sherohman wrote > > Second, the taper stats read "N/AN/A" for all drives that were dumped. > > This would seem to indicate that nothing was actually written to the > > tape, wouldn't it? And, based on that, am I correct to infer that it > > would be better to amflush last night's dumps onto the same tape instead > > of advancing to the next one as instructed by the report? > > Well, there's either a problem with the tape, the drive, or the system. OK, I can accept that. And I suppose that, as a result, amflush, even if it completes without incident, may well produce an unusable backup. But, on the off chance that it works, would it be less bad to overwrite last night's tape (since it appears that no device was fully written, I would expect everything to still be on the holding disk) or the next one in the sequence (which would definitely destroy an existing backup volume, but is what the report said to do)? > Look in your system logs -- amanda is just telling you what the OS told > it. There's some issue with your tape drive and/or tapes and/or SCSI > chain and/or ... you get the picture. *sigh* There it is... A dozen lines of complaints from the SCSI driver. Looks like the drive's been timing out and getting reset. I would guess that this is a problem with the drive, since it's had trouble with 3 or 4 different tapes. Thanks.
Re: Spectra Logic Treefrog configuration
On Thu, 7 Mar 2002, F.M. Taylor wrote: - - How do I move a tape to the door. Thats the only thing I can't seem to - figure out. On my Spectra Logic (2000) there is no special provision for removing a tape. I just eject the tape (amtape eject), open the door and remove the tape by hand. -- -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
amanda-2.4.3b2-20020306 build failed
Hello, On a OSF1 V5.1 732 alpha I am getting the following output from an attempted build. Can someone suggest something for me to examine to make this error go away? I have made sure that I have a recent GNU libtool in my path. thanks -JK . . . config.status: creating Makefile config.status: creating config/config.h Making all in config make[1]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/config' cd .. \ && CONFIG_FILES= CONFIG_HEADERS=config/config.h \ /usr/bin/sh ./config.status config.status: creating config/config.h config.status: config/config.h is unchanged make all-am make[2]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/config' make[2]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/config' make[1]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/config' Making all in common-src make[1]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/common-src' source='alloc.c' object='alloc.lo' libtool=yes \ depfile='.deps/alloc.Plo' tmpdepfile='.deps/alloc.TPlo' \ depmode=tru64 /usr/bin/sh ../config/depcomp \ /usr/bin/sh ../libtool --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include -O2 -c -o alloc.lo `test -f alloc.c || echo './'`alloc.c ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found ../libtool: print: not found make[1]: *** [alloc.lo] Error 1 make[1]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b2-20020306/common-src' make: *** [all-recursive] Error 1 #
Re: Spectra Logic Treefrog configuration
How do I move a tape to the door. Thats the only thing I can't seem to figure out. -- Mike Taylor Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 053 210 N 7th St. Terre Haute, IN. SANS GSEC http://www.sans.org/
Re: amanda reporting nearly-empty tape as full?
On Thu, 7 Mar 2002 at 12:08pm, Dave Sherohman wrote > Late last week, amanda started to consistently produce reports such as > the following: > > *** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]]. > *** PERFORMED ALL DUMPS TO HOLDING DISK. > *snip* > > So, first off, the big question: Why is amanda first claiming that it > ran out of tape, then saying that only 27.3% of the tape was used? The error above is why. After using 27.3% of the length defined in your tapetype, the OS told amanda it had hit an I/O error, and amanda couldn't write to the tape any more. > Second, the taper stats read "N/AN/A" for all drives that were dumped. > This would seem to indicate that nothing was actually written to the > tape, wouldn't it? And, based on that, am I correct to infer that it > would be better to amflush last night's dumps onto the same tape instead > of advancing to the next one as instructed by the report? Well, there's either a problem with the tape, the drive, or the system. > And, finally, how do I actually debug and fix this? Look in your system logs -- amanda is just telling you what the OS told it. There's some issue with your tape drive and/or tapes and/or SCSI chain and/or ... you get the picture. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Compaq TL891 on Solaris
Hi, On Wed, Mar 06, 2002 at 03:48:52PM +0100, Roland Barmettler wrote: > Hi > > We're currently using Amanda 2.4.1p1 on Solaris 2.5.1 with a Compaq > TL891 DLT library. But we were unable to get the changer working with > mtx (current version) and sst, so we have to change tapes manually. > (that's why we have a library... *รง%&$!) Hmm, did you gave chg-scsi a try ??, if no try it and may be i can help a little bit to get it running . Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
RE: netusage, high or low?
Also, as to my original question, I am still wondering whether I should bump
these numbers up or down in order to increase the amount of traffice (or
numbers of running dumpers) that amanda will allow.
netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
define interface le0 {
comment "100 Mbps ethernet"
use 4000 kbps
I'm pretty sure I RAISE the netusage variable, but what do I do to the
interface 'use' attribute?
B
-Original Message-
From: Martin Hepworth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 9:32 AM
To: [EMAIL PROTECTED]
Cc: Brandon Moro
Subject: Re: netusage, high or low?
Brandon
err you mention the le0 interface in the config.
Is this correct 'cos the the le0 interface is a 10base system, not
100base!..
--
Martin
Brandon Moro wrote:
> Hello all!
>
> I am having some troubles with my AMANDA backups running too long. They
> often take 20+ hours,
> sometimes even breaking the 24-hour mark. The average amount of data I
get
> is only about 35GB.
>
> I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with
256MB
> RAM, on a 100mbps
> connection. I have 2 DLT 7000 tape drives set up (though it very rarely
> roles over).
>
> Recently, I put a larger holding disk on the server and found that my run
> time was cut more than in half!
> However, I notice that I am still only getting a total of about 3GB an
hour.
> The data runs from the holding
> disk to tape at more like 6MB/s.
>
> We have a couple of other backup systems running on almost identical
> hardware that puts more than
> twice as much data to tape in slightly less time. So I guess what I am
> really asking is, am I missing
> something in the configuration of AMANDA sthat will allow better usage of
> the network connection?
>
> I found this in the amanda.conf file:
>
> netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
> (blah blah)
>
> network interfaces
>
> . Attributes are:
> use - bandwidth above which amanda won't
> start
> backups using this interface.
> Note that if
> a single backup will take more
> than that,
> amanda won't try to make it run
> slower!
>
> define interface local {
> comment "a local disk"
> use 1000 kbps
> }
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
>
>
> So, does this mean that if my dumpers are using 4000kbps, amanda won't
allow
> any more
> dumpers to start (even if the maximum number of allowed dumpers has not
been
> reached)?
>
> Can I improve performance by raising the netusage variable and "use"
> attribute to something
> more in line with the actual capacity of the amanda-server's network
> connection?
>
> Also, the network interface on the amanda-server is actually "hme0". Are
> the above simply
> examples? Should I create a new interface definition?
>
> Thanks for your help!
>
> Brandon Moro
> Systems Administration, Unify Corporation
> [EMAIL PROTECTED]
> -
>>From meanness first this Portsmouth Yankey rose, And still to meanness all
> his conduct flows.--Oppression, A poem by an American (Boston, 1765).
>
>
>
RE: netusage, high or low?
Here, we use Cabletron Systems 6000 switches. The amanda-server and the
switch report that the amanda-server is up on a 100m fdx connection. I am
sure that the network itself is not the problem. I get backups of the
amanda-server to a budtool backup server at lightning speeds. Therefore, I
think the problem lies in my configuration.
As Mr. Hepworth mentioned, the le0 interface is the 10mbps interface. And I
know that the interface that my amanda-server is running on is called
'hme0'. Need I delete the 'le0' and 'local' network interfaces from the
amanda.conf and make one for 'hme0' ? I cannot find anyplace in the
amanda.conf that calls the functions:
> define interface local {
> comment "a local disk"
> use 1000 kbps
> }
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
In the amanda.conf file, above these interface definitions, it says that
these are referred to by the disklist file. I assume then that the
interface to be used should be called in the dumptype? I don't see any
examples of such in the dumptype area of amanda.conf... And it also
mentions that:
-the valuse below are only samples (referring to the two above interface
definitions).
So, do I need to define them elsewhere as well?
Thanks again for the help!
Brandon Moro
Systems Administration, Unify Corporation
[EMAIL PROTECTED]
-Original Message-
From: Martin Hepworth [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 07, 2002 9:53 AM
To: Brandon Moro
Cc: [EMAIL PROTECTED]
Subject: Re: netusage, high or low?
Brandon
d'oh just read the whole email..
If your SUN is connected to a cisco switch make sure is actually running
at 100m fdx as alot of the older SUNs and Cisco have some wierd problem
with autonegotiate. I've also seen problems with Cisco's under high load
with SNMP turned on giving throughput problems.
If you do have problems 1) force the cisco and the SUN to 100 full
duplex (see www.unixadmin.net/howto/100FullHowto.html for the SUN). 2)
turn off snmp on the cisco.
--
martin
Brandon Moro wrote:
> Hello all!
>
> I am having some troubles with my AMANDA backups running too long. They
> often take 20+ hours,
> sometimes even breaking the 24-hour mark. The average amount of data I
get
> is only about 35GB.
>
> I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with
256MB
> RAM, on a 100mbps
> connection. I have 2 DLT 7000 tape drives set up (though it very rarely
> roles over).
>
> Recently, I put a larger holding disk on the server and found that my run
> time was cut more than in half!
> However, I notice that I am still only getting a total of about 3GB an
hour.
> The data runs from the holding
> disk to tape at more like 6MB/s.
>
> We have a couple of other backup systems running on almost identical
> hardware that puts more than
> twice as much data to tape in slightly less time. So I guess what I am
> really asking is, am I missing
> something in the configuration of AMANDA sthat will allow better usage of
> the network connection?
>
> I found this in the amanda.conf file:
>
> netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
> (blah blah)
>
> network interfaces
>
> . Attributes are:
> use - bandwidth above which amanda won't
> start
> backups using this interface.
> Note that if
> a single backup will take more
> than that,
> amanda won't try to make it run
> slower!
>
> define interface local {
> comment "a local disk"
> use 1000 kbps
> }
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
>
>
> So, does this mean that if my dumpers are using 4000kbps, amanda won't
allow
> any more
> dumpers to start (even if the maximum number of allowed dumpers has not
been
> reached)?
>
> Can I improve performance by raising the netusage variable and "use"
> attribute to something
> more in line with the actual capacity of the amanda-server's network
> connection?
>
> Also, the network interface on the amanda-server is actually "hme0". Are
> the above simply
> examples? Should I create a new interface definition?
>
> Thanks for your help!
>
> Brandon Moro
> Systems Administration, Unify Corporation
> [EMAIL PROTECTED]
> -
>>From meanness first this Portsmouth Yankey rose, And still to meanness all
> his conduct flows.--Oppression, A poem by an American (Boston, 1765).
>
>
>
Re: file too large
I've never had amflush complain about chunks being cruft files. It writes them to tape and removes them. If amdump dies you might end up with cruft files (both chunks and full files), but an amcleanup followed by an amflush generally clears things out. Frank --On Thursday, March 07, 2002 12:30:54 -0500 Mike Cathey <[EMAIL PROTECTED]> wrote: > Joshua, > > The annyoing thing about using this hack is that if you have to use amflush >(something goes wrong), then it (amflush) gives you errors about removing cruft files >for all of the files that split creates. An ingenious hack nonetheless... :) > > If you have the disk space, you could switch the holding partition to ReiserFS or >maybe ext3 (it supports files larger than 2GB right?) > > I'm assuming his amanda server is running on linux... > > Cheers, > > Mike > > -- > > Mike Cathey - http://www.mikecathey.com/ > Network Administrator > RTC Internet - http://www.catt.com/ > > Joshua Baker-LePain wrote: > >> On Wed, 6 Mar 2002 at 4:32pm, Charlie Chrisman wrote >> >> >>> /-- countach.i /dev/sda3 lev 0 FAILED ["data write: File too large"] >>> >>> I get this for two of my clients? what does this mean? >>> >>> >> FAQ. Set your chunksize to something less then 2GB-32Kb. 1GB is fine -- >> there's no performance penalty. >> >> > -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
RE: Tapetype: STD2401LW
Those are some good speeds. What scsi card are you using, and what scsi
devices are on them? What's board/chip combo is the machine?
They aren't suspiciously fast, but I haven't been able to replicate them.
BTW- I find the email list atrocious, and consider it a read only device.
-dan
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Thursday, March 07, 2002 12:49 PM
> Subject: Re: Tapetype: STD2401LW
>
>
> Thanks to all nine of you (boy do I feel dumb) who pointed out that
> hardware compression should have been off. I forgot that
> rebooting this
> machine reset the drive to hardware compression on, argh.
> Five minutes
> with a screwdriver and no more... :)
>
> Some more realistic results:
>
>
> define tapetype unknown-tapetype {
> comment "Seagate STD2401LW DSS4 20/40GB DAT Drive"
> length 19457 mbytes
> filemark 1 kbytes
> speed 2681 kps
> }
>
> One other note... for two days now I've been getting timeouts
> on the primary MX server for the amanda list (
> mx-1.omniscient.com ). Has anyone else seen these issues?
> I've been able to send mail by connecting via telnet to port
> 25 and entering my headers and data block by hand, but I'd
> prefer not to have to do that ;) Is is er... Is it just
> my end, and some flaky MTA, oir is mx-1
> (surly.omniscient.com) under a heavy load so much of the time
> that the MTA times out? I noticed telnetting in that it took
> 15 seconds to get a connection... rather long,. but who's to
> say it's not some network issues on my end...
>
> Thanks again to everyone for pointing out the error of my way :)
>
> --
> Mark Hazen DataBuilt, Inc. (843) 836-2101 Ext. 251
>
> They may forget what you said, but they will never forget
> how you made them feel. --Carl W. Buechner
>
>
Re: file too large
On Thu, 7 Mar 2002 at 12:30pm, Mike Cathey wrote > The annyoing thing about using this hack is that if you have to use > amflush (something goes wrong), then it (amflush) gives you errors about > removing cruft files for all of the files that split creates. An > ingenious hack nonetheless... :) > > If you have the disk space, you could switch the holding partition to > ReiserFS or maybe ext3 (it supports files larger than 2GB right?) ext2 supports >2GB files. The problem lies in glibc and the kernel being compiled with the proper support. RH7.0 wasn't compiled this way, 7.1+ were. So another FS won't help. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amanda reporting nearly-empty tape as full?
Late last week, amanda started to consistently produce reports such as
the following:
- Forwarded message from backup <[EMAIL PROTECTED]> -
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
THESE DUMPS WERE TO DISK. Flush them onto tape Daily01 or a new tape.
Tonight's dumps should go onto 1 tape: Daily02.
FAILURE AND STRANGE DUMP SUMMARY:
nova hda1 lev 0 FAILED [disk hda1 offline on nova?]
catmd1 lev 0 FAILED [out of tape]
taper: FATAL syncpipe_get: w: unexpected EOF
bradleymd10 lev 1 FAILED [no more holding disk space]
catmd5 lev 1 FAILED [can't dump no-hold disk in degraded mode]
peterbilt //server/f$ lev 0 FAILED [can't dump no-hold disk in degraded mode]
STATISTICS:
Total Full Daily
Dump Time (hrs:min)0:12 0:00 0:00 (0:12 start)
Output Size (meg)5584.3 569.8 5014.5
Original Size (meg) 14467.9 2202.412265.5
Avg Compressed Size (%)38.6 25.9 40.9
Tape Used (%) 27.32.8 24.5 (level:#disks ...)
Filesystems Dumped 15 7 8 (1:8)
Avg Dump Rate (k/s) 460.3 1032.8 433.0
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -- --
bradley md10 1 FAILED
bradley md616922029568 42.70:50 592.6N/AN/A
...
- End forwarded message -
So, first off, the big question: Why is amanda first claiming that it
ran out of tape, then saying that only 27.3% of the tape was used?
Second, the taper stats read "N/AN/A" for all drives that were dumped.
This would seem to indicate that nothing was actually written to the
tape, wouldn't it? And, based on that, am I correct to infer that it
would be better to amflush last night's dumps onto the same tape instead
of advancing to the next one as instructed by the report?
And, finally, how do I actually debug and fix this?
Thanks, and more information is available on request, of course, just
tell me what would be useful.
Re: netusage, high or low?
Brandon
d'oh just read the whole email..
If your SUN is connected to a cisco switch make sure is actually running
at 100m fdx as alot of the older SUNs and Cisco have some wierd problem
with autonegotiate. I've also seen problems with Cisco's under high load
with SNMP turned on giving throughput problems.
If you do have problems 1) force the cisco and the SUN to 100 full
duplex (see www.unixadmin.net/howto/100FullHowto.html for the SUN). 2)
turn off snmp on the cisco.
--
martin
Brandon Moro wrote:
> Hello all!
>
> I am having some troubles with my AMANDA backups running too long. They
> often take 20+ hours,
> sometimes even breaking the 24-hour mark. The average amount of data I get
> is only about 35GB.
>
> I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with 256MB
> RAM, on a 100mbps
> connection. I have 2 DLT 7000 tape drives set up (though it very rarely
> roles over).
>
> Recently, I put a larger holding disk on the server and found that my run
> time was cut more than in half!
> However, I notice that I am still only getting a total of about 3GB an hour.
> The data runs from the holding
> disk to tape at more like 6MB/s.
>
> We have a couple of other backup systems running on almost identical
> hardware that puts more than
> twice as much data to tape in slightly less time. So I guess what I am
> really asking is, am I missing
> something in the configuration of AMANDA sthat will allow better usage of
> the network connection?
>
> I found this in the amanda.conf file:
>
> netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
> (blah blah)
>
> network interfaces
>
> . Attributes are:
> use - bandwidth above which amanda won't
> start
> backups using this interface.
> Note that if
> a single backup will take more
> than that,
> amanda won't try to make it run
> slower!
>
> define interface local {
> comment "a local disk"
> use 1000 kbps
> }
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
>
>
> So, does this mean that if my dumpers are using 4000kbps, amanda won't allow
> any more
> dumpers to start (even if the maximum number of allowed dumpers has not been
> reached)?
>
> Can I improve performance by raising the netusage variable and "use"
> attribute to something
> more in line with the actual capacity of the amanda-server's network
> connection?
>
> Also, the network interface on the amanda-server is actually "hme0". Are
> the above simply
> examples? Should I create a new interface definition?
>
> Thanks for your help!
>
> Brandon Moro
> Systems Administration, Unify Corporation
> [EMAIL PROTECTED]
> -
>>From meanness first this Portsmouth Yankey rose, And still to meanness all
> his conduct flows.--Oppression, A poem by an American (Boston, 1765).
>
>
>
Re: Tapetype: STD2401LW
Thanks to all nine of you (boy do I feel dumb) who pointed out that
hardware compression should have been off. I forgot that rebooting this
machine reset the drive to hardware compression on, argh. Five minutes
with a screwdriver and no more... :)
Some more realistic results:
define tapetype unknown-tapetype {
comment "Seagate STD2401LW DSS4 20/40GB DAT Drive"
length 19457 mbytes
filemark 1 kbytes
speed 2681 kps
}
One other note... for two days now I've been getting timeouts on the primary MX server
for the amanda list ( mx-1.omniscient.com ). Has anyone else seen these issues? I've
been able to send mail by connecting via telnet to port 25 and entering my headers and
data block by hand, but I'd prefer not to have to do that ;) Is is er... Is it
just my end, and some flaky MTA, oir is mx-1 (surly.omniscient.com) under a heavy load
so much of the time that the MTA times out? I noticed telnetting in that it took 15
seconds to get a connection... rather long,. but who's to say it's not some network
issues on my end...
Thanks again to everyone for pointing out the error of my way :)
--
Mark Hazen DataBuilt, Inc. (843) 836-2101 Ext. 251
They may forget what you said, but they will never forget
how you made them feel. --Carl W. Buechner
Re: netusage, high or low?
Brandon
err you mention the le0 interface in the config.
Is this correct 'cos the the le0 interface is a 10base system, not
100base!..
--
Martin
Brandon Moro wrote:
> Hello all!
>
> I am having some troubles with my AMANDA backups running too long. They
> often take 20+ hours,
> sometimes even breaking the 24-hour mark. The average amount of data I get
> is only about 35GB.
>
> I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with 256MB
> RAM, on a 100mbps
> connection. I have 2 DLT 7000 tape drives set up (though it very rarely
> roles over).
>
> Recently, I put a larger holding disk on the server and found that my run
> time was cut more than in half!
> However, I notice that I am still only getting a total of about 3GB an hour.
> The data runs from the holding
> disk to tape at more like 6MB/s.
>
> We have a couple of other backup systems running on almost identical
> hardware that puts more than
> twice as much data to tape in slightly less time. So I guess what I am
> really asking is, am I missing
> something in the configuration of AMANDA sthat will allow better usage of
> the network connection?
>
> I found this in the amanda.conf file:
>
> netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
> (blah blah)
>
> network interfaces
>
> . Attributes are:
> use - bandwidth above which amanda won't
> start
> backups using this interface.
> Note that if
> a single backup will take more
> than that,
> amanda won't try to make it run
> slower!
>
> define interface local {
> comment "a local disk"
> use 1000 kbps
> }
>
> define interface le0 {
> comment "100 Mbps ethernet"
> use 4000 kbps
>
>
> So, does this mean that if my dumpers are using 4000kbps, amanda won't allow
> any more
> dumpers to start (even if the maximum number of allowed dumpers has not been
> reached)?
>
> Can I improve performance by raising the netusage variable and "use"
> attribute to something
> more in line with the actual capacity of the amanda-server's network
> connection?
>
> Also, the network interface on the amanda-server is actually "hme0". Are
> the above simply
> examples? Should I create a new interface definition?
>
> Thanks for your help!
>
> Brandon Moro
> Systems Administration, Unify Corporation
> [EMAIL PROTECTED]
> -
>>From meanness first this Portsmouth Yankey rose, And still to meanness all
> his conduct flows.--Oppression, A poem by an American (Boston, 1765).
>
>
>
Re: file too large
Joshua, The annyoing thing about using this hack is that if you have to use amflush (something goes wrong), then it (amflush) gives you errors about removing cruft files for all of the files that split creates. An ingenious hack nonetheless... :) If you have the disk space, you could switch the holding partition to ReiserFS or maybe ext3 (it supports files larger than 2GB right?) I'm assuming his amanda server is running on linux... Cheers, Mike -- Mike Cathey - http://www.mikecathey.com/ Network Administrator RTC Internet - http://www.catt.com/ Joshua Baker-LePain wrote: > On Wed, 6 Mar 2002 at 4:32pm, Charlie Chrisman wrote > > >>/-- countach.i /dev/sda3 lev 0 FAILED ["data write: File too large"] >> >>I get this for two of my clients? what does this mean? >> >> > FAQ. Set your chunksize to something less then 2GB-32Kb. 1GB is fine -- > there's no performance penalty. > >
netusage, high or low?
Hello all!
I am having some troubles with my AMANDA backups running too long. They
often take 20+ hours,
sometimes even breaking the 24-hour mark. The average amount of data I get
is only about 35GB.
I am running my amanda-server on Solaris8, on a Sun Ultra5 400MHz with 256MB
RAM, on a 100mbps
connection. I have 2 DLT 7000 tape drives set up (though it very rarely
roles over).
Recently, I put a larger holding disk on the server and found that my run
time was cut more than in half!
However, I notice that I am still only getting a total of about 3GB an hour.
The data runs from the holding
disk to tape at more like 6MB/s.
We have a couple of other backup systems running on almost identical
hardware that puts more than
twice as much data to tape in slightly less time. So I guess what I am
really asking is, am I missing
something in the configuration of AMANDA sthat will allow better usage of
the network connection?
I found this in the amanda.conf file:
netusage 4000 Kbps # maximum net bandwidth for Amanda, in KB per sec
(blah blah)
network interfaces
. Attributes are:
use - bandwidth above which amanda won't
start
backups using this interface.
Note that if
a single backup will take more
than that,
amanda won't try to make it run
slower!
define interface local {
comment "a local disk"
use 1000 kbps
}
define interface le0 {
comment "100 Mbps ethernet"
use 4000 kbps
So, does this mean that if my dumpers are using 4000kbps, amanda won't allow
any more
dumpers to start (even if the maximum number of allowed dumpers has not been
reached)?
Can I improve performance by raising the netusage variable and "use"
attribute to something
more in line with the actual capacity of the amanda-server's network
connection?
Also, the network interface on the amanda-server is actually "hme0". Are
the above simply
examples? Should I create a new interface definition?
Thanks for your help!
Brandon Moro
Systems Administration, Unify Corporation
[EMAIL PROTECTED]
-
>From meanness first this Portsmouth Yankey rose, And still to meanness all
his conduct flows.--Oppression, A poem by an American (Boston, 1765).
Disklist Piority
Is there are way of forcing amanda to backup the directories in the disklist in a certain order or at least tell it to back up a thew directories first? - David Flood Systems Administrator [EMAIL PROTECTED] Tel: +44 (0)1224 262721 Robert Gordon University School of Computing St. Andrews Street Aberdeen -
RE: tapetype and tapedev without tape drive
The drive will not arrive for almost two weeks. For now I want to use "file:...". Here is the error that I get now: ERROR: file:/usr/local/share/amanda/bak/: not an amanda tape (expecting a new tape) Here is a snippet from my Amanda.conf: runtapes 1 # number of tapes to be used in a single run of amdump #tpchanger "chg-manual" # the tape-changer glue script tapedev "file:/usr/local/share/amanda/bak/" # the no-rewind tape device to be used #rawtapedev "/dev/null" # the raw device to be used (ftape only) #changerfile "/usr/local/share/amanda/metconnect/changer" #changerfile "/usr/adm/amanda/DailySet1/changer-status" #changerfile "/usr/local/etc/amanda/DailySet1/changer.conf" changerdev "/dev/null" Would I have to define "file:..." in the tapetype section? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Joshua Baker-LePain Sent: Wednesday, March 06, 2002 4:39 PM To: Jeffrey S. Auerbach Cc: [EMAIL PROTECTED] Subject: RE: tapetype and tapedev without tape drive On Wed, 6 Mar 2002 at 4:25pm, Jeffrey S. Auerbach wrote > >the file: driver in your tapetype -- details in amanda(8). > > Not sure I understand, I can't find the correct driver, or do I create a > tapetype called "disk" with the appropriate settings? > Look in the "OUTPUT DRIVERS" section of the man page (amanda(8)) -- there are options for 'tapedev' that aren't actually a physical tape device. But if it you're just waiting for your tape drive to arrive, I wouldn't bother with that. Just define tapedev as whatever it will be and dump to disk (i.e. in degraded mode). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Build dies trying to make amoverview
On Wed, 6 Mar 2002, Bernhard R. Erdmann wrote: > > I am attempting to make amanda 2.4.2p2 on a NetBSD 1.5_ALPHA system > > The make dies with the following message: > > > > cat amcheckdb.sh > amcheckdb > > chmod a+x amcheckdb > > cat amcleanup.sh > amcleanup > > chmod a+x amcleanup > > cat amdump.sh > amdump > > chmod a+x amdump > > make: don't know how to make amoverview. Stop > > *** Error code 1 > > Use GNU make (gmake) Thanks, it worked! --Ruth Anne
Re: incremental backups and one full
On Thu, 7 Mar 2002 at 4:15pm, Tom Van de Wiele wrote > I have 5 tapes, for 5 workingdays a week. I backup 4 partitions, two > being on the tapehost itself, 2 on a remote host. > Right now, the system does a backup every day (the dumptype is "always > full"). The 2 partitions on the host itself can do a full backup > everyday (no network traffic). The two other partitions on the other > host: I want to do a full dump on fridaynight, and during the week I > want incremental backups. Ah, the old "Do it my way!" desire. Is there a reason you want to force amanda into your schedule? Amanda works best (and easiest) when you let it make its own schedule. You can mix full-only and incrementals in one config, but not with your own schedule (unless (I think) you do an incr-only strategy for those partitions and then do an 'amadmin force' every Friday). To answer your question, the "easiest" way to do this is with two configs. > Is this more clear? Did I make a mistake in my configuration? (because > this seems to work) > > Again, my values: > > dumpcycle : 4 days > runspercycle: 5 days > tapecycle: 5 tapes Unless you're running amdump 5 times in 4 days, you want "dumpcycle 1 week" and "runspercycle 5". Also, if you start doing incrementals, you want more tapes. If, e.g., your tape drive eats a tape, it may well contain the only level 0 of a particular filesystem... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Fwd: tape changer problem
Hi, i bet sg0 is not your correct changer-device. What do you get if you type: cat /proc/scsi/scsi this shows you the devices known to your linux-system. In this list locate your changer. If it's the firste device, /dev/sg0 is ok, if its the second, use /dev/sg1 .. Hope it helps Christoph Zhen Liu schrieb: > > Zhen Liu > Via Webmail > [EMAIL PROTECTED] > -- Forwarded message --- > > From: Zhen Liu <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Mon, 04 Mar 2002 12:03:21 -0500 > > Hi, > > I am working on the amanda backup project now, and I am a newbie for > both amanda and linux... right now, I have some problem with our tape > changer...SOS!!! & HELP!!! > > The OS I am working on is Linux RH7.1, the tape changer we have is > Adic Fastor, Quantum 7000 tape drive. > > I guess that something must be wrong with my configuration...when i > run amcheck i get "amcheck-server: could not get changer info: open: > /dev/sg0: success" > > -relevant part from /etc/amanda/daily/amanda.conf > > runtapes 2 > tpchanger "chg-scsi" > tapedev "0" > changerfile "etc/amanda/DailySet1/changer.conf" > changerdev "dev/sg0 > > - /etc/amanda/DailySet1/changer.conf- > number_configs 1 > # eject 1 > sleep60 > cleanmax 1000 > changerdev /dev/sg0 > > # > # Next comes the data for drive 0 > # > config 0 > drivenum 0 > dev /dev/nst0 > startuse 0 > enduse 6 > statfile /etc/amanda/DailySet1/st0-slot > cleancart-1 > cleanfile/etc/amanda/DailySet1/st0-clean > usagecount /etc/amanda/DailySet1/st0-totaltime > > So, I am totally lost...Help? > > Thanks... > > Zhen Liu > Via Webmail > [EMAIL PROTECTED]
Re: incremental backups and one full
Hey I have 5 tapes, for 5 workingdays a week. I backup 4 partitions, two being on the tapehost itself, 2 on a remote host. Right now, the system does a backup every day (the dumptype is "always full"). The 2 partitions on the host itself can do a full backup everyday (no network traffic). The two other partitions on the other host: I want to do a full dump on fridaynight, and during the week I want incremental backups. Is this more clear? Did I make a mistake in my configuration? (because this seems to work) Again, my values: dumpcycle : 4 days runspercycle: 5 days tapecycle: 5 tapes thnx Tom Paul Bijnens wrote: > > Tom Van de Wiele wrote: > > > > Hi list > > > > I'm running amanda without any problems, but I want to change > > something. Right now, I have a dumpcycle of 4 days, runspercycle 5 days > > and a tapecycle of 5 tapes. The backups run at 01am every night, 5 > > (work)days a week. I make a full backup everyday of 4 partitions, 2 > > local on the tapeserver, and 2 remote. > > That's very confusing to me. > > dumpcycle 4 days means: one full backup every 4 days. > runspercycle 5 means: I will insert 5 tapes in those 4 dumpcycle days > that's probably not what you intend! > Then you say, you make a full backup of 4 partitions everyday? > But you said the dumpcycle was 4 days! > > -- > Paul Bijnens, Lant Tel +32 16 40.51.40 > Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 > http://www.lant.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 * > *** -- Tom Van de Wiele System Administrator Eduline Colonel Bourgstraat 105a 1140 Brussel http://www.eduline.be
Re: Fwd: tape changer problem
On Thursday 07 March 2002 09:18 am, Zhen Liu wrote: >Zhen Liu >Via Webmail >[EMAIL PROTECTED] This is a repost. Did you not receive my reply from yesterday? That reply should have contained something helpfull... >-- Forwarded message --- > > >From: Zhen Liu <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Date: Mon, 04 Mar 2002 12:03:21 -0500 > >Hi, > >I am working on the amanda backup project now, and I am a newbie > for both amanda and linux... right now, I have some problem > with our tape changer...SOS!!! & HELP!!! > >The OS I am working on is Linux RH7.1, the tape changer we have > is Adic Fastor, Quantum 7000 tape drive. > >I guess that something must be wrong with my > configuration...when i run amcheck i get "amcheck-server: could > not get changer info: open: /dev/sg0: success" > >-relevant part from /etc/amanda/daily/amanda.conf > >runtapes 2 >tpchanger "chg-scsi" >tapedev "0" >changerfile "etc/amanda/DailySet1/changer.conf" >changerdev "dev/sg0 > >- /etc/amanda/DailySet1/changer.conf- >number_configs 1 ># eject 1 >sleep60 >cleanmax 1000 >changerdev /dev/sg0 > ># ># Next comes the data for drive 0 ># >config 0 >drivenum 0 >dev /dev/nst0 >startuse 0 >enduse 6 >statfile /etc/amanda/DailySet1/st0-slot >cleancart-1 >cleanfile/etc/amanda/DailySet1/st0-clean >usagecount /etc/amanda/DailySet1/st0-totaltime > > >So, I am totally lost...Help? > >Thanks... > > >Zhen Liu >Via Webmail >[EMAIL PROTECTED] -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.6+% setiathome rank, not too shabby for a hillbilly
Re: can't restore irix client with linux host
On Thu, 7 Mar 2002 at 4:19pm, Harri Haataja wrote > But shouldn't an XFS kernel also preserve ACLs and attrs of restoring an > xfs dump image to an xfs volume? > Yep (which is rather nifty). But that means one has to install a new kernel with XFS support. I was simply pointing out the *easiest* way to read xfsrestore images on Linux. I'll add (since you brought it up) that installing an XFS kernel isn't all that much harder and (personally) I've had very good luck with XFS on Linux (knock on wood). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: can't restore irix client with linux host
On Thu, Mar 07, 2002 at 08:58:22AM -0500, Joshua Baker-LePain wrote: > On Wed, 6 Mar 2002 at 5:03pm, Jenn Sturm wrote > > > That should read "Now I've got a successful backup of the IRIX box, > > but when I try to restore on the Linux host,..." > One option for being able to restore files from the IRIX box on the > Linux tape server is to install xfsdump/xfsrestore on your Linux tape > server. SGI has ported them to Linux. You wouldn't even need to install > a patched kernel (with XFS filesystem support) if all you want to do is > run xfsrestore. Just install (RPMs available) xfsdump, recompile amanda, > and you're off and running. Of course, this way you'll *still* be losing > ACL information. To get everything back, run amrecover on the Irix > client, which will automatically use the xfsrestore available on the SGI > box. But shouldn't an XFS kernel also preserve ACLs and attrs of restoring an xfs dump image to an xfs volume? -- "Those who do not understand Unix are condemned to reinvent it, poorly." -- Henry Spencer "Those who try to (re)implement windows(tm) are missing the point of unix." -- A. P. Garcia
Fwd: tape changer problem
Zhen Liu Via Webmail [EMAIL PROTECTED] -- Forwarded message --- From: Zhen Liu <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date: Mon, 04 Mar 2002 12:03:21 -0500 Hi, I am working on the amanda backup project now, and I am a newbie for both amanda and linux... right now, I have some problem with our tape changer...SOS!!! & HELP!!! The OS I am working on is Linux RH7.1, the tape changer we have is Adic Fastor, Quantum 7000 tape drive. I guess that something must be wrong with my configuration...when i run amcheck i get "amcheck-server: could not get changer info: open: /dev/sg0: success" -relevant part from /etc/amanda/daily/amanda.conf runtapes 2 tpchanger "chg-scsi" tapedev "0" changerfile "etc/amanda/DailySet1/changer.conf" changerdev "dev/sg0 - /etc/amanda/DailySet1/changer.conf- number_configs 1 # eject 1 sleep60 cleanmax 1000 changerdev /dev/sg0 # # Next comes the data for drive 0 # config 0 drivenum 0 dev /dev/nst0 startuse 0 enduse 6 statfile /etc/amanda/DailySet1/st0-slot cleancart-1 cleanfile/etc/amanda/DailySet1/st0-clean usagecount /etc/amanda/DailySet1/st0-totaltime So, I am totally lost...Help? Thanks... Zhen Liu Via Webmail [EMAIL PROTECTED]
Re: can't restore irix client with linux host
On Wed, 6 Mar 2002 at 5:03pm, Jenn Sturm wrote > That should read "Now I've got a successful backup of the IRIX box, > but when I try to restore on the Linux host,..." > As everyone has pointed out dump/restore are fs specific, and restore on Linux won't read an xfsdump image. Going with tar is one option. However, if you're using ACLs or any other advanced XFS features, tar won't back those up. One option for being able to restore files from the IRIX box on the Linux tape server is to install xfsdump/xfsrestore on your Linux tape server. SGI has ported them to Linux. You wouldn't even need to install a patched kernel (with XFS filesystem support) if all you want to do is run xfsrestore. Just install (RPMs available) xfsdump, recompile amanda, and you're off and running. Of course, this way you'll *still* be losing ACL information. To get everything back, run amrecover on the Irix client, which will automatically use the xfsrestore available on the SGI box. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: incremental backups and one full
Tom Van de Wiele wrote: > > Hi list > > I'm running amanda without any problems, but I want to change > something. Right now, I have a dumpcycle of 4 days, runspercycle 5 days > and a tapecycle of 5 tapes. The backups run at 01am every night, 5 > (work)days a week. I make a full backup everyday of 4 partitions, 2 > local on the tapeserver, and 2 remote. That's very confusing to me. dumpcycle 4 days means: one full backup every 4 days. runspercycle 5 means: I will insert 5 tapes in those 4 dumpcycle days that's probably not what you intend! Then you say, you make a full backup of 4 partitions everyday? But you said the dumpcycle was 4 days! -- Paul Bijnens, Lant Tel +32 16 40.51.40 Interleuvenlaan 15 H, B-3001 Leuven, BELGIUM Fax +32 16 40.49.61 http://www.lant.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: Failed and Strange Dump Details
After further digging into debug files and the amanda FAQ I figured out my etimeout value was too small. -Original Message- From: Davidson, Brian Sent: Wednesday, March 06, 2002 2:19 PM To: [EMAIL PROTECTED] Subject: Failed and Strange Dump Details I consistantly get the following error backing up on a Sun client: db-test.em / lev 0 FAILED [mesg read: Connection reset by peer] the other disks I backup on the same box work just fine: DUMP SUMMARY: DUMPER STATSTAPER STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s -- - db-test.ems. /eec1 1 2 200.0 0:00 5.6 N/A N/A db-test.ems. -xport/home 1 166266200.0 0:07 90.9 N/A N/A I am also excluding the above two disks from the / backup with and exclude file: # cat /usr/local/lib/amanda/exclude.gtar ./eec ./export/home I've checked the FAQ but can't find anything related directly to the failure message I'm getting above. Any help would be greatly appreciated. Thanks, Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
incremental backups and one full
Hi list I'm running amanda without any problems, but I want to change something. Right now, I have a dumpcycle of 4 days, runspercycle 5 days and a tapecycle of 5 tapes. The backups run at 01am every night, 5 (work)days a week. I make a full backup everyday of 4 partitions, 2 local on the tapeserver, and 2 remote. Now, I want the 2 remote partitions to be backed up full once a week, and the 4 other days incremental. Can I do this without making seperate confs? thanks kind regards Tom Van de Wiele -- Tom Van de Wiele System Administrator Eduline Colonel Bourgstraat 105a 1140 Brussel http://www.eduline.be
