Re: Amanda not backing up Veritas file systems correctly
[EMAIL PROTECTED] wrote: Actually, I don't have those entries in /etc/vfstab. I will give that a try. For future reference, in order to handle transient filesystems such as this, it might be better off evaluating the output of mount rather than the filesystem table. Except I can't remember if it gives FS info. If you have amanda sources around, take a look in the dir client-src. There is file name getfsent.c which contains the code. The beginning comment is: /* * You are in a twisty maze of passages, all alike. * Geesh. */ And that becomes clear when trying to understand the next few lines :-) To help debugging this, you can compile getfsent into a standalone program. Just type make getfsent in that directory. When you run it as ./getfsent it shows which blocks were defined in the maze of passages and shows what amanda thinks about each filesystem on the host. -- 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: Amanda not backing up Veritas file systems correctly
You know, I am always amazed at the different things to be found in amanda's source code. I tried writing a more detailed INTERNALS document a while ago: it did not work out. I will try the make getfsent. thank you again for your time. --jason ~~~ Jason Brooks ~ (503) 641-3440 x1861 Direct ~ (503) 924-1861 Email to: [EMAIL PROTECTED] Twiki: http://twiki.wrs.com/do/view/Main/JasonBrooks Senior Systems Administration Analyst Wind River Systems 8905 SW Nimbus ~ Suite 255 Beaverton, Or 97008 -Original Message- From: Paul Bijnens [mailto:[EMAIL PROTECTED] Sent: Friday, 28 May, 2004 00:02 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Amanda not backing up Veritas file systems correctly [EMAIL PROTECTED] wrote: Actually, I don't have those entries in /etc/vfstab. I will give that a try. For future reference, in order to handle transient filesystems such as this, it might be better off evaluating the output of mount rather than the filesystem table. Except I can't remember if it gives FS info. If you have amanda sources around, take a look in the dir client-src. There is file name getfsent.c which contains the code. The beginning comment is: /* * You are in a twisty maze of passages, all alike. * Geesh. */ And that becomes clear when trying to understand the next few lines :-) To help debugging this, you can compile getfsent into a standalone program. Just type make getfsent in that directory. When you run it as ./getfsent it shows which blocks were defined in the maze of passages and shows what amanda thinks about each filesystem on the host. -- 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 * ** *
Error compiling on TRU64 4.0F
Hi, I'm trying to build amanda client binaries for TRU64 4.0F. I am able to run configure fine (minus /sbin/dump issues). When I run make, it errors out with the following message: cc -g -o .libs/amqde amqde.o ./.libs/libamclient.so ../common-src/.libs/libamanda.so -lm -ltermcap -rpath /mnt/raid/dist/lib ld: Unresolved: snprintf *** Exit 1 Stop. *** Exit 1 Anybody understand why this is failing? -Rob PS - here is my configure line: ./configure --prefix=/mnt/raid/dist --with-suffixes=no --with-index-server=main --with-user=amanda --with-group=amanda --without-server --without-restore --without-amrecover --with-config=simnet --with-gnutar=/mnt/raid/dist/bin/tar --with-smbclient=no
Re: Amrecover
Now i think the problem is other: [EMAIL PROTECTED] backup]# amrecover Daily AMRECOVER Version 2.4.4p2. Contacting server on tux2.employer.com.br ... 220 tux2 AMANDA index server (2.4.4p2) ready. 200 Access OK Setting restore date to today (2004-05-28) 200 Working date set to 2004-05-28. Scanning /dumps/amanda... 200 Config set to Daily. 200 Dump host set to tux2.employer.com.br. Trying disk /backup ... $CWD '/backup' is on disk '/backup' mounted at '/backup'. 200 Disk set to /backup. /backup amrecover ls 2004-05-28 . 2004-05-28 bin/ 2004-05-28 bkp/ 2004-05-28 cafe/ 2004-05-28 cafesistemas/ 2004-05-28 dev/ 2004-05-28 etc/ 2004-05-28 lib/ 2004-05-28 servdados/ 2004-05-28 servdados2/ 2004-05-28 servdados3/ 2004-05-28 servinter/ 2004-05-28 sql_bkp/ amrecover ls 2004-05-28 . 2004-05-28 bin/ 2004-05-28 bkp/ 2004-05-28 cafe/ 2004-05-28 cafesistemas/ 2004-05-28 dev/ 2004-05-28 etc/ 2004-05-28 lib/ 2004-05-28 servdados/ 2004-05-28 servdados2/ 2004-05-28 servdados3/ 2004-05-28 servinter/ 2004-05-28 sql_bkp/ amrecover cd sql_bkp /backup/sql_bkp amrecover ls 2004-05-28 . 2004-05-28 sql.tgz amrecover add sql.tgz Added /sql_bkp/sql.tgz amrecover extract Extracting files using tape drive /dev/nst0 on host tux2.employer.com.br. The following tapes are needed: Employer0 Restoring files into directory /backup Continue [?/Y/n]? Y Extracting files using tape drive /dev/nst0 on host tux2.employer.com.br. Load tape Employer0 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.timestamp.debug file on tux2.employer.com.br. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? Below is my amidxtaped debu file: amidxtaped: debug 1 pid 3457 ruid 502 euid 502: start at Fri May 28 08:14:44 2004 amidxtaped: version 2.4.4p2 amidxtaped: time 0.000: SECURITY USER root amidxtaped: time 0.078: bsd security: remote host tux2.employer.com.br user root local user amanda amidxtaped: time 0.158: amandahosts security check passed amidxtaped: time 0.158: CONFIG=Daily amidxtaped: time 0.158: LABEL=Employer0 amidxtaped: time 0.158: FSF=1 amidxtaped: time 0.158: HEADER amidxtaped: time 0.158: DEVICE=/dev/nst0 amidxtaped: time 0.158: HOST=^tux2.employer.com.br$ amidxtaped: time 0.158: DISK=^/backup$ amidxtaped: time 0.158: DATESTAMP=20040528 amidxtaped: time 0.158: END amidxtaped: time 0.282: amrestore_nargs=0 amidxtaped: time 0.282: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = /dev/nst0 argv[4] = ^tux2.employer.com.br$ argv[5] = ^/backup$ argv[6] = 20040528 amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information amidxtaped: time 0.340: amrestore terminated normally with status: 1 amidxtaped: time 0.340: rewinding tape ... amidxtaped: time 40.076: done amidxtaped: time 40.076: pid 3457 finish time Fri May 28 08:15:24 2004 - Original Message - From: Paul Bijnens [EMAIL PROTECTED] To: Marcelo Leão Caffaro [EMAIL PROTECTED] Sent: Thursday, May 27, 2004 5:20 PM Subject: Re: Amrecover Marcelo Leão Caffaro wrote: This is my debug file amindexd So I may conclude there was no amidxtaped.XXX.debug log file? Then have a look in the (x)inetd.conf on the server. The server needs the server amandaidx (10082/tcp) to handle the index, which works fine, and when reading the backup itself, it needs service amidxtape (10083/tcp). Maybe a typo in the that config? -- 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: Error compiling on TRU64 4.0F
I figured out the problem. snprintf vsnprintf are absent in libc for TRU64 4.0F. However, they can be found in the libdb.so library. So, I was able to fix my problem by adding LD=-ldb to the configure line. -Rob -Original Message- From: Dege, Robert C. Sent: Friday, May 28, 2004 9:47 AM To: Amanda List (E-mail) Subject: Error compiling on TRU64 4.0F Hi, I'm trying to build amanda client binaries for TRU64 4.0F. I am able to run configure fine (minus /sbin/dump issues). When I run make, it errors out with the following message: cc -g -o .libs/amqde amqde.o ./.libs/libamclient.so ../common-src/.libs/libamanda.so -lm -ltermcap -rpath /mnt/raid/dist/lib ld: Unresolved: snprintf *** Exit 1 Stop. *** Exit 1 Anybody understand why this is failing? -Rob PS - here is my configure line: ./configure --prefix=/mnt/raid/dist --with-suffixes=no --with-index-server=main --with-user=amanda --with-group=amanda --without-server --without-restore --without-amrecover --with-config=simnet --with-gnutar=/mnt/raid/dist/bin/tar --with-smbclient=no
Re: Amrecover
Hi, Marcelo, on Freitag, 28. Mai 2004 at 16:42 you wrote to amanda-users: MLC amrestore: WARNING: not at start of tape, file numbers will be offset mt -f /dev/st0 rewind -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Archiving With Amanda?
I have some files I'd like to permanently remove from my system (archiving to tape). It would be nice to have them listed in amanda's index and have amanda keep track of them for me. Does anyone know a way to do this? Thanks, Steve
Re: Archiving With Amanda?
On Fri, 28 May 2004 at 8:51am, Steven Backus wrote I have some files I'd like to permanently remove from my system (archiving to tape). It would be nice to have them listed in amanda's index and have amanda keep track of them for me. Does anyone know a way to do this? Set up a new config called (e.g.) Archive. Set 'dumpcycle 0', tapecycle to something large, and, in your dumptypes, 'record no'. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Archiving With Amanda?
steven create a new backup set called 'archive', as opposed to the one you have now. then run it whenever... -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 Steven Backus wrote: I have some files I'd like to permanently remove from my system (archiving to tape). It would be nice to have them listed in amanda's index and have amanda keep track of them for me. Does anyone know a way to do this? Thanks, Steve ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **
Re: Amrecover
Marcelo Leão Caffaro wrote: Now i think the problem is other: [...] Load tape Employer0 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.timestamp.debug file on tux2.employer.com.br. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header We're further now. That's already good news. Below is my amidxtaped debu file: [...] amrestore: WARNING: not at start of tape, file numbers will be offset That was the problem. Two possible solutions: 1. Manualy rewind the tape before your read it. ( mt -f /dev/nst0 rewind ) You position it yourself to the correct image with mt fsf ###, if you like. 2. Since amanda 2.4.4 amanda can do this for you, but you need to add these two lines to amanda.conf: amrecover_do_fsf yes# this implies a rewind amrecover_check_label yes -- 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: Archiving With Amanda?
Steven Backus wrote: I have some files I'd like to permanently remove from my system (archiving to tape). It would be nice to have them listed in amanda's index and have amanda keep track of them for me. Does anyone know a way to do this? Mark the tape as no-reuse. Then amanda will not recycle the tape, but still keep track of it. I suggest you add a special config for this, instead of the daily. Call it archive or such. Add record no, dumpcycle 0 and index yes to the dumptype, (and even skip-incr yes and strategy no-inc to speed up estimates). record no is important to avoid messing up the daily schedule. I suggest you use gnutar to backup; who knows what hardware you need to restore the files to in 5 years from now. Add the necessary entries to the disklist. Label a tape, e.g. ARCHIVE-, or even ARCH-20040528-BigProject. Run amdump archive. Run amverify archive. Run amadmin archive no-reuse ARCHIVE-. rm -rf BigProject It's nice to let amreport generate some Postscript labels to go with the tape too. -- 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: Archiving With Amanda
Wow guys that was fast and great, you guys rock. Thanks a lot. Steve
Re: Archiving With Amanda?
On Fri, May 28, 2004 at 08:51:49AM -0600, Steven Backus wrote: I have some files I'd like to permanently remove from my system (archiving to tape). One point in addition to what everyone else has said: it would be wise to make at least two copies of the archive tape(s). Media has a nasty habit of going bad over time. When I had to archive and delete some data, this describes how I made duplicates of the archive tapes: http://groups.yahoo.com/group/amanda-users/message/49373 (Simply amdumping twice would not make *identical* copies, since the first run would change the files' last-access timestamps, if nothing else.) -- | | /\ |-_|/ Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
MapBarCode error
Hello all, when I try to run amcheck, I keep getting a MapBarCode error, which causes amcheck to exit tape scanning prematurely. Here's a snippet of output: bash$ amcheck simnet Amanda Tape Server Host Check - Holding disk /mnt/raid/holding: 3250292 KB disk space available, that's plenty amcheck-server: slot 3: date 20180417 label SIMNET-04 (active tape) amcheck-server: fatal slot MapBarCode,: DB Version does not match ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 141.154 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.121 seconds, 0 problems found Does anyone know why I'm getting this error message? I'm using amanda with a Qualstar TLS-4222 with (2) SDX-700C AIT3 tape drives. There is no BarCode reader in the unit. -Rob
Re: Archiving With Amanda?
On Fri, May 28, 2004 at 03:03:42PM -0400, Eric Siegerman wrote:
(Simply amdumping twice would not make *identical* copies, since
the first run would change the files' last-access timestamps, if
nothing else.)
Changing the last-access time of a file is only an issue for mechanisms
that open the files in question. For example, tar opens (individual)
files that it reads. On the other hand, {,ufs}dump does not: the thing
it opens is a file system, so it does not change inode contents at all.
That said, there exist other reasons the product of another backup
process is unlikely to be an identical copy of the first.
IIRC, someone posted a note about how he ran an amdump, and as chunks
were written to the holding disk (well, before the chunks were taped
unlinked), he made another link to each file, so after the first taping,
the files in the holding disk were still there, and an amflush run created
another tape with the same data.
Peace,
david
--
David H. Wolfskill [EMAIL PROTECTED]
Re: Amrecover
The amanda movie, part I amrecover [EMAIL PROTECTED] backup]# amrecover Daily AMRECOVER Version 2.4.4p2. Contacting server on tux2.employer.com.br ... 220 tux2 AMANDA index server (2.4.4p2) ready. 200 Access OK Setting restore date to today (2004-05-28) 200 Working date set to 2004-05-28. Scanning /dumps/amanda... 200 Config set to Daily. 200 Dump host set to tux2.employer.com.br. Trying disk /backup ... $CWD '/backup' is on disk '/backup' mounted at '/backup'. 200 Disk set to /backup. /backup amrecover ls 2004-05-28 . 2004-05-28 bin/ 2004-05-28 bkp/ 2004-05-28 cafe/ 2004-05-28 cafesistemas/ 2004-05-28 dev/ 2004-05-28 etc/ 2004-05-28 lib/ 2004-05-28 servdados/ 2004-05-28 servdados2/ 2004-05-28 servdados3/ 2004-05-28 servinter/ 2004-05-28 sql_bkp/ amrecover cd servdados /backup/servdados amrecover ls 2004-05-28 . 2004-05-28 sistemas.tgz 2004-05-28 sistemas.tgz1 amrecover add sistemas.tgz Added /servdados/sistemas.tgz amrecover extract Extracting files using tape drive /dev/nst0 on host tux2.employer.com.br. The following tapes are needed: Employer0 Restoring files into directory /backup Continue [?/Y/n]? Y Extracting files using tape drive /dev/nst0 on host tux2.employer.com.br. Load tape Employer0 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.timestamp.debug file on tux2.employer.com.br. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? Y amrecover Amidxtaped Debug file: amidxtaped: debug 1 pid 4238 ruid 502 euid 502: start at Fri May 28 13:58:22 2004 amidxtaped: version 2.4.4p2 amidxtaped: time 0.000: SECURITY USER root amidxtaped: time 0.001: bsd security: remote host tux2.employer.com.br user root local user amanda amidxtaped: time 0.001: amandahosts security check passed amidxtaped: time 0.001: CONFIG=Daily amidxtaped: time 0.001: LABEL=Employer0 amidxtaped: time 0.001: FSF=1 amidxtaped: time 0.001: HEADER amidxtaped: time 0.001: DEVICE=/dev/nst0 amidxtaped: time 0.001: HOST=^tux2.employer.com.br$ amidxtaped: time 0.001: DISK=^/backup$ amidxtaped: time 0.001: DATESTAMP=20040528 amidxtaped: time 0.001: END amidxtaped: time 0.005: amrestore_nargs=0 amidxtaped: time 0.005: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = -l argv[4] = Employer0 argv[5] = -f argv[6] = 1 argv[7] = /dev/nst0 argv[8] = ^tux2.employer.com.br$ argv[9] = ^/backup$ argv[10] = 20040528 Wrong label: 'EmployerFull0' amidxtaped: time 50.866: amrestore terminated normally with status: 1 amidxtaped: time 50.866: rewinding tape ... amidxtaped: time 61.220: done amidxtaped: time 61.220: pid 4238 finish time Fri May 28 13:59:23 2004 - Original Message - From: Paul Bijnens [EMAIL PROTECTED] To: Marcelo Leão Caffaro [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, May 28, 2004 11:48 AM Subject: Re: Amrecover Marcelo Leão Caffaro wrote: Now i think the problem is other: [...] Load tape Employer0 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.timestamp.debug file on tux2.employer.com.br. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header We're further now. That's already good news. Below is my amidxtaped debu file: [...] amrestore: WARNING: not at start of tape, file numbers will be offset That was the problem. Two possible solutions: 1. Manualy rewind the tape before your read it. ( mt -f /dev/nst0 rewind ) You position it yourself to the correct image with mt fsf ###, if you like. 2. Since amanda 2.4.4 amanda can do this for you, but you need to add these two lines to amanda.conf: amrecover_do_fsf yes # this implies a rewind amrecover_check_label yes -- 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 * ***
amcheck errors
Hello guys, It's my first time trying to setup amanda and I am getting this output when I run amcheck myconfiguration : Amanda Tape Server Host Check - Holding disk /var/tmp: 194660 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 4.573 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.079 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) My OS is Red Hat 8.0 Some could help me ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br
Re: amcheck errors
Olá Fábio, vc nao pode associar localhost no disklist, tambem passei por esse problema. Valeu - Original Message - From: Fábio Mendonça Albuquerque Cunha [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 28, 2004 5:45 PM Subject: amcheck errors Hello guys, It's my first time trying to setup amanda and I am getting this output when I run amcheck myconfiguration : Amanda Tape Server Host Check - Holding disk /var/tmp: 194660 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 4.573 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.079 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) My OS is Red Hat 8.0 Some could help me ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br
Re: MapBarCode error
On Friday 28 May 2004 15:31, Dege, Robert C. wrote: Hello all, when I try to run amcheck, I keep getting a MapBarCode error, which causes amcheck to exit tape scanning prematurely. Here's a snippet of output: bash$ amcheck simnet Amanda Tape Server Host Check - Holding disk /mnt/raid/holding: 3250292 KB disk space available, that's plenty amcheck-server: slot 3: date 20180417 label SIMNET-04 (active tape) amcheck-server: fatal slot MapBarCode,: DB Version does not match ERROR: new tape not found in rack (expecting a new tape) NOTE: skipping tape-writable test Server check took 141.154 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.121 seconds, 0 problems found Does anyone know why I'm getting this error message? I'm using amanda with a Qualstar TLS-4222 with (2) SDX-700C AIT3 tape drives. There is no BarCode reader in the unit. -Rob It sounds as if you may have either emubarcode, or something similar in your amanda.conf. There are a couple of keywords in amanda that (I've surveyed the code in question) if found, default to yes, so the only way to shut things up is to comment those lines out. I believe thats one of them. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.23% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: Hello guys, It's my first time trying to setup amanda and I am getting this output when I run amcheck myconfiguration : Amanda Tape Server Host Check - Holding disk /var/tmp: 194660 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 4.573 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.079 seconds, 1 problem found And we are back to the single, most covered in the docs, error. We don't mean to get short with newbies, but the use of localhost is a no-no. Please change your disklist entry to use the FQDN of the machine in question. Then, backup just a few days in the archives where I have posted the amanda file that goes in /etc/xinetd.d, and I'll mention that it may be you do not have the /home/(user)/.amandahosts file properly configured. Also, I suspect thats an rpm install, as 2.4.2p2 is getting pretty long in the tooth now. I'm running 2.4.5b1-20040510 snapshot here. While it is possible to beat the rpm versions around and make them work, generally speaking its a lot easier to build from the tarball, it takes me about 4 minutes to build each new snapshot and install it by use of the scripts I use here. (brought to you by Amanda 2.4.2p2) My OS is Red Hat 8.0 Some could help me ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.23% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
Thanks Gene and Marcelo I run my backups and it's ok ! But now, when I try to recover this backup I get this output of amrecover: [EMAIL PROTECTED] DailySet1]# amrecover DailySet1 AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 asterix AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Why amanda is looking for a localhost, if I set up my .amandahosts like this : [EMAIL PROTECTED] amanda]# vi .amandahosts asterix amanda Someone could help me with this ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br On Fri, 28 May 2004 17:16:21 -0400, Gene Heskett gene escreveu: De: Gene Heskett gene Data: Fri, 28 May 2004 17:16:21 -0400 Para: [EMAIL PROTECTED] Assunto: Re: amcheck errors On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: Hello guys, It's my first time trying to setup amanda and I am getting this output when I run amcheck myconfiguration : Amanda Tape Server Host Check - Holding disk /var/tmp: 194660 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 4.573 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.079 seconds, 1 problem found And we are back to the single, most covered in the docs, error. We don't mean to get short with newbies, but the use of localhost is a no-no. Please change your disklist entry to use the FQDN of the machine in question. Then, backup just a few days in the archives where I have posted the amanda file that goes in /etc/xinetd.d, and I'll mention that it may be you do not have the /home/(user)/.amandahosts file properly configured. Also, I suspect thats an rpm install, as 2.4.2p2 is getting pretty long in the tooth now. I'm running 2.4.5b1-20040510 snapshot here. While it is possible to beat the rpm versions around and make them work, generally speaking its a lot easier to build from the tarball, it takes me about 4 minutes to build each new snapshot and install it by use of the scripts I use here. (brought to you by Amanda 2.4.2p2) My OS is Red Hat 8.0 Some could help me ? Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) 99.23% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amcheck errors
On Friday 28 May 2004 18:34, Fábio Mendonça Albuquerque Cunha wrote: Thanks Gene and Marcelo My second reply to this post after I'd thought about it a bit. I run my backups and it's ok ! But now, when I try to recover this backup I get this output of amrecover: [EMAIL PROTECTED] DailySet1]# amrecover DailySet1 AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 asterix AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as amanda not allowed from [EMAIL PROTECTED] amandahostsauth failed Why amanda is looking for a localhost, if I set up my .amandahosts like this : [EMAIL PROTECTED] amanda]# vi .amandahosts asterix amanda Someone could help me with this ? Is this from an rpm install? The reason I ask is that the tape-servers FQDN (in your case localhost) is compiled into amanda when its built. Your initial invocation of amrecover should have looked like this: [EMAIL PROTECTED] root]# amrecover DailySet1 AMRECOVER Version 2.4.5b1-20040510. Contacting server on coyote.coyote.den ... 220 coyote AMANDA index server (2.4.5b1-20040510) ready. 200 Access OK Setting restore date to today (2004-05-28) 200 Working date set to 2004-05-28. Scanning /dumps... 200 Config set to DailySet1. 501 Host coyote.coyote.den is not in your disklist. Trying host coyote.coyote.den ... 501 Host coyote.coyote.den is not in your disklist. Trying host coyote ... 200 Dump host set to coyote. Trying disk /root ... $CWD '/root' is on disk '/root' mounted at '/root'. 200 Disk set to /root. /root amrecover As you can see, it looked for the FQDN of the machine, then finally settled for its alias as listed in /etc/hosts. This is just one of the many reasons one should build amanda from scratch, those rpms are broken if 'localhost' is compiled in. One could even say they are drain bamaged. :-) If thats the case, rpm -e those broken rpms. Then get the latest tarball of the 2.4.5b1 series from a link near the bottom of the front page at amanda.org. Configuring and building amanda requires an unpriviledged user, such as amanda, who should be a member of some much higher group such as disk or backup. I've had to unpack amanda as root on a few occasions even though I'm sitting in the /home/amanda directory when I do the unpack. In that event, while still root, do a 'chown -R amanda:disk name-of-amanda-dir' to fix up the perms so amanda can build it. Here is the script I use, copied into the top level dir the tarball unpacks to, and then run as the user amanda here at this hillbillies house: -- #!/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 # the next 2 lines are in case you've changed something and are # rebuilding amanda again. make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-tape-device=/dev/nst0 \ --with-changer-device=/dev/sg1 \ --with-gnu-ld --prefix=/usr/local \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote.coyote.den \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda make --- adjust the tape-server to your machines FQDN. Delete the changer-device= line if you don't have one. Set the exec bit on this script, and do a './whatever-name-you-gave-it', or use a child of sh and do 'sh ./whatever-etc' This will configure and make amanda, which takes about 3 minutes on this machine. Then become root, and do the 'make install', which takes another minute or so. That will get rid of the localhost stuff as long as you don't have any localhosts in your disklist. Then we can sort your next problems knowing we have a good install to work with. Regards, InfraNet Tecnologia Fábio M. A. Cunha (55 11) 5542-0941 ramal 22 (55 11) 9603-6377 www.infranetsp.com.br On Fri, 28 May 2004 17:16:21 -0400, Gene Heskett gene escreveu: De: Gene Heskett gene Data: Fri, 28 May 2004 17:16:21 -0400 Para: [EMAIL PROTECTED] Assunto: Re: amcheck errors On Friday 28 May 2004 16:45, Fábio Mendonça Albuquerque Cunha wrote: Hello guys, It's my first time trying to setup amanda and I am getting this output when I run amcheck myconfiguration : Amanda Tape Server Host Check - Holding disk /var/tmp: 194660 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 4.573 seconds Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 30.079 seconds, 1 problem found And we are back to the single, most covered in the
