Re: FreeBSD client

2006-04-29 Thread Toomas Aas

John Clement wrote:

I can't find any documentation on getting the client working on BSD so 
started going by all the information I've gleened troubleshooting the 
Linux machines here.  


Getting the client working on FreeBSD is nothing special :) Just install 
the client (I understand that's already done) and add the amandad entry 
to /etc/inetd.conf.


 I can't find a .amandahosts file, do I need to create this and if so
 where?  Or should this information go somewhere else?

This file needs to be in the home directory of the amanda user (in your 
case, operator). You can find out what this directory is by running

chsh operator.

I believe the default home directory for operator on FreeBSD is /

Generally when installing Amanda on FreeBSD I prefer to not use operator 
but still create a special 'amanda' user and add this user to group 
'operator'. Operator's standard home directory being / is one of the 
reasons - I don't like the idea of amanda files living directly under /. 
The alternative is to change the home directory of operator to somewhere 
else, which I also don't like. I *have* done it on some machines, 
though, and they have been running for several years without problems.


I assume /tmp/amanda should exist on the machine and be writable and 
ownder by operator:operator (operator being the default username the 
client seems to install by, and operator being BSD's equiv of 'disk' 
group), is this so?


Yes. But this directory should be created automatically by Amanda.


C2 Jukebox with LTO3 drive

2006-04-29 Thread Brian Cuttler

Hi y'all,

I'm running Solaris 9 with Amanda 2.4.4 (hoping to find the time
to upgrade soon, but its working great), MTX is v 1.2.17rel

We have been running the data to a StorEdge L9 jukebox with LTO tapes.

We are in process of installing a StorEdge C2 jukebox with an LTO3 tape.

We see the new tape drive at /dev/rmt/2, but do not have a device
file for the jukebox. Quantum says that its just offset by the LUN
number, SUN says to install Legato or Netbackup or something so I
have a passthrough driver.

Have any of you installed this jukebox ? Do I need the additional
software in order to create a proper device file for the jukebox ?

The StorEdge L9 jukebox has a sepate scsi id from its tape drive
and I'm able to see a device in directory /dev/scsi/changer/ but
this is not the case with the C2. I'm uncertain how the L9 changer
device was created.

thank you,

Brian
---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



Re: C2 Jukebox with LTO3 drive

2006-04-29 Thread Jon LaBadie
On Wed, Apr 26, 2006 at 03:22:04PM -0400, Brian Cuttler wrote:
 
 Hi y'all,
 
 I'm running Solaris 9 with Amanda 2.4.4 (hoping to find the time
 to upgrade soon, but its working great), MTX is v 1.2.17rel
 
 We have been running the data to a StorEdge L9 jukebox with LTO tapes.
 
 We are in process of installing a StorEdge C2 jukebox with an LTO3 tape.
 
 We see the new tape drive at /dev/rmt/2, but do not have a device
 file for the jukebox. Quantum says that its just offset by the LUN
 number, SUN says to install Legato or Netbackup or something so I
 have a passthrough driver.
 
 Have any of you installed this jukebox ? Do I need the additional
 software in order to create a proper device file for the jukebox ?
 
 The StorEdge L9 jukebox has a sepate scsi id from its tape drive
 and I'm able to see a device in directory /dev/scsi/changer/ but
 this is not the case with the C2. I'm uncertain how the L9 changer
 device was created.


Check out two files in /kernel/drv, st.conf and sgen.conf.
The st.conf file as supplied does not look at lun's  0.
I think the end of the st.conf file looks like this as supplied.

#---

name=st class=scsi target=0 lun=0;
name=st class=scsi target=1 lun=0;
name=st class=scsi target=2 lun=0;
name=st class=scsi target=3 lun=0;
name=st class=scsi target=4 lun=0;
name=st class=scsi target=5 lun=0;
name=st class=scsi target=6 lun=0;

#
#   In case there are wide tape drives, one can use these targets
#
#name=st class=scsi target=8 lun=0;
#name=st class=scsi target=9 lun=0;
#name=st class=scsi target=10 lun=0;
#name=st class=scsi target=11 lun=0;
#name=st class=scsi target=12 lun=0;
#name=st class=scsi target=13 lun=0;
#name=st class=scsi target=14 lun=0;
#name=st class=scsi target=15 lun=0;


Note, even the higher numbered scsi targets are not looked at.
If you know your scsi target, say 5 like mine, add a line like:

name=st class=scsi target=5 lun=1;

I think the only problem with adding more lines or uncommenting
existing lines is slightly slower boot times.

The sgen.conf file has similar lines that may need
uncommenting or editing.  And you may need to add
something like this from my edited sgen.conf:

#
# Added by jhl
#

device-type-config-list=changer;
inquiry-config-list=HP,   HP DDS-3 4mm DAT loader,
HP,   C1557A;

The strings are what is identified during boot and
can be seen with a prtconf -??? sorry, forget the
options.

This would give you devices under /dev/scsi/???,
where ??? might be changer or sequential.

After the changes, you will need to do a reconfigure
reboot.  Or, devfsadm might work without the reboot.

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


FW: Re: FW: Re: Mutliple configs sharing the same indexes

2006-04-29 Thread stan
- Forwarded message from stan [EMAIL PROTECTED] -

From: stan [EMAIL PROTECTED]
To: Jean-Louis Martineau [EMAIL PROTECTED]
Cc: amanda users list amanda-users@amanda.org
Subject: Re: FW: Re: Mutliple configs sharing the same indexes
Date: Thu, 27 Apr 2006 21:57:57 -0400
User-Agent: Mutt/1.5.4i
X-Operating-System: Debian GNU/Linux
X-Kernel-Version: 2.4.23
X-Uptime: 21:40:46 up 10 days, 23:04,  1 user,  load average: 0.04, 0.04, 0.00
X-Editor: gVim

On Thu, Apr 27, 2006 at 08:53:50PM -0400, Jean-Louis Martineau wrote:
 stan wrote:
 This thread seesm to have died out.
 
 But I still don't quite see how to solve my restore issues.
 
 Can someone point out the error of my ways here?
   
 
 You must share the complete database between both config,
 that include the disklist, tapelist file and logdir.
 
 The output of 'amadmin config find' should be the same.

OK, that got me pointed in the right direction on that.
The tapelist* files were not links.

I fixed that, and now when running amrecover with the config
set to disk_only, I gte the correct indexes, but after that:

Extracting files using tape drive /dev/nst0 on host amanda.meadwestvaco.com.
Load tape DailyDump15 now
Continue [?/Y/n/s/t]?
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
amrecover: Extractor child exited with status 1

Why is it still wnating to use the tape drive (this is the compiled 
in default BTW).

To review the amanda.conf file for disk only looks like this:

tpchanger chg-multi
changerfile /opt/amanda/etc/disk_only/chg-multi.conf
tapetype HARD-DISK

Souldn't the tpchanger define overide this?

-- 
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong 
Terror 
- New York Times 9/3/1967

- End forwarded message -

How can I overide the selction of the device file to use the
disk based vtapes?


-- 
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite Vietcong 
Terror 
- New York Times 9/3/1967


can this list be sent in digest format?

2006-04-29 Thread Craig Dewick


Sorry for the post direct to the list about this, but I couldn't see 
anything on the Amanda pages about whether this list can be received in 
digestified format instead of seperate messages. I get so many lists that 
it's difficult to read the important stuff (and this list rates as very 
important!).


Having a digest option would be helpful. 8-)

Craig.

--
Post by Craig Dewick (tm). Web -- http://lios.apana.org.au/~cdewick;.
Email me at [EMAIL PROTECTED]. Explore my public-domain Sun
Microsystems technical data archive at http://www.sunshack.org;. Sun Micro
enthusiasts/users webring at http://n.webring.com/hub?ring=sunmicrosystemsu;.


Re: can this list be sent in digest format?

2006-04-29 Thread Jon LaBadie
On Sun, Apr 30, 2006 at 09:57:23AM +1000, Craig Dewick wrote:
 
 Sorry for the post direct to the list about this, but I couldn't see 
 anything on the Amanda pages about whether this list can be received in 
 digestified format instead of seperate messages. I get so many lists that 
 it's difficult to read the important stuff (and this list rates as very 
 important!).
 
 Having a digest option would be helpful. 8-)

Don't know if you can from amanda.org.  Might check with the majordomo
help page or write to [EMAIL PROTECTED]

However, yahoogroups is a subscriber to the list.  Yeah, I actually
submitted a subscribe request under the yahoogroup name.  Sort of
an archive and a way of reading it from a browser.

Because it is also a group, you should be able to request emails of
the postings.  And yahoogroups does have a daily digest capability.

One limitation to reading on yahoo, you can't post from there.

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