SCSI or amanda trouble?

[Hery Zo RAKOTONDRAMANANA]

Hi all,

by the way, wish all of you all the best things for this new year.

My problem is that I frequently have these messages:

*** A TAPE ERROR OCCURRED: [reading label: Input/output error].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: TestConf10.

or this one:

The dumps were flushed to tape TestConf08.
*** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
Some dumps may have been left in the holding disk.
Run amflush again to flush them to tape.
The next tape Amanda expects to use is: TestConf09.

Thinking this could be an SCSI issue, I installed a second SCSI controller on my backup server and attached the tape drive on it, but the problem still remains. 

Somehow, I now have this in my kernel messages (which didn't happen when I only had one SCSI controller):

Jan 16 16:17:09 parasy kernel: st0: Error with sense data: Info fld=0x2, Current st09:00: sense key Medium Error
Jan 16 16:17:09 parasy kernel: Additional sense indicates Write error


Any ideas or indications on this issue are greatly appreciated.

Regards.

Hery Zo RAKOTONDRAMANANA
Simicro Internet

Re: amrecover tapeless-mode

[Jean-Louis Martineau]

On Wed, Jan 15, 2003 at 03:44:01PM +0100, Thomas Bex wrote:
> Hi,
> 
> I set up amanda in tapeless mode with an external firewire disk on 
> debian woody.
> Amdump runs fine but most time I try to restore data, I get errors being 
> not at the beginning of the tape.
> 
> amrestore: WARNING: not at start of tape, file numbers will be offset
> amrestore:   0: skipping *
> amrestore:   1: skipping *
> amrestore:   2: reached end of tape: date 20030115
> amidxtaped: amrestore terminated normally with status: 1
> amidxtaped: could not stat file:/mnt/firewire/
> 
> So, how do I "rewind" a harddisk?

With ammt: ammt -f file:/mnt/firewire rewind

Jean-Louis
-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834

Astromerkez'den Ücretsiz Astroloji Raporu!..

[Astromerkez]

 

  

Dünya'nın İlk Astroloji
ve Gizli İlimler Portalıwww.astromerkez.com
  
  

 
Dünya'nın ilk
astroloji portalından büyük hizmet!!! 
Ücretsiz 
astroloji raporu. Tam 8 sayfa.
Ve yine
ücretsiz çiftlerin uyum raporu.
Sınırlı
bir süre için. Kaçırmayın!...
 www.astromerkez.com
da 
 
  

Re: compile error on 2.4.3-20030104

[Jean-Louis Martineau]

Hi,

The newer amidxtaped need the server library which is not build if
you set --without-server

The fix is not build amidxtaped and amrestore if --without-server is set.

The next snapshot will be available soon.

Jean-Louis

On Thu, Jan 16, 2003 at 02:22:49PM -0800, DK Smith wrote:
> 
> ###3
> 
> Making all in restore-src
> make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src'
> source='amidxtaped.c' object='amidxtaped.o' libtool=no \
> depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \
> depmode=gcc3 /bin/sh ../config/depcomp \
> gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src 
>-I../server-src  -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2   -c `test -f 
>'amidxtaped.c' || echo './'`amidxtaped.c
> amidxtaped.c: In function `main':
> amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type
> make[1]: *** No rule to make target `../server-src/libamserver.la', needed by 
>`amidxtaped'.  Stop.
> make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src'
> make: *** [all-recursive] Error 1
> 

> ./configure   \
>   --without-server\
>   --prefix=/usr/local_legless/amanda-2.4.3-20030104 \
>   --with-tmpdir=/tmp/amanda   \
>   --with-includes=/usr/local/gnu/include  \
>   --with-libraries=/usr/local/gnu/lib \
>   --with-gnutar   \
>   --with-gnutar-listdir=/var/amanda/gnutar-listdir\
>   --without-amandahosts   \
>   --with-user=amanda  \
>   --with-group=disk   \
>   --with-debugging\
>   --with-debug-days=4 \
> 
> 
> 
> ###3

-- 
Jean-Louis Martineau email: [EMAIL PROTECTED] 
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834

Re: Excluding files question

[Adnan Olia]

Thanks Jon,

I think I can work something out based on your suggestion..thanks again

Adnan

"Jon LaBadie" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> On Thu, Jan 16, 2003 at 03:54:20PM -0600, Adnan Olia wrote:
> > Hi all,
> >
> > Does anybody knows how to exclude files (by file size) during the dump
> > process?
>
> No builtin way I know of.  You could run a "find  -size " to
> generate a list of files to exclude and put that into the exclude file
> before running amdump.
>
> --
> Jon H. LaBadie  [EMAIL PROTECTED]
>  JG Computing
>  4455 Province Line Road(609) 252-0159
>  Princeton, NJ  08540-4322  (609) 683-7220 (fax)
>

Re: question

[Gene Heskett]

On Thursday 16 January 2003 18:27, [EMAIL PROTECTED] wrote:
>I installed and configured Amanda in our system (client/server).
>How do a back up?
>Could you please show me an example?
>
>Thanks!
>
>David

First, we have to assume that you've become the user 'amanda' and 
that you've used the error catchers in amcheck to makes ure the 
configration is correct.

In the user amanda's crontab, a couple of lines need to be added
--
15 11 * * * /usr/local/sbin/amcheck -m DailySet1
# adjust the above 11:15am times to suit your operation
15 00 * * * /usr/local/sbin/amdump DailySet1
# ditto for this midnight+15 minutes setting.
--
The -m in the first line will make amanda email you prompting for 
the right tape if it is not already in the drive or robot magazine.

This will run amcheck and amdump everyday.

Is this what you wanted?

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly

Re: Strange Amandad problem using xinetd and RedHat 8.0

[Gene Heskett]

On Thursday 16 January 2003 13:17, Michael Lang wrote:
>Hi to all,
>
>i encounter a strange problem with amandad on a client using
> RedHat 8.0 kernel 2.4.20 xinet 2.3.7-5.
>
>I´ve setup the xinetd config as described in the INSTALL it also
> works 2 times fine but as i try a third amcheck BackupSet the
> requested Host times out and there´s  one amandad zombie hanging
> around, which can only
>
>be removed by restarting xinetd.
>
>using the default kernel 2.4.18-14 it works fine without any
> problem.

Thats odd, Michael.  I've had no such problems here on a rh8.0 
system, currently up to kernel 2.4.21-pre3, with the same 2.3.7-5 
xinetd.

Couple of questions.  Is the .amandhosts file up to date, and perms 
set for 0600?  And are you using individual files for amanda in 
xinetd.d, or one merged one?  I don't think it makes any diff, I 
use a merged all in one file for that here, listing all 3 services 
in one file.

Is there a timeout, where the zombie disappears eventually?

>any hint would be nice ... thanks

Thats about my best shot.  I'm not an expert, I just play one as a 
almost-retired tv engineer. :)

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly

question

[David . Lee]

I installed and configured Amanda in our system (client/server).
How do a back up?
Could you please show me an example?

Thanks!

David

Re: Problems with labelstr

[Gene Heskett]

On Thursday 16 January 2003 12:09, Dan Spray wrote:

Please don't post html messages to this list, we expect plain old 
ascii text so we have a choice in the displayed font size, this is 
truely tiny and hard to read.

>Thanks to all who helped with this problem.  I assumed that it was
>something along those lines, I guess I need to understand regular
>expressions better.
>
>Now I am getting another error, I pasted it below if anyone knows
> what needs done differently.
>
>Thanks in advance,
>
>Dan
>
>[root@ZEUS config]# su amanda -c "amlabel config Daily-Wed"
>rewinding, reading label, not an amanda tape
>rewinding, writing label Daily-Wed, checking labelamlabel:
> couldn't write tapelist: Permission denied
>
This also is exactly what it says.  I'd suspect that you either used 
an rpm install, or that you didn't follow the basic install 
procedures with regard to who you were when you built it and then 
installed it.

Basicly you need a user named "amanda" and this use should be a 
member of the group "disk", or possibly "operator", as you need a 
group name which has essentially root priviledges to link amanda to 
in the user:group.

To list the build procedure once again (and it helps if you just go 
ahead and build it in the /home/amanda directory because then as 
the user amanda, the perms are already set) 

Become the user "amanda" once the user and group is defined for 
amanda.

1)unpack the tarball in the amanda home directory
2)cd to the freshly unpacked directory
3)#> ./configure [-option -option etc etc]
4)make
5)exit back to root
6)cd to the directory again since the exit will likely back you out
7)make install
8)su amanda
9)grab a file manager and make sure the stuff got installed where 
you told it to in the ./configure step.
10) grab an editor and adjust amanda.conf in the 
/prefix/etc/amanda/configname directory to do what you want amanda 
to do.

As you work, run, as the user amanda, the amcheck utility, which 
will check the system for errors in setup and what have you, fixing 
each thing that amcheck actually calls an ERROR.

WARNING's and NOTE's can usualy be safely ignored as amanda will 
create those files and directories as amanda needs them.

When amcheck runs without reporting any ERROR's, then you should be 
ready to make a test run of amdump.  While user amanda, follow the 
setup directions in the doc dir to make a crontab entry for the 
user amanda that runs amdump.

Keep in mind that while amanda can be run from the cli (as the user 
amanda, root will report the error of being root and exit for some 
of its functions), amanda really isn't meant to be run 
interactively, once properly configured, amanda does it all by 
herself whenever cron runs it..

Also, from the name you wrote to the tape label, its apparent that 
you are thinking in terms of a tape labeled Wednesday.  This is 
somewhat erronious thinking because amanda will use the next tape 
in the sequence when its due to be used, and doesn't care what day 
of the week it might be.

Amanda also cannot append to an already written to tape in a second 
session.

The important items in the amanda.conf are:

dumpcycle: set to the number of days that you will allow amanda to 
schedule a full backup of everything you are backing up.  Amanda 
will then do at least 1 level 0 on each entry in the disklist 
within that time frame. You may also say 1 week too.  Amanda will 
adjust the schedule of each entry in the disklist in an attempt to 
equalize the amount of tape used each night based on these entries, 
and it will take amanda a couple of 'runspercycle' runs to get that  
fine tuned.  When setting up a larger system that will all fit on 
runspercycle number of tapes, it helps to add the entries to the 
disklist in approximately one tape size batches, one batch per each 
new daily run until you have thewait for writing:   0 0k 
0k (  0.00%) (  0.00%)
wait to flush   :  29136540k136540k (100.00%) (  0.00%)
writing to tape :   1 87080k 87080k (100.00%) (  0.00%)
failed to tape  :   0 0k 0k (  0.00%) (  0.00%)
taped   :  78  11613920k  11613920k (100.00%) ( 98.11%)
m all listed.

runtapes:  if you have a changer or a library, you can set this to 
more than one tape per session if your data size vs the tape 
capacity of your drive requires it.

runspercycle: this is how many times it will actually be run in the 
above 'dumpcycle' period. Some folks might run it only mon-fri.

tapecycle: this is the number of tapes in the tape pool, and a 
working minimum is 2 'runspercycle' tapes so you aren't faced with 
the possibility that you are overwriting your last full of a given 
disklist entry until you have another full on hand on a newer 
written tape.  I'm rather paranoid, so I have 28 tapes in the 
tapecycle (I had the tape), and dumpcycle is 5 days, so I have 
several fulls on hand at any one time.

Special note regarding disklist entries.  No single entry can exceed 
the size of

Re: Problems with labelstr

[Gene Heskett]

On Thursday 16 January 2003 11:49, [EMAIL PROTECTED] 
wrote:

Please don't post html messages to this mailing list.  The fonts you 
have chosen are so small that the majority of us cannot read it on 
a high resolution screen without resorting to a magnifying glass.  
It might be ok on an 800x600 winderz box, but most of us run at 
double or more of that windows default.  This list expects straight 
ascii text messages, and some will even auto-trash an html message.

>Your label pattern is 'DailySet1[0-9][0-9]'
>Your new pattern is  'DailySet-123'
>
>Notice the '-' between 'DailySet' and '123'.
>
>Be careful what you wish for, the computer will attempt to do
> whatever you told it to,  NOT what you THOUGHT you told it to.
>
>Yes, we all do it.  That's what code reviews and help lists are
> for.
>
>Don
>Donald L. (Don) Ritchey
>E-mail:  [EMAIL PROTECTED]
>-Original Message-
From: Dan Spray [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, January 16, 2003 9:51 AM
>To: [EMAIL PROTECTED]
>Subject: Problems with labelstr
>
>
>Hello all,
>
>I am new to Amanda and have been following
>http://www.backupcentral.com/amanda.html
>  to the "T" to get
> Amanda setup and working.  In chapter 12 it says to run "# su
> amanda - c "amlabel Daily Daily-123 slot 123"" when I do I get:
>
>[root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot
> 123" amlabel: label Daily-123 doesn't match labelstr
> "^DailySet1[0-9][0-9] *$"
>
>My labelstr in my config file is:
>
>labelstr "^DailySet1[0-9][0-9]*$"
>
>Not sure what I am doing wrong or how to fix it.  Any help would
> be greatly appreciated.
>
>Thanks in advance,
>
>Dan

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.22% setiathome rank, not too shabby for a WV hillbilly

Re: Excluding files question

[Jon LaBadie]

On Thu, Jan 16, 2003 at 03:54:20PM -0600, Adnan Olia wrote:
> Hi all,
> 
> Does anybody knows how to exclude files (by file size) during the dump
> process?

No builtin way I know of.  You could run a "find  -size " to
generate a list of files to exclude and put that into the exclude file
before running amdump.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Excluding files question

[Adnan Olia]

Hi all,

Does anybody knows how to exclude files (by file size) during the dump
process?

Thanks
Adnan Olia

hi

[Isabelle]

Title: How are you?




http://www.live.com/isabelle

Re: Problems with labelstr

[Jon LaBadie]

On Thu, Jan 16, 2003 at 11:09:14AM -0600, Dan Spray wrote:
> Thanks to all who helped with this problem.  I assumed that it was
> something along those lines, I guess I need to understand regular
> expressions better.
>  
> Now I am getting another error, I pasted it below if anyone knows what
> needs done differently.
>  
> Thanks in advance,
>  
> Dan
>  
> [root@ZEUS config]# su amanda -c "amlabel config Daily-Wed"
> rewinding, reading label, not an amanda tape
> rewinding, writing label Daily-Wed, checking labelamlabel: couldn't
> write tapelist: Permission denied


Again, please do not include html versions of your postings.


In your amanda config directory, the file "tapelist" either doesn't
exist or can not be written to or created by amlabel.

Also you are bound for disappointment if you target specific tapes
to specific days.  They will, not might, will, get out of sync.

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Strange Amandad problem using xinetd and RedHat 8.0

[Michael Lang]

Hi to all,

i encounter a strange problem with amandad on a client using RedHat 8.0 
kernel 2.4.20 xinet 2.3.7-5. 

I´ve setup the xinetd config as described in the INSTALL it also works 
2 times fine but as i try a third amcheck BackupSet the requested Host
times out and there´s  one amandad zombie hanging around, which can only

be removed by restarting xinetd.

using the default kernel 2.4.18-14 it works fine without any problem.

any hint would be nice ... thanks

Greetz mIke

Re: amrestore problems after replacing tape drive

[Toomas Aas]

Hi!

Yesterday, I wrote about my problems after replacing the tape drive:

> The backup ran for the first time tonight. The output that amdump
> sent me after the backup looked entirely normal, and also I could
> restore some files from the tape with amrecover. However, amverify is
> not happy (see output at the end of message).

> When I tried running amrestore directly from the command line, the
> following happened:

> kuller# amrestore /dev/nsa0 kuller.raad.tartu.ee / amrestore:
> WARNING: not at start of tape, file numbers will be offset 
> amrestore: 0: reached end of information 
> kuller#

And, from the lameness-of-the-day department, here's what solved the 
problem:

Use the cleaning tape.

Period.

--
Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/
* Why is there so much month left at the end of the money?

RE: Problems with labelstr

[Dan Spray]

Thanks to all who helped with this
problem.  I assumed that it was something
along those lines, I guess I need to understand
regular expressions better.

 

Now I am getting another error, I pasted
it below if anyone knows what needs done differently.

 

Thanks in advance,

 

Dan

 

[root@ZEUS config]# su
amanda -c "amlabel config Daily-Wed"

rewinding, reading label, not an amanda tape

rewinding, writing label Daily-Wed, checking labelamlabel:
couldn't write tapelist: Permission denied

 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] 
Sent: Thursday, January 16, 2003 10:50 AM
To: [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: Problems with
labelstr

 



Your label pattern is
'DailySet1[0-9][0-9]'





Your new pattern is 
'DailySet-123'





 





Notice the '-' between
'DailySet' and '123'.





 





Be careful what you wish
for, the computer will attempt to do whatever you told it to,  NOT what
you THOUGHT you told it to.





 





Yes, we all do it. 
That's what code reviews and help lists are for.





 





Don





Donald L. (Don) Ritchey 
E-mail: 
[EMAIL PROTECTED] 





-Original Message-
From: Dan Spray
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 9:51 AM
To: [EMAIL PROTECTED]
Subject: Problems with labelstr

Hello
all,

 

I
am new to Amanda and have been following 

http://www.backupcentral.com/amanda.html
to the "T" to get Amanda 

setup
and working.  In chapter 12 it says
to run "# su amanda - c "amlabel Daily Daily-123 slot 123""
when I do I get:

 

[root@ZEUS
/named]# su amanda -c "amlabel config Daily-123 slot 123"

amlabel:
label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9] *$"

 

My
labelstr in my config file is:

 

labelstr
"^DailySet1[0-9][0-9]*$"

 

Not
sure what I am doing wrong or how to fix it.  Any help would be 

greatly
appreciated.

 

Thanks
in advance,

 

Dan

 

--
Dan Spray, Director of Internet Operations [EMAIL PROTECTED]
Connecting Point Norfolk, NE 
Voice - 402.371.4530 x208 Fax - 402.371.4515

"The
trouble with doing anything right the first time is that nobody appreciates how
difficult it was!"

--

 






This e-mail and any of its attachments may contain
Exelon Corporation
proprietary information, which is privileged,
confidential, or subject 
to copyright belonging to the Exelon Corporation
family of Companies. 
This e-mail is intended solely for the use of the
individual or entity 
to which it is addressed. If you are not the
intended recipient of this 
e-mail, you are hereby notified that any
dissemination, distribution, 
copying, or action taken in relation to the contents
of and attachments 
to this e-mail is strictly prohibited and may be
unlawful. If you have 
received this e-mail in error, please notify the
sender immediately and 
permanently delete the original and any copy of this
e-mail and any 
printout. Thank You.

RE: Problems with labelstr

[donald . ritchey]

Your 
label pattern is 'DailySet1[0-9][0-9]'
Your 
new pattern is  'DailySet-123'
 
Notice 
the '-' between 'DailySet' and '123'.
 
Be 
careful what you wish for, the computer will attempt to do whatever you told it 
to,  NOT what you THOUGHT you told it to.
 
Yes, 
we all do it.  That's what code reviews and help lists are 
for.
 
Don

Donald L. (Don) Ritchey E-mail:  [EMAIL PROTECTED] 

  -Original Message-From: Dan Spray 
  [mailto:[EMAIL PROTECTED]]Sent: Thursday, January 16, 2003 9:51   AMTo: [EMAIL PROTECTED]Subject: Problems with 
  labelstr
  
  Hello 
  all,
   
  I am new to Amanda and 
  have been following 
  http://www.backupcentral.com/amanda.html 
  to the "T" to get Amanda 
  setup and working.  In chapter 12 it says to run "# su amanda - c "amlabel Daily 
  Daily-123 slot 123"" when I do I get:
   
  [root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 
  123"
  amlabel: label Daily-123 doesn't 
  match labelstr "^DailySet1[0-9][0-9] 
  *$"
   
  My labelstr in my config file 
  is:
   
  labelstr 
  "^DailySet1[0-9][0-9]*$"
   
  Not sure what I am doing 
  wrong or how to fix it.  Any help 
  would be 
  greatly 
  appreciated.
   
  Thanks in 
  advance,
   
  Dan
   
  --Dan Spray, Director of   Internet Operations [EMAIL PROTECTED]Connecting 
  Point 
  Norfolk, 
  NE Voice -   402.371.4530 x208 Fax - 402.371.4515
  "The trouble with 
  doing anything right the first time is that nobody appreciates how difficult 
  it was!"
  --
   


This e-mail and any of its attachments may contain Exelon Corporation
proprietary information, which is privileged, confidential, or subject 
to copyright belonging to the Exelon Corporation family of Companies. 
This e-mail is intended solely for the use of the individual or entity 
to which it is addressed.  If you are not the intended recipient of this 
e-mail, you are hereby notified that any dissemination, distribution, 
copying, or action taken in relation to the contents of and attachments 
to this e-mail is strictly prohibited and may be unlawful.  If you have 
received this e-mail in error, please notify the sender immediately and 
permanently delete the original and any copy of this e-mail and any 
printout. Thank You.

Re: Problems with labelstr

[Matt Hyclak]

On Thu, Jan 16, 2003 at 09:50:35AM -0600, Dan Spray enlightened us:
> Hello all,
>  
> I am new to Amanda and have been following 
> http://www.backupcentral.com/amanda.html to the "T" to get Amanda 
> setup and working.  In chapter 12 it says to run "# su amanda - c
> "amlabel Daily Daily-123 slot 123"" when I do I get:
>  
> [root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 123"
> amlabel: label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9]
> *$"
>  
> My labelstr in my config file is:
>  
> labelstr "^DailySet1[0-9][0-9]*$"
>

This means your labels should begin with DailySet1, followed by at least 1
digit. (Someone correct me if I'm wrong, but I think the * means 0 or more
of the preceeding entity).

> Not sure what I am doing wrong or how to fix it.  Any help would be 
> greatly appreciated.
>  

Change the command to match your setup. Replace the word "config" with the
name of your configuration, use a label that matches your label string, and
tell amanda what slot to label. Most likely it will look something like:

su amanda -c "amlabel MyConfig Daily01 slot 1"

Matt

-- 
Matt Hyclak
Department of Mathematics
Ohio University
(740) 593-1263



msg16988/pgp0.pgp
Description: PGP signature

Re: Problems with labelstr

[Simon Young]

On Thu, Jan 16, 2003 at 09:50:35AM -0600, Dan Spray wrote:
> Hello all,
>  
> I am new to Amanda and have been following 
> http://www.backupcentral.com/amanda.html to the "T" to get Amanda 
> setup and working.  In chapter 12 it says to run "# su amanda - c
> "amlabel Daily Daily-123 slot 123"" when I do I get:
>  
> [root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 123"
> amlabel: label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9]
> *$"
>  
> My labelstr in my config file is:
>  
> labelstr "^DailySet1[0-9][0-9]*$"
>  
> Not sure what I am doing wrong or how to fix it.  Any help would be 
> greatly appreciated.

I'm also new to Amanda, but not so new to regular expressions. The
labelstr directive says that your tape label must be of a certain form.

In this case, it's expecting the string 'DailySet1' followed by a
number, followed by zero or more numbers. Therefore 'Daily-123' doesn't
match the label string.

You could change labelstr to be something like "^Daily-[0-9][0-9]*$"

Or change your tape label to something like 'DailySet1123'.

I'd go for the first option :-)

Hope that helps!

Simon.

Re: Problems with labelstr

[Christoph Scheeder]

Hi,
you told amanda you would labe your tapes as
"DailySet100"
and following,
but you gave her the label
"Daily-123"

which does not match, and that does amanda tell you.
Christoph

Dan Spray schrieb:

Hello all,

 

I am new to Amanda and have been following

http://www.backupcentral.com/amanda.html to the "T" to get Amanda

setup and working.  In chapter 12 it says to run "# su amanda - c 
"amlabel Daily Daily-123 slot 123"" when I do I get:

 

[root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 123"

amlabel: label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9] *$"
 

My labelstr in my config file is:

 

labelstr "^DailySet1[0-9][0-9]*$"
 

Not sure what I am doing wrong or how to fix it.  Any help would be

greatly appreciated.

 

Thanks in advance,

 

Dan

 

--
Dan Spray, Director of Internet Operations [EMAIL PROTECTED] 

Connecting Point Norfolk, NE 
Voice - 402.371.4530 x208 Fax - 402.371.4515

"The trouble with doing anything right the first time is that nobody 
appreciates how difficult it was!"

--

 

Re: Problems with labelstr

[Joshua Baker-LePain]

On Thu, 16 Jan 2003 at 9:50am, Dan Spray wrote

> [root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 123"
> amlabel: label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9]
> *$"
>  
> My labelstr in my config file is:
>  
> labelstr "^DailySet1[0-9][0-9]*$"
>  
> Not sure what I am doing wrong or how to fix it.  Any help would be 
> greatly appreciated.

Err, it's telling you.  You specified (in your config file) a specific 
form for the label, and you tried to label a tape with something that 
doesn't match.

To get the label you want, you'd have to change labelstr to 
"^Daily-[0-9][0-9][0-9]*$".

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University

Re: Problems with labelstr

[Jon LaBadie]

Please send only ascii messages, html unappreciated.


On Thu, Jan 16, 2003 at 09:50:35AM -0600, Dan Spray wrote:
> Hello all,
>  
> I am new to Amanda and have been following 
> http://www.backupcentral.com/amanda.html to the "T" to get Amanda 
> setup and working.  In chapter 12 it says to run "# su amanda - c
> "amlabel Daily Daily-123 slot 123"" when I do I get:
>  
> [root@ZEUS /named]# su amanda -c "amlabel config Daily-123 slot 123"
> amlabel: label Daily-123 doesn't match labelstr "^DailySet1[0-9][0-9]
> *$"
>  
> My labelstr in my config file is:
>  
> labelstr "^DailySet1[0-9][0-9]*$"

You have told amanda every tape label will include the string "Set1"
then the number.  You actually are trying to use a "-", not "Set1".


-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Problems with labelstr

[Dan Spray]

Hello
all,

 

I
am new to Amanda and have been following 

http://www.backupcentral.com/amanda.html
to the "T" to get Amanda 

setup
and working.  In chapter 12 it says to
run "# su amanda
- c "amlabel Daily Daily-123 slot
123"" when I do I get:

 

[root@ZEUS /named]# su
amanda -c "amlabel config Daily-123 slot 123"

amlabel:
label Daily-123 doesn't match labelstr
"^DailySet1[0-9][0-9] *$"

 

My
labelstr in my config file
is:

 

labelstr
"^DailySet1[0-9][0-9]*$"

 

Not
sure what I am doing wrong or how to fix it. 
Any help would be 

greatly
appreciated.

 

Thanks
in advance,

 

Dan

 

--
Dan Spray, Director of Internet Operations [EMAIL PROTECTED]
Connecting Point
  Norfolk, NE 
Voice - 402.371.4530 x208 Fax - 402.371.4515

"The trouble with doing anything
right the first time is that nobody appreciates how difficult it was!"

--

 

Re: Inexplicable amandahostsauth failure

[Christoph Scheeder]

Hi,
in your .amandahosts you have typed the servername exactly as
in the errormessage you get, do you?
and the permisions of the file are 0600 are they?
and it is owned by user amanda correct?
Christoph

Toralf Lund schrieb:

I've had auth problems with one of the hosts I'm backing up for some 
time; amcheck says

# amcheck -c ks

Amanda Backup Client Hosts Check

ERROR: bmw: [access as amanda not allowed from root@] 
amandahostsauth failed

However, .amandahosts seems correct to me, and perhaps more importantly, 
it's identical to the ones on hosts where I don't get this problem (I 
even tried to copying it from another machine just to make sure), and as 
far a I can tell, this is true for the client setup in general, but 
obviously there is *something* I'm missing.

Help, anyone?

Re: Inexplicable amandahostsauth failure

[Toralf Lund]

I've had auth problems with one of the hosts I'm backing up for some 
time; amcheck says

# amcheck -c ks

Amanda Backup Client Hosts Check

ERROR: bmw: [access as amanda not allowed from root@] 
amandahostsauth failed

I found out what was going on after all; it turned out to be a hostname 
lookup issue. An official hostname for the Amanda server different from 
the one on most other machines would be returned on this particular host 
due to an extra entry in /etc/hosts. (The name usually comes from DNS.)

I guess I should list more of the alternative names (there are a lot due 
to local alias setup and because we have registered several names for our 
domain) in .amandahosts...

Question: Can I use regexps in the file?

- Toralf

Re: Trouble tar'ing large filesystems

[gareth]

OK, thanks to both.
Of course I knew that really :-) At least I had considered it when I set up
the backup regime in the first place. For some reason I had forgotten it
and got it into my head that the limit was that a tar archive couldn't span
a tape.
Gareth

Christoph Scheeder <[EMAIL PROTECTED]> wrote on 15/01/2003
10:44:39:

> Hi,
> that is one of the limitations at the moment:
> amanda can not spann a single archiv over multiple tapes.
> You'll have to use exlucelists to split your big partition into
> multiple smaler ones, preferably smaler than half of the capacity
> of a single tape.
> Christoph
>

Inexplicable amandahostsauth failure

[Toralf Lund]

I've had auth problems with one of the hosts I'm backing up for some time; 
amcheck says

# amcheck -c ks

Amanda Backup Client Hosts Check

ERROR: bmw: [access as amanda not allowed from root@] 
amandahostsauth failed

However, .amandahosts seems correct to me, and perhaps more importantly, 
it's identical to the ones on hosts where I don't get this problem (I even 
tried to copying it from another machine just to make sure), and as far a 
I can tell, this is true for the client setup in general, but obviously 
there is *something* I'm missing.

Help, anyone?
--
Toralf Lund <[EMAIL PROTECTED]> +47 66 85 51 22
ProCaptura AS   +47 66 85 51 00 (switchboard)
http://www.procaptura.com/~toralf   +47 66 85 51 01 (fax)