newbie question
Hi all, I'm interresting to use amanda for backbup my network. We do not have tape support but we have a NetApp File Server. So, can Amanda makes backupsand restore of servers through network on File Server. thank, bye kamel latrach [EMAIL PROTECTED] __o _`\,_ ..(_)/ (_)
Re: Disklist Piority
[EMAIL PROTECTED] writes: 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, There is a priority parameter for dumptypes. But it does not work for your purpose. priority string Default: medium. When there is no tape to write to, Amanda will do incremental backups in priority order to the holding disk. The priority may be high(2), medium(1), low(0) or a number of your choice. Having the backup sequence fixed is counterproductive in normal environments: Fast, high backup levels get stalled until the slow level 0 of that big disk is done. Total backup time goes skyrocketing because you loose the parallesism between clients. Why do you want a fixed sequence? Would this help: starttime int Default: none. Backups will not start until after this time of day. The value should be hh*100+mm, e.g. 6:30PM (18:30) would be entered as 1830. You could delay the unimportant directories. Johannes Nieß
Re: amanda reporting nearly-empty tape as full?
Dave Sherohman wrote:
*** THE DUMPS DID NOT FINISH PROPERLY!
*** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]].
*** PERFORMED ALL DUMPS TO HOLDING DISK.
...
FAILURE AND STRANGE DUMP SUMMARY:
...
catmd1 lev 0 FAILED [out of tape]
taper: FATAL syncpipe_get: w: unexpected EOF
...
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 -
You broke the report off just too early :-)
First Amanda said that it was writing md1 from host cat to tape
while it ran out of tape.
In the NOTES section of the Amanda report you'll find something
like: (cut from my last archive report)
NOTES:
taper: tape ARCHIVE-040 kb 34115424 fm 111 writing file: short write
driver: going into degraded mode because of tape error.
From the taper line there, I can see that my backup ran into EOT
while writing 34115424 Kbytes (file 111).
Of course the last dump is not useful, so in the STATISTICS section
it reports only (for my report) 110 files, and it's used space:
Tape Size (meg) 30922.630922.6 0
Tape Used (%) 81.5 81.5 0 (level:#disks ...)
Filesystems Taped 110110 0
So the tape contains 30922 Mbytes USEFUL backup data, and that's
81.5% of the capacity I stated in the tapetype definition:
38000 mbytes / ( 30922 Mbytes + (110 * 500 Kbyte/filemark) )= 0.815 = 81.5 %
The rest of the tape was filled while writing an image that ran into EOT,
but is not calculated in this amount.
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?
It ran out of tape somewhere after 27.3%. For an exact amount of Kilobytes
see the NOTES section in the Amanda report.
You can adjust the capacity you specified in your tapetype definition
if you feel you were a bit optimistic.
Or your capacity is for not-hardware compression, and you use both
hard- and software compression... resulting in LESS native capicity on tape.
Or you ran into an error somewhere halfway the tape (bad tape? drive? computer?)
Look into the system logs to find out (dmesg, syslog, etc).
--
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 *
***
SUMMARY: amrecover: did not get a reserved port: 50059
Thanks: John Dalbec, Jason Thomas It worked! I comented the lines in stream.c and amrecover goes fine. Regards, On Wed, 6 Mar 2002, John Dalbec wrote: This is fixed in CVS. The following patch fixed the problem for me, but YMMV. In particular, if your firewall is picky about source ports for outgoing connections, it won't help you. Note that this is *not* the patch in CVS; OTOH it only affects one file rather than two. It also brings the behavior of --with-portrange in line with the comments in the configure file. (With this patch, the --with-portrange option only affects server ports (that listen for connections), rather than also affecting client ports (that initiate connections).) John --- amanda-2.4.2p2/common-src/stream.c.orig Tue Feb 27 19:53:16 2001 +++ amanda-2.4.2p2/common-src/stream.c Tue Dec 18 15:41:55 2001 -214,10 +214,12 * to get the desired port, and to make sure we return a port that * is within the range it requires. */ +/* #ifdef PORTRANGE if (bind_portrange(client_socket, claddr, PORTRANGE) == 0) goto out; #endif +*/ if (bind_portrange(client_socket, claddr, 512, IPPORT_RESERVED - 1) == 0) goto out; Jason Thomas wrote: amrecover is broken it does this to me as well, and someone else also reported this problem. just do your recover manually. use 'dd' On Wed, Mar 06, 2002 at 01:56:58PM +0100, Jordi Vidal wrote: Hi I cant use amrecover, it fails with a port problem: -- [root@tapeserver /root]# /usr/local/amanda/sbin/amrecover Test-CFG AMRECOVER Version 2.4.2p2. Contacting server on tapeserver ... amrecover: did not get a reserved port: 50059 -- It is the same machine client and server. I compiled amanda with: ./configure --prefix=/usr/local/amanda --with-user=amanda --with-group=disk --with-portrange=5,50100 --with-udpportrange=512,520 (BTW: Was udpportrange 1024 a stupid setting?)
Re: netusage, high or low?
Brandon
From what I've read on this list the netusage parameter is merely
advisory to help with the planner.
--
Martin
Brandon Moro wrote:
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?
If I remember corredctly the defined interfaces are only needed if you
are specifying that a given disklist entry is to backed up directly via
an specific interface (I.E. Private backup networks).
When you look at the report do you see any client contention (I'm sure
you do but is it substantial). I had an issue where the holding_area
was on a heavily utilized bus so the throughput was noticably slower.
So I spread the spindles across different buses (sp???)
What kind of traffic are you seeing when you do a netstat -i 5. You can
raise the netusage amount. But you will find that the hardware does all
of the required throttling needed.
Don
Brandon Moro wrote:
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).
corrupt tape label
Hello, I had an amanda tape (DLTIV) that all of a sudden became corrupt. AMANDA kept returning these errors in amreport: These dumps were to tape daily0_tape3. *** A TAPE ERROR OCCURRED: [[writing filemark: Input/output error]]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: daily0_tape4. When I ran su amanda -c amcheck daily0 on that tape, I got an error that read something like this: I/O error cannot read label This isn't a very important tape as it's overwritten every 5 days, so I ran amrmtape on it and then added it back with amlabel. Anyway, in the end, amflush worked when I ran it on the tape. But I was wondering if I should have just tried to run amlabel on the tape (in hopes that a new label would fix the problem) instead of removing the tape first. Any suggestions as to how to handle future label problems like this? Thanks, Brad
Solution: errors during make
Greetings all, I was having difficulting getting the Amanda client compiled on a Solaris 6 workstation and subsequently found the solution on Google. Here's what I was getting when trying to run make: --- Snip: begin error --- ar cru .libs/libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o ../libtool: ar: not found make[1]: *** [libamanda.la] Error 1 --- Snip: end error --- The solution turned out to be simple. I had to modify my path statement to include /usr/ccs/bin and then it compiled fine. I thought I would post this to the list for in order that others may find it when searching. Jeff
tapedev=otherhost:/dev/nst0 ?
Hi Can I build amanda server in a host without tape and use some other host tapes? The goal is to save the tapeserver (the machine that has the tape device) from CPU load when using compression best Just like tar cf otherhost:/dev/nst0 /disk2dump Regards
Re: amanda reporting nearly-empty tape as full?
On Fri, Mar 08, 2002 at 11:36:11AM +0100, Paul Bijnens wrote: You broke the report off just too early :-) Ah, well... First Amanda said that it was writing md1 from host cat to tape while it ran out of tape. In the NOTES section of the Amanda report you'll find something like: (cut from my last archive report) NOTES: taper: tape ARCHIVE-040 kb 34115424 fm 111 writing file: short write driver: going into degraded mode because of tape error. The report I forwarded yesterday had: NOTES: planner: Adding new disk peterbilt://server/f$. planner: Last full dump of bradley:md10 on tape Daily08 overwritten on this run. planner: Adding new disk nova:hda1. taper: tape Daily08 kb 0 fm 0 writing filemark: Input/output error driver: going into degraded mode because of tape error. Which I'd say confirms that it didn't really run out of tape. Or your capacity is for not-hardware compression, and you use both hard- and software compression... resulting in LESS native capicity on tape. Is hardware compression controlled by the host or the drive? I'm currently using a Linux host and a Quantum DLT4000 drive; the drive's compression LED stays on (my predecessor set this up and I'm only now having the need to look closely at it), so I assume it's using hardware compression. So far, I've only been able to turn it off by using the drive's Density Override button; is there another/a better way? (Yeah, I would RTFdriveM, but I have no idea where TFM is. Disappeared before I got here.) Or you ran into an error somewhere halfway the tape (bad tape? drive? computer?) Look into the system logs to find out (dmesg, syslog, etc). It gets worse... This morning, I didn't have an amanda report waiting in my mailbox, so I tried to ssh to the tape host. No response. Go into the server room, punch it up on the KVM, and see a kernel panic. Looks like swap got hosed and the machine locked up while running the backup last night. *sigh*
Re: tapedev=otherhost:/dev/nst0 ?
On Fri, 8 Mar 2002 at 4:23pm, Jordi Vidal wrote Can I build amanda server in a host without tape and use some other host tapes? The goal is to save the tapeserver (the machine that has the tape device) from CPU load when using compression best Why not just use compress client best? That makes the clients do the compression, not the tape server. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amanda article in SysAdmin magazine
On Thu, 7 Mar 2002 at 7:13pm, Jon LaBadie wrote 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 The mailing lists that form the primary support vehicle for Amanda are informative with a low signal-to-noise ratio. ^^^ I hope he meant high SNR! :) Overall, not a bad article -- thanks for the heads up. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amanda reporting nearly-empty tape as full?
Dave Sherohman wrote: taper: tape Daily08 kb 0 fm 0 writing filemark: Input/output error Which indicates it could write anything to tape yet! It had a problem just after writing the label already, seems to me. Is hardware compression controlled by the host or the drive? I'm currently using a Linux host and a Quantum DLT4000 drive; the drive's compression LED stays on (my predecessor set this up and I'm only now having the need to look closely at it), so I assume it's using hardware compression. So far, I've only been able to turn it off by using the drive's Density Override button; is there another/a better way? (Yeah, I would RTFdriveM, but I have no idea where TFM is. Disappeared before I got here.) On the drive, you can probably do it with the buttons. On the host you can control it with the 'mt-st compression' command. But be warned that when you have a tape written in some density/compression mode the drive automatically adjusts itself to those settings when you insert the tape. That means that if you have tapes written with hardware compression on, amanda will read the tape to verify the label, and thereby getting the parameters set again to what was done before. To get out of this, you'll have to relabel a tape manually, by e.g. first setting the buttons, then immediately write some data to it (do not first read the tape!). It gets worse... This morning, I didn't have an amanda report waiting in my mailbox, so I tried to ssh to the tape host. No response. Go into the server room, punch it up on the KVM, and see a kernel panic. Looks like swap got hosed and the machine locked up while running the backup last night. *sigh* These are all very strong indications of some hardware malfunction. (unless you recently upgraded your kernel to some experimental version :-) -- 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 * ***
Barcode reader
Hi all, I'm happily using chg-scsi with our StorEdge and backups are going well. Thanks to you all for helping me sort out a couple of things. I've tried to find an answer to this in the archives but to no avail. The StorEdge we use has a barcode reader, and the tapes are physically labelled. If I use mtx to check status, I get a nice list of tapes and barcode entries. I have an entry for labelfile in my changer config file, but when I run the chg-scsi -info command, I get 10 20 1 0 The fourth entry indicates I have no reader, but I do. How can I tell amanda and chg-scsi that there's a reader to use? - - - -- Eric Trager
Re: amanda article in SysAdmin magazine
Joshua Baker-LePain wrote: On Thu, 7 Mar 2002 at 7:13pm, Jon LaBadie wrote 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 The mailing lists that form the primary support vehicle for Amanda are informative with a low signal-to-noise ratio. ^^^ I hope he meant high SNR! :) Overall, not a bad article -- thanks for the heads up. I did! This mailing list is one of the most helpful I have seen or participated in. DTS -- David T. Smith PGP Fingerprint: 7B01 0086 BC4E C092 5348 B9AE E79A 07F2 9E59 29C2 ph: 1 203 364 1796 fax: 1 203 364 1795 cell: 1 203 770 1685 E-mail [EMAIL PROTECTED]
root-tar failing
-- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool Here's the log from the failed backup: FAILED AND STRANGE DUMP DETAILS: /-- olympus/dev/root lev 1 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [olympus:/dev/root level 1] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: ./dev/fd: Cannot savedir: Function not implemented ? gtar: ./dev/fd: Warning: Cannot savedir: Function not implemented | gtar: ./tmp/.eventmond.cmd.sock: socket ignored | gtar: ./tmp/.eventmond.events.sock: socket ignored | gtar: ./tmp/.eventmond.info.sock: socket ignored | gtar: ./tmp/.mediad_socket: socket ignored | gtar: ./tmp/.mkpd_socket: socket ignored | gtar: ./tmp/.rtmond_socket: socket ignored | gtar: ./tmp/espdb.sock: socket ignored ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..TK/01: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/spool/90.olympus..OU: Warning: Cannot stat: No such file or directory | gtar: ./var/spool/lp/CMDSOCK: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 3114987520 (2.9GB, 752kB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ .---. |Jennifer Sturm | |System Administrator and Research Support Specialist | |Chemistry Department | |Hamilton College | | | |[EMAIL PROTECTED]| |315-859-4745 | |www.chem.hamilton.edu | .---. |Duct tape is like the force. It has a light side, | | and a dark side, and it holds the universe together. | | -Carl Zwanzig | | | | | |One only needs two tools in life: WD-40 to make things| | go, and duct tape to make them stop. | | -G. Weilacher | .---.
Re: root-tar failing
On Fri, Mar 08, 2002 at 01:02:11PM -0500, Jenn Sturm wrote: -- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool Ignore the socket ignored messages. I can't imagine you'd care to archive those. Also ignore the no such file or directory stuff. That's saying some file was present when the backup was scheduled, which vanished before it could be saved. You probably don't care. Somebody else can probably offer better advice on exclude.gtar. I got mine to where I wanted it a long time ago, and have attempted to forget about that traumatic ordeal, since. Here's the log from the failed backup: FAILED AND STRANGE DUMP DETAILS: /-- olympus/dev/root lev 1 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [olympus:/dev/root level 1] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: ./dev/fd: Cannot savedir: Function not implemented ? gtar: ./dev/fd: Warning: Cannot savedir: Function not implemented | gtar: ./tmp/.eventmond.cmd.sock: socket ignored | gtar: ./tmp/.eventmond.events.sock: socket ignored | gtar: ./tmp/.eventmond.info.sock: socket ignored | gtar: ./tmp/.mediad_socket: socket ignored | gtar: ./tmp/.mkpd_socket: socket ignored | gtar: ./tmp/.rtmond_socket: socket ignored | gtar: ./tmp/espdb.sock: socket ignored ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..TK/01: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/spool/90.olympus..OU: Warning: Cannot stat: No such file or directory | gtar: ./var/spool/lp/CMDSOCK: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 3114987520 (2.9GB, 752kB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ .---. |Jennifer Sturm | |System Administrator and Research Support Specialist | |Chemistry Department | |Hamilton College | | | |[EMAIL PROTECTED]| |315-859-4745 | |www.chem.hamilton.edu | .---. |Duct tape is like the force. It has a light side, | | and a dark side, and it holds the universe together. | | -Carl Zwanzig | | | | | |One only needs two tools in life: WD-40 to make things| | go, and duct tape to make them stop. | | -G. Weilacher | .---. -- - Dan Wilder [EMAIL PROTECTED] Technical Manager Editor SSC, Inc. P.O. Box 55549 Phone: 206-782-8808 Seattle, WA 98155-0549URL http://embedded.linuxjournal.com/ -
Re: root-tar failing
Jenn Sturm wrote: -- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool I was experiencing the exact same problems backing up my Irix box. My exclude file looks as follows: CDROM CIFS Desktop users users2 scratch tmp dev usrs The users.. and usrs directories are backed up as filesystems so that's why they are excluded here. I'm not sure whether this is sufficient, but it definitely took care of my problems. Remember though that the exclude file needs to reside on the client that's being backed up. I.e. you can have a different exclude file for each client. Amanda will look for the exclude file in the directory specified in the dumptype - on the client. Jan -- Jan Boshoff PhD Student, Chemical Engineering Univ. of Delaware, DE USA www.che.udel.edu/research_groups/nanomodeling
Re: root-tar failing
Look in /tmp/amanda for runtar.*.debug file(s). In the debug file is the command line used to invoke tar, look for --exclude-from and make sure that the path and filename specified are as expected. If not, verify that your dumptype in amanda.conf includes exclude list exclude.gtar Good luck, Frank --On Friday, March 08, 2002 13:02:11 -0500 Jenn Sturm [EMAIL PROTECTED] wrote: -- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool Here's the log from the failed backup: FAILED AND STRANGE DUMP DETAILS: /-- olympus/dev/root lev 1 FAILED [/usr/local/bin/tar returned 2] sendbackup: start [olympus:/dev/root level 1] sendbackup: info BACKUP=/usr/local/bin/tar sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... - sendbackup: info end ? gtar: ./dev/fd: Cannot savedir: Function not implemented ? gtar: ./dev/fd: Warning: Cannot savedir: Function not implemented | gtar: ./tmp/.eventmond.cmd.sock: socket ignored | gtar: ./tmp/.eventmond.events.sock: socket ignored | gtar: ./tmp/.eventmond.info.sock: socket ignored | gtar: ./tmp/.mediad_socket: socket ignored | gtar: ./tmp/.mkpd_socket: socket ignored | gtar: ./tmp/.rtmond_socket: socket ignored | gtar: ./tmp/espdb.sock: socket ignored ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/mom_priv/jobs/90.olympus..TK/01: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..JB: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/server_priv/jobs/90.olympus..SC: Warning: Cannot stat: No such file or directory ? gtar: ./var/spool/PBS/spool/90.olympus..OU: Warning: Cannot stat: No such file or directory | gtar: ./var/spool/lp/CMDSOCK: socket ignored | gtar: ./var/spool/postfix/private/bounce: socket ignored | gtar: ./var/spool/postfix/private/bsmtp: socket ignored | gtar: ./var/spool/postfix/private/cyrus: socket ignored | gtar: ./var/spool/postfix/private/defer: socket ignored | gtar: ./var/spool/postfix/private/error: socket ignored | gtar: ./var/spool/postfix/private/ifmail: socket ignored | gtar: ./var/spool/postfix/private/lmtp: socket ignored | gtar: ./var/spool/postfix/private/local: socket ignored | gtar: ./var/spool/postfix/private/rewrite: socket ignored | gtar: ./var/spool/postfix/private/smtp: socket ignored | gtar: ./var/spool/postfix/private/uucp: socket ignored | gtar: ./var/spool/postfix/private/virtual: socket ignored | gtar: ./var/spool/postfix/public/cleanup: socket ignored | gtar: ./var/spool/postfix/public/flush: socket ignored | gtar: ./var/spool/postfix/public/showq: socket ignored | Total bytes written: 3114987520 (2.9GB, 752kB/s) ? gtar: Error exit delayed from previous errors sendbackup: error [/usr/local/bin/tar returned 2] \ .---. | Jennifer Sturm | | System Administrator and Research Support Specialist | | Chemistry Department | | Hamilton College | | | | [EMAIL PROTECTED]| | 315-859-4745 | | www.chem.hamilton.edu | .---. | Duct tape is like the force. It has a light side, | | and a dark side, and it holds the universe together. | | -Carl Zwanzig | | | | | | One only needs two tools in life: WD-40 to make things| | go, and duct tape to make them stop. | | -G. Weilacher | .---. -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: root-tar failing
On Fri, 8 Mar 2002, Dan Wilder wrote: On Fri, Mar 08, 2002 at 01:02:11PM -0500, Jenn Sturm wrote: -- I've configured my Linux box to backup my Irix box using tar, as recommended on this list. It works great for everything but the root paritition. I've tried dumptype comp-root-tar and root-tar, and it continues to fail. I tried creating an exclude.gtar file, and that doesn't seem to be helping any. Here's the contents of the exclude.gtar file. Does the hostname of the Irix box need to be in there? ./dev/fd ./tmp ./var/spool Ignore the socket ignored messages. I can't imagine you'd care to archive those. Also ignore the no such file or directory stuff. That's saying some file was present when the backup was scheduled, which vanished before it could be saved. You probably don't care. Somebody else can probably offer better advice on exclude.gtar. I got mine to where I wanted it a long time ago, and have attempted to forget about that traumatic ordeal, since. I think you need to wildcard the directories like so: ./tmp/* ./var/spool/* etc -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: tapedev=otherhost:/dev/nst0 ?
Thank for your reply I know the client best option but it dont fit my needs. The clients are Windowses, and I have a spare Linux not in production to carry the load compression. On Fri, 8 Mar 2002, Joshua Baker-LePain wrote: Can I build amanda server in a host without tape and use some other host tapes? The goal is to save the tapeserver (the machine that has the tape device) from CPU load when using compression best Why not just use compress client best? That makes the clients do the compression, not the tape server.
Re: Barcode reader
On Fri, 8 Mar 2002, Eric Trager wrote: - - Hi all, - - I'm happily using chg-scsi with our StorEdge and backups are going well. - Thanks to you all for helping me sort out a couple of things. - - I've tried to find an answer to this in the archives but to no avail. The - StorEdge we use has a barcode reader, and the tapes are physically - labelled. If I use mtx to check status, I get a nice list of tapes and - barcode entries. - - I have an entry for labelfile in my changer config file, but when I run - the chg-scsi -info command, I get - - 10 20 1 0 - - The fourth entry indicates I have no reader, but I do. How can I tell - amanda and chg-scsi that there's a reader to use? In changer.conf set havereader=1 -- Stephen Carville UNIX and Network Administrator DPSI (formerly Ace USA Flood Services) 310-342-3602 [EMAIL PROTECTED]
RE: tapedev=otherhost:/dev/nst0 ?
Then make the spare Linux box the one that uses the Samba client to pull data from the Windows boxes. We've been doing that here for a while with no problems. Sample disklist amandaserver /dev/hda1 amandaserver /dev/hda2 spareserver /dev/hda1 spareserver //win1/cshare spareserver //win1/dshare -Original Message- From: Jordi Vidal [mailto:[EMAIL PROTECTED]] Sent: Friday, March 08, 2002 2:39 PM To: Joshua Baker-LePain Cc: Amanda List Subject: Re: tapedev=otherhost:/dev/nst0 ? Thank for your reply I know the client best option but it dont fit my needs. The clients are Windowses, and I have a spare Linux not in production to carry the load compression. On Fri, 8 Mar 2002, Joshua Baker-LePain wrote: Can I build amanda server in a host without tape and use some other host tapes? The goal is to save the tapeserver (the machine that has the tape device) from CPU load when using compression best Why not just use compress client best? That makes the clients do the compression, not the tape server.
amanda 2.4.3b3
The Amanda core team is pleased to announce the release of Amanda 2.4.3b3. It is the third beta release of 2.4.3. All known bugs are fixed. It can be dowloaded from http://www.amanda.org/ This release include a change in the behavior of the exclude option in a dumptype. It it now possible to have many 'exclude' and many 'exclude list' simultaneously. In previous release, only the last one was used. Look at the amanda man page for a description. The command 'amadmin config disklist' will show the exclude used. You need to upgrade the server and client to use multiple exclude, you will get the following message from amcheck if your client is not upgraded: ahost /usr lev 0 FAILED [badly formatted response from ahost] The new 'include' option in a dumptype and the new format of a disklist entry (diskdevice different than the diskname) make it easier to separate a disk in multiple disklist entry using GNUTAR. Look at the amanda man page and example/disklist file for example on how to use it. You need to upgrade the server and client to use 'include' or the new disklist format. Here's a list of the changes for release 2.4.3b3 (from the NEWS file): Look at the ChangeLog file for more details. * --with-maxtapeblocksize configure options * blocksize tapetype option * file-pad tapetype option * Multiple exclude in dumptype * Option include in dumptype * New disklist syntax: * hostname diskname [ diskdevice ] dumptype [ spindle [ interface ] ] * chg-zd-mtx: Major cleanup and general overhaul. * amrecover: new listdisk command. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Archive bit not getting reset on Windows clients
I am having a problem with my Windows backups. I have a user 'backup' defined for each Windows system and that user is given full access rights (everything is checked) for the share. It backs up ok, but doesn't reset the archive setting so that it is basically trying a level 0 dump all the time (even when it thinks it is doing a level 1 as best I can tell). Any one have any ideas of things to check? This is causing my backups to have problems nightly as my DDS-4 isn't big enough for a full of all shares (plus by unix/linux backups each night). Thanks, Gene -- Gene Matthews Matthews Midrange Consulting, Inc. (678) 923-8327 (877) 882-6291 (toll free) http://mmc-inc.com
Re: amanda 2.4.3b3
Hello John, Maybe libtool doesn't support your OSF1 V5.1 732 alpha. You can debug libtool or configure with --disable-libtool Jean-Louis On Fri, Mar 08, 2002 at 01:52:50PM -0800, John Koenig wrote: Thank you for all your (and everyone else involved) hard work... Though... I am having build issues... Can someone suggest soemething that I should examine (and fix) to make the build work properly? thank you... -JFK # 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.3b3/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.3b3/config' make[2]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' make[1]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config' Making all in common-src make[1]: Entering directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/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.3b3/common-src' make: *** [all-recursive] Error 1 # The Amanda core team is pleased to announce the release of Amanda 2.4.3b3. It is the third beta release of 2.4.3. All known bugs are fixed. -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amanda 2.4.3b3
Hello again...
I took the advice and inserted --disable-libtool into my configure.
(OSF1 V5.1 732 alpha)
Files actually started to compile this time instead of dying right at the
beginning..
This time... not long after some files *did* compile, it seems the broken libtool
invocation showed up again... How can that be? I said 'disable-libtool'.
Does this information plus the fact that the 2.4.2p2 build worked fine without the
disabling the use of libtool, provide any useful information to the maintainers?
###
Here is my output from the most recent build attempt of amanda-2.4.3b3:
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.3b3/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.3b3/config'
make[2]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config'
make[1]: Leaving directory `/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/config'
Making all in common-src
make[1]: Entering directory
`/net/redbelly/scratch1/Admin/Build/amanda-2.4.3b3/common-src'
source='alloc.c' object='alloc.o' libtool=no \
depfile='.deps/alloc.Po' tmpdepfile='.deps/alloc.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f alloc.c || echo './'`alloc.c
source='amflock.c' object='amflock.o' libtool=no \
depfile='.deps/amflock.Po' tmpdepfile='.deps/amflock.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f amflock.c || echo './'`amflock.c
source='debug.c' object='debug.o' libtool=no \
depfile='.deps/debug.Po' tmpdepfile='.deps/debug.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f debug.c || echo './'`debug.c
source='dgram.c' object='dgram.o' libtool=no \
depfile='.deps/dgram.Po' tmpdepfile='.deps/dgram.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f dgram.c || echo './'`dgram.c
cc: Warning: dgram.c, line 110: In this statement, the referenced type of the pointer
value len is unsigned int, which is not compatible with int because they differ
by signed/unsigned attribute. (ptrmismatch1)
if(getsockname(s, (struct sockaddr *)name, len) == -1) {
^
cc: Warning: dgram.c, line 292: In this statement, the referenced type of the pointer
value addrlen is unsigned long, which is not compatible with int. (ptrmismatch)
(struct sockaddr *)fromaddr, addrlen);
-^
source='error.c' object='error.o' libtool=no \
depfile='.deps/error.Po' tmpdepfile='.deps/error.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f error.c || echo './'`error.c
source='file.c' object='file.o' libtool=no \
depfile='.deps/file.Po' tmpdepfile='.deps/file.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f file.c || echo './'`file.c
source='fileheader.c' object='fileheader.o' libtool=no \
depfile='.deps/fileheader.Po' tmpdepfile='.deps/fileheader.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f fileheader.c || echo './'`fileheader.c
source='match.c' object='match.o' libtool=no \
depfile='.deps/match.Po' tmpdepfile='.deps/match.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f match.c || echo './'`match.c
source='protocol.c' object='protocol.o' libtool=no \
depfile='.deps/protocol.Po' tmpdepfile='.deps/protocol.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f protocol.c || echo './'`protocol.c
source='regcomp.c' object='regcomp.o' libtool=no \
depfile='.deps/regcomp.Po' tmpdepfile='.deps/regcomp.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -I/usr/local/gnu/include
-O2 -c `test -f regcomp.c || echo './'`regcomp.c
source='regerror.c' object='regerror.o' libtool=no \
depfile='.deps/regerror.Po' tmpdepfile='.deps/regerror.TPo' \
depmode=tru64 /usr/bin/sh ../config/depcomp \
cc
