Problem in Amanda Report
Hi, I'm a new user of Amanda. It's been running fine for some time since I got this job but I'm now getting a problem in the mail report of one of the backup servers, specifically in the Dump Summary : there are 2 result lines for each entrey in the disklist file, one says save was ok, the other just says MISSING. Here is an example (hostnamesand directories generalized for security purposes) : host1 /directory/saved 0 5820990 5821024 -- 268:26 361.4 4:30 21583.3 host1 /directory/saved MISSING This happens for every host on that server, everyday since it started, whatever the dump level is and whether or not the dumps can fit in a single tape or need 2. This doesn't happen on the second backup server (cloned machine, except for the disklist). Does anyone have an idea ? ThanksNicolas Maire
Re: Problem in Amanda Report
Hi, This happens for every host on that server, everyday since it started, whatever the dump level is and whether or not the dumps can fit in a single tape or need 2. This doesn't happen on the second backup server (cloned machine, except for the disklist). Does anyone have an idea ? I would double check the disklist, copy disklist from one server to the other and see if anything similar could be reproduced. Best regards, Olivier
/var/lib/amanda/.amandahosts: incorrect permissions
Hi, When I run amcheck, I get the following error: Amanda Backup Client Hosts Check ERROR: NAK bacchus: access as amanda not allowed from [EMAIL PROTECTED]: /var/lib/amanda/.amandahosts: incorrect permissions; file must be accessible only by its owner Client check: 16 hosts checked in 1.123 seconds, 1 problem found I'm running amanda 2.5.0 on the server and so on the client. My .amandahosts on the client looks like: -rw-r--r--1 amanda disk 398 Apr 11 14:56 .amandahosts and contains the alphabetical name of the amanda server, so the IP of the amanda server but I still get this error. I didn't have any problems till I upgraded both systems (server and client) to amanda 2.5.0 and the .amandahosts file remained unchanged. Before doing the upgrade, I was running amanda 2.4.5 and everything was fine. Regards, Iulian Topliceanu
Re: /var/lib/amanda/.amandahosts: incorrect permissions
On Tue, Apr 18, 2006 at 03:37:48PM +0200, Iulian Topliceanu wrote: Hi, When I run amcheck, I get the following error: Amanda Backup Client Hosts Check ERROR: NAK bacchus: access as amanda not allowed from [EMAIL PROTECTED]: /var/lib/amanda/.amandahosts: incorrect permissions; file must be accessible only by its owner Would you put your password in a file I can read? Client check: 16 hosts checked in 1.123 seconds, 1 problem found I'm running amanda 2.5.0 on the server and so on the client. My .amandahosts on the client looks like: -rw-r--r--1 amanda disk 398 Apr 11 14:56 .amandahosts I can read this file that might contain passwords -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: /var/lib/amanda/.amandahosts: incorrect permissions
Jon LaBadie wrote: Client check: 16 hosts checked in 1.123 seconds, 1 problem found I'm running amanda 2.5.0 on the server and so on the client. My .amandahosts on the client looks like: -rw-r--r--1 amanda disk 398 Apr 11 14:56 .amandahosts I can read this file that might contain passwords Sorry, my bad. Works now.
Re: What is the best way to duplicate a tape?
On Mon, 2006-04-17 at 16:01 -0400, Jon LaBadie wrote: On Mon, Apr 17, 2006 at 01:35:04PM -0600, Tom Schutter wrote: I was wondering if anyone can tell be the best way to duplicate an Amanda tape on a Linux box. I will have two identical tape drives. I would much prefer to use standard UNIX commands. The program tcopy would be perfect, but it is not available on Debian, it a google search indicates that is has problems. I would think that dd could do the trick, but what is the correct incantation? tcopy was going to be my suggestion until you said you were not using Solaris :( Is tcopy available on any other OS? If you know the tape block size (amanda's is 32K) then I think it would be: dd bs=32k if=/dev/xxx of=/dev/yyy where xxx are the no compression devices or with compression turned off. As I type this I realize that dd will only copy the first tape file. So this will have to loop. And you will need to use the no-rewind device. So something like: $ mt -f /dev/nxxx rewind $ mt -f /dev/nyyy rewind $ while dd bs=32k if=/dev/nxxx of=/dev/nyyy do : # a colon == no-op command done dd returns 0 on successful copy, non-zero on failure. The loop should terminate when the input fails at EOT. Perfect, just what I needed. For the archives, a slight improvement (so the command is easier to repeat): while dd bs=32k if=/dev/nxxx of=/dev/nyyy ; do : ; done -- Tom Schutter (mailto:[EMAIL PROTECTED]) Platte River Associates, Inc. (http://www.platte.com)
amcheck error : can not execute ...
Hi list ! I've got this error message when running amcheck: ERROR: www-dev: [can not execute /sbin/dump: No such file or directory] ERROR: www-dev: [can not execute /sbin/restore: No such file or directory] ERROR: www-dev: [can not read/write /var/lib/dumpdates: No such file or directory] www-dev is my remote client which I want to back-up. I've read several thread about guys who had this error and I found this relevant answer: There was no dump program available when you configured amanda. If you're going to back up with gnutar, there's no problem, but you'll have to live with the message unless you rebuild amanda after setting DUMP to /usr/bin/true or something like that. Do you think it's the same problem i've got ? The problem is that I ran apt from this client in order to install amanda. Do you think I can reconfigure Amanda ? (dpkg-reconfigure with special options ?) thks for any suggestion Thomas
Re: amcheck error : can not execute ...
On Tue, Apr 18, 2006 at 06:39:46PM +0200, Thomas Ginestet wrote: The problem is that I ran apt from this client in order to install amanda. Do you think I can reconfigure Amanda ? (dpkg-reconfigure with special options ?) All you should have to do is apt-get install dump. Debian doesn't install dump by default. Ross
Re: Defining a sensible backup routine
On Monday 17 April 2006 19:24, Jon LaBadie wrote: One of the goals of the amanda planner is to have a consistant sized backup each run. That is clearly not going to happen with the DLEs you are backing up. If you want to defeat this aspect of amanda's planning the parameters are there, probably maxpromotedays 0 is what you want. Backup failed today, with the errors /usr/local/etc/amanda/Daily/amanda.conf, line 26: configuration keyword expected /usr/local/etc/amanda/Daily/amanda.conf, line 26: end of line expected amgetconf: errors processing config file /usr/local/etc/amanda/Daily/amanda.conf Line 26 says maxpromotedays 0# Ensure reasonable number of incrementals I had initially missed the final 's' of maxpromotedays, but even after correcting that, amcheck gives the same errors. What could I be overlooking? Anne pgptyryqfcCKh.pgp Description: PGP signature
Re: /var/lib/amanda/.amandahosts: incorrect permissions
On Tuesday 18 April 2006 09:37, Iulian Topliceanu wrote: Hi, When I run amcheck, I get the following error: Amanda Backup Client Hosts Check ERROR: NAK bacchus: access as amanda not allowed from [EMAIL PROTECTED]: /var/lib/amanda/.amandahosts: incorrect permissions; file must be accessible only by its owner Thats correct, it must be owned by the user running amanda, and the perms must be set to 0600. Client check: 16 hosts checked in 1.123 seconds, 1 problem found I'm running amanda 2.5.0 on the server and so on the client. My .amandahosts on the client looks like: -rw-r--r--1 amanda disk 398 Apr 11 14:56 .amandahosts and contains the alphabetical name of the amanda server, so the IP of the amanda server but I still get this error. I didn't have any problems till I upgraded both systems (server and client) to amanda 2.5.0 and the .amandahosts file remained unchanged. Before doing the upgrade, I was running amanda 2.4.5 and everything was fine. Regards, Iulian Topliceanu -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Defining a sensible backup routine
On Tue, Apr 18, 2006 at 07:13:39PM +0100, Anne Wilson wrote: On Monday 17 April 2006 19:24, Jon LaBadie wrote: One of the goals of the amanda planner is to have a consistant sized backup each run. That is clearly not going to happen with the DLEs you are backing up. If you want to defeat this aspect of amanda's planning the parameters are there, probably maxpromotedays 0 is what you want. Backup failed today, with the errors /usr/local/etc/amanda/Daily/amanda.conf, line 26: configuration keyword expected /usr/local/etc/amanda/Daily/amanda.conf, line 26: end of line expected amgetconf: errors processing config file /usr/local/etc/amanda/Daily/amanda.conf Line 26 says maxpromotedays 0 # Ensure reasonable number of incrementals I had initially missed the final 's' of maxpromotedays, but even after correcting that, amcheck gives the same errors. What could I be overlooking? You shouldn't trust everything said on the mailing list ;( According to the manpage for amanda/amanda.conf, it is singular, no s. But check it for spelling too. If amcheck still complains show us a chunk of your config file around the problem line. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Defining a sensible backup routine
Anne Wilson wrote: On Monday 17 April 2006 19:24, Jon LaBadie wrote: One of the goals of the amanda planner is to have a consistant sized backup each run. That is clearly not going to happen with the DLEs you are backing up. If you want to defeat this aspect of amanda's planning the parameters are there, probably maxpromotedays 0 is what you want. Backup failed today, with the errors /usr/local/etc/amanda/Daily/amanda.conf, line 26: configuration keyword expected /usr/local/etc/amanda/Daily/amanda.conf, line 26: end of line expected amgetconf: errors processing config file /usr/local/etc/amanda/Daily/amanda.conf Line 26 says maxpromotedays 0 # Ensure reasonable number of incrementals I had initially missed the final 's' of maxpromotedays, but even after correcting that, amcheck gives the same errors. What could I be overlooking? On the older 2.4.5 version I have, the man page shows it as singular, but I don't use it so it could be a typo. Are you sure that's a number zero and not a letter o? Do you possibly have an error on a previous line (mismatched quotes or such) confusing the parser. Frank Anne -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Forcing full backups on a regular basis
Hi folks, I'm using amanda to back up three servers using tpchanger chg-disk. Everything is working fine, however due to the fact that I don't have a real tape changer I'd like to be able to take a given snapshot of all systems from time to time and burn it to DVD. I've already configured the virtual tapes to be somewhat smaller than a DVD. From what I understand dumpcycle only specifies that a full dump must happen (at least) every 7 days but otherwise it attempts to distribute those full dumps from various filesystems. Is there a way of enforcing this automatically so that there is a predictable schedule when a dump will contain a full backup of everything (i.e.: every Thursday night)? I realize I could probably run two backup schedules (one daily, one weekly) and turn incremental off on one of them completely, but that just seems clunky to me unless there's a way of utilizing the same tapes on two schedules?! Alternately I guess I could build a little script that would allow me to build a full image on demand from the incremental if I understand amanda properly. That would probably suit my purposes as well. Any help would be appreciated! cheers, Gabe
Re: Defining a sensible backup routine
On Tuesday 18 April 2006 19:58, Frank Smith wrote: On the older 2.4.5 version I have, the man page shows it as singular, but I don't use it so it could be a typo. Hmm - you're right. I checked the man page for 2.5 and it is singular, so it was right the first time. Are you sure that's a number zero and not a letter o? Certain. I deleted it and re-entered, to make sure. Do you possibly have an error on a previous line (mismatched quotes or such) confusing the parser. The previous line is a blank line. 'Enter' after a line that had been unremarked before. Anne pgpn2Mfhyu5AP.pgp Description: PGP signature
Re: Defining a sensible backup routine
On Tuesday 18 April 2006 19:48, Jon LaBadie wrote: You shouldn't trust everything said on the mailing list ;( :-) According to the manpage for amanda/amanda.conf, it is singular, no s. But check it for spelling too. Checked, and checked. If amcheck still complains show us a chunk of your config file around the problem line. maxpromotedays 0# Ensure reasonable number of incrementals dumpcycle 7 # The number of days in the normal dump cycle runspercycle 7 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) maxpromoteday 0 # Ensure reasonable number of incrementals tapecycle 21 tapes # the number of tapes in rotation (Ignore comments that no longer apply to settings - I just haven't cleaned up yet) Anne pgpWzFyPgndmj.pgp Description: PGP signature
Amanda 2.5 Debian UDP problem
Hi, I have setup amanda and a test client for it, my problem is that I get: WARNING: work: selfcheck request failed: timeout waiting for ACK when runing amcheck. It works fine if I use the client on localhost but not with a client on another machine. I've looked at the trafic with tcpdump: the server send packges but the client never reply's. I've read the mailing list and googled a bit but nothing I found solved my problem. Did anyone had this problem? Help, please... Best regards, Luis PS: amandad is started with inetd because it saves the following log: amandad: debug 1 pid 1883 ruid 34 euid 34: start at Tue Apr 18 12:54:51 2006 amandad: version 2.5.0 amandad: build: VERSION=Amanda-2.5.0 amandad:BUILT_DATE=Mon Apr 3 05:06:49 PDT 2006 amandad:BUILT_MACH=Linux rover 2.6.15-15-686 #1 SMP PREEMPT Mon Feb 6 18:34:45 UTC 2006 i686 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--prefix=/usr' '--bindir=/usr/sbin' '--mandir=/usr/share/man' '--libexecdir=/usr/lib/amanda' '--enable-shared' '--sysconfdir=/etc' '--localstatedir=/var/lib' '--with-gnutar-listdir=/var/lib/amanda/gnutar-lists' '--with-index-server=localhost' '--with-user=backup' '--with-group=backup' '--with-bsd-security' '--with-amandahosts' '--with-smbclient=/usr/bin/smbclient' '--with-debugging=/var/log/amanda' '--with-dumperdir=/usr/lib/amanda/dumper.d' '--with-tcpportrange=5,50100' '--with-udpportrange=840,860' '--with-maxtapeblocksize=256' '--no-create' '--no-recursion' amandad: paths: bindir=/usr/sbin sbindir=/usr/sbin amandad:libexecdir=/usr/lib/amanda mandir=/usr/share/man amandad:AMANDA_TMPDIR=/tmp/amanda amandad:AMANDA_DBGDIR=/var/log/amanda CONFIG_DIR=/etc/amanda amandad:DEV_PREFIX=/dev/ RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore VDUMP=UNDEF VRESTORE=UNDEF amandad:XFSDUMP=/sbin/xfsdump XFSRESTORE=/sbin/xfsrestore amandad:VXDUMP=UNDEF VXRESTORE=UNDEF amandad:SAMBA_CLIENT=/usr/bin/smbclient GNUTAR=/bin/tar amandad:COMPRESS_PATH=/bin/gzip UNCOMPRESS_PATH=/bin/gzip amandad:LPRCMD=/usr/bin/lpr MAILER=/usr/bin/Mail amandad:listed_incr_dir=/var/lib/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=localhost amandad:DEFAULT_TAPE_DEVICE=null: HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=backup FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 29.972: pid 1883 finish time Tue Apr 18 12:55:21 2006
Re: Defining a sensible backup routine
On Tue, Apr 18, 2006 at 08:15:50PM +0100, Anne Wilson wrote: On Tuesday 18 April 2006 19:48, Jon LaBadie wrote: You shouldn't trust everything said on the mailing list ;( :-) According to the manpage for amanda/amanda.conf, it is singular, no s. But check it for spelling too. Checked, and checked. If amcheck still complains show us a chunk of your config file around the problem line. maxpromotedays 0 # Ensure reasonable number of incrementals ^^ dumpcycle 7 # The number of days in the normal dump cycle runspercycle 7# the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) maxpromoteday 0 # Ensure reasonable number of incrementals ^ tapecycle 21 tapes# the number of tapes in rotation Two entries for same parameter? (Ignore comments that no longer apply to settings - I just haven't cleaned up yet) Few do. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Forcing full backups on a regular basis
On Tue, Apr 18, 2006 at 03:05:06PM -0400, Gabriel O'Brien wrote: Hi folks, I'm using amanda to back up three servers using tpchanger chg-disk. Everything is working fine, however due to the fact that I don't have a real tape changer I'd like to be able to take a given snapshot of all systems from time to time and burn it to DVD. I've already configured the virtual tapes to be somewhat smaller than a DVD. From what I understand dumpcycle only specifies that a full dump must happen (at least) every 7 days but otherwise it attempts to distribute those full dumps from various filesystems. Is there a way of enforcing this automatically so that there is a predictable schedule when a dump will contain a full backup of everything (i.e.: every Thursday night)? See amadmin manpage for options to force level 0's on demand. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Amanda 2.5 Debian UDP problem
Hi, On Tue, 2006-04-18 at 21:40 +0100, Luis Rodrigues wrote: Hi, I have setup amanda and a test client for it, my problem is that I get: WARNING: work: selfcheck request failed: timeout waiting for ACK when runing amcheck. It works fine if I use the client on localhost but not with a client on another machine. I've looked at the trafic with tcpdump: the server send packges but the client never reply's. I get this problem when the server is behind a firewall that is blocking traffic from the client... read up on the ports usage stuff (http://www.amanda.org/docs/portusage.html) and make sure none of that is getting blocked. Cam
