DIÞ TÝCARETTE KARÝYER FIRSATI.

2003-11-07 Thread info




D 
Ticarette KARYER Frsat.

Kazan Dolu 
bir dnyann Kaplar SZLER iin Alyor.

D Ticarete ADIM Atmaya 

H A Z I 
R M I S I N I 
Z ! ! ! ! 

%30'a varan 
NDRMLER


Ayrntl bilgi iin:0(212) 347 28 
20



INTERACADEMY
D 
Ticaret Eitim i ve 
Danmanlk



info@interacademy.net
Gazeteciler Sitesi Matbuat Sk.No:2 
Esentepe/L.




Re: amcheck timeout - dgram_recv timeouts...

2003-11-07 Thread Martin

 Yes, I used to have the same problem. However, one day the problem
 disappeared and left me wondering what the cause of the problem was.
Haven't
 had any trouble since. Are you backing up to disk or tape? inetd.conf?
 services file?
 I remember updating TAR on one of the machines back then, but I guess that
 is not likely to be the solution

 
  Has anyone seen this error message?
 
  amandad: time 29.994: dgram_recv: timeout after 30
  seconds
  amandad: error receiving message: timeout
  amandad: time 29.994: error receiving message:
  timeout
  amandad: time 29.994: pid 11932 finish time Wed Nov
  09:50:39 2003
 
  Amanda 2.3.4b on Linux
 
  Thanks in advance!
  Michael
 
 
  __
  Do you Yahoo!?
  Protect your identity with Yahoo! Mail AddressGuard
  http://antispam.yahoo.com/whatsnewfree
 
 





Re: amcheck fails

2003-11-07 Thread Christoph Brunner
Am Donnerstag, 6. November 2003 17:31 schrieben Sie:
 On Thu, 6 Nov 2003 at 5:04pm, Christoph Brunner wrote

   Is there a firewall on this box?  What are the settings?  Are TCP
   wrappers getting in the way?  If you watch the traffic during the
   amcheck, what do you see?
 
  The firewall is already offline.
 
  Here is a tcpdump-listing during amcheck, but i do not really understand
  the output, so please say, if you expected something different (i have
  replaced the ips with names)
  ==
  tcpdump: listening on eth0
  16:41:58.661929 backup03m.658  zulu.10080: udp 117 (DF)
  16:41:58.669527 zulu.10080  backup03m.658: udp 50 (DF)
  16:41:58.670657 zulu.10080  backup03m.658: udp 83 (DF)
  16:41:58.670757 backup03m.658  zulu.10080: udp 50 (DF)
  16:41:58.682902 backup03m.658  zulu.10080: udp 201 (DF)
  16:41:58.690293 zulu.10080  backup03m.658: udp 50 (DF)
  16:41:58.725535 zulu.10080  backup03m.658: udp 414 (DF)
  16:41:58.725615 backup03m.658  zulu.10080: udp 50 (DF)
 
  backup03m is both the host amanda is running on and a backup client
  (which does not work, amcheck says 'host down'), zulu is a backup client
  that works.

 The first line says that backup03m sent a UDP packet from port 658 (a
 priviledged port) to port 10080 (the standard amanda listening port) on
 zulu.  zulu responds with a couple of of packets, and then they have some
 more conversation.

 Try again doing a tcpdump on the loopback device (lo on my box).  That's
 where traffic to the backup host itself will go.

Hi,

a tcpdump on the loopback device says:
=
tcpdump: listening on lo
10:40:45.589797 backup03m.1008  backup03m.10080: udp 117 (DF)
10:40:55.482650 backup03m.1008  backup03m.10080: udp 117 (DF)
10:41:05.482671 backup03m.1008  backup03m.10080: udp 117 (DF)

6 packets received by filter
0 packets dropped by kernel
=

Shouldn't there be responds from port 10080 to 1008?

Nice greetings,
Christoph



Re: amcheck fails

2003-11-07 Thread Joshua Baker-LePain
On Fri, 7 Nov 2003 at 10:45am, Christoph Brunner wrote

 a tcpdump on the loopback device says:
 =
 tcpdump: listening on lo
 10:40:45.589797 backup03m.1008  backup03m.10080: udp 117 (DF)
 10:40:55.482650 backup03m.1008  backup03m.10080: udp 117 (DF)
 10:41:05.482671 backup03m.1008  backup03m.10080: udp 117 (DF)
 
 6 packets received by filter
 0 packets dropped by kernel
 =
 
 Shouldn't there be responds from port 10080 to 1008?

Yep.  Which tells me that amandad isn't listening *or* is refusing the 
connection.  What distro is this?  What does 'netstat -l | grep amanda' 
say?  Are you using inetd or xinetd?  If the latter, what's in 
/etc/hosts.{deny,allow}?

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




Re: Getting AMANDA stats without e-mail

2003-11-07 Thread Brian Cuttler
Bob,

I'd never heard that - nor has it been a problem at my site where we
do run sendmail - clients (non-hub) on all but one amanda server.

We have also run an amanda server on our mailhub with no difficulty.

The one exception I meantioned above is for a firewall system backing
up the clients (itself plus one in dmz) but not transmitting any mail
by choice of our security admin who didn't want any mail leaving the dmz.
ie: That is not because of amanda issues.

Is this just something you where told or have you run into a difficulty
and if so, what ?



 I've been told that I can not run sendmail or any mail system on the Sun 
 Solaris server that I run the Amanda server on. Does anyone know how I 
 can get the reports that I have normally sent to root's e-mail system 
 some other way? Is their an option to getting the e-mails like in a 
 report file? I know that I can put another e-mail address in the 
 amanda.conf file. But, without sendmail running on my solaris system I 
 have no way of sending it to another e-mail system. I think the e-mail 
 will just hang in the mqueue folder until I delete it. Thanks.
 Bob...
 
 -- 
 **
 Bob Zahn UNIX Systems Adminstrator Oklahoma City Community College
 [EMAIL PROTECTED] 405.682.1611.7619   S. May Avenue
 [EMAIL PROTECTED]   Oklahoma City, OK 73159
 **
 
 



Re: Getting AMANDA stats without e-mail

2003-11-07 Thread Dan Lorenzini

I think they may be disallowing sendmail to comply with a security
policy.  Using amreport to generate the report and leave it in a file
is an acceptable alternative.  We do this in addition to sending mail.

Dan Lorenzini   Greenwich Capital Markets
[EMAIL PROTECTED]   600 Steamboat Road
203-625-6088Greenwich, CT 06830



Your message dated: Fri, 07 Nov 2003 09:44:11 EST

 Bob,
 
 I'd never heard that - nor has it been a problem at my site where we
 do run sendmail - clients (non-hub) on all but one amanda server.
 
 We have also run an amanda server on our mailhub with no difficulty.
 
 The one exception I meantioned above is for a firewall system backing
 up the clients (itself plus one in dmz) but not transmitting any mail
 by choice of our security admin who didn't want any mail leaving the dmz.
 ie: That is not because of amanda issues.
 
 Is this just something you where told or have you run into a difficulty
 and if so, what ?
 
 
 
  I've been told that I can not run sendmail or any mail system on the Sun 
  Solaris server that I run the Amanda server on. Does anyone know how I 
  can get the reports that I have normally sent to root's e-mail system 
  some other way? Is their an option to getting the e-mails like in a 
  report file? I know that I can put another e-mail address in the 
  amanda.conf file. But, without sendmail running on my solaris system I 
  have no way of sending it to another e-mail system. I think the e-mail 
  will just hang in the mqueue folder until I delete it. Thanks.
  Bob...
  
  -- 
  **
  Bob Zahn UNIX Systems Adminstrator Oklahoma City Community College
  [EMAIL PROTECTED]   405.682.1611.7619   S. May Avenue
  [EMAIL PROTECTED]   Oklahoma City, OK 73159
  **
  
  
 


Re: amcheck fails

2003-11-07 Thread Christoph Brunner
Am Freitag, 7. November 2003 15:38 schrieben Sie:
 On Fri, 7 Nov 2003 at 10:45am, Christoph Brunner wrote

  a tcpdump on the loopback device says:
  =
  tcpdump: listening on lo
  10:40:45.589797 backup03m.1008  backup03m.10080: udp 117 (DF)
  10:40:55.482650 backup03m.1008  backup03m.10080: udp 117 (DF)
  10:41:05.482671 backup03m.1008  backup03m.10080: udp 117 (DF)
 
  6 packets received by filter
  0 packets dropped by kernel
  =
 
  Shouldn't there be responds from port 10080 to 1008?

 Yep.  Which tells me that amandad isn't listening *or* is refusing the
 connection.  What distro is this?  What does 'netstat -l | grep amanda'
 say?  Are you using inetd or xinetd?  If the latter, what's in
 /etc/hosts.{deny,allow}?

Hi,

netstat says:

tcp0  0 *:amandaidx *:* LISTEN
udp0  0 *:amanda*:*


Distribution is Gentoo Linux 1.4.
I'm using xinetd, /etc/hosts.{deny,allow} doesn't exist.

Any ideas?

Nice greetings,
Christoph



Re: amcheck fails

2003-11-07 Thread Joshua Baker-LePain
On Fri, 7 Nov 2003 at 3:54pm, Christoph Brunner wrote

 netstat says:
 
 tcp0  0 *:amandaidx *:* LISTEN
 udp0  0 *:amanda*:*
 
 
 Distribution is Gentoo Linux 1.4.
 I'm using xinetd, /etc/hosts.{deny,allow} doesn't exist.

As Jon asked, what's in /tmp/amanda/selfcheck*debug after a failed amcheck 
run?  Actually, what files get greated in /tmp/amanda when you do amcheck, 
and what are their contents?

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




bedava domain (www.isminiz.ws.tc + 10 MB webalani+ 50 mb Trafik)

2003-11-07 Thread [EMAIL PROTECTED]
Title: Türkiye




Türkiye´de ilk !! 



Yönlendirme deil
!! 



Tamamen size ait
domain (www.isminiz.ws.tc), 
10 mb web
alan, 50 mb trafik !! 


Kiisel
ve kurumsal web sitenizi, ksa ve aklda kalc bir internet adresi ve 10 mb
webalann ücret ödemeden, annda kurabilirsiniz.



1x www.isminiz.ws.tc
(* Üstelik sadece 0.00 $)!!

10 MB Web alan (*
Üstelik sadece 0.00 $)!!

50 mb Trafik (*
Üstelik sadece 0.00 $)!!


www.domain.ws.tc



  

Network recovery with changer

2003-11-07 Thread Stephen Walton
Setup:  all RedHat 8 shop, Amanda 2.4.4p1 locally compiled, HP DAT-4
changer on server, some files which need to be recovered to client. 
ambackup runs fine on server: amverify as well as manual 'tar -tzvf'
shows that the backups are fine.  amrecover on server successfully runs
and restores files to the server.

I start amrecover on client in the usual way;  add and extract. 
amrecover tells me I need tape 1.  ssh to server, use amtape to manually
load tape needed.  Tell amrecover to continue with extraction. 
amrecover gives following answer:

 Continue [?/Y/n/s/t]? y
 EOF, check amidxtaped.debug file on server.
 amrecover: short block 0 bytes

Checking amidxtaped.debug file on server shows it believes
amdump/amrecover to be running because /var/opt/amanda/daily/log
exists.  Well, of course it does, and it contains the single line

 INFO amidxtaped amidxtaped

Quitting amrecover causes the creation of an amindexd.debug file in
/tmp/amanda which contains a list of the contents of the desired backup
file on the correct tape.  So what is going on here?  

On a related topic, and one which I've searched in vain on the
FAQ-O-Matic and every place else for the answer:  what exactly do I put
in amanda.conf to have amrecover automatically change to the correct
tape?
-- 
Stephen Walton [EMAIL PROTECTED]
Dept. of Physics  Astronomy, Cal State Northridge



Re: Network recovery with changer

2003-11-07 Thread Jon LaBadie
On Fri, Nov 07, 2003 at 09:22:49AM -0800, Stephen Walton wrote:
 
 On a related topic, and one which I've searched in vain on the
 FAQ-O-Matic and every place else for the answer:  what exactly do I put
 in amanda.conf to have amrecover automatically change to the correct
 tape?


Did you check the amanda man page?

Mine shows these that I've not used but I think are what you seek.


 amrecover_do_fsf bool
  Default:  off.  Amrecover will call amrestore with  the
  -f flag for faster positioning of the tape.

 amrecover_check_label bool
  Default:  off.  Amrecover will call amrestore with  the
  -l flag to check the label.

 amrecover_changer string
  Default: ''.  Amrecover will use the changer if you use
  'settape  STRING'  and that string is the same as the
  amrecover_changer setting.


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


Re: Getting AMANDA stats without e-mail

2003-11-07 Thread Paul Bijnens
Dan Lorenzini wrote:

I think they may be disallowing sendmail to comply with a security
policy.  Using amreport to generate the report and leave it in a file
is an acceptable alternative.  We do this in addition to sending mail.
I hope you all are aware than SENDING mail is a complete different
thing than receiving mail.  You don't need to have a sendmail daemon
running to send mail:  it can be invoked by the mailer program just
to send the mail.  It will never listen to port 25 for receiving mail.
But stupid policies do exist, yes, I know.

--
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  *
***



client timing out

2003-11-07 Thread C. Wilson
I have not been able to get a backup of one of my amanda clients for 3
days. The only errors I can find is in the
amandad.20031104013547000.debug, which are:

amandad: time 7453.715: dgram_recv: timeout after 10 seconds
amandad: time 7453.715: waiting for ack: timeout, retrying
amandad: time 7463.715: dgram_recv: timeout after 10 seconds
amandad: time 7463.715: waiting for ack: timeout, retrying
amandad: time 7473.715: dgram_recv: timeout after 10 seconds
amandad: time 7473.715: waiting for ack: timeout, retrying
amandad: time 7483.715: dgram_recv: timeout after 10 seconds
amandad: time 7483.715: waiting for ack: timeout, retrying
amandad: time 7493.715: dgram_recv: timeout after 10 seconds
amandad: time 7493.715: waiting for ack: timeout, giving up!
amandad: time 7493.715: pid 4331 finish time Tue Nov  4 03:40:41 2003

I've searched the FAQ which suggested that I increase the ctimeout value
in the amanda.conf file. I increased the value from 30 to 120 on the
Amanda server, but it's still timing out. 

Should I keep increasing the ctimeout value until I find the magic
number or is there anything else I should be looking at?

Thanks in advance,

CWilson


Re: client timing out

2003-11-07 Thread Paul Bijnens
C. Wilson wrote:

I have not been able to get a backup of one of my amanda clients for 3
days. The only errors I can find is in the
amandad.20031104013547000.debug, which are:


You left out the noop request just before, I believe.

amandad: time 7453.715: dgram_recv: timeout after 10 seconds
amandad: time 7453.715: waiting for ack: timeout, retrying
amandad: time 7463.715: dgram_recv: timeout after 10 seconds
amandad: time 7463.715: waiting for ack: timeout, retrying
amandad: time 7473.715: dgram_recv: timeout after 10 seconds
amandad: time 7473.715: waiting for ack: timeout, retrying
amandad: time 7483.715: dgram_recv: timeout after 10 seconds
amandad: time 7483.715: waiting for ack: timeout, retrying
amandad: time 7493.715: dgram_recv: timeout after 10 seconds
amandad: time 7493.715: waiting for ack: timeout, giving up!
amandad: time 7493.715: pid 4331 finish time Tue Nov  4 03:40:41 2003
I've searched the FAQ which suggested that I increase the ctimeout value
in the amanda.conf file. I increased the value from 30 to 120 on the
Amanda server, but it's still timing out. 
This is just a symptom that the the computer never received an ack
packet.  Something in the netwrok setup?  (is the computer replying
to the correct server?  multiple Network card?  Firewall blocking?
etc. etc.)
Increasing the ctimeout will not help.
--
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: client timing out

2003-11-07 Thread C. Wilson
Paul Bijnens wrote:
 
 C. Wilson wrote:
 
  I have not been able to get a backup of one of my amanda clients for 3
  days. The only errors I can find is in the
  amandad.20031104013547000.debug, which are:
 
 You left out the noop request just before, I believe.
 
 
  amandad: time 7453.715: dgram_recv: timeout after 10 seconds
  amandad: time 7453.715: waiting for ack: timeout, retrying
  amandad: time 7463.715: dgram_recv: timeout after 10 seconds
  amandad: time 7463.715: waiting for ack: timeout, retrying
  amandad: time 7473.715: dgram_recv: timeout after 10 seconds
  amandad: time 7473.715: waiting for ack: timeout, retrying
  amandad: time 7483.715: dgram_recv: timeout after 10 seconds
  amandad: time 7483.715: waiting for ack: timeout, retrying
  amandad: time 7493.715: dgram_recv: timeout after 10 seconds
  amandad: time 7493.715: waiting for ack: timeout, giving up!
  amandad: time 7493.715: pid 4331 finish time Tue Nov  4 03:40:41 2003
 
  I've searched the FAQ which suggested that I increase the ctimeout value
  in the amanda.conf file. I increased the value from 30 to 120 on the
  Amanda server, but it's still timing out.
 
 This is just a symptom that the the computer never received an ack
 packet.  Something in the netwrok setup?  (is the computer replying
 to the correct server?  multiple Network card?  Firewall blocking?
 etc. etc.)
 Increasing the ctimeout will not help.
 
 --
 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  *
 ***
I have two amandad debug files on the client:
amandad.20031107100613000.debug
amandad.20031107100613.debug

The noop is in the amandad.20031107100613.debug file, that has no
errors. The amandad.20031107100613000.debug file is the one with the
timeout errors.

I find no errors in my Amanda server debug files.

There's no firewall and I don't see any evidence that's it's dropping
off the net. It only has one ethernet card and I checked to make sure
the router and the box were set at Full Duplex. No packet loss or
collisions and DNS seems to be working fine.

I'm still confussed on what it can be and how to resolve it.

Thanks for your response,

CWilson


Re: Network recovery with changer

2003-11-07 Thread Stephen Walton
On Fri, 2003-11-07 at 09:33, Jon LaBadie wrote:
 On Fri, Nov 07, 2003 at 09:22:49AM -0800, Stephen Walton wrote:
  
  what exactly do I put
  in amanda.conf to have amrecover automatically change to the correct
  tape?
 
 Did you check the amanda man page?
 
  amrecover_changer string

Thanks for the response, Jon. It turns out that both questions I asked
(why was amrecover failing and how to get it to work with the changer)
are related.  I found by experiment that I have to settape /dev/nst0
in amrecover before it will work, and then also manually load the tape
amrecover says it needs.

I do know of the amrecover_changer parameter, and it is set to
/dev/nst0in my amanda.conf, but amrecover still does not change
tapes.  The relevant lines from my configuration are

tpchanger chg-scsi
tapedev 0
changerfile /etc/opt/amanda/daily/chg-scsi-compaq.conf
amrecover_changer /dev/nst0

This does not work with amrecover but I'm unable to find a combination
which does.
-- 
Stephen Walton [EMAIL PROTECTED]
Dept. of Physics  Astronomy, Cal State Northridge



Re: Network recovery with changer

2003-11-07 Thread Jon LaBadie
On Fri, Nov 07, 2003 at 01:27:28PM -0800, Stephen Walton wrote:
 On Fri, 2003-11-07 at 09:33, Jon LaBadie wrote:
  On Fri, Nov 07, 2003 at 09:22:49AM -0800, Stephen Walton wrote:
   
   what exactly do I put
   in amanda.conf to have amrecover automatically change to the correct
   tape?
  
  Did you check the amanda man page?
  
   amrecover_changer string
 
 Thanks for the response, Jon. It turns out that both questions I asked
 (why was amrecover failing and how to get it to work with the changer)
 are related.  I found by experiment that I have to settape /dev/nst0
 in amrecover before it will work, and then also manually load the tape
 amrecover says it needs.
 
 I do know of the amrecover_changer parameter, and it is set to
 /dev/nst0in my amanda.conf, but amrecover still does not change
 tapes.  The relevant lines from my configuration are
 
 tpchanger chg-scsi
 tapedev 0
 changerfile /etc/opt/amanda/daily/chg-scsi-compaq.conf
 amrecover_changer /dev/nst0
 
 This does not work with amrecover but I'm unable to find a combination
 which does.

As I noted, I've not used them.

However I would not except your string /dev/nst0 to be what
it is looking for when the parameter name is ... changer.
That is your tape drive isn't it?

Perhaps the value it wants is the device of your changer,
but I suspect that is in the *.conf file.  So maybe it is
the changer script name?  Looks like yours is chg-scsi-compaq.

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


Will Amanda work with Qualstar TLS-5433 SAIT library

2003-11-07 Thread Fran Fabrizio








Our group is thinking of purchasing a Qualstar
TLS-5433 SAIT library. From the
documentation Ive read, Amanda supports some, but not all, changers/robots. Will this be a supported model?



Also, the following excerpt from the Amanda chapter of the Unix
Backup And Recovery book has me a bit concerned:



AMANDA supports using more than one tape in a single
run, but does not yet split a dump image across tapes. This also means it does
not support dump images larger than a single tape.



Does not yet split a dump
image across tapes. I assume dump image = one unit
or partition to be backed up. /home
for example. So if /home is larger
than the size of a single tape, do I then need to subdivide /home into say
/home/faculty and /home/students in order to backup successfully? Im just a little fuzzy on what
exactly an image is. (Sorry, new on the job and to sysadmin in general)



Thanks,

Fran








Re: Will Amanda work with Qualstar TLS-5433 SAIT library

2003-11-07 Thread Frank Smith


--On Friday, November 07, 2003 17:44:28 -0600 Fran Fabrizio [EMAIL PROTECTED] wrote:

 Our group is thinking of purchasing a Qualstar TLS-5433 SAIT library.
 From the documentation I've read, Amanda supports some, but not all,
 changers/robots.  Will this be a supported model?
  
I use it on Qualstar TLS4480 and RLS-4445 libraries.  I would imagine
that all their libraries use the same controller, but you could
ask them to be sure.

 Also, the following excerpt from the Amanda chapter of the Unix Backup
 And Recovery book has me a bit concerned:
  
 AMANDA supports using more than one tape in a single run, but does not
 yet split a dump image across tapes. This also means it does not support
 dump images larger than a single tape.
  
 Does not yet split a dump image across tapes.  I assume dump image =
 one unit or partition to be backed up.  /home for example.  So if
 /home is larger than the size of a single tape, do I then need to
 subdivide /home into say /home/faculty and /home/students in order to
 backup successfully?  I'm just a little fuzzy on what exactly an image
 is. (Sorry, new on the job and to sysadmin in general)
An 'image' is a single partition or directory that you want backed up.
Also known on this list a a DLE, or 'disklist entry' since it is one
line in the config file which lists the filesystems to back up.
  Yes, you will need to specify subdirectories if the entire directory
is larger than a tape.  Some people are working on a patch to allow
spanning tapes with a single entry but I don't know how far along
that is.
  Check the archives for ideas on how to use includes and excludes to
split directories while still being sure a new subdirectory will get
backed up.

Frank
 
  
 Thanks,
 Fran



-- 
Frank Smith  [EMAIL PROTECTED]
Systems Administrator   Voice: 512-374-4673
Hoover's Online   Fax: 512-374-4501



Re: Will Amanda work with Qualstar TLS-5433 SAIT library

2003-11-07 Thread Gene Heskett
On Friday 07 November 2003 18:44, Fran Fabrizio wrote:
Our group is thinking of purchasing a Qualstar TLS-5433 SAIT
 library. From the documentation I've read, Amanda supports some,
 but not all, changers/robots.  Will this be a supported model?

Also, the following excerpt from the Amanda chapter of the Unix
 Backup And Recovery book has me a bit concerned:

AMANDA supports using more than one tape in a single run, but does
 not yet split a dump image across tapes. This also means it does
 not support dump images larger than a single tape.

Does not yet split a dump image across tapes.  I assume dump
 image = one unit or partition to be backed up.  /home for
 example.  So if /home is larger than the size of a single tape, do
 I then need to subdivide /home into say /home/faculty and
 /home/students in order to backup successfully?  I'm just a little
 fuzzy on what exactly an image is. (Sorry, new on the job and to
 sysadmin in general)

As an overview, you have it understood ok I think.  The only caveat is 
that dump cannot do a subdir tree.  But tar works just fine provided 
the version is at least 1.13-19, with 1.13-25 being the prefered 
flavor these days.  If your tar --version says its just 1.13, its 
busted, goto ftp.alpha.org and get the newer one.


Thanks,
Fran

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.



Re: Network recovery with changer

2003-11-07 Thread Gene Heskett
On Friday 07 November 2003 16:27, Stephen Walton wrote:
On Fri, 2003-11-07 at 09:33, Jon LaBadie wrote:
 On Fri, Nov 07, 2003 at 09:22:49AM -0800, Stephen Walton wrote:
  what exactly do I put
  in amanda.conf to have amrecover automatically change to the
  correct tape?

 Did you check the amanda man page?

  amrecover_changer string

Thanks for the response, Jon. It turns out that both questions I
 asked (why was amrecover failing and how to get it to work with the
 changer) are related.  I found by experiment that I have to
 settape /dev/nst0 in amrecover before it will work, and then also
 manually load the tape amrecover says it needs.

I do know of the amrecover_changer parameter, and it is set to
/dev/nst0in my amanda.conf, but amrecover still does not change
tapes.  The relevant lines from my configuration are

I believe thats the wrong device, should it not be /dev/sgX?,  where 
the X is derived from your /var/log/dmesg when it discovered the 
changer?

tpchanger chg-scsi
tapedev 0
changerfile /etc/opt/amanda/daily/chg-scsi-compaq.conf
amrecover_changer /dev/nst0

This does not work with amrecover but I'm unable to find a
 combination which does.

-- 
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED]  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.



Ýnternet telefonu

2003-11-07 Thread nettePHONE
Title: NETTEALO.COM








   
 
  
  
 
   

 
   
 
Uzun mesafe telefon 
  
  grmelerinize 
  ok fazla 
  para m dyorsunuz ?
te size sadece 
  100 milyon TRL+KDV 
  gibi bir fiyata sahip olabileceiniz 
  internet telefonu... 
 

  
  

  
  

  



Bu bir bilgilendirme mesaj olup, spam deildir. irketimiz tarafndan tantm amal yollanmtr.Bu tr mesajlar almak istemiyorsanz ltfen buraya tklaynz .






Ýnternet telefonu

2003-11-07 Thread nettePHONE
Title: NETTEALO.COM








   
 
  
  
 
   

 
   
 
Uzun mesafe telefon 
  
  grmelerinize 
  ok fazla 
  para m dyorsunuz ?
te size sadece 
  100 milyon TRL+KDV 
  gibi bir fiyata sahip olabileceiniz 
  internet telefonu... 
 

  
  

  
  

  



Bu bir bilgilendirme mesaj olup, spam deildir. irketimiz tarafndan tantm amal yollanmtr.Bu tr mesajlar almak istemiyorsanz ltfen buraya tklaynz .






() !! !! @

2003-11-07 Thread




 

  

   



 

  ()   .
 .
  . 

 



   

  

 

 

  












 

 

  

   



 

 If you don't want this type of information or e-mail, please click the 'refuse' button.
  []  .

 

 




   
 .
  44-21  10F.  02-786-6614.
  

  

 

 [URL] http://daily.daemonnews.org/view_story.php3?story_id8

Program download ga

2003-11-07 Thread riggprnyp
Title: oexx




  

ProgramDownloadOrg
  
  

Program Download Organizasyonu

ÜCRETSÝZ
TÜRKÇE veya YABANCI
YENÝ ve HÝT VERSÝYONLAR
VÝRÜS ve TROJAN PROGRAMLARI
SON GÜNCELLEMELER
	

9.000 ADET PROGRAM ÝÇÝN TIKLAYIN
	Sizinde iþinize yarayacak bir program vardýr