Re: Problems with flush-thresholds
Jean-Louis, thanks so much for producing this patch. I applied it
without problems to the amanda-3.2.1 tar file.
However, I haven't compiled or installed it yet. My amanda was installed
from the amanda-backup-server-3.2.1-1.rhel5.rpm package. I'm concerned
that just compiling and installing the tar file will break parts of the
system, because it won't be installed in the same way as the RH package.
Is there any way to apply the patch, then repackage it just like the
original rpm, then install it as an update to my current version? Is
this something you could give me some brief instruction on, or are there
any pointers for doing this on the web?
Thanks, again, for all your help.
-Kevin
On Thu, 2011-02-03 at 07:14 -0500, Jean-Louis Martineau wrote:
Kevin,
Can you try the attached patch?
Jean-Louis
Kevin Zembower wrote:
Sorry this has taken so long. Thank you for any help or advice you can
provide.
-Kevin
On Wed, 2010-12-22 at 07:15 -0500, Jean-Louis Martineau wrote:
Kevin,
Post the amdump.? log file, I want to look at it.
Jean-Louis
Kevin Zembower wrote:
I'm having problems when I try to set amanda up to completely fill my
tapes. One of my disklist entries is about 600GB at level 0. I'm using
amanda 3.2.1 on a RHEL5 tapehost with Ultrium tapes that hold 200GB. I
set:
flush-threshold-dumped 100
flush-threshold-scheduled 100
taperflush 100
autoflush yes
When I watch amstatus, I see the big DLE tape tape up to 100%, but then
it reports a PARTIAL tape. Then all the other DLEs waiting to tape
report process canceled waiting to be taped and they stay on the
holding disk. The report states that 602GB were left on the holding
disk.
When I set the three variables to 0, taping proceeds normally, and the
big DLE and the rest of the DLEs span four tapes correctly. However,
most of the time, the tapes are only filled to less than 5%.
Any suggestions on what I can do to fill tapes to capacity? Thanks for
your help and suggestions.
-Kevin
differences between files attachment (large-dle-flush-threshold.diff)
diff --git a/server-src/driver.c b/server-src/driver.c
index 51b55db..bfccdab 100644
--- a/server-src/driver.c
+++ b/server-src/driver.c
@@ -3703,11 +3703,10 @@ tape_action(
off_t sched_size;
off_t dump_to_disk_size;
int dump_to_disk_terminated;
-off_t my_flush_threshold_dumped;
-off_t my_flush_threshold_scheduled;
-off_t my_taperflush;
int nb_taper_active = nb_sent_new_tape;
int nb_taper_flushing = 0;
+off_t data_next_tape = 0;
+off_t data_lost = 0;
dumpers_size = 0;
for(dumper = dmptable; dumper (dmptable+inparallel); dumper++) {
@@ -3748,11 +3747,19 @@ tape_action(
tapeq_size -= taper1-left;
}
if (taper1-disk) {
+ off_t data_to_go;
if (taper1-dumper) {
- tapeq_size += sched(taper1-disk)-est_size - taper1-written;
+ data_to_go = sched(taper1-disk)-est_size - taper1-written;
} else {
- tapeq_size += sched(taper1-disk)-act_size - taper1-written;
+ data_to_go = sched(taper1-disk)-act_size - taper1-written;
}
+ data_next_tape += data_to_go - taper1-left;
+ if (data_to_go taper1-left) {
+ data_lost += taper1-written - taper1-left;
+ } else {
+ data_lost += data_to_go - taper1-left;
+ }
+ tapeq_size += data_to_go;
}
}
driver_debug(1, _(tapeq_size: %lld\n), (long long)tapeq_size);
@@ -3771,19 +3778,6 @@ tape_action(
nb_taper_active++;
}
}
-if (nb_taper_active = 1) {
-my_flush_threshold_dumped = flush_threshold_dumped +
- (nb_taper_active-nb_taper_active) * tape_length;
-my_flush_threshold_scheduled = flush_threshold_scheduled +
-(nb_taper_active-nb_taper_active) *
tape_length;
-my_taperflush = taperflush + (nb_taper_active-nb_taper_active) *
tape_length;
-} else {
-my_flush_threshold_dumped = flush_threshold_dumped +
- nb_taper_active * tape_length;
-my_flush_threshold_scheduled = flush_threshold_scheduled +
-nb_taper_active * tape_length;
-my_taperflush = taperflush + nb_taper_active * tape_length;
-}
// Changing conditionals can produce a driver hang, take care.
//
@@ -3796,8 +3790,9 @@ tape_action(
result |= TAPE_ACTION_NO_NEW_TAPE;
} else if (current_tape conf_runtapes
taper_nb_scan_volume == 0
-((my_flush_threshold_dumped tapeq_size
- my_flush_threshold_scheduled sched_size) ||
+((flush_threshold_dumped tapeq_size
+ flush_threshold_scheduled sched_size
Don't understand what's happening specifying Samba shares to amadmin find
I don't understand what's happening when I try to specify Samba shares on the command line: [EMAIL PROTECTED]:~$ amadmin DBackup find centernet Scanning /dumps/amanda2... Scanning /dumps/amanda... Scanning /dumps/amanda2... Scanning /dumps/amanda... date host disk lv tape or file file status snip 2005-10-21 centernet.jhuccp.org //db/e$0 DBackup29 7 OK snip 2005-10-21 centernet.jhuccp.org //db/f$0 DBackup29 9 OK snip [EMAIL PROTECTED]:~$ amadmin DBackup find centernet //db/e$ snip No dump to list [EMAIL PROTECTED]:~$ amadmin DBackup find centernet //db/f$ snip No dump to list [EMAIL PROTECTED]:~$ amadmin DBackup find centernet //db/f$ snip No dump to list [EMAIL PROTECTED]:~$ amadmin DBackup find centernet.jhuccp.org //db/f$ snip No dump to list [EMAIL PROTECTED]:~$ amadmin DBackup find centernet.jhuccp.org '//db/f$' snip No dump to list [EMAIL PROTECTED]:~$ Why don't I ever list the backups done on 21-Oct? Thanks for helping me with this. -Kevin
Re: Need help diagnosing hostname problems
Thank you, Olivier, Scott and Matt, for all your suggestions. Your helpfulness is part of what makes Amanda a truly great solution. The problem, as you all suggested, seems to be the lack of a reverse DNS look-up capability: [EMAIL PROTECTED]:~$ host www.jhuccp.org www.jhuccp.org has address 162.129.45.74 [EMAIL PROTECTED]:~$ head /etc/hosts 127.0.0.1 localhost 10.253.192.204 www.jhuccp.org snip [EMAIL PROTECTED]:~$ host -n 10.253.192.204 Host 204.192.253.10.in-addr.arpa not found: 3(NXDOMAIN) [EMAIL PROTECTED]:~$ My hosts are in a DMZ, in the 10.253.192/24 network. They're NATted to the outside Internet as hosts in the 162.129.45/24 network. The solution proposed by the folks who control the DNS was to use a /etc/hosts file. As you probably know, this provides forward DNS-like lookups, but not reverse. At this point, they seem unwilling to provide a split DNS that would resolve correctly in both forward and reverse directions for the DMZ. I'm betting this might be a fairly common problem that some of you all have solved before. What's your preferred solution? I can think of a couple of alternatives, such as: - set up my own DNS on one of my hosts in the DMZ. This isn't too hard, but is one more thing to maintain. I'd probably choose tinydns, since I already run qmail. - hack amanda to remove the check for reverse DNS. If this is preferred, can anyone give me a hint where to find this and how to best do it? - Can /etc/hosts or something related provide static reverse DSN look-ups? This would be an easy solution, but I don't know of anything that does it. Thanks you all, again, for all your suggestions and advice. -Kevin Olivier Nicole [EMAIL PROTECTED] 10/19/05 09:36PM Hi, ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found That seems like network issue to me, rather than amanda issue. Did you make sure that your amanda server can ping to www.jhuccp.org? After renumbering did you change your DNS server address? Bests, olivier
Need help diagnosing hostname problems
I had an amanda setup that worked fine until two weeks ago, when I had to change the network addresses of all my hosts and move them into a separate DMZ, using a different, new DNS. Now, I'm not able to get one host to respond, and the output is puzzling: [EMAIL PROTECTED]:/tmp/amanda-dbg$ amcheck -c DBackup Amanda Backup Client Hosts Check ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] Client check: 2 hosts checked in 0.702 seconds, 1 problem found (brought to you by Amanda 2.4.4p3) [EMAIL PROTECTED]:/tmp/amanda-dbg$ dig www.jhuccp.org ; DiG 9.2.4 www.jhuccp.org ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 41347 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.jhuccp.org.IN A ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204 ;; Query time: 2 msec ;; SERVER: 10.23.2.10#53(10.23.2.10) ;; WHEN: Wed Oct 19 11:36:58 2005 ;; MSG SIZE rcvd: 48 [EMAIL PROTECTED]:/tmp/amanda-dbg$ I'm puzzled by the response in amcheck, ERROR: www.jhuccp.org: [addr 10.253.192.205: hostname lookup failed] compared to the correct response in dig, ;; ANSWER SECTION: www.jhuccp.org. 3600IN A 10.253.192.204. The IP address that amcheck responded with, 10.253.192.205, is the IP for the tapehost itself, cn2. Is amcheck complaining that 10.253.192.204 doesn't resolve to www.jhuccp.org (it shouldn't; www.jhuccp.org is 205), or is it complaining that 10.253.192.205 doesn't resolve correctly to the name of the tapehost? I tried to check the debug files generated in /tmp/amanda-dbg/. There were four files generated from 'amcheck -c DBackup', but none of them seemed to contain any information regarding this failure. Thanks for any suggestions or advice in working on this problem. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: turn off hardware compression
See 'man mt'. On my Linux Debian system, mt datcompression 1 #prints DAT compression mt datcompression 0 #disables DAT compression mt datcompression x #where x is anything other than 0 or 1 enables DAT compression Hope this helps. -Kevin Nina Pham [EMAIL PROTECTED] 12/01/04 07:11PM I having problem with the backup. The backup tape capacity is 20/40G, I tried to backup only around 17 G compressed. Following are the error message tar: Removing leading `/' from member names tar: /dev/st0: Wrote only 0 of 10240 bytes tar: Error is not recoverable: exiting now So I tried tar -M, it shows that the tape is out of space. I suspect something wrong with the hardware compression. Is there a command to check if the hardware compression is on or off? how can I turn it on or off? Thanks in advance
Re: Amanda Compression
'Kosher for Passover', I think. -Kevin Paul Bijnens [EMAIL PROTECTED] 09/23/04 10:51AM Brian Cuttler wrote: ...Unless of course the K is within a circle. Then it means something else entirely. K within a circle??? I already know C, R within a circle, but not heard of K with a circle. Ready to learn more :-) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Still hoping for answer for amanda port usage
Hi, Frank, thanks for your work and efforts to help me with my problem. Please see my remarks, preceded by *** (stupid GroupWise email client won't quote correctly), below. -Kevin Frank Smith [EMAIL PROTECTED] 09/15/04 07:34PM --On Wednesday, September 15, 2004 15:28:21 -0400 KEVIN ZEMBOWER [EMAIL PROTECTED] wrote: The discussion's petered out on my request for which ports to ask the firewall administrator to open to allow amanda to work through our firewall, but I'm still hoping for an answer, as I still can't come up with one myself. There was one comment that ports 10080-10083 are fixed, no matter what --with-???portrange switches are used. Is this fact or fiction? I think fact. Those are the ones listed in /etc/services. *** I thought that these were set up in /etc/services based on the settings --with-portrange, --with-tcpportrange and --with-udpportrange, or if they're fixed and unchangeable. There's no 'amanda' listing in the assigned numbers in RFC 1700 (http://www.faqs.org/rfcs/rfc1700.html). In the spirit of re-phrasing the question, can anyone help me complete the following sentence to my firewall administrator: Please open port numbers through for [UDP|TCP|both] packets [from|to] my tapehost (inside fw) [to|from] my client(s). That sentence may have to be completed more than once for each different range, protocol or direction. Usually, when discusion dies down without a clear answer it means nobody is really sure of the exact answer, although I think someone gave you a very good description of the backup process port usage. ***Yes, I really appreciate Michael taking the time to try to explain that to me. Unfortunately, I didn't understand it completely and had some follow-up questions, which went unanswered. My next attempt will be to look into the files John Jackson mentions in the port usage document, and see if I can figure out from the source code what ports are used. I've been putting this off, as I don't know C, but it's looking like this is the only way to answer the questions I have. Whatever I learn, I'll post back here. I've got firewall rules that work (for me), but they may be allowing more than absolutely necessary (i.e., some ports open bidirectionally when they only need to be open one direction with the 'established allow' rule covering the response packets). In the interest of science (and my own curiosity) I've set up a packet capture on one of my VPN boxes to log network traffic between one of my tape servers and a remote client tonight. Since the two servers don't normally talk with each other except for the backup, tomorrow I should be able to see the exact sequence of events, and since that client is a very small backup (/etc and /vaar/spool/cron/crontabs) it shouldn't be a huge mass to wade through. I'll let you know tomorrow what I discover. *** Thank you so much for offering to do this. I'm anxious to learn what you find out. Frank Thanks, again, for any help. -Kelvin - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Still hoping for answer for amanda port usage
Oh, just to make sure I understand correctly what you're saying: The 1008x ports are not compiled into the program by any of the '--with-???portrange' configuration options. Instead, they're determined at run-time by examining the entries in /etc/service. That makes a lot of sense, but I didn't understand or even consider that until now. Thanks so much. -Kevin Eric Siegerman [EMAIL PROTECTED] 09/16/04 12:57PM On Wed, Sep 15, 2004 at 03:28:21PM -0400, KEVIN ZEMBOWER wrote: There was one comment that ports 10080-10083 are fixed, no matter what --with-???portrange switches are used. Is this fact or fiction? (c) Neither of the above :-) The 1008x ports are not affected by the --with-*portrange options, but neither are they fixed in the sense of being hard-coded integers; they are *determined* by the entries in /etc/services. When deciding which well-known port to listen on or connect to, the Amanda code looks up the service name in /etc/services, and uses the port number it finds there (see getservbyname(3)). As I understand it (which I semi do -- I fully understood it a year and a half ago when I set up Amanda here, but you know how it goes :-/), Amanda uses the --with-*portrange options only for ports that are *not* well-known, i.e. not listed in /etc/services. There are (at least) two standard patterns for starting a connection (whether that's a real TCP connection or merely an exchange of UDP packets): 1. using a well-known port: - the listener listens on a well-known port, L1 - the initiator chooses an arbitrary port I1 for its own end, and uses it to connect to L1 at the listener end 2. not: - the listener chooses an arbitrary port L2, listens on L2, and communicates L2's port number to the initiator via some pre-existing channel (pipe, network connection, disk file, whatever) - the initiator receives the port number L2; it chooses an arbitrary port I2, and uses that to connect to L2 In Amanda, L1 is one of the three entries from /etc/services (1008x by default). If I remember correctly, I1, I2, and L2 are all determined by the --with-*portrange options. Note (and this I *am* sure of) that in Amanda, it is not dependable that initiator==client and listener==server. The client initiates some connections, but the tape server initiates others. -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, Foucault's Pendulum
Status of --with-portrange?
I'm getting ready to write up my notes on what I learned on amanda's use of ports in firewalls, and have one further question. Someplace, I thought I read that the configuration option '--with-portrange' is obsolete and should not be used. Instead, '--with-tcpportrange' is preferred. Is this correct? Any subtleties I should include? Thanks. -Kevin - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Still hoping for answer for amanda port usage
The discussion's petered out on my request for which ports to ask the firewall administrator to open to allow amanda to work through our firewall, but I'm still hoping for an answer, as I still can't come up with one myself. There was one comment that ports 10080-10083 are fixed, no matter what --with-???portrange switches are used. Is this fact or fiction? In the spirit of re-phrasing the question, can anyone help me complete the following sentence to my firewall administrator: Please open port numbers through for [UDP|TCP|both] packets [from|to] my tapehost (inside fw) [to|from] my client(s). That sentence may have to be completed more than once for each different range, protocol or direction. Thanks, again, for any help. -Kelvin - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Amcheck and amdump port usage?
Andreas, thanks for writing and your advice. Unfortunately, I can't control any aspect of the firewall. It is administered by another group within my organization. I don't believe that they understand the firewall software thoroughly. Furthermore, it seems to be five-year-old software which is no longer being maintained. I don't believe that it's very sophisticated and able to use syn/ack flags. I'm very frustrated. If you tell me that I have to open all ports from 1024 through 65535, using TCP, inbound from my client(s) to my tapehost, that's fine with me. I don't believe that this is a significant security risk. However, I have to spell out exactly what I need, in this format, for the firewall administrators to act on it. Thanks again for your thoughts. -Kevin Andreas Putzo [EMAIL PROTECTED] 09/13/04 05:07PM On Monday 13 September 2004 22:54, KEVIN ZEMBOWER wrote: [amanda network traffic] I don't know for sure, but i think, amanda won't bind to a specific from-port. Normally the kernel choses a high (semi-)random port. But you can still build your firewall rules depending on the destination host/port and syn/ack flags for the tcp connections. regards, Andreas
Amcheck and amdump port usage?
I'm still trying to troubleshoot my problem getting Amanda to work though a firewall. I've read John Jackson's port usage document and the FAQ at http://amanda.sourceforge.net/fom-serve/cache/139.html. I'd like someone to comment on whether or not I have the overall communication sequence correct below. Then, I'd like information on how this is different if amcheck rather than amdump is run. In compiling amanda, I used these options: --with-portrange=10080,10083 --with-tcpportrange=10080,10083 --with-udpportrange=850,854. This is what I understand concerning the sequence of port usage in making an amanda backup: 1. The tapehost makes a 'start backup' request of the client, originating on port 850-854 to port 10080-10083 using UDP. The contents of the packet contain a port number in the range 850-854 which is open on the tapehost, listening for TCP connections. 2. The client responds by sending a UDP packet from any (?) port to port 850-854 on the tapehost. [Q: Can ports 850-854 on the tapehost be open to receive both UDP and TCP packets at the same time?] The contents of the packet are port numbers in the range 10080-10083 on the client which are listening for TCP packets from the tapehost. 3. The tapehost responds by sending a packet from port 10080-10083 using TCP to port 10080-10083 on the client. This packet starts the transmission of the backup data from the client to the tapehost, using the same port numbers just used. Thanks for reviewing this and letting me know whether I've got it right. I appreciate your patience and help. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Amcheck and amdump port usage?
Michael, thank you for taking the time to try to help me. Please see my further questions below. Michael Loftis [EMAIL PROTECTED] 09/13/04 03:04PM --On Monday, September 13, 2004 14:24 -0400 KEVIN ZEMBOWER [EMAIL PROTECTED] wrote: 1. The tapehost makes a 'start backup' request of the client, originating on port 850-854 to port 10080-10083 using UDP. The contents of the packet contain a port number in the range 850-854 which is open on the tapehost, listening for TCP connections. Your steps are pretty wrong so lets start over.. 1. tapehost makes 'start backup, estimate/etc' call to amandad over UDP on remote (usually 10080) client sends back response(s) to udp port (udpportrange). The UDP packet is sent from the tapehost from which port? Is it correct that it always goes to port 10080 on the client, no matter what is defined in the compilation of amanda with --with-portrange --with-udpportrange or --with-tcpportrange? Which port on the client does the response come from? 2. after response/receipt of estimates (Assuming backup run) at some point later the server sends start backup, this packet contains a tcp port to connect to on the server in the tcpportrange/portrange (these are the same). the client may also connect to amandaidx on the tape server as well to transmit indices at this time (I can't remember, and it does depend on the index option in the dumptype config). Once connected the client begins transmitting backup data to the server. Is it correct that the packet of 'start backup' from the tapehost is sent UDP? From which port on tapehost? What port on the client is it addressed to? Is it the same ports on both tapehost and client as the ports in step 1? Is the amandaidx port on the tapehost always 10082/tcp, regardless of the --with-???portrange switches? That's it, two (ish) step process. If it's a check request it just does a test to see if it can get an estimate or backup by dispatching the appropriate commands on the client side, then responding back to the tapehost on the indicated UDP port (udpportrange). If it's going to be a backup then further TCP connections will be made to the ports indicated when the backup starts. For estimates they come back via UDP packets. And, again, the packet is UDP, from which port on the client to which port on the tapehost? Same as in step 1? No TCP connections are made to udpportrange, and the server never connects to the client. The server doesn't tell the client to start backup until it's ready for data to flow to it. Thanks, again, for your patience in answering these questions. -Kevin
Errors in amstatus output
I just noticed these errors in the output of amstatus, from a run last night:
[EMAIL PROTECTED]:/etc/amanda/Outside$ amstatus Outside
Using /var/amanda/Outside/amdump.1 from Fri Sep 10 00:45:02 EDT 2004
www:sda1 10k finished (0:51:14)
www:sda10 2 1919k finished (0:51:51)
www:sda11 0 3319737k finished (4:42:52)
www:sda12 1 150k wait for dumping driver: (aborted)
Use of uninitialized value in printf at /usr/local/sbin/amstatus line 742.
www:sda14 00k failed to tape (7:20:40)
Use of uninitialized value in addition (+) at /usr/local/sbin/amstatus line 757.
Use of uninitialized value in addition (+) at /usr/local/sbin/amstatus line 767.
www:sda2 2 104343k finished (0:56:14)
www:sda5 1 120k finished (0:52:07)
www:sda6 1 3094k wait for dumping driver: (aborted)
www:sda7 0 5295676k finished (3:01:40)
www:sda8 250437k finished (1:02:50)
SUMMARY part real estimated
size size
partition : 10
estimated : 10 14068515k
flush : 0 0k
failed : 00k ( 0.00%)
wait for dumping: 2 3244k ( 0.02%)
dumping to tape : 00k ( 0.00%)
dumping : 0 0k 0k ( 0.00%) ( 0.00%)
dumped : 8 13847339k 14065271k ( 98.45%) ( 98.43%)
wait for writing: 1 0k 5075107k ( 0.00%) ( 0.00%)
wait to flush : 0 0k 0k (100.00%) ( 0.00%)
writing to tape : 0 0k 0k ( 0.00%) ( 0.00%)
failed to tape : 1 0k 5075107k ( 0.00%) ( 0.00%)
taped : 7 8772232k 8990164k ( 97.58%) ( 62.35%)
tape 1: 7 8772232k 8990164k ( 53.47%) Outside-04
4 dumpers idle : not-idle
taper idle
network free kps: 5800
holding space : 3392k (100.00%)
dumper0 busy : 6:29:10 ( 99.93%)
taper busy : 6:27:14 ( 99.43%)
0 dumpers busy : 0:00:16 ( 0.07%) start-wait: 0:00:16 (100.00%)
1 dumper busy : 6:29:10 ( 99.93%)not-idle: 6:27:14 ( 99.50%)
start-wait: 0:00:59 ( 0.25%)
no-bandwidth: 0:00:56 ( 0.24%)
[EMAIL PROTECTED]:/etc/amanda/Outside$
Has the bahavior of amstatus changed? I thought you couldn't get an amstatus after the
run was completed.
Here's the section of the code:
737 elsif($taper_finished{$hostpart} 0)
{
738 if( defined $opt_failed ||
739 (defined
$opt_waittaper ($taper_finished{$hostpart} == -1))) {
740 printf %8s ,
$datestamp if defined $opt_date;
741 printf
%-${maxnamelength}s%2d, $host:$partition, $level{$hostpa
741 rt};
742 printf %9dk,
$size{$hostpart};
743 if($in_flush == 0) {
744 print
failed to tape;
745 }
746 else {
747 print
failed to flush;
748 }
749 print (will retry)
unless $taper_finished{$hostpart} -1;
750 if( defined
$starttime ) {
751 print (,
showtime($taper_time{$hostpart}), );
752 }
753 print \n;
754 }
755
756 $tfpartition++;
757 $tfsize += $size{$hostpart};
758 if(defined $esize{$hostpart})
{
759 $tfesize +=
$esize{$hostpart};
760 }
761 else {
762 $tfesize +=
$size{$hostpart};
763 }
764
765 if($in_flush == 0) {
766 $twpartition++;
767
Amanda through a VPN?
Has anyone ever set up Amanda to work through a VPN as an alternative to working correctly through a firewall? I'm not sure a VPN is even the right tool to use. I'm so frustrated with our networking group, which implements a single change in the firewall, then requires that we wait until the next morning to make a second trial if the first one doesn't work. I believe that no one really thorough understands the firewall software, an Elron CommandView firewall, which seems to be out of production. The last mention I can find of it through Google dates to 1999. Links to their website redirect to zixcorp.com. Consequently, I'm exploring other options to get Amanda to work through or around this firewall. The first I thought of was a VPN. However, I only know what I've read about VPNs; I've never set one up or worked with it. Would a VPN work? Is it the right tool to use, short of getting the firewall to work properly in the first place? Any recommendation on specific VPN solutions to use? Anyone done this before? I tried searching on 'vpn' in this list's archives, but didn't turn up anything. Thanks for all your help and suggestions. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Amanda through a VPN?
Frank and Rebecca, thank you for your comments and suggestions. I understand that I'll still need to work with the firewall administrators. It's just seems so much more complex to do Amanda's ports right -- only open the ones needed, using only the protocol and in only the right direction -- than to say Open port 10080 in both direction between tapehost and client. Right now, the firewall seems to have ports 10080-84 opened correctly (tested with telnet and tcpdump). They could just let this be. Our setup is that our web servers are outside the firewall, but the tapehost and other administrative hosts, as well as all the Windows-based desktops are inside. We use 176.14/16 addresses inside, but 'real' IP addresses outside. However, the hosts are side-by-side in the same rack. If I do go with some sort of VPN, am I on the right track here?: Both the tapehost and the client(s) all have to have a VPN (daemon? client?) on them, such as OpenVPN or vtun. I ask the firewall folks to open one port, like 10080, to TCP and UDP, in both directions to and from the tapehosts and the client(s). The notes in amanda.conf state that the OS routing tables control which interface is used, so I make some change there to connect from the tapehost to the clients using the VPN. This will all probably be clear to me when I pick a VPN and read the documentation. Thanks, again, for your advice and suggestions. -Kevin Frank Smith [EMAIL PROTECTED] 09/08/04 04:05PM --On Wednesday, September 08, 2004 14:41:34 -0400 KEVIN ZEMBOWER [EMAIL PROTECTED] wrote: Has anyone ever set up Amanda to work through a VPN as an alternative to working correctly through a firewall? I'm not sure a VPN is even the right tool to use. Yes, we use VPNs to backup some of the data at our remote colos. I'm not sure its going to make your firewall setup any easier to implement (it will still require some firewall changes), but once you get the VPN working you can change what goes through it without having to modify the intervening firewalls. I'm so frustrated with our networking group, which implements a single change in the firewall, then requires that we wait until the next morning to make a second trial if the first one doesn't work. I believe that no one really thorough understands the firewall software, an Elron CommandView firewall, which seems to be out of production. The last mention I can find of it through Google dates to 1999. Links to their website redirect to zixcorp.com. Personally, I'd be scared if I were depending on a firewall that hasn't been updated for 5 years. Consequently, I'm exploring other options to get Amanda to work through or around this firewall. The first I thought of was a VPN. However, I only know what I've read about VPNs; I've never set one up or worked with it. Would a VPN work? Yes, it can. Is it the right tool to use, short of getting the firewall to work properly in the first place? It depends. How sensitive is your data? The backups are streamed in in the clear, although possibly compressed, so there is the potential for someone to grab it as it goes by. With a VPN the data stream (at least between the VPN boxes) is encrypted, so impractical for someone to steal the data in that portion of the data path. If your network is secure (relative to the sensitivity of your data) then it may not have much of an advantage. If it is very sensitive data and you are sending it across the Internat then a VPN should be a requirement. Any recommendation on specific VPN solutions to use? Anyone done this before? I tried searching on 'vpn' in this list's archives, but didn't turn up anything. Being a thrifty person, I'm a fan of using a pair of cheap Linux boxes (my backups can soak a 10Mb link over a couple of 800MHz Pentiums without any problems with a 2.4 kernel and FreeS/WAN), the 2.6 kernels have IPSEC capabilities built in. As a bonus you can run iptables (netfilter) on the same boxes and firewall what goes through your tunnel. You may have to do some work setting up routing on both ends so your backups actually use the VPN. Frank Thanks for all your help and suggestions. -Kevin Zembower - E. Kevin Zembower Internet Systems Group manager Johns Hopkins University Bloomberg School of Public Health Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Interpreting amplot for newbies
For some reason, I though amplot was too difficult to set up and use, so I never tried it for the last three years that I've used Amanda. Now, with a new installation, I've tried it. However, I'm not sure how to read and understand the plots. Would anyone be willing to take a look at the amplot output at http://www.jhuccp.org/20040828.pdf and http://www.jhuccp.org/20040831.pdf and give me any suggestions on how my setup could be tuned? In general, I think everything's okay, since all the lines are below 100% capacity, but that's the limit of what I can get from the plots. Specifically, is it normal or common for there to be an almost 50 minute dead-space at the beginning of each run? I'm familiar with the idea of needing time to compute estimates, but this seems excessive. Also, should I worry about these lines when I produce an amplot: [EMAIL PROTECTED]:/var/amanda/DBackup$ amplot -e -p -l -t 2 amdump.2 Unknown statement# driver: tape size 19714048 20040828 INFO# dumper: bind_portrange: all ports between 850 and 854 busy 20040828 INFO# dumper: bind_portrange: all ports between 10080 and 10083 busy Thanks for your thoughts and suggestions. I appreciate your advice. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Amplot on letter-size paper?
I just started using amplot, and am having some difficulty. All my plots seem to be for legal size paper, 14 inches long. Any way to change them into letter? I don't see any text at the top, as the man page indicates; it runs off the page just above the '100%' in the holding disk area. Thanks. I also can't figure out how to cause my printer to use legal paper. I've tried using 'mpage -bLegal' but it didn't work, but that's another problem. Thanks for any suggestions. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Restore buffer?
I have never bothered setting up or using the restore component of Amanda (amrestore). I dd the backup from the tape, uncompress if necessary and pipe to restore or tar -x. I put the restored file in my (root or amanda) directory and could then compare it to the existing file if I wanted to. In this sense, amanda can do what you require. This is done by a (skilled?) administrator, however. If users needed to do this, it might be too complex and done too infrequently for them to do without error. Hope this helps. -Kevin - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 Darren Landrum [EMAIL PROTECTED] 08/25/04 01:32PM I am in charge of seeting up a new backup server for the County of Montrose, CO. My boss has asked me to put together a system that will allow us to buffer a restore job (say, grabbing a file from tape) before sending the file back to its proper place on a server. The reason he feels this is necessary is so we can look at a file restored from tape before we destroy anything that might be on the server proper. That way, it can be confirmed by the user that this is indeed the file(s) they need restored before we commit to the final action. Is Amanda capable of this kind of operation? Thank you very much for your time. -- Regards, Darren Landrum Montrose County IT
Re: AMANDA Documentation at www.oops.co.at
Stefan, thank for taking the time to do this. In the spirit of bug-finding, I am unable to print page 93 of today's version of the postscript file. Don't know if this is related to the error below. I'm using Adobe Acrobat 6.0 inside of IE 6.0 on a Windows XP platform (no flames; required on the organization's LAN). Thanks, again. -Kevin [EMAIL PROTECTED] 08/24/04 10:30AM Hi, Paul, on Dienstag, 24. August 2004 at 15:34 you wrote to amanda-users: papc In a message dated: Tue, 24 Aug 2004 00:15:31 +0200 papc Stefan G. Weichinger said: Just get the file at: http://www.oops.co.at/AMANDA-docs/index.html papc Hmmm, ghostscript seems to have trouble converting this to postscript: papc $ pdf2ps amanda.pdf amanda.ps papc Unknown operator: '. papc Error: /syntaxerror in --token-- papc Operand stack: papc365361 2546 0 4 --dict:9/9(ro)(G)-- --nostringval-- Errm, you're right, I have no clue why this happens, have to dig that up. Fortunately I am able to generate ps straight with my buildtree. You said, you want a pdf, so I gave you pdf ;-) So you would like me to put the ps-file online, too, am I right ? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Another 'Amanda through firewall' problem
Two years ago, I wrote here about problems getting Amanda to work through a firewall using NAT which couldn't be turned-off. I finally gave up in frustration, despite the helpful advice of the folks here, and set up two separate backup systems, one inside and outside the firewall. Adding to my frustration is the fact that I don't administer the firewall, and can't verify directly that what I requested was implemented. Now, I'm trying again to back up all my host with just one Amanda system. My tapehost 'centernet' is trying to back up hosts 'admin' and 'mailinglists' in addition to itself, inside the firewall, and hosts 'www' and 'real' outside the firewall. I've read and tried to follow the advice given to others in this situation. I changed the file common-src/security.c to comment out the section where the port number is checked. I also used the script, first given here, pasted in at the end of this note, to configure Amanda on both the server and the clients. I have the new Amanda system (tapehost inside the firewall) working on all the other hosts inside the firewall, but it times out with the hosts outside the firewall. When I amcheck it, I don't get anything written in either the working or non-working clients, in either /tmp/Amanda or /tmp/Amanda-dbg. Can anyone suggest any diagnostic tools or methods that I can use to verify that the firewall is set up the way I requested? I've tried to use 'netcat' in the past to verify proper transmission through a firewall, but don't understand how I could use it in this case, as I don't know what port the firewall will NAT the request to. I'm not getting any diagnostic messages in any of the logs I've looked at, on either the host or clients. Any suggestions? Thanks for all your help and advice. -Kevin Zembower = [EMAIL PROTECTED]:~$ cat configure_amanda.sh #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` != 'amanda' ]; then echo echo Warning echo Amanda needs to be configured and built by the user amanda, echo but must be installed by user root. echo exit 1 fi echo Warning echo Did you remember to make the changes in common_src/security.c echo to disable the port check, to allow amanda to work through a echo NATted firewall like CCP's? echo make clean rm -f config.status config.cache ../configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --prefix=/usr/local \ --with-portrange=10080,10083 \ --with-tcpportrange=10080,10083 \ --with-udpportrange=850,854 \ --with-debugging=/tmp/amanda-dbg/ \ --with-config=DBackup \ --with-smbclient=/usr/bin/smbclient \ --with-configdir=/etc/amanda [EMAIL PROTECTED]:~$
Re: problems when ejecting tapes
I always get this message when I amlabel a brand new tape. I think it's caused by trying to read an unformatted, unused tape. But, as Paul says, it can also be caused by trying to read the tape too soon after inserting it. -Kevin Paul Bijnens [EMAIL PROTECTED] 08/17/04 12:43PM CPH wrote: Also when I put the next tape in and try to do an amlabel I get the error message : amlabel: tape_rewind: rewinding tape: /dev/nst0: Input/output error Maybe because you are too fast? Wait for the leds to stop flickering. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Erroneous Last full dump overwritten message
I go this message last night: NOTES: planner: Last full dump of www:sda11 on tape overwritten in 1 run. And yet, I have plenty of level 0 backups: [EMAIL PROTECTED]:~$ amadmin Outside find www sda11 Scanning /dumps/amanda... date host disk lv tape or file file status 2004-06-09 www sda11 2 Outside-21 10 OK 2004-06-11 www sda11 3 Outside-01 12 OK 2004-06-12 www sda11 0 Outside-02 15 OK 2004-06-15 www sda11 1 Outside-03 12 OK 2004-06-16 www sda11 2 Outside-04 13 OK 2004-06-17 www sda11 3 Outside-05 11 OK 2004-06-19 www sda11 3 Outside-07 14 OK 2004-06-22 www sda11 0 Outside-08 15 OK 2004-06-23 www sda11 1 Outside-09 13 OK 2004-06-24 www sda11 2 Outside-10 13 OK 2004-06-25 www sda11 3 Outside-11 9 OK 2004-06-26 www sda11 0 Outside-12 16 OK 2004-06-29 www sda11 1 Outside-13 12 OK 2004-06-30 www sda11 2 Outside-14 11 OK 2004-07-01 www sda11 3 Outside-15 10 OK 2004-07-02 www sda11 3 Outside-16 12 OK 2004-07-03 www sda11 3 Outside-17 11 OK 2004-07-07 www sda11 0 --- 0 FAILED (driver) [dump to tape failed] 2004-07-07 www sda11 0 --- 0 FAILED (dumper) [data write: Connection reset by peer] 2004-07-07 www sda11 0 Outside-19 14 [out of tape] 2004-07-08 www sda11 0 Outside-20 16 OK [EMAIL PROTECTED]:~$ This indicates that one was just made last night, but three others existed within the tapecycle. My amanda.conf setting are: dumpcycle 8 # the number of days in the normal dump cycle runspercycle 8 # the number of amdump runs in dumpcycle days tapecycle 15 tapes # the number of tapes in rotation Is this message indicating that there's no level 0 backup within the last dumpcycle tapes? This isn't a big concern; I've been just ignoring it for a couple of years now. But today, I'm curious and have the time to write about it. Also, is there something missing after the word 'tape' in the message, planner: Last full dump of www:sda11 on tape overwritten in 1 run.? On my other operating amanda system, this is usually filled in by the tape name. Thanks for your thoughts and suggestions. -Kevin - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
And ignoring other SAMBA errors (Was: Re: changing strange SAMBA message to error)
I have the exact opposite problem. I have some error indications that I'd like to ignore, as they consistently happen and don't mean that there's a problem, if I understand them correctly. Here's two examples: /-- admin //db/f$ lev 0 STRANGE sendbackup: start [admin://db/f$ level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? INFO: Debug class all level = 1 (pid 25061 from pid 25061) | added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 | tar: dumped 85 files and directories | Total bytes written: 4812196352 sendbackup: size 4699411 sendbackup: end \ I don't know what this means, but I don't think it means that there's an error. I'd even like to ignore these errors: /-- admin //db/c$ lev 0 STRANGE sendbackup: start [admin://db/c$ level 0] sendbackup: info BACKUP=/usr/bin/smbclient sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... - sendbackup: info end ? INFO: Debug class all level = 1 (pid 21854 from pid 21854) | added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\system (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software.LOG (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default.LOG (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY.LOG (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SYSTEM.ALT (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM (\WINNT\system32\config\) ? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM.LOG (\WINNT\system32\config\) ? ERRDOS - ERRnoaccess opening remote file \pagefile.sys (\) | tar: dumped 5940 files and directories | Total bytes written: 471141888 sendbackup: size 460100 sendbackup: end \ I know that these error messages mean that files are not being backed up correctly. However, our restoration process on this host would be to install a fresh Windows NT server, then restore from backups the database files on it which were backed up correctly. Is there any way short of recompiling to tell Amanda to ignore these in the daily report? It's not worth the trouble to me to recompile the program just to get rid of them. Thanks. -Kevin Paul Bijnens [EMAIL PROTECTED] 06/23/04 11:12AM Harlan Harris wrote: I'm running Amanda on a heterogeneous network. Server is a Linux box. Some of the clients are Windows machines, and we're running Samba. Mostly works OK, except that sometimes the Windows machines have errors that look like the following: ? Call timed out: server did not respond after 2 milliseconds listing \Program Files\Microsoft Office\* Currently, this call timed out message is being labeled as strange, but I really need to change that to an error, since data is being lost when this happens. How do I reconfigure (or recompile?) Amanda so that this sort of error is categorized as an error, rather than strange? Thanks, You should add some regular expressions in client-src/sendbackup-gnutar.c, around line 120: 118 #if SAMBA_VERSION = 2 119 /* Backup attempt of nonexisting directory */ 120 AM_ERROR_RE(ERRDOS - ERRbadpath (Directory invalid.)), 121 #endif Then recompile. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
Re: Dealing with a dump too big
Hi, Stefan, Thanks for pointing out the option on amdump to just backup a single host or partition; I never used that, and overlooked what you were trying to tell me in my original response. I've been working since yesterday to implement your suggestions. I'll modify the slashes to back-slashes today, when I'm able to make an individual run for just the admin //db/f$ share. WRT the '$' metacharacter, what I actually had to run was: amdump DailySet1 admin '//db/f\$' Thanks, again, for your help and suggestions. -Kevin [EMAIL PROTECTED] 06/21/04 01:37PM Hi, Kevin, on Montag, 21. Juni 2004 at 19:19 you wrote to amanda-users: KZ Stefan, hi, thanks for your suggestions. KZ Here's the output before any changes are made: [EMAIL PROTECTED]:~ amadmin DailySet1 disklist admin //db/ KZ snip of info for admin //db/c$ and admin //db/e$ KZ line 100: KZ host admin: KZ interface default KZ disk //db/f$: KZ program GNUTAR KZ exclude file ./inetsrv/ And now you modified it to the backslashes? KZ [Why can't I enter 'amadmin DailySet1 disklist admin KZ //db/f$'? I get amadmin: no disk matched, unless I trim it back KZ to amadmin DailySet1 disklist admin //db/.] The character $ seems to be interpreted as the regex-metacharacter. KZ As Paul points out, the problem is a flaw in the way KZ estimated sizes are computed: it ignores the excluded files and KZ directories. This way the estimates should be bigger than the actual dumps. KZ Won't your suggestion to: KZ amadmin DailySet1 force admin //db/f$ KZ amdump DailySet1 admin //db/f$ KZ just force admin //db/f$ to do a level 0 dump, but all the KZ rest of the backup targets do whatever they were scheduled to do? KZ This normally takes 4-6 hours on my system, and wouldn't complete KZ before the normally scheduled backup. I am doing 'amadmin KZ DailySet1 force admin //db/f$' for tonight's backup. the second line would just dump the DLE given, //db/f$. SYNOPSIS amdump config [ host [ disk ]* ]* Stefan.
Dealing with a dump too big
I'm trying to deal with a problem which I've just noticed. I've completely overwritten
my level 0 backup of a disk called admin://db/f$. This is a SAMBA share from an NT
server. I think I have complete level one backups:
[EMAIL PROTECTED]:~ amadmin DailySet1 find admin //db/ |fgrep //db/f$
2004-05-20 admin //db/f$ 1 DailySet109 8 OK
2004-05-21 admin //db/f$ 1 DailySet11113 OK
2004-05-24 admin //db/f$ 1 DailySet112 7 OK
2004-05-25 admin //db/f$ 1 DailySet114 8 OK
2004-05-26 admin //db/f$ 1 DailySet11510 OK
2004-05-27 admin //db/f$ 1 DailySet11610 OK
2004-05-28 admin //db/f$ 1 DailySet117 8 OK
2004-05-31 admin //db/f$ 1 DailySet118 7 OK
2004-06-01 admin //db/f$ 1 DailySet119 8 OK
2004-06-02 admin //db/f$ 1 DailySet121 8 OK
2004-06-04 admin //db/f$ 1 DailySet123 9 OK
2004-06-07 admin //db/f$ 1 DailySet12411 OK
2004-06-08 admin //db/f$ 1 DailySet125 9 OK
2004-06-09 admin //db/f$ 1 DailySet126 8 OK
2004-06-10 admin //db/f$ 1 DailySet12712 OK
2004-06-11 admin //db/f$ 1 DailySet12810 OK
2004-06-14 admin //db/f$ 1 DailySet101 9 OK
2004-06-15 admin //db/f$ 1 DailySet10212 OK
2004-06-16 admin //db/f$ 1 DailySet10410 OK
2004-06-17 admin //db/f$ 1 DailySet10510 OK
2004-06-18 admin //db/f$ 1 --- 0 FAILED (planner) [dumps way too
big, 5679359 KB, must skip incremental dumps]
2004-06-18 admin //db/f$/inetsrv 0 DailySet10613 OK
[EMAIL PROTECTED]:~
The last daily report I got, in the planner section, said:
planner: admin //db/f$ 20040618 0 [dump larger than tape, 13855177 KB, full dump
delayed]
The disk F: on the NT server is indeed 13G in size, but I didn't think that would be a
problem, since I excluded //db/f$/inetsrv, which is 9.1G. This filesystem, which I
just backup for the first time last run, backed up at level 0 just fine:
[EMAIL PROTECTED]:~ amadmin DailySet1 info admin //db/
snip
Current info for admin //db/f$:
Stats: dump rates (kps), Full: 4221.0, 4333.0, 4412.0
Incremental: 4607.0, 4309.0, 4723.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20040514 DailySet10515 4621248 4622030 1095
1 20040617 DailySet10510 5662420 5662530 1229
Current info for admin //db/f$/inetsrv:
Stats: dump rates (kps), Full: 3642.0, -1.0, -1.0
Incremental: -1.0, -1.0, -1.0
compressed size, Full: -100.0%,-100.0%,-100.0%
Incremental: -100.0%,-100.0%,-100.0%
Dumps: lev datestmp tape file origK compK secs
0 20040618 DailySet10613 9174403 9193950 2524
[EMAIL PROTECTED]:~
The pertinent sections of my disklist and amanda.conf files are:
[EMAIL PROTECTED]:~ grep admin /etc/amanda/DailySet1/disklist
admin //db/f$ db-f-nocomp-medpri-tar-exclude-inetsrv #DB server, Drive F: excluding
\inetsrv
admin //db/f$/inetsrv nocomp-medpri-tar #DB server, Drive F:\inetsrv\
[EMAIL PROTECTED]:~
From amanda.conf:
# Special dumptypes for excluding directories
define dumptype db-f-nocomp-medpri-tar-exclude-inetsrv{
nocomp-medpri-tar
comment Special for admin//db/f$, excluding /inetsrv/
exclude ./inetsrv/
}
My questions are:
1. What's the long term solution to this problem? Have I done something wrong in the
amanda.conf or disklist files?
2. Is there anything I can do right now, before the nightly normal run, to get a level
0 backup of just this share?
Thanks for all your help and suggestions.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Re: Dealing with a dump too big
Stefan, hi, thanks for your suggestions.
Here's the output before any changes are made:
[EMAIL PROTECTED]:~ amadmin DailySet1 disklist admin //db/
snip of info for admin //db/c$ and admin //db/e$
line 100:
host admin:
interface default
disk //db/f$:
program GNUTAR
exclude file ./inetsrv/
priority 1
dumpcycle 3
maxdumps 1
maxpromoteday 1
strategy STANDARD
compress NONE
auth BSD
kencrypt NO
holdingdisk YES
record YES
index NO
skip-incr NO
skip-full NO
line 101:
host admin:
interface default
disk //db/f$/inetsrv:
program GNUTAR
priority 1
dumpcycle 3
maxdumps 1
maxpromoteday 1
strategy STANDARD
compress NONE
auth BSD
kencrypt NO
holdingdisk YES
record YES
index NO
skip-incr NO
skip-full NO
[EMAIL PROTECTED]:~
[Why can't I enter 'amadmin DailySet1 disklist admin //db/f$'? I get amadmin: no disk
matched, unless I trim it back to amadmin DailySet1 disklist admin //db/.]
As Paul points out, the problem is a flaw in the way estimated sizes are computed: it
ignores the excluded files and directories.
Won't your suggestion to:
amadmin DailySet1 force admin //db/f$
amdump DailySet1 admin //db/f$
just force admin //db/f$ to do a level 0 dump, but all the rest of the backup targets
do whatever they were scheduled to do? This normally takes 4-6 hours on my system,
and wouldn't complete before the normally scheduled backup. I am doing 'amadmin
DailySet1 force admin //db/f$' for tonight's backup.
Thanks, again, for your suggestions.
-Kevin
[EMAIL PROTECTED] 06/21/04 12:43PM
Hi, Kevin,
on Montag, 21. Juni 2004 at 17:46 you wrote to amanda-users:
KZ The disk F: on the NT server is indeed 13G in size, but I
KZ didn't think that would be a problem, since I excluded
KZ //db/f$/inetsrv, which is 9.1G. This filesystem, which I just
KZ backup for the first time last run, backed up at level 0 just fine:
KZ The pertinent sections of my disklist and amanda.conf files are:
[EMAIL PROTECTED]:~ grep admin /etc/amanda/DailySet1/disklist
KZ admin //db/f$ db-f-nocomp-medpri-tar-exclude-inetsrv #DB
KZ server, Drive F: excluding \inetsrv
KZ admin //db/f$/inetsrv nocomp-medpri-tar #DB server, Drive
F:\inetsrv\
[EMAIL PROTECTED]:~
KZ From amanda.conf:
KZ # Special dumptypes for excluding directories
KZ define dumptype db-f-nocomp-medpri-tar-exclude-inetsrv{
KZnocomp-medpri-tar
KZcomment Special for admin//db/f$, excluding /inetsrv/
KZexclude ./inetsrv/
KZ }
KZ My questions are:
KZ 1. What's the long term solution to this problem? Have I done
KZ something wrong in the amanda.conf or disklist files?
The usage of excludes is a bit different when backing up smb-shares.
Please give me the output of
amadmin DailySet1 disklist admin //db/f$
which should tell us more about how AMANDA interprets your cascading
of exclusions ...
Execute this before and after you edited the following =
You can only use ONE exclusion-option with smbclient ...
AFAIK this should be:
exclude .\inetsrv\*
in this case (Win uses backslashes ...)
KZ 2. Is there anything I can do right now, before the nightly
KZ normal run, to get a level 0 backup of just this share?
You can do this (after editing your exclusion):
amadmin DailySet1 force admin //db/f$
amdump DailySet1 admin //db/f$
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Re: Troubleshooting a slowdown problem?
Frank, thanks, again, for your analysis. When you mentioned the connection speed, I remembered that I had to ask our network administrators to change the speed and auto-negotiation properties on the Cisco switch that the old centernet host was plugged into to fix the speed at 100baseTx-FD and turn off auto-negoiation. I've forgotten to do that for the new centernet host. On the admin host, it was okay: admin:~ # mii-diag Using the default interface 'eth0'. Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 . Basic mode control register 0x2100: Auto-negotiation disabled, with Speed fixed at 100 mbps, full-duplex. You have link beat, and everything is working OK. Link partner information is not exchanged when in fixed speed mode. End of basic transceiver information. admin:~ # admin:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:27:B6:FB:E7 inet addr:172.16.2.7 Bcast:172.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::290:27ff:feb6:fbe7/10 Scope:Link inet6 addr: fe80::90:27b6:fbe7/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22539412 errors:0 dropped:0 overruns:0 frame:0 TX packets:16228564 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:768887232 (733.2 Mb) TX bytes:1301570470 (1241.2 Mb) Interrupt:21 Base address:0x8000 admin:~ # uptime 11:00am up 2 days, 18:06, 1 user, load average: 2.01, 1.97, 1.59 admin:~ # date Fri Jun 18 11:00:23 EDT 2004 admin:~ # Even thought the admin host has only been up 2 days, there are zero collisions and carrier errors. When I tested the file transfer speed between centernet and admin, before making any changes, I also noticed that auto-negoiation was on, and that it was not set to full duplex: cn2:~# mii-diag Using the default interface 'eth0'. Basic registers of MII PHY #1: 3000 782d 02a8 0154 05e1 4081 0003 . The autonegotiated capability is 0080. The autonegotiated media type is 100baseTx. Basic mode control register 0x3000: Auto-negotiation enabled. You have link beat, and everything is working OK. Your link partner advertised 4081: 100baseTx. End of basic transceiver informaion. cn2:~# [EMAIL PROTECTED]:~/dblogs$ ncftpput -u kevinz -p xx admin ~/ 20040610.popline..wpd 20040610.popline.wpd: 988.09 MB 36.13 kB/s ncftpput 20040610.popline.wpd: data transfer aborted by local user. [EMAIL PROTECTED]:~/dblogs$ After fixing the speed to 100baseTx-FD and turning auto-negoiation off, the speed improved 300 times: cn2:~# mii-diag -F 100baseTx-FD Using the default interface 'eth0'. Setting the speed to fixed, Control register 2100. Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 4081 0001 . The autonegotiated capability is 0080. The autonegotiated media type is 100baseTx. Basic mode control register 0x2100: Auto-negotiation disabled, with Speed fixed at 100 mbps, full-duplex. You have link beat, and everything is working OK. Your link partner advertised 4081: 100baseTx. End of basic transceiver informaion. cn2:~# cn2:~# mii-diag Using the default interface 'eth0'. Basic registers of MII PHY #1: 2100 780d 02a8 0154 05e1 4081 0001 . The autonegotiated capability is 0080. The autonegotiated media type is 100baseTx. Basic mode control register 0x2100: Auto-negotiation disabled, with Speed fixed at 100 mbps, full-duplex. You have link beat, and everything is working OK. Your link partner advertised 4081: 100baseTx. End of basic transceiver informaion. [EMAIL PROTECTED]:~/dblogs$ ncftpput -u kevinz -p xx admin ~/ 20040610.popline..wpd 20040610.popline.wpd: 988.09 MB 11.04 MB/s ncftpput 20040610.popline.wpd: data transfer aborted by local user. [EMAIL PROTECTED]:~/dblogs$ I should have also noticed the large number of collision and carrier errors on centernet: cn2:~# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:B0:D0:49:55:20 inet addr:172.16.2.4 Bcast:172.16.255.255 Mask:255.255.0.0 IPX/Ethernet 802.3 addr:0958:00B0D0495520 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:43966452 errors:0 dropped:0 overruns:0 frame:0 TX packets:50236123 errors:0 dropped:0 overruns:25 carrier:10736563 collisions:11145079 txqueuelen:100 RX bytes:1206617378 (1.1 GiB) TX bytes:469366 (3.7 GiB) Interrupt:16 Base address:0x5000 cn2:~# uptime 11:00:06 up 45 days, 13 min, 1 user, load average: 0.00, 0.04, 0.13 cn2:~# date Fri Jun 18 11:00:07 EDT 2004 cn2:~# I compared this with the OLD centernet host, which I still have up and has been up much longer than either admin or the new centernet: OLD centernet: centernet:~ # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:A0:C9:E4:5B:D5 inet addr:172.16.2.6
Re: Troubleshooting a slowdown problem?
Paul, thanks for your thoughts. I don't think so. The whole amanda.conf concerning the
holding disks is:
holdingdisk hd1 {
comment main holding disk
directory /var/amanda # where the holding disk is
use -0Mb# how much space can we use on it. Use everything.
chunksize 1Gb # size of chunk if you want big dump to be
}
holdingdisk hd2 {
directory /dumps2/amanda
use -0 Mb
}
reserve 50 # percent
[EMAIL PROTECTED]:/etc/amanda/DailySet1 amcheck DailySet1
Amanda Tape Server Host Check
-
Holding disk /dumps2/amanda: 28166344 KB disk space available, using 28166344 KB
Holding disk /var/amanda: 8307732 KB disk space available, using 8307732 KB
NOTE: skipping tape-writable test
Tape DailySet106 label ok
Server check took 10.613 seconds
Amanda Backup Client Hosts Check
Client check: 3 hosts checked in 1.359 seconds, 0 problems found
(brought to you by Amanda 2.4.4)
[EMAIL PROTECTED]:/etc/amanda/DailySet1 df -h
FilesystemSize Used Avail Use% Mounted on
/dev/sda3 7.6G 5.2G 2.0G 72% /
/dev/sda1 22M 3.4M 17M 16% /boot
/dev/sdb1 8.3G 8.0k 7.9G 1% /var/amanda
/dev/sdc1 33G 4.9G 26G 16% /dumps2
shmfs1010M 0 1010M 0% /dev/shm
[EMAIL PROTECTED]:/etc/amanda/DailySet1
Can you think of something I'm overlooking?
Thanks, again.
-Kevin
Paul Bijnens [EMAIL PROTECTED] 06/18/04 12:43PM
KEVIN ZEMBOWER wrote:
I don't know why the 33G of
holding disk space doesn't seem like enough or isn't getting used.
I'll reverse the order of holding disk hd1, which is only 8G, with
hd2, 33G, so maybe it'll use the larger one first.
Any other parameters in the config for holding disk that could
affect the use of it?
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: Troubleshooting a slowdown problem?
Jon, I apologize. My email reader, GroupWise, doesn't quote lines, so I'd have to
manually break each line and insert . That gets me into trouble with the other half
of the world who want their email readers to adjust line length to the width that they
prefer.
You know, I've never looked at the amanda man page for the 'use' value. I just went by
the comments in the amanda.conf file, which state, a non-positive value means: use
all space but that value. So I couldn't use 0 (zero) because that would say use only
zero KB according to these comments. I used '-0' meaning 'use everything BUT 0 KB'.
Thanks for pointing this out. I'll change it right away, and see if that makes a
difference.
Thanks, again, for your suggestions.
-Kevin
[EMAIL PROTECTED] 06/18/04 01:45PM
Boy is it hard to send a reply that makes sense when there
is a mixture of unedited top and bottom postings :(
On Fri, Jun 18, 2004 at 01:12:35PM -0400, KEVIN ZEMBOWER wrote:
KEVIN ZEMBOWER wrote:
Paul, thanks for your thoughts. I don't think so. The whole amanda.conf concerning
the holding disks is:
holdingdisk hd1 {
comment main holding disk
directory /var/amanda # where the holding disk is
use -0Mb# how much space can we use on it. Use everything..
chunksize 1Gb # size of chunk if you want big dump to be
}
holdingdisk hd2 {
directory /dumps2/amanda
use -0 Mb
}
reserve 50 # percent
Can you think of something I'm overlooking?
Just a wierd, unlikely, possibility.
The amanda man page says for the use parameter
- a positive number means use only that amount
- a zero means use all available
- a negative number means use all EXCEPT that amount
You use parameter fits none of these exactly in that you have
a negative zero. Is it possible the zero is being interpreted
as all and the negative as except?
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Troubleshooting a slowdown problem?
# /
centernet sda3 comp-user# /usr
centernet sda5 comp-user# /opt/analog/logdata
centernet sda6 comp-user# /var/www/centernet/htdocs
centernet sda7 comp-user# /var/lib/mysql
centernet sda9 comp-user# /var/www/centernet/logs
[EMAIL PROTECTED]:/etc/amanda/DailySet1
[EMAIL PROTECTED]:/etc/amanda/DailySet1 egrep -v (^( |\t)*#|^$) amanda.conf
org JHU/CCP # your organization name for reports
mailto [EMAIL PROTECTED]# space separated list of operators at your site
dumpuser amanda # the user to run dumps under
inparallel 8# maximum dumpers that will run in parallel (max 63)
dumporder # specify the priority order of each dumper
netusage 25000 Kbps# maximum net bandwidth for Amanda, in KB per sec
dumpcycle 3 # the number of days in the normal dump cycle
runspercycle 3 # the number of amdump runs in dumpcycle days
tapecycle 25 tapes # the number of tapes in rotation
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
etimeout 300# number of seconds per filesystem for estimates.
dtimeout 1800 # number of idle seconds before a dump is aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
tapebufs 20
tapedev /dev/nst0 # the no-rewind tape device to be used
rawtapedev /dev/null # the raw device to be used (ftape only)
tapetype Python-DDS3# what kind of tape it is (see tapetypes below)
labelstr ^DailySet1[0-9][0-9]*$ # label constraint regex: all tapes must match
holdingdisk hd1 {
comment main holding disk
directory /var/amanda # where the holding disk is
use -0Mb# how much space can we use on it. Use everything.
chunksize 1Gb # size of chunk if you want big dump to be
}
holdingdisk hd2 {
directory /dumps2/amanda
use -0 Mb
}
reserve 50 # percent
autoflush yes #
infofile /var/log/amanda/DailySet1/curinfo# database DIRECTORY
logdir /var/log/amanda/DailySet1# log directory
indexdir /var/log/amanda/DailySet1/index # index directory
define tapetype Python-DDS3 {
comment Dell Python with DDS-3 tapes
length 11570 mbytes
filemark 0 kbytes
speed 1078 kps
lbl-templ /usr/local/etc/amanda/DailySet1/3holeJHUCCP.ps
}
define dumptype global {
comment Global definitions
}
define dumptype comp-user {
global
comment Non-root partitions on reasonably fast machines
compress client fast
priority medium
}
define interface local {
comment a local disk
use 1000 kbps
}
define interface le0 {
comment 10 Mbps ethernet
use 400 kbps
}
[EMAIL PROTECTED]:/etc/amanda/DailySet1
Thanks for any suggestions on what's happening, and how to fix it. Please let me know
if there's some other diagnostic I should run to further define this problem.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Re: Troubleshooting a slowdown problem?
Eric and Frank, thank you very much for your detailed analysis of my problem. I just noticed on the most recent amstatus I ran that centernet:sda5 completed, and admin:sda3 is now dumping to tape. I've pasted in the most recent amstatus to the end of this note. I guess the reason that it says just dumping to tape rather than centernet's dumping 1332992k ( 73.56%) (2:02:34) is that admin is the tapehost itself. The holding disks on the tapehost are large, I thought: [EMAIL PROTECTED]:~ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda3 7.6G 5.2G 2.0G 72% / /dev/sda1 22M 3.4M 17M 16% /boot /dev/sdb1 8.3G 753M 7.1G 10% /var/amanda #This is hd1 (holding disk 1) /dev/sdc1 33G 4.9G 26G 16% /dumps2 # and this is hd2 shmfs1009M 0 1009M 0% /dev/shm [EMAIL PROTECTED]:~ They don't seem to be in use at this late stage of this backup: [EMAIL PROTECTED]:/dumps2/amanda du -sxh . /var/amanda/ 8.0k. 12k /var/amanda [EMAIL PROTECTED]:/dumps2/amanda Centernet is a low-volume web server, primarily. Even while running the backup, the load was less than 2. It's a 600MHz dual Pentium Dell PowerEdge 2450 with 256MB, 100MHz RAM. The tapehost, in contrast, right now has a load of almost 4: [EMAIL PROTECTED]:/dumps2/amanda uptime 4:24pm up 1 day, 23:30, 1 user, load average: 3.77, 3.71, 3.57 [EMAIL PROTECTED]:/dumps2/amanda There's no firewall between centernet and the tapehost, admin. Both are inside our firewall. The network is switched 100Mbps Ethernet. Here's a ps list of the amanda jobs currently running on the tapehost: [EMAIL PROTECTED]:/dumps2/amanda ps aux|grep amanda amanda4342 0.0 0.2 2220 1044 ?SJun16 0:00 /bin/sh -c /usr/local/sbin/amdump DailySet1 /usr/bin/mt -f /dev/nst0 offline amanda4346 0.0 0.2 2228 1104 ?SJun16 0:00 /bin/sh /usr/local/sbin/amdump DailySet1 amanda4381 0.0 0.2 2204 1080 ?SJun16 0:02 /usr/local/libexec/driver DailySet1 amanda4382 0.1 0.3 2780 1600 ?SJun16 2:16 taper DailySet1 amanda4383 0.4 0.2 2492 1216 ?SJun16 5:12 dumper0 DailySet1 amanda4384 0.0 0.2 2488 1208 ?SJun16 1:07 dumper1 DailySet1 amanda4385 0.0 0.2 2488 1208 ?SJun16 0:28 dumper2 DailySet1 amanda4386 0.0 0.1 2272 940 ?SJun16 0:00 dumper3 DailySet1 amanda4387 0.0 0.1 2272 940 ?SJun16 0:00 dumper4 DailySet1 amanda4388 0.1 0.2 2808 1536 ?DJun16 1:50 taper DailySet1 amanda4389 0.0 0.1 2272 940 ?SJun16 0:00 dumper5 DailySet1 amanda4390 0.0 0.1 2272 940 ?SJun16 0:00 dumper6 DailySet1 amanda4391 0.0 0.1 2272 940 ?SJun16 0:00 dumper7 DailySet1 amanda7185 0.0 0.1 2012 916 ?S15:52 0:00 /usr/local/libexec/sendbackup amanda7187 57.4 0.1 1612 684 ?S15:52 24:33 /usr/bin/gzip --fast amanda7188 0.1 0.2 2348 1512 ?S15:52 0:03 dump 0usf 1048576 - /dev/sda3 amanda7189 0.7 0.3 2440 1640 ?S15:53 0:19 dump 0usf 1048576 - /dev/sda3 amanda7190 1.0 0.2 2348 1504 ?S15:53 0:27 dump 0usf 1048576 - /dev/sda3 amanda7191 1.1 0.2 2348 1504 ?S15:53 0:28 dump 0usf 1048576 - /dev/sda3 amanda7192 1.0 0.2 2348 1504 ?S15:53 0:27 dump 0usf 1048576 - /dev/sda3 amanda7248 0.0 0.1 2064 924 pts/0S16:07 0:00 su - amanda amanda7249 0.0 0.2 2612 1508 pts/0S16:07 0:00 -bash amanda7335 0.0 0.2 2440 1504 pts/0R16:35 0:00 ps aux amanda7336 0.0 0.1 1540 576 pts/0S16:35 0:00 grep amanda [EMAIL PROTECTED]:/dumps2/amanda I'll send in the daily report as soon as I receive it. Normally, I would have interrupted amanda around 2:00pm by just killing all the amanda jobs on admin and running amcleanup. Then, I would put the next tape in and run amflush. This would complete before I needed to put the next tape in for the nightly run and go home. Tonight, I'll just let it run out. In addition, there's a thunderstorm rolling through Baltimore right now and all the lights are flickering. All the servers are on a UPS, but my workstation isn't. The partitions on admin like admin://db/c$ are actually Samba shares from an NT host. Thanks, again, for all your suggestions. I won't make any changes right now, until you've had a chance to look at the daily report. I appreciate all your help. It still hasn't ended and it's 5:03 and I'm hungry and tired, so I'm going home. I'll talk with you all again tomorrow. -Kevin Zembower [EMAIL PROTECTED]:/dumps2/amanda amstatus DailySet1 Using /var/log/amanda/DailySet1/amdump from Wed Jun 16 20:00:00 EDT 2004 admin://db/c$ 0 462720k finished (20:56:41) admin://db/e
Re: Troubleshooting a slowdown problem?
Ohh, it ended just as I pressed 'send.' Here's the daily report:
These dumps were to tape DailySet104.
The next tape Amanda expects to use is: DailySet105.
FAILURE AND STRANGE DUMP SUMMARY:
admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
admin //db/e$ lev 1 STRANGE
admin //db/f$ lev 1 STRANGE
admin //db/c$ lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min)21:03
Dump Time (hrs:min) 29:18 28:55 0:23
Output Size (meg) 10446.5 7946.7 2499.8
Original Size (meg) 15747.413247.4 2500.0
Avg Compressed Size (%)58.5 58.5 23.5 (level:#disks ...)
Filesystems Dumped 17 13 4 (1:4)
Avg Dump Rate (k/s) 101.4 78.2 1882.1
Tape Time (hrs:min)2:52 2:27 0:25
Tape Size (meg) 10446.7 7946.9 2499.8
Tape Used (%) 90.3 68.7 21.6 (level:#disks ...)
Filesystems Taped17 13 4 (1:4)
Avg Tp Write Rate (k/s) 1038.9 922.9 1730.4
USAGE BY TAPE:
Label Time Size %Nb
DailySet104 2:52 10446.7 90.317
FAILED AND STRANGE DUMP DETAILS:
/-- admin //db/f$/inetsrv/webpub/images lev 1 STRANGE
sendbackup: start [admin://db/f$/inetsrv/webpub/images level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4428 from pid 4428)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 5 files and directories
| Total bytes written: 22528
sendbackup: size 22
sendbackup: end
\
/-- admin //db/e$ lev 1 STRANGE
sendbackup: start [admin://db/e$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4462 from pid 4462)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 9 files and directories
| Total bytes written: 1536
sendbackup: size 2
sendbackup: end
\
/-- admin //db/f$ lev 1 STRANGE
sendbackup: start [admin://db/f$ level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4482 from pid 4482)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
| tar: dumped 215 files and directories
| Total bytes written: 2620979200
sendbackup: size 2559550
sendbackup: end
\
/-- admin //db/c$ lev 0 STRANGE
sendbackup: start [admin://db/c$ level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
? INFO: Debug class all level = 1 (pid 4486 from pid 4486)
| added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\system
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\software.LOG
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\default.LOG
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SECURITY.LOG
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SYSTEM.ALT
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM
(\WINNT\system32\config\)
? ERRDOS - ERRbadshare opening remote file \WINNT\system32\config\SAM.LOG
(\WINNT\system32\config\)
? ERRDOS - ERRnoaccess opening remote file \pagefile.sys (\)
| tar: dumped 5941 files and directories
| Total bytes written: 470870016
sendbackup: size 459834
sendbackup: end
\
NOTES:
planner: Last full dump of admin://db/f$ on tape DailySet105 overwritten in 1 run.
planner: admin //db/f$ 20040616 0 [dump larger than tape, 12838742 KB, full dump
delayed]
planner: Full dump of centernet:sda2 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda2 promoted from 1 day ahead.
planner: Full dump of admin:sdb1 promoted from 2 days ahead.
planner: Full dump of mailinglists:hda7 promoted from 1 day ahead.
planner: Full dump of centernet:sda9 promoted from 2 days ahead.
planner: Full dump of admin://db/c$ promoted from 1 day ahead.
planner: Full dump of mailinglists:hda1 promoted from 2 days ahead.
planner: Full dump of centernet:sda3 promoted from 2 days ahead.
Dump larger than tape problem
I'm struggling to solve a dump larger than tape problem, and not making much progress. I'm asking for suggestions and troubleshooting techniques. I'm trying to back up the Samba share admin//db/f$. I've broken it up into two sections: [EMAIL PROTECTED]:~ amadmin DailySet1 disklist admin //db/f$/ line 82: host admin: interface default disk //db/f$: program GNUTAR exclude file ./inetsrv/webpub/images/ priority 1 dumpcycle 3 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record YES index NO skip-incr NO skip-full NO line 83: host admin: interface default disk //db/f$/inetsrv/webpub/images: program GNUTAR priority 1 dumpcycle 3 maxdumps 1 maxpromoteday 1 strategy STANDARD compress NONE auth BSD kencrypt NO holdingdisk YES record YES index NO skip-incr NO skip-full NO [EMAIL PROTECTED]:~ I get this error when backing it up to a DDS-3 tape, which should hold 11.5G, according to a tapetest run: NOTES: planner: admin //db/f$ 20030915 0 [dump larger than tape, 12101907 KB, full dump delayed] But, each of the sections is less than 11G: ( Total size of //db/f$:) [EMAIL PROTECTED]:/etc/amanda/DailySet1 smbclient //db/f$ -U amanda%CiScO -Tc /dev/null INFO: Debug class all level = 1 (pid 16901 from pid 16901) added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 Output is /dev/null, assuming dry_runDomain=[DBWG] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] directory \inetsrv\ directory \inetsrv\ftp\ snip directory \temp\ tar: dumped 35364 files and directories Total bytes written: 12408697856 [EMAIL PROTECTED]:/etc/amanda/DailySet1 (Size of just /inetsrv/webpub/images directory tree:) [EMAIL PROTECTED]:/etc/amanda/DailySet1 smbclient //db/f$ -U amanda%CiScO -TcX /dev/null /inetsrv/webpub/images INFO: Debug class all level = 1 (pid 16904 from pid 16904) added interface ip=172.16.2.7 bcast=172.16.255.255 nmask=255.255.0.0 Output is /dev/null, assuming dry_runDomain=[DBWG] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] directory \inetsrv\ directory \inetsrv\ftp\ snip directory \temp\ tar: dumped 1359 files and directories Total bytes written: 5436378112 [EMAIL PROTECTED]:/etc/amanda/DailySet1 Therefore, 12.4G minus 5.4G is 7G. It's like amanda is not taking into account the excluded directories when making the size estimate, and then giving up on the level 0 backup because it seems too big. Here's the info output, if it's helpful: [EMAIL PROTECTED]:/etc/amanda/DailySet1 amadmin DailySet1 info admin //db/f$/ Current info for admin //db/f$: Stats: dump rates (kps), Full: 2993.0, 3469.0, 1124.0 Incremental: 4738.0, 4651.0, 4646.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20030827 DailySet11215 8426319 8443840 2821 1 20030915 DailySet12615 4895256 4895330 1033 Current info for admin //db/f$/inetsrv/webpub/images: Stats: dump rates (kps), Full: 2661.0, 2785.0, -1.0 Incremental: 230.0, 5.0, 21.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20030915 DailySet12616 6809105 6826070 2565 [EMAIL PROTECTED]:/etc/amanda/DailySet1 Any suggestions on changes or procedures to overcome this problem? I'm getting desperate; it's just been making level 1 backups for a week now. Thanks for all your help and suggestions. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Dump larger than tape problem
Eric, thanks for your response. It does seem to me that amanda is backing up correctly the sub-share //db/f$/inetsrv/webpub/images, because of these lines in the info output: Current info for admin //db/f$/inetsrv/webpub/images: Stats: dump rates (kps), Full: 2661.0, 2785.0, -1.0 Incremental: 230.0, 5.0, 21.0 compressed size, Full: -100.0%,-100.0%,-100.0% Incremental: -100.0%,-100.0%,-100.0% Dumps: lev datestmp tape file origK compK secs 0 20030915 DailySet12616 6809105 6826070 2565 It just doesn't seem to ignore the exclude file for the full-share backup. -Kevin eric a. Farris [EMAIL PROTECTED] 09/17/03 10:59AM On Wed, Sep 17, 2003 at 10:41:28AM -0400, KEVIN ZEMBOWER wrote: I have had similar problems, and what i've found is that the smallest unit that amanda will back up through samba is a *share*, and specifying individual directories (disk //server/share/dir1) is fruitless. Can someone confirm this? Is this a limitation of Samba, or Amanda? -- eric a. Farris http://eafarris.al.umces.edu/ Systems Administrator UMCES Appalachian Laboratory http://www.al.umces.edu/
Re: not secure port
Steve, I had this exact problem. The problem is that the way NAT is done is to choose an arbitrary port number and associate it with an IP inside the NAT. Search the archive of this list for Amanda through translated addresses where Pedro Caria shared with me a patch to remove the port check from amanda. This could work, but I never tried it. I just gave up and created two separate backup systems. Search also for Amanda and firewall This was another thread that I started in which folks gave useful suggestions. Hope this helps. Let me know if I can help in any other way. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 Steve Bertrand [EMAIL PROTECTED] 12/12/02 09:01AM Hi there. I have a problem for which I have done research on using google, mailing lists and other resourses, but have gotten no definitive answer to date. If someone could help me I would be ever greatful. I have amanda set up on FreeBSD, which was working great behind a Linksys NAT gateway, pulling backups from several locations on the Internet. I have since relocated my amanda box to a different physical location, and it is now behind a Netopia nat gateway. The internal IP address of the box has changed, as well as the external IP of the nat gateway. I have updated .amandahosts on all machines accordingly, but now I get the following on all of my remote machines I am backing up: ERROR: svr3: [host netopia-external-ip.domain.com : port 64559 not secure] I rebuilt amanda with the following: --with-tcpports=1500,2000 --with-udpports=800,900 with no luck. Could someone please advise. Tks, Steve Bertrand
Debian amanda: changing backup operator?
I'm trying to get the Debian distribution of amanda to work with my compiled-from-scratch version on the tapehost. I know that the general advice of this group is to ignore the various distribution versions and compile from scratch, but I like the idea of keeping a host within it's package maintenance system, for the ease of updating. The Debian version was compiled with the backup operator at backup. I compiled the tapehost and many of my clients with amanda as the backup operator. With amanda in both the /home/amanda/.amandahosts lists on the tapehost and client, I get this message in the debug file: bsd security: remote host admin.jhuccp.org user amanda local user backup check failed: [access as backup not allowed from [EMAIL PROTECTED]] amandahostsauth failed I've also tried all the combinations of amanda and backup in both the tapehost and clients .amandahosts files. All return the same error. Is there an easy solution, short of recompiling amanda? I thought the purpose of putting the backup operator with the client's hostname in the tapehost's .amandahosts file was to deal with this exact situation. I'd normally check the archives for this, as I'm pretty sure this is a FAQ, but the www.amanda.org site seems to be down, and I'm anxious for a solution. Thanks for your time, help and patience. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Never mind: Debian amanda: changing backup operator?
Hope nobody put much time into this. Once I discovered that the backup user's home directory is /var/backups, and that /var/backups/.amandahosts is aliased to /etc/amandahosts, when I changed the entry in /etc/amandahosts to the proper tapehost hostname and the backup name that the tapehost was compiled with, everything seemed to work. Thanks for your patience. -Kevin I'm trying to get the Debian distribution of amanda to work with my compiled-from-scratch version on the tapehost. I know that the general advice of this group is to ignore the various distribution versions and compile from scratch, but I like the idea of keeping a host within it's package maintenance system, for the ease of updating. The Debian version was compiled with the backup operator at backup. I compiled the tapehost and many of my clients with amanda as the backup operator. With amanda in both the /home/amanda/.amandahosts lists on the tapehost and client, I get this message in the debug file: bsd security: remote host admin.jhuccp.org user amanda local user backup check failed: [access as backup not allowed from [EMAIL PROTECTED]] amandahostsauth failed I've also tried all the combinations of amanda and backup in both the tapehost and clients .amandahosts files. All return the same error. Is there an easy solution, short of recompiling amanda? I thought the purpose of putting the backup operator with the client's hostname in the tapehost's .amandahosts file was to deal with this exact situation. I'd normally check the archives for this, as I'm pretty sure this is a FAQ, but the www.amanda.org site seems to be down, and I'm anxious for a solution. Thanks for your time, help and patience. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: sites using amanda - possible survey
On 25-Jan-2002, I started a thread with the subject Who uses Amanda? I got many answers up through 30-Jan. One of the most comprehensive came from John Jackson: = There are currently 1187 addresses on the amanda-users mailing list, and 561 on amanda-hackers. Running that all through uniq (and some other Perl magic), I came up with 1257 domains represented. Some caveats about that number. Not all sites running Amanda subscribe to the mailing lists, but not everybody subscribed to the list runs Amanda. Also, some of the addresses are clearly internal mailing lists, so the number of people who actually get the E-mail is certainly higher. Looking through the list, paying particular attention to .com's (since they are so much more important the rest of us peons :-), I see several names I recognize right away: 3com.com (3com) adp.com (ADP) attbi.com (ATT) bbn.com (BBN) boeing.com(Boeing) corning.com (Corning) cypress.com (Cypress) daimlerchrysler.com (Chysler) dell.com (Dell) fedex.com (Federal Express) ge.com(General Electric) goodyear.com (GoodYear) harris.com(Harris) honeywell.com (Honeywell) hp.com(Hewlitt-Packard) ibm.com (IBM) informix.com (Informix) kodak.com (Kodak) mot.com (Motorola) nokia.com (Nokia) nsc.com (National Semiconductor) oracle.com(Oracle) philips.com (Phillips) redhat.com(Red Hat) ricoh.com (Ricoh) siemens.com (Siemans) sun.com (Sun) trw.com (TRW) valinux.com (VA Linux) xerox.com (Xerox) I'm sure there's a few billion dollars of worth floating around there, and I only looked at the U.S. .com entries. There are almost 500 international entries and another hundred .edu's (and if you don't think universities are in it for the money ... :-). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] = You should be able to search the archives with this specific subject and find all the responses. Let me know if I can help in any way. -Kevin Zembower Toni Schlichting [EMAIL PROTECTED] 08/26/02 03:59PM Meanwhile I prepared a list of projects in which Amanda was used. As F-O-M doesn't provide much information I followed a recommendation of Dietmar Goldbeck who suggested to search google like this: http://www.google.de/search?num=50hl=enie=UTF-8oe=UTF-8q=amanda+datensicherung I exchanged the term datensicherung with backup and ended up with a huge number of hits. Then I searched the list for entries which gave a strong indication like this one: http://leda.law.harvard.edu/leda/manual/install/ Where I could find the following statement: At the LII we use and like the Amanda backup software This finally lead to an entry in my list. What do you think about the idea to contact all the admins who placed those nice statements on the web-sites, to make them enter their project into F-O-M? Best Regards Toni Greg A. Woods wrote: [ On Sunday, August 25, 2002 at 12:54:22 (-0500), Brandon D. Valentine wrote: ] Subject: Re: sites using amanda - possible survey On Sun, 25 Aug 2002, Jon LaBadie wrote: I've not seen a survey done in this mailing list, but I wonder if one would be appropriate to get a reasonable answer to this question. Then we could put a as of date XYZ, amanda was known to be in use in these organizations into the F-O-M. I did this several months ago: http://amanda.sourceforge.net/fom-serve/cache/319.html
Updating to SuSE 8.0 breaks amanda
From the for-what-it's-worth dept: When I updated two of my SuSE 7.2 systems to 8.0, the amanda client no longer worked. These were systems which I compiled and customized amanda from source code on. When I ran /var/lib/amandad manually, I got a message that libreadline 4.2.0 couldn't be found. When I ran rpm -q readline my version was something like readline 2.?. I went to the SuSE ftp site and downloaded the package readline-4.2-47.i386.rpm (for my machine) and updated readline with the command rpm -Uv readline-4.2-47.i386.rpm'. This seems to have fixed the problem. Running amcheck on the tapehost no longer causes an error on these two amanda clients. Don't know why this works, or why upgrading from 7.2 to 8.0 should break it, but it's working now and I'm off to put out another fire. I'll write back to this list if the actual backup of these two hosts fails tonight. -Kevin Zembower
Re: How to determine cause of Amanda slowdown?
Well, so much for the NIC and switch causing the amanda slowdown. I changed the settings on my NIC last night before the amanda run to 100baseT-FD. However, the dump is still running now, 15 hours later. I'm going to examining the switch shortly to see if there were many errors or collisions. Here's what amstatus said a few minutes ago: amanda@admin:~ amstatus DailySet1 Using /var/log/amanda/DailySet1/amdump from Thu Aug 8 18:00:00 EDT 2002 admin://db/c$1 380k finished (18:14:30) admin://db/e$1 10k finished (18:13:21) admin://db/f$0 7066846k wait for dumping admin:sda1 1 10k finished (18:13:37) admin:sda3 13085k wait for dumping admin:sdb1 03970k finished (18:13:54) centernet:sda1 02975k finished (18:16:12) centernet:sda3 0 1564325k finished (8:22:23) centernet:sdb1 11581k finished (18:14:42) centernet:sdb2 0 70452k finished (18:52:25) centernet:sdc1 1 1k finished (18:13:22) cgi:hda1 02294k finished (18:13:56) cgi:hda3 0 604189k finished (8:39:55) kzlaptop:hda504181k finished (18:16:44) kzlaptop:hda711926k finished (18:16:16) mailinglists:hda10 943k finished (18:15:37) mailinglists:hda217725k finished (18:18:42) mailinglists:hda71 41k finished (18:15:24) virtual:hda1 0 944k finished (18:13:35) virtual:hda3 0 1432404k writing to tape (8:57:43) www2:sda10 0 [Request to www2 timed out.] www2:sda11 0 [Request to www2 timed out.] www2:sda50 [Request to www2 timed out.] www2:sda70 [Request to www2 timed out.] www2:sda80 [Request to www2 timed out.] www2:sda90 [Request to www2 timed out.] SUMMARY part real estimated size size partition : 26 estimated : 0 0k failed : 6 0k ( 0.00%) wait for dumping: 27069931k ( 0.00%) dumping to tape : 0 0k ( 0.00%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 18 3698351k 4633924k ( 79.81%) ( 0.00%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 1 1432404k 1342192k (106.72%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 17 2265947k 3291732k ( 68.84%) ( 0.00%) 8 dumpers idle : no-diskspace taper writing, tapeq: 0 network free kps: 2600 holding space : 2062091k ( 59.01%) dumper0 busy : 14:14:54 ( 96.67%) dumper1 busy : 13:38:37 ( 92.57%) dumper2 busy : 0:05:06 ( 0.58%) dumper3 busy : 14:44:22 (100.00%) dumper4 busy : 0:03:14 ( 0.37%) dumper5 busy : 0:00:59 ( 0.11%) taper busy : 0:42:07 ( 4.76%) 0 dumpers busy : 0:00:00 ( 0.00%) 1 dumper busy : 0:28:59 ( 3.28%)no-bandwidth: 0:28:59 (100.00%) 2 dumpers busy : 0:36:32 ( 4.13%)no-bandwidth: 0:36:32 (100.00%) 3 dumpers busy : 13:33:43 ( 92.01%)no-bandwidth: 13:33:42 (100.00%) 4 dumpers busy : 0:02:06 ( 0.24%)no-bandwidth: 0:01:54 ( 90.50%) start-wait: 0:00:12 ( 9.50%) 5 dumpers busy : 0:02:30 ( 0.28%)no-bandwidth: 0:02:03 ( 82.11%) client-constrained: 0:00:25 ( 17.09%) start-wait: 0:00:01 ( 0.80%) 6 dumpers busy : 0:00:30 ( 0.06%)no-diskspace: 0:00:15 ( 49.47%) no-bandwidth: 0:00:12 ( 40.64%) client-constrained: 0:00:02 ( 6.82%) amanda@admin:~ In the first section, the admin://db/f$ is a samba connection to a Windows NT host through the tapebackup host. The F: drive is primarily one huge database file. The admin:sda3 is the root directory on the tapebackup host itself. I should have commented out www2, since I know it's a dead host. What's the meaning of this line in the second section: 8 dumpers idle : no-diskspace Is this an error message? Should I try to allocate more disk space to the dump disk? Do the last lines about 1-6 dumpers busy, due to no-bandwidth indicate that I need to increase the netusage? I currently have netusage 1200 Kbps # maximum net bandwidth for Amanda, in KB
Re: How to determine cause of Amanda slowdown?
Joshua, thank you very much. This is exactly what I was thinking of. I used an earlier version, mii-tool, which looks like it's been upgraded to mii-diag. Using this, I found that the NIC had negotiated 100baseT-HD rather than FD. I then used this tool to force the connection to 100baseT-FD. Oddly enough, the mii-diag still reported that the NIC thought that the 'link partner' was 100baseT-HD. However, no errors were showing up on the switch's diagnostics. Paul also reported problems with Cisco switches and NICs that auto-negotiate. My network engineer here told me to not use auto-negotiation, but couldn't explain why, so I just ignored it. I'll let folks know tomorrow whether this speeded things up or not. Thanks, again, for all your help. -Kevin Joshua Baker-LePain [EMAIL PROTECTED] 08/08/02 12:32PM On Thu, 8 Aug 2002 at 12:15pm, KEVIN ZEMBOWER wrote admin:/proc/net # ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:90:27:B6:FB:E7 inet addr:172.16.2.7 Bcast:172.16.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:259376827 errors:0 dropped:0 overruns:0 frame:0 TX packets:188989102 errors:0 dropped:0 overruns:0 carrier:65070 collisions:54220248 txqueuelen:100 RX bytes:2574728265 (2455.4 Mb) TX bytes:2729800656 (2603.3 Mb) This is the system on the 100Base-T line connected directly to a Cisco switch, which should be set at full duplex. Does the fact that they're any collisions at all indicate that this is not working in full duplex mode? The collisions are 21% of the number of RX packets, and 28% of the TX packets. Are these numbers excessive? Yes. You shouldn't have collisions. At one time I knew of a program or command that you could run to display the settings of the NIC, like auto-negotiate and so forth. For the life of me I can remember it now. Any suggestions for determining this information? It depends on the NIC. Don Becker has diagnostic tools for all sorts of NICs: http://www.scyld.com/diag/index.html -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda and firewall
Wow, you and I are at almost the exact same place with the same problem. I too am getting errors about port numbers that I didn't set up in the configuration, when I compiled amanda. I've been assuming that my firewall was translating port addresses in addition to IP addresses, but this doesn't seem possible or workable. For what it's worth, I compiled both the tapeserver and client copies of amanda with: ./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948 --with-user=amanda --with-group=disk --with-portrange=10084,10100 --without-server For the tapeserver. I left out the --without-server. The errors I was getting referred to the 4 range (Sorry, don't have an exact copy. Will try to generate one tomorrow.). We use an Elron firewall here. Odd that we're both JHU, too. -Kevin Zembower Nevin Kapur [EMAIL PROTECTED] 01/15/02 04:15PM I'm having some trouble setting up an Amanda client sitting in a DMZ of a firewall to talk to an Amanda server sittin inside a firewall. I've tried to follow the answer in the FAQ and also read the various posts on amanda-users. However, I can't get it to work and some questions till linger: 1. When the docs say pass --with-(udp)portrange=xxx,yyy to configure, which configure are they talking about? The client or the server? 2. In John R. Jackon's post Use of UDP/TCP ports in Amanda..., in the secition titles Firewalls and NAT, it says Just pick user UDP and TCP port ranges and build Amanda with them... Again, is this on the client side or the server side? Or both? 3. I've compiled Amanda with --with-portrange=4711,4715 --with-udpportrange=850,854 on both client and server side, but when I run amcheck, I get errors like: ERROR: xxx: [host : port 7062 not secure] where xxx is the name of the machine in the DMZ that I'm trying to back up and is the name of our firewall/router, not the server that sits inside it. I hope I am being clear. TIA -Nevin
Re: Amanda through translated addresses
I haven't been paying attention to this whole thread, but thought I'd throw my two cents in. I was never able to get amanda to work through a firewall using NAT. The way NAT works in the Elron Commander firewall, and most other ones, I think, is by arbitrarily reassigning port numbers to keep track of which connection on the inside corresponds to which communication on the outside. Example: Amanda on host tapehost talks to host X from port 932/UDP (I'm making this up from my setup). Host X responds correctly, because it was addressed from the proper privileged (1024) port. Now, amanda on host tapehost wants to talk to host X from port 932/UDP, but the request gets sent to the firewall. The firewall assigns a random port, in the unprivileged range (1024), let's say 10080. It records in it's lookup table that packets from tapehost are assigned to port 10800. In most applications, this would be fine, as the recipient would send the packets back to the firewall at port 10080, and the firewall would match port 10080 with tapehost and send the packet in to it. However, with amanda, when host X gets the packet from port 10080, it rejects it with an error message like Unprivileged port To diagnosis this, I used a combination of netcat and tcpdump, on both the sender and recipient. I was never able to overcome this, because the Elron firewall software can't not translate the port, as far as I and our Information Services group could tell. Since the original poster didn't mention this error message at all, this explanation may not relate to his problem. Sorry if this doesn't apply. If it does, and you have further questions, please write. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
SOLVED: Newbie: Can't get amanda user to work
Joshua WINS THE PRIZE! The home directory in /etc/passwd for amanda was /var/lib/amanda. When I changed it to /home/amanda, it worked great. For those of you interested, here's the /home/amanda/.amandahosts file that's working (with two additional hosts added and working): admin:/home/amanda # cat .amandahosts # admin:/home/amanda/.amandahosts created by Kevin Zembower on 11-Dec-2001 admin.jhuccp.orgamanda virtual.jhuccp.org amanda centernet.jhuccp.orgamanda admin:/home/amanda # It's still puzzling to me why the .amandahosts file, with the two additional hosts, was being recognized in /home/amanda, but still giving me the error with the tapeserver host. Oh, well, I'm not going to spend too much time pondering it. Another question: does this mean I can completely delete /var/lib/amanda? The only thing in it currently is the .amandahost file. Thank you again, Joshua. If we're ever in the same city, I owe you a beer. -Kevin Zembower Joshua Baker-LePain [EMAIL PROTECTED] 12/11/01 12:00PM On Tue, 11 Dec 2001 at 10:02am, KEVIN ZEMBOWER wrote Thank you to all the generous folks who have given me suggestions. Unfortunately, I still can't get it to work. I still get the same error massage with [access as amanda not allowed from [EMAIL PROTECTED]]. Here's some clarification on my system. I'm trying to backup the tapeserver. My tape is on a machine called admin.jhuccp.org. The userID for both client and server is amanda, group is disk. I thought there was only one machine -- what do you mean for both client and server? I've tried all these variations in the /home/amanda/.amandahosts and /var/lib/amanda/.amandahosts files (one at a time; the comments are how I kept track of what I tried): admin:/home/amanda # cat .amandahosts #admin.jhuccp.org amanda.admin.jhuccp.org #admin amanda.admin.jhuccp.org admin [EMAIL PROTECTED] #admin amanda #admin.jhuccp.org [EMAIL PROTECTED] admin:/home/amanda # You still haven't hit the write one. The format is 'machinename user' So, /home/amanda/.amandahosts should include: admin.jhuccp.orgamanda Other questions -- are you sure that /home/amanda is the home directory of the amanda user? It's listed in /etc/passwd. As an aside, is it still necessary to have both /var/lib/amanda/.amandahosts and /home/amanda/.amandahosts files? Do they have to be the same? AFAIK, it never was necessary. The only .amandahosts you need resides in ~amanda. Any additional suggestions? What OS/distro are you using -- that's helpful info. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Problem solving error: amandad: dgram_send_addr:sendto(0.0.0.0.948) failed: Invalid argument
I need a hand trying to figure out where to start troubleshooting my Amanda problem. I had an Amanda system which worked fine, until I rebooted one of my clients. Now amcheck says this client times out. The first hint of trouble shows up in /tmp/amanda/amandad.?.debug: amandad: dgram_send_addr: sendto(0.0.0.0.948) failed: Invalid argument Making it this far indicates to me that amanda is listening correctly, therefore xinetd is working correctly. Seems to me that the lookup of the IP address of the host requesting the amcheck, the tapehost, is failing. I tried to check this on the client, but for some reason, it doesn't have nslookup or hosts loaded. It's my guess that amanda uses an internal routine which will still work, even if nslookup or hosts is not found on the host, but I'm not sure if this is correct. Any suggestions on what to check first on trying to solve this problem and get amanda back working on this client? Thanks for your time and help with this. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Amanda through translated addresses
I haven't been paying attention to this whole thread, but thought I'd throw my two cents in. I was never able to get amanda to work through a firewall using NAT. The way NAT works in the Elron Commander firewall, and most other ones, I think, is by arbitrarily reassigning port numbers to keep track of which connection on the inside corresponds to which communication on the outside. Example: Amanda on host tapehost talks to host X from port 932/UDP (I'm making this up from my setup). Host X responds correctly, because it was addressed from the proper privileged (1024) port. Now, amanda on host tapehost wants to talk to host X from port 932/UDP, but the request gets sent to the firewall. The firewall assigns a random port, in the unprivileged range (1024), let's say 10080. It records in it's lookup table that packets from tapehost are assigned to port 10800. In most applications, this would be fine, as the recipient would send the packets back to the firewall at port 10080, and the firewall would match port 10080 with tapehost and send the packet in to it. However, with amanda, when host X gets the packet from port 10080, it rejects it with an error message like Unprivileged port To diagnosis this, I used a combination of netcat and tcpdump, on both the sender and recipient. I was never able to overcome this, because the Elron firewall software can't not translate the port, as far as I and our Information Services group could tell. Since the original poster didn't mention this error message at all, this explanation may not relate to his problem. Sorry if this doesn't apply. If it does, and you have further questions, please write. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Restoring Samba files?
I just set up my first backup using Samba (my amanda setup's been working well since December). I'll know tonight if it completed successfully. I'm puzzled by a restore question. I've never implemented indexing, and don't use amrecover or amrestore. Instead, I just dd the file off the tape and pipe it to restore on the tapeserver, in a tmp directory, then ftp the file back where it belongs. This works fine for me, as I am practically the only user on my systems, and files very seldom need restoration. Will I be able to do this same procedure with files originally on the Windows (Samba) shares? In other words, will I be able to restore the file or directories into a tmp file on my Unix (Linux) tapeserver, then ftp it back to the PC where it came from? Will I have to use any different programs or systems? Will I lose any information (permissions, dates and times, etc.) this way, versus restoring with amrecover or amrestore? Thanks for your thoughts and suggestions on this. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Problems with Amanda through a firewall with NAT
I'm hoping someone can give me some advice on setting up Amanda with a
firewall and Network Address Translation.
My amanda system backs up hosts both inside and outside the firewall.
The clients's inside backup fine. I've never been able to get the ones
outside to pass the amcheck DailySet1 -c check:
amanda@admin:~ amcheck DailySet1 -c
Amanda Backup Client Hosts Check
WARNING: external: selfcheck request timed out. Host down?
WARNING: www: selfcheck request timed out. Host down?
WARNING: real: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.058 seconds, 3 problems found
(brought to you by Amanda 2.4.3b1)
amanda@admin:~
I compiled amanda, both on admin (inside the firewall tapeserver
host) and on www (outside the firewall amanda client) with this
configuration:
./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948
--with-user=amanda --with-group=disk
In my /home/amanda/.amandahosts file on admin, the tapeserver, I have:
www.jhuccp.org amanda
My /home/amanda/.amandahosts file on www is:
www:~ # cat /home/amanda/.amandahosts
162.129.225.189 amanda
www:~ #
162.129.225.189 is the IP address for the host admin. This host's
reverse lookup doesn't resolve to a domain name outside the firewall,
just an IP address.
I've run netcat on admin on ports 932/tcp and /udp and 10100/tcp and
/udp. Here's two samples of the output on each end. In the first, www
is sending on 932/tcp:
www:~ # netcat -v 162.129.225.189 932
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
(UNKNOWN) [162.129.225.189] 932 (?) open
ddd
punt!
www:~ #
admin:~ # netcat -v -l -p 932
listening on [any] 932 ...
connect to [172.16.2.7] from www.jhuccp.org [162.129.225.190] 35919
ddd
admin:~ #
Notice that NAT translates the IP address which www is sending to
(162.129.225.189) outside the firewall to 162.129.225.190, which is used
inside the firewall. I don't know why this is necessary. The guy
configuring the firewall assures me that it is. This then is resolved by
a DNS reverse lookup to www.jhuccp.org. The fact that the packets
('ddd') pass okay reassures me that it is working.
In this second example of using netcat, www is listening on port
10100/tcp:
admin:~ # netcat -v www 10100
www.jhuccp.org [162.129.225.190] 10100 (?) open
fff
punt!
admin:~ #
www:~ # netcat -v -l -p 10100
listening on [any] 10100 ...
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
connect to [162.129.225.190] from (UNKNOWN) [162.129.225.189] 41885
fff
www:~ #
Based on this, I think the firewall's passing the traffic and the NAT
is working properly.
Anyone have any further suggestions for things I can change or other
diagnostic methods I can use to fix this?
Thank you all very much for your time and thoughts. Have a happy and
safe New Year.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Amanda install reality check
For-what-it's-worth dept.: In the year that I've been a full-time Unix system administrator, I guess I've installed 40-50 different packages, mostly from source. Amanda was the second most time-consuming and difficult; only Xwindows was harder for me. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 gene [EMAIL PROTECTED] 02/06/02 01:49PM snip I seem to be really struggling to get this to work. I did think it would be easier than this ;-) /snip Gene
Alternative solutions to my firewall problems with amanda
I just noticed, from the reply to someone else's question on this list, the answers on http://amanda.sourceforge.net/fom-serve/cache/14.html offered by [EMAIL PROTECTED], to wit: It seems that there is another reason for this error-message [port not secure], too. In my case it was a problem with masqueraded connections. I could solve the problem in my case, by simply not using masquerading ;) but other solutions like port forwarding or by tunneling over ssh could solve the problem (with some luck). [EMAIL PROTECTED] Does anyone use either of these solutions, port forwarding or tunneling over ssh, and can give me some pointers on how to get started learning about them and applying them? I know these terms just as definitions, but have never tried to use port-forwarding. I use ssh all the time from my tapeserver backup host, out to my boxes outside the firewall. It works like a champ. Thanks to everyone on this list for their suggestions and patience with my problem. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Suggestion for next amanda: put tcpportrange in amadminversion output
One of the things which was disquieting to me while trying to troubleshoot my problems with TCP and UDP ports was the inability to check what options I had compiled with using amadmin conf version. I've pasted in the results of my system at the end of this message. It seemed like many other compile time definitions were listed in the defs section. I initially doubted whether I had compiled it right, because --with-udpportrange=932,948 and --with-tcpportrange=10080,10100 didn't appear. I believe that this section is output in some of the routine logging files, also. Just my suggestion. Wasn't sure if I could or should submit this to the amanda-dev list, since I don't subscribe to it. -Kevin Zembower amanda@admin:~ amadmin DailySet1 version build: VERSION=Amanda-2.4.3b1 BUILT_DATE=Fri Jan 4 11:18:53 EST 2002 BUILT_MACH=Linux admin 2.4.4-64GB-SMP #1 SMP Fri May 18 14:54:08 GMT 2001 i686 unknown CC=gcc paths: bindir=/usr/local/bin sbindir=/usr/local/sbin libexecdir=/usr/local/libexec mandir=/usr/local/man AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar COMPRESS_PATH=/usr/bin/gzip UNCOMPRESS_PATH=/usr/bin/gzip MAILER=/usr/bin/Mail listed_incr_dir=/usr/local/var/amanda/gnutar-lists defs: DEFAULT_SERVER=admin DEFAULT_CONFIG=DailySet1 DEFAULT_TAPE_SERVER=admin DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amanda@admin:~ - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Who uses Amanda?
Thank you, Scaglione, for a clever possible solution that I wouldn't have thought of on my own. -Kevin Zembower Scaglione Ermanno [EMAIL PROTECTED] 01/29/02 11:48AM On Fri, 25 Jan 2002, KEVIN ZEMBOWER wrote: - (This might seem like a stupid question to this group, but) I'm being - challenged by the folks who can't get my firewall setup to work with - Amanda that I should adopt a more industry-standard backup product. I solved my firewall problems using a cheap VPN over SSH, it is not fast but it works, this is a HOWTO for linux http://www.linuxdoc.org/HOWTO/VPN-HOWTO.html but it should work with any unix (i did it on solaris). Our tape server is behind a NAT so the VPN needs to be used just for the restores, hopefully not too often. I installed the script from the howto with some minor adaptations and told everyone that the VPN should be started before using amrecover and stopped after that. Ok I didnt actually tried a big restore over it but everyone is more confident now that they see amrecover working and can browse through the backups :-) There are certainly alternatives, both commercial and free to this solution, I choosed it because port 22 was already open on the firewall.
My firewall problems with amanda (long)
65535 932948 In On 932 948 1024 65535 Out Off I think what's needed is to make the Source and Destination ports the same in each line. However, when I make this suggestion to the firewall managers, they reply, A) We tried this and you told us it didn't work, and B) none of the examples in the manual show the Source and Destination ports the same, one set always has the limits of the non-privileged ports, so we won't try it because it couldn't be right. At this time, we're waiting to hear from the tech support folks at Elron to see if they suggest a method. In their manual, they say, Some applications can't be made to work with the CommandView firewall. I hope this isn't the case here. Thank you all for your interest. If anyone has any suggestions or questions, I'd love to hear them. When this problem gets resolved one way or the other, I'll report back to the list. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Who uses Amanda?
(This might seem like a stupid question to this group, but) I'm being challenged by the folks who can't get my firewall setup to work with Amanda that I should adopt a more industry-standard backup product. Hogwash. But, I would like to at least offer an answer. Anyone have any guesses how many institutions and individuals are using amanda? Anyone know, or want to self-disclose, some noteworthy institutions using amanda? If you think this would clog up the list too badly, email me privately at [EMAIL PROTECTED], and after a week or so, I'll compile a list and post it to the email list. Thanks for your patience. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Problem with amoverview: Bad interpreter?
I just noticed a problem this morning. When I run amoverview, I get: amanda@admin:~ amoverview DailySet1 bash: /usr/local/sbin/amoverview: bad interpreter: No such file or directory amanda@admin:~ I could have sworn I've run amoverview on this system before without problems. The listing doesn't seem to indicate that anything has changed with the file: -rwxr-xr-x1 amanda disk 4351 Jan 4 11:21 /usr/local/sbin/amoverview However, amcheck seems to work fine: amanda@admin:~ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/amanda: 5664532 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet106 label ok Server check took 20.453 seconds Amanda Backup Client Hosts Check Client check: 5 hosts checked in 0.065 seconds, 0 problems found (brought to you by Amanda 2.4.3b1) amanda@admin:~ I also got what looks like a normal backup off the system last night. I searched the archives for interpreter but got no hits. Anyone seen this problem before? Any suggestions for fixing it? Thanks for your thoughts and time. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Problem with amoverview: Bad interpreter?
Thank you so much, Paul. Yes, it was that simple. I did change a symlink for perl, but I just didn't realize that amoverview was a perl program until I looked at it. Thanks for your help. -Kevin Zembower Paul Bijnens [EMAIL PROTECTED] 01/24/02 10:40AM KEVIN ZEMBOWER wrote: I just noticed a problem this morning. When I run amoverview, I get: amanda@admin:~ amoverview DailySet1 bash: /usr/local/sbin/amoverview: bad interpreter: No such file or directory Somebody moved perl to another place, or simply renamed it (or removed it?) See the first line in amoverview. It looks like: #!/bin/perl at me, and it should point to the perl executable. -- 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 * ***
Does this amverify indicate problems?
Friends, with the recent posting indicating the need to check backup tapes, I recently ran amverify for the first time. Since I've been running amanda overall less than a month, I've never had to do a restore from the tapes. On the face of it, the amverify pasted in below looks disastrous. Since this is my first amverify, I have no experience reading and interpreting this report. Is this as bad as it looks? Would I be able to recover anything from these tapes? I know the true test is to try to recover something, which is what I'll do today. Thanks for your thoughts. -Kevin Zembower amanda@admin:~ amverify DailySet1 No tape changer... Tape device is /dev/nst0... Verify summary to root [EMAIL PROTECTED] Defects file is /tmp/amanda/amverify.10232/defects amverify DailySet1 Thu Jan 17 09:02:49 EST 2002 Using device /dev/nst0 Waiting for device to go ready... Rewinding... Processing label... Volume DailySet125, Date 20020116 Rewinding... Checked cgi.hda1.20020116.1 ** Error detected (centernet.sda1.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring centernet.sda1.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out ** Error detected (mailinglists.hda1.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring mailinglists.hda1.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out ** Error detected (admin.sda1.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring admin.sda1.20020116.1 amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out ** Error detected (admin.sdb1.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring admin.sdb1.20020116.1 amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out ** Error detected (centernet.sdb2.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring centernet.sdb2.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out ** Error detected (mailinglists.hda7.20020116.1) amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring mailinglists.hda7.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out Too many errors. Rewinding... Errors found: DailySet125 (centernet.sda1.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring centernet.sda1.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out DailySet125 (mailinglists.hda1.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring mailinglists.hda1.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out DailySet125 (admin.sda1.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring admin.sda1.20020116.1 amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out DailySet125 (admin.sdb1.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring admin.sdb1.20020116.1 amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out DailySet125 (centernet.sdb2.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring centernet.sdb2.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out DailySet125 (mailinglists.hda7.20020116.1): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: restoring mailinglists.hda7.20020116.1 gzip: stdin: unexpected end of file amrestore: 1: reached end of information /sbin/restore: Tape is not a dump tape 64+0 in 64+0 out amanda@admin:~ - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Tapetype when utilizing hardware compression
IIRC, the tapetype test uses random data, so hardware compress may (?)
actually increase the amount of the data.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Don Potter [EMAIL PROTECTED] 01/17/02 09:10AM
I ran the tapetype test to our tapedrive (ADIC DS9400D) using DLTTAPE
IV. I frontpaneled the compression so I expected at least 40 GB when
the tapetype was completed. But I only got about 17GB:
Command: tapetype -d /dev/rmt/0n
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 17587 mbytes
filemark 13 kbytes
speed 1011 kps
}
Then I ran it with software compression (/dev/rmt/0cn) and I only got
20 GB:
Command: tapetype -d /dev/rmt/0cn
define tapetype unknown-tapetype {
comment just produced by tapetype program
length 19565 mbytes
filemark 4 kbytes
speed 1101 kps
}
Both ways I would of expected close to double the native writes. Any
ideas why the compression would not of increased.
Any suggestions would be appreciated.
Don Potter
RE: [data write: File too large]
I see! said the blind carpenter, who picked up his hammer and saw. -My ninth grade science teacher, Brother Paul, a terrible punner. -Kevin Pedro Aguayo [EMAIL PROTECTED] 01/15/02 09:45AM Ahh! I see said the blind man. Pedro -Original Message- From: Adrian Reyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 9:24 AM To: Pedro Aguayo Cc: Rivera, Edwin; [EMAIL PROTECTED] Subject: Re: [data write: File too large] On Tue, Jan 15, 2002 at 09:14:33AM -0500, Pedro Aguayo wrote: But, I think Edwin doesn't have this problem, meaning he says he doesn't have a file larger than 2gb. I had none, either, but the filesystem was dumped into a file as a whole, leading to a huge file, same with tar. The problem only occurs as holding-disk is used. Continuously writing a stream of unlimited size to a tape is no problem, but as soon as you try to do this onto a filesytem, you run in whatever limits you have, mostly 2GB-limits on a single file. No holding-disk - no big file - no problem. (well, tape might have to stop more often because of interruption in data-flow) Regards, Adrian Reyer -- Adrian Reyer Fon: +49 (7 11) 2 85 19 05 LiHAS - Servicebuero SuttgartFax: +49 (7 11) 5 78 06 92 Adrian Reyer Joerg Henner GbR Mail: [EMAIL PROTECTED] Linux, Netzwerke, Consulting Support http://lihas.de/
Re: Amanda and firewall
Wow, you and I are at almost the exact same place with the same problem. I too am getting errors about port numbers that I didn't set up in the configuration, when I compiled amanda. I've been assuming that my firewall was translating port addresses in addition to IP addresses, but this doesn't seem possible or workable. For what it's worth, I compiled both the tapeserver and client copies of amanda with: ./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948 --with-user=amanda --with-group=disk --with-portrange=10084,10100 --without-server For the tapeserver. I left out the --without-server. The errors I was getting referred to the 4 range (Sorry, don't have an exact copy. Will try to generate one tomorrow.). We use an Elron firewall here. Odd that we're both JHU, too. -Kevin Zembower Nevin Kapur [EMAIL PROTECTED] 01/15/02 04:15PM I'm having some trouble setting up an Amanda client sitting in a DMZ of a firewall to talk to an Amanda server sittin inside a firewall. I've tried to follow the answer in the FAQ and also read the various posts on amanda-users. However, I can't get it to work and some questions till linger: 1. When the docs say pass --with-(udp)portrange=xxx,yyy to configure, which configure are they talking about? The client or the server? 2. In John R. Jackon's post Use of UDP/TCP ports in Amanda..., in the secition titles Firewalls and NAT, it says Just pick user UDP and TCP port ranges and build Amanda with them... Again, is this on the client side or the server side? Or both? 3. I've compiled Amanda with --with-portrange=4711,4715 --with-udpportrange=850,854 on both client and server side, but when I run amcheck, I get errors like: ERROR: xxx: [host : port 7062 not secure] where xxx is the name of the machine in the DMZ that I'm trying to back up and is the name of our firewall/router, not the server that sits inside it. I hope I am being clear. TIA -Nevin
Tapetype for Python with DDS-3 in Dell PowerEdge 2300
for what-it's-worth department:
Here's the tapetype I created from the output of running tapetype on
the built-in tape drive on my Dell PowerEdge 2300 tower server, using
DDS-3 tapes.
If there's any other information that I could provide to make this more
useful, please ask, and I'll be glad to send it in.
Hope this helps someone.
-Kevin Zembower
define tapetype Python-DDS3 {
# Created by Kevin Zembower on 10-Dec-2001 from data from tapetest
# for built-in tape drive on Dell PowerEdge 2300 server
# with hardware compression turned off
comment Dell Python with DDS-3 tapes, no h/w compression
length 11570 mbytes
filemark 0 kbytes
speed 1078 kps
}
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Tapetype for Python tape drive using DDS-2 tapes in DellPowerEdge 2450
for what-it's-worth department:
Pasted in below is the output of running tapetest on the built-in tape
drive on my Dell PowerEdge 2450 rack-mount server, using DDS-2 tapes. I
edited the definition for my system.
If there's any other information that I could provide to make this more
useful, please ask, and I'll be glad to send it in.
Hope this helps someone.
-Kevin Zembower
wrote 122625 32Kb blocks in 375 files in 4448 seconds (short write)
wrote 122413 32Kb blocks in 751 files in 4446 seconds (short write)
define tapetype Python-DDS2 {
#Created by Kevin Zembower on 4-Jan-2002 from data from tapetest
# for built-in tape drive on Dell PowerEdge 2450 server (www host)
# with hardware compression turned off
comment Dell Python with DDS-2 tapes, no h/w compression
length 3838 mbytes
filemark 18 kbytes
speed 881 kps
}
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Problems with Amanda through a firewall with NAT
Sorry if this is a duplicate. I can't remember seeing it on the listserv
output, and no one offered any suggestions, but it was over the
holidays. Any ideas of things I can try?
-Kevin Zembower
---
I'm hoping someone can give me some advice on setting up Amanda with a
firewall and Network Address Translation.
My amanda system backs up hosts both inside and outside the firewall.
The clients's inside backup fine. I've never been able to get the ones
outside to pass the amcheck DailySet1 -c check:
amanda@admin:~ amcheck DailySet1 -c
Amanda Backup Client Hosts Check
WARNING: external: selfcheck request timed out. Host down?
WARNING: www: selfcheck request timed out. Host down?
WARNING: real: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.058 seconds, 3 problems found
(brought to you by Amanda 2.4.3b1)
amanda@admin:~
I compiled amanda, both on admin (inside the firewall tapeserver
host) and on www (outside the firewall amanda client) with this
configuration:
./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948
--with-user=amanda --with-group=disk
In my /home/amanda/.amandahosts file on admin, the tapeserver, I have:
www.jhuccp.org amanda
My /home/amanda/.amandahosts file on www is:
www:~ # cat /home/amanda/.amandahosts
162.129.225.189 amanda
www:~ #
162.129.225.189 is the IP address for the host admin. This host's
reverse lookup doesn't resolve to a domain name outside the firewall,
just an IP address.
I've run netcat on admin on ports 932/tcp and /udp and 10100/tcp and
/udp. Here's two samples of the output on each end. In the first, www
is sending on 932/tcp:
www:~ # netcat -v 162.129.225.189 932
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
(UNKNOWN) [162.129.225.189] 932 (?) open
ddd
punt!
www:~ #
admin:~ # netcat -v -l -p 932
listening on [any] 932 ...
connect to [172.16.2.7] from www.jhuccp.org [162.129.225.190] 35919
ddd
admin:~ #
Notice that NAT translates the IP address which www is sending to
(162.129.225.189) outside the firewall to 162.129.225.190, which is used
inside the firewall. I don't know why this is necessary. The guy
configuring the firewall assures me that it is. This then is resolved by
a DNS reverse lookup to www.jhuccp.org. The fact that the packets
('ddd') pass okay reassures me that it is working.
In this second example of using netcat, www is listening on port
10100/tcp:
admin:~ # netcat -v www 10100
www.jhuccp.org [162.129.225.190] 10100 (?) open
fff
punt!
admin:~ #
www:~ # netcat -v -l -p 10100
listening on [any] 10100 ...
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
connect to [162.129.225.190] from (UNKNOWN) [162.129.225.189] 41885
fff
www:~ #
Based on this, I think the firewall's passing the traffic and the NAT
is working properly.
Anyone have any further suggestions for things I can change or other
diagnostic methods I can use to fix this?
Thank you all very much for your time and thoughts. Have a happy and
safe New Year.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
Problems with Amanda through a firewall with NAT
I'm hoping someone can give me some advice on setting up Amanda with a
firewall and Network Address Translation.
My amanda system backs up hosts both inside and outside the firewall.
The clients's inside backup fine. I've never been able to get the ones
outside to pass the amcheck DailySet1 -c check:
amanda@admin:~ amcheck DailySet1 -c
Amanda Backup Client Hosts Check
WARNING: external: selfcheck request timed out. Host down?
WARNING: www: selfcheck request timed out. Host down?
WARNING: real: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.058 seconds, 3 problems found
(brought to you by Amanda 2.4.3b1)
amanda@admin:~
I compiled amanda, both on admin (inside the firewall tapeserver
host) and on www (outside the firewall amanda client) with this
configuration:
./configure --with-tcpportrange=10084,10100 --with-udpportrange=932,948
--with-user=amanda --with-group=disk
In my /home/amanda/.amandahosts file on admin, the tapeserver, I have:
www.jhuccp.org amanda
My /home/amanda/.amandahosts file on www is:
www:~ # cat /home/amanda/.amandahosts
162.129.225.189 amanda
www:~ #
162.129.225.189 is the IP address for the host admin. This host's
reverse lookup doesn't resolve to a domain name outside the firewall,
just an IP address.
I've run netcat on admin on ports 932/tcp and /udp and 10100/tcp and
/udp. Here's two samples of the output on each end. In the first, www
is sending on 932/tcp:
www:~ # netcat -v 162.129.225.189 932
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
(UNKNOWN) [162.129.225.189] 932 (?) open
ddd
punt!
www:~ #
admin:~ # netcat -v -l -p 932
listening on [any] 932 ...
connect to [172.16.2.7] from www.jhuccp.org [162.129.225.190] 35919
ddd
admin:~ #
Notice that NAT translates the IP address which www is sending to
(162.129.225.189) outside the firewall to 162.129.225.190, which is used
inside the firewall. I don't know why this is necessary. The guy
configuring the firewall assures me that it is. This then is resolved by
a DNS reverse lookup to www.jhuccp.org. The fact that the packets
('ddd') pass okay reassures me that it is working.
In this second example of using netcat, www is listening on port
10100/tcp:
admin:~ # netcat -v www 10100
www.jhuccp.org [162.129.225.190] 10100 (?) open
fff
punt!
admin:~ #
www:~ # netcat -v -l -p 10100
listening on [any] 10100 ...
162.129.225.189: inverse host lookup failed: Unknown host : No such
file or directory
connect to [162.129.225.190] from (UNKNOWN) [162.129.225.189] 41885
fff
www:~ #
Based on this, I think the firewall's passing the traffic and the NAT
is working properly.
Anyone have any further suggestions for things I can change or other
diagnostic methods I can use to fix this?
Thank you all very much for your time and thoughts. Have a happy and
safe New Year.
-Kevin Zembower
-
E. Kevin Zembower
Unix Administrator
Johns Hopkins University/Center for Communications Programs
111 Market Place, Suite 310
Baltimore, MD 21202
410-659-6139
What to do about the holidays?
It just dawned on me that I won't be in the office next Monday or Tuesday. I have a backup cronned for M-F at 1800. My first idea of what to do is just to leave the system alone, let it backup to disk Monday and Tuesday, and first thing Wednesday, amflush the backup to tape. Is this okay to do? Is this what most folks are doing? I could also comment out the cron jobs for Monday and Tuesday easily enough. Would this be better? Thanks for your suggestions. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: What to do about the holidays?
Joshua, thank you for your advice. That's exactly what I'll do. -Kevin Zembower Joshua Baker-LePain [EMAIL PROTECTED] 12/19/01 11:29AM On Wed, 19 Dec 2001 at 10:55am, KEVIN ZEMBOWER wrote It just dawned on me that I won't be in the office next Monday or Tuesday. I have a backup cronned for M-F at 1800. My first idea of what to do is just to leave the system alone, let it backup to disk Monday and Tuesday, and first thing Wednesday, amflush the backup to tape. Is this okay to do? Is this what most folks are doing? I could also comment out the cron jobs for Monday and Tuesday easily enough. Would this be better? I do indeed just let amanda run and amflush when I get back. And I'll be out for a week. If you want any level 0s to get done, make sure you set reserve to something less than 100. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Need exact settings for firewall with amanda
I've been successful so far setting up Amanda to back up my hosts inside my firewall, where my tapeserver is also located. Now, I'm trying to set it up to also backup the hosts outside the firewall. Unfortunately, I don't control the firewall, I have to just tell the folks who do exactly what I need. So far, I've told them I need the following ports opened: 10080/udp 10082/tcp 10083/tcp I just noticed that, while these are the ports listed in the INSTALL document, the patch-system actually put these lines in my /etc/services (client only; no tape server): www:/tmp/amanda # grep amanda /etc/services amanda 10080/udp amanda 10080/tcp kamanda 10081/udp amandaidx 10082/tcp Is there a misprint in the INSTALL document? Should I also asked the firewall group to open port 10080/tcp? If anyone's ever done this (specify the firewall settings needed by amanda), could you let me know what you requested? Thanks for your help. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Newbie: Tape doesn't eject?
Thanks, Stephen, for sharing your experience with amanda with me. I'll add the eject to my crontab; that's a good idea. I suspect that what's confusing amanda in making my initial backup is the fact that I've still got running another, homebrew, backup system that's also writing to /etc/dumpdates. On the other hand, the report does say that the size of the backup of the two machines that worked is 3.5G, which might be close to a level 0 backup on these two machines. I'm still left with one question. Is it permissible to run more than one amdump in a day, even if tapes are changed between runs? Would this do anything positive, like push forward a more extensive dump that might be normally scheduled for the next day? Or, would amanda just see that not much has changed in the hour or two since the last dump, and not do much of anything? Thanks for your thoughts. -Kevin Zembower Stephen Walton [EMAIL PROTECTED] 12/12/01 12:44AM Hi, /tmp/amanda/sendsize.*.debug file, and this showed that I had a directory named /etc/amandates, instead of a file. I mad the same mistake. However, when my backup finished, the report noted that the tape was only 10% full, and it didn't eject. The 10% full number depends on timing of full dumps and so on. If you've set everything up right, then either amanda should have done a full dump of everything the first time out, or postponed some of them for later. I see everything from 10% to 99% full on my regular backups depending on how the mix of full incrementals works out. amdump does not eject a tape. In my crontab I have something like: 5 12 * * * /opt/amanda/sbin/amdump daily /bin/mt -t /dev/rmt/0m offl to get a tape eject when the backup is done. -- Stephen Walton, Professor of Physics and Astronomy, California State University, Northridge [EMAIL PROTECTED]
Re: Newbie: Can't get amanda user to work
Thank you to all the generous folks who have given me suggestions. Unfortunately, I still can't get it to work. I still get the same error massage with [access as amanda not allowed from [EMAIL PROTECTED]]. Here's some clarification on my system. I'm trying to backup the tapeserver. My tape is on a machine called admin.jhuccp.org. The userID for both client and server is amanda, group is disk. I've tried all these variations in the /home/amanda/.amandahosts and /var/lib/amanda/.amandahosts files (one at a time; the comments are how I kept track of what I tried): admin:/home/amanda # cat .amandahosts #admin.jhuccp.org amanda.admin.jhuccp.org #admin amanda.admin.jhuccp.org admin [EMAIL PROTECTED] #admin amanda #admin.jhuccp.org [EMAIL PROTECTED] admin:/home/amanda # Both files are owned by amanda:disk and have 0600 permissions. As an aside, is it still necessary to have both /var/lib/amanda/.amandahosts and /home/amanda/.amandahosts files? Do they have to be the same? My /etc/inetd.conf and /etc/services were patched by 'patch-system': admin:/home/amanda # grep amanda /etc/services amanda 10080/udp amanda 10080/tcp kamanda 10081/udp amandaidx 10082/tcp admin:/home/amanda # grep amanda /etc/inetd.conf # amanda backup server with indexing capabilities # amandaidx stream tcp nowait root /usr/lib/amanda/amindexd amindexd # amidxtape stream tcp nowait root /usr/lib/amanda/amidxtaped amidxtaped # amanda backup client # amandadgram udp waitamanda /usr/lib/amanda/amandad amandad amandadgram udp wait amanda /usr/local/libexec/amandad amandad amandaidx stream tcp nowait amanda /usr/local/libexec/amindexd amindexd amidxtape stream tcp nowait amanda /usr/local/libexec/amidxtaped amidxtaped admin:/home/amanda # Any additional suggestions? Thanks for continuing to think about this. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139 Ana Maria Escalante [EMAIL PROTECTED] 12/10/01 08:32PM Hi Kevin: I am not sure if I understood everything from your message, but it is not clear to me, which user will be doing the backups from the server (amanda is the default user) and whether your client machine is the same as your server. You must have a .amandahosts file in the client amanda home directory, that gives access to amanda user from the server machine. In my setup, my backup admin acount is amanda, my server is server.domain.mx and my client is client.domain.mx. I have an .amandahosts file in amanda s home directory in the client with the following line: server.domain.mxamanda You will also need an .amandahosts file in the server s amanda s home directory, with the client machines name and root as the authorized user, in order to recover from the clients, but that is another story. If you have a .rhosts file in your clients amanda s home directory, it must have this same line. I have heard about it :) Hope this helps. Good luck ... Ana Maria On Mon, 10 Dec 2001, KEVIN ZEMBOWER wrote: I'm trying to get my first setup of amanda working. Running amcheck gives me: admin:/home/amanda # su amanda -c /usr/local/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/amanda: 5807968 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sdb1: does not exist NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda1: does not exist NOTE: info dir /var/log/amanda/DailySet1/curinfo/admin/sda3: does not exist Server check took 16.516 seconds Amanda Backup Client Hosts Check ERROR: admin: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Client check: 1 host checked in 0.029 seconds, 1 problem found (brought to you by Amanda 2.4.3b1) admin:/home/amanda # Yet, I have a .amandahosts file with what I think are the proper contents and permissions: admin:/home/amanda # ll /home/amanda/.amandahosts -rw-r--r--1 amanda disk 30 Dec 10 16:36 /home/amanda/.amandahosts admin:/home/amanda # cat /home/amanda/.amandahosts admin [EMAIL PROTECTED] admin:/home/amanda # I'm stumped. I've tried or checked all the suggestions in the FAQ-a-matic for this topic. It's probably something simple, that I don't see because I'm new to amanda. Any suggestions? Thanks for your help. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
Re: Newbie: Can't get amanda user to work
Thank you for your clarifying question, Jon. Yes, the machine name is admin and the user name is amanda. I tried: admin amanda admin.jhuccp.org amanda admin [EMAIL PROTECTED] admin.jhuccp.org [EMAIL PROTECTED] So far, no joy. Oddly enough, I've gone ahead and added two other hosts. When I run amcheck now, it says: Amanda Backup Client Hosts Check ERROR: admin: [access as amanda not allowed from [EMAIL PROTECTED]] amandahostsauth failed Client check: 3 hosts checked in 0.049 seconds, 1 problem found From this, I take it that the other two hosts are okay. Is this a good assumption? Thanks, again, for taking the time to write. -Kevin Zembower Jon LaBadie [EMAIL PROTECTED] 12/11/01 11:30AM On Tue, Dec 11, 2001 at 10:02:36AM -0500, KEVIN ZEMBOWER wrote: Thank you to all the generous folks who have given me suggestions. Unfortunately, I still can't get it to work. I still get the same error massage with [access as amanda not allowed from [EMAIL PROTECTED]]. Here's some clarification on my system. I'm trying to backup the tapeserver. My tape is on a machine called admin.jhuccp.org. The userID for both client and server is amanda, group is disk. I've tried all these variations in the /home/amanda/.amandahosts and /var/lib/amanda/.amandahosts files (one at a time; the comments are how I kept track of what I tried): admin:/home/amanda # cat .amandahosts #admin.jhuccp.org amanda.admin.jhuccp.org #admin amanda.admin.jhuccp.org admin [EMAIL PROTECTED] #admin amanda #admin.jhuccp.org [EMAIL PROTECTED] admin:/home/amanda # End of included message I don't use this mechanism myself, but weren't the suggestions for the format machine_name user_name I.e. I think the appropriate line might be admin.jhuccp.org amanda -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing [EMAIL PROTECTED] 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Newbie: Tape doesn't eject?
Just completed my first amanda backup successfully, mostly. However, I got an error on three of my five hosts about missing results. Looking this up in the searchable archives led me to the /tmp/amanda/sendsize.*.debug file, and this showed that I had a directory named /etc/amandates, instead of a file. I removed the directory, touched the file, then chmod and chown it to amanda:disk 0600. Should be fine, I think. However, when my backup finished, the report noted that the tape was only 10% full, and it didn't eject. Is this normal amanda behavior, to not eject a tape until it's full? I want to run amdump over again right away. Should I manually eject the tape (with mt) and insert a new one, or just start amdump again with the same tape in the drive? Thanks, again, for all your help. -Kevin Zembower - E. Kevin Zembower Unix Administrator Johns Hopkins University/Center for Communications Programs 111 Market Place, Suite 310 Baltimore, MD 21202 410-659-6139
How can I tell what's happening?
How can I tell whether anything good is happening with my amanda backup? I'm new to amanda and trying to get it working on a system that I suspect has never been backed up. (I see messages in amdump like "isgadmin:/dev/hda1 overdue 11318 days for level 0.") My tapelist shows: su-2.03# cat tapelist 20001226 daily02 reuse 20001221 daily09 reuse 2817 daily01 reuse 0 daily10 reuse 0 daily08 reuse 0 daily07 reuse 0 daily06 reuse 0 daily05 reuse 0 daily04 reuse 0 daily03 reuse Which to me indicates that I successfully made a backup on Aug. 17, Dec. 21 and 26. (We've been faithfully changing tapes daily for the last five months. Oh, well ...) No other tapes seem to be used. "amstatus daily" shows: Using /var/log/amanda/daily/amdump from Tue Dec 26 16:01:00 EST 2000 centernet:/dev/sda1 0 no estimate centernet:/dev/sda3 0 no estimate centernet:/dev/sdb1 0 no estimate centernet:/dev/sdb2 0 no estimate cgi:/dev/hda112304k finished (16:30:02) cgi:/dev/hda30 647610k dumping to tape (16:30:05) isgadmin:/dev/hda1 0 no estimate isgadmin:/dev/hda2 0 no estimate isgback:/dev/ad0s1a 0 [input: No such file or directory] (16:30:03) isgback:/dev/ad0s1e 0 [input: No such file or directory] (16:30:03) isgback:/dev/ad0s1f 0 [input: No such file or directory] (16:30:04) mailinglists:/dev/hda1 0 no estimate mailinglists:/dev/hda2 0 no estimate mailinglists:/dev/hda7 0 no estimate virtual:/dev/hda10 no estimate virtual:/dev/hda30 no estimate SUMMARY part real estimated size size partition : 16 estimated : 51284715k failed : 14 635815k ( 49.49%) wait for dumping: 0 0k ( 0.00%) dumping to tape : 1 647610k ( 50.41%) dumping : 00k0k ( 0.00%) ( 0.00%) dumped : 1 2304k 1290k (178.60%) ( 0.18%) wait for writing: 00k0k ( 0.00%) ( 0.00%) writing to tape : 00k0k ( 0.00%) ( 0.00%) failed to tape : 00k0k ( 0.00%) ( 0.00%) taped : 1 2304k 1290k (178.60%) ( 0.18%) 3 dumpers idle : not-idle taper writing, tapeq: 0 network free kps: 2970 holding space :10652k (100.00%) dumper0 busy : 0:14:16 ( 98.88%) taper busy : 0:00:09 ( 1.07%) 0 dumpers busy : 0:00:06 ( 0.79%)no-diskspace: 0:00:06 (100.00%) 1 dumper busy : 0:14:19 ( 99.20%)no-diskspace: 0:14:16 ( 99.69%) not-idle: 0:00:02 ( 0.31%) Is cgi:hda3 still dumping to tape? This job has been running since about 4:00pm on Dec. 26. It's now 11am on Dec. 28. The Dec. 21 job did lead me to believe that the tape ran for 60 hours. Is this possible or likely? Yesterday, the tape showed activity, on and off, all during the day, so I didn't disturb it. Today, I haven't caught it doing anything when I walk into the next room. I attached amdump and the log file, if they help. Any suggestions for this amanda newbie? Thanks in advance for your help and efforts. -Kevin Zembower E. Kevin Zembower 410-659-6139 ÿWPCL ûÿ 2 B J #| x Ð °° ÐÐ ÐÐÐ Ø p °Ð ÐÃ ÃFrom: Ä ÄÁØ Ø ÁKevin Zembower [EMAIL PROTECTED] Ã ÃTo:Ä ÄÁØØ Á[EMAIL PROTECTED] Ã ÃDate: Ä ÄÁØ Ø Á12/28/00 10:04AM ÐÐ °` ¸ hÀpÈ x Ð (#%Ø'0*,à.813è5@8:ðH? AøCPF¨H KXM°OR`T¸VYh[À]` °Ð Ðamdump: start at Tue Dec 26 16:01:00 EST 2000 planner: pid 18247 executable /usr/local/libexec/planner version 2.4.2-19991216-beta1 planner: build: VERSION="Amanda-2.4.2-19991216-beta1" planner:BUILT_DATE="Thu May 18 11:29:28 EDT 2000" planner:BUILT_MACH="FreeBSD isgback.jhuccp.org 4.0-RELEASE FreeBSD 4.0-RELEASE #0: Mon Mar 20 22:50:22 GMT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC i386" planner:CC="gcc" planner: paths: bindir="/usr/local/bin" sbindir="/usr/local/sbin" planner:libexecdir="/usr/local/libexec" mandir="/usr/local/man" planner:AMANDA_TMPDIR="/tmp/amanda" AMANDA_DBGDIR="/tmp/amanda" pla
Re: How can I tell what's happening?
Thanks, John, for taking the time to try to give me a hand. I've only gotten one email report, but I did get that one, so I believe that the "mailto" is correct. That one came after the Dec. 21 run. It's also the one that gave me the idea that it took 60 hours. I can only "find" one log file: su-2.03# find / -name "log*2000*" -print /usr/local/etc/amanda/daily/log.20001226.0 This is the one I attached to the message. As to the errors: error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not allowed from [EMAIL PROTECTED]] error result for host isgadmin disk /dev/hda1: isgadmin: [access as amanda not allowed from [EMAIL PROTECTED]] These are puzzling, since I have both a /var/lib/amanda/.amandahosts and a /home/amanda/.amandahosts file (the passwd entry for amanda is: amanda:x:37:6:Amanda Admin:/var/lib/amanda:/bin/bash ), both files are identical, both are owned by amanda:amanda, and both contain "isgback.jhuccp.org amanda. On what I believe is a related note, I also get this error in the log file: FAIL dumper isgback /dev/ad0s1a 0 [[access as amanda not allowed from [EMAIL PROTECTED]] open of /home/amanda/.amandahosts failed I believe that this is related to the fact that /home/amanda/.amandahosts has owner:group of 37:102, neither one of which show up in /etc/passwd or /etc/group, although, as you can see from the preceding paragraph, amanda IS user 37 over on the isgadmin box. The /home directory is actually an NIS mount from the isgadmin machine, but this doesn't seem to be working well either, since I get an "Operation not permitted" error when I try to chown them. One more thing I've discovered in the three weeks that I've been here that I need to fix. I just learned from my coworker that the tape drive has been running intermittently today. Any hope that anything useful is being written to the tape? If so, I'm happy to let it run over the holidays, and work on the problem on Tuesday. But, if it's just garbage, I'll kill it now and start working on troubleshooting. It seems to me that your overall advice is to kill amanda and work on getting amcheck to run without error. Please help me to make sure I do this right. Is killing amanda completely as simple as looking at "ps -aux" and killing individually anything related to amanda or owned by amanda, such as taper or dumper? Should I then manually remove any files, or will amcleanup do all this for me? Anything else I should do to kill it completely, so that I can work with amcheck without any interference? Thanks, again, for all your help. Have a happy New Year. -Kevin Zembower E. Kevin Zembower 410-659-6139 [EMAIL PROTECTED] 12/28/00 12:40PM How can I tell whether anything good is happening with my amanda backup? ... The usual way is to look at the E-mail report you get after every run. You are getting those, right? If not, you'd better take a look at "mailto" in amanda.conf. Take a look at amanda.conf for the "logdir" variable. In that directory should be a bunch of files named log.MMDD.N. You can regenerate a report like this: amreport CONFIG -l LOGDIR/log.MMDD.N Which to me indicates that I successfully made a backup on Aug. 17, Dec. = 21 and 26. ... That only says Amanda rewrote the tape label on those days. It does not mean anything useful happened. I attached amdump and the log file, if they help. And they show all sorts of problems (which would also be in the E-mail): error result for host isgadmin disk /dev/hda2: isgadmin: [access as amanda not allowed from [EMAIL PROTECTED]] error result for host isgadmin disk /dev/hda1: isgadmin: [access as amanda not allowed from [EMAIL PROTECTED]] See the FAQ at www.amanda.org for information on this error. planner: FAILED mailinglists /dev/hda1 0 [missing result for /dev/hda1 in mailinglists response] planner: FAILED virtual /dev/hda1 0 [missing result for /dev/hda1 in virtual response] planner: FAILED centernet /dev/sda1 0 [missing result for /dev/sda1 in centernet response] These say Amanda was not able to get any estimates from these hosts. Later on: driver: result time 1743.049 from dumper0: FAILED 01-4 [access as amanda not allowed from [EMAIL PROTECTED]] open of /home/amanda/.amandahosts failed I don't know why this happened, but it's bad. The first rule with Amanda is always to run "amcheck CONFIG". If it's not happy (which I'm pretty sure it will not be for you), amdump is also not going to work. -Kevin Zembower John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
