Re: a very lost changer user

[Frank Smith]

--On Wednesday, February 05, 2003 18:20:42 -0500 Geoff Gowey <[EMAIL PROTECTED]> wrote:


Not sure if I have this config correctly and would be extremely thankful if anyone could point my in the right direction.  What I need to do is back up multiple boxes at once.  The setup is what I outlined in my last post:
Linux (2.4.20 kernel)

ADIC Scalar 100 - 4x Quantum DLT7000 Drives
  - the picker has a barcode scanner
120 DLT IV's
  - all have bar codes
Adaptec 2944UW controller

I think chg-scsi is most appropriate due to the fact I want to be using more than one drive at once. Also, the unit has a reader and all cartridges are tagged making what I think is an ideal application for chg-scsi.  Thanks in advance.

Geoff



Amanda only uses one drive (unless you use the RAIT device driver to stripe or mirror
the data, which doesn't seem to be the case in your config).  Otherwise you would need
multiple configs running simultaneously, each with its own config specifying its own
drive(s).  There was recently a thread on the list on how do that, check the archives.

Other comments on your amanda config file:


org "DailySet1"		# your organization name for reports
mailto "bin"		# space separated list of operators at your site
dumpuser "bin"	# the user to run dumps under

inparallel 4		# maximum dumpers that will run in parallel (max 63)
			# this maximum can be increased at compile-time,
			# modifying MAX_DUMPERS in server-src/driverio.h
netusage  10 mbps	# maximum net bandwidth for Amanda, in KB per sec

dumpcycle 4 weeks	# the number of days in the normal dump cycle


Are you sure you want this?  It means that each disklist entry (DLE) will only
be gauranteed a full backup every 4 weeks.  IT also means that if you need to
restore it you have to use up to 20 tapes to do it (since your running 5 days/week)


runspercycle 20 # the number of amdump runs in dumpcycle days
			# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 120 tapes	# the number of tapes in rotation
			# 4 weeks (dumpcycle) times 5 tapes per week (just
			# the weekdays) plus a few to handle errors that
			# need amflush and so we do not overwrite the full
			# backups performed at the beginning of the previous
			# cycle

bumpsize 20 Mb		# minimum savings (threshold) to bump level 1 -> 2
bumpdays 1		# minimum days at each level
bumpmult 4		# threshold = bumpsize * bumpmult^(level-1)

etimeout 300		# number of seconds per filesystem for estimates.


Might be too small if you have large filesystems with many small files


# etimeout -600		# total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.

dtimeout 1800		# number of idle seconds before a dump is aborted.

ctimeout 30		# maximum number of seconds that amcheck waits
			# for each client host

tapebufs 20
# A positive integer telling taper how many 32k buffers to allocate.
# WARNING! If this is set too high, taper will not be able to allocate
# the memory and will die.  The default is 20 (640k).


runtapes 1		# number of tapes to be used in a single run of amdump


Only one tape will be used each night.  Will it fit?  If not, set it to the maximum
number of tapes you want to use each night (6 is the most you could use with your
current config (120 tapes/20 runs, but 4 would allow for occasional problems).


tpchanger "chg-scsi"	# the tape-changer glue script
tapedev "0"	# the no-rewind tape device to be used
changerfile "/usr/local/etc/amanda/DailySet1/chg-scsi.conf"

tapetype DLT7000-IV		# what kind of tape it is (see tapetypes below)
labelstr "^DailySet1[0-9][0-9]*$"	# label constraint regex: all tapes must match


holdingdisk hd1 {
comment "main holding disk"
directory "/dumps/amanda"	# where the holding disk is
use 290 Mb		# how much space can we use on it
			# a non-positive value means:
			#use all space but that value


If your DLEs are larger than this number then it won't do you any good,
Amanda only writes chunks to the holding disk if they'll all fit, since it
doesn't start writing a DLE to tape until the last chunk is written to disk.
If your DLEs are larger than the holding disk they will get written directly
to tape, which is much slower if your client and network can't stream the
data as fast as your drive needs it (causing it to repeated stop and reposition
itself, wasting time and tape).


chunksize 1Gb 	# size of chunk if you want big dump to be
			# dumped on multiple files on holding disks
			#  N Kb/Mb/Gb split images in chunks of size N
			#	  The maximum value should be
			#	  (MAX_FILE_SIZE - 1Mb)
			#  0  same as INT_MAX bytes
}

# If amanda cannot find a tape on which to store backups, it will run
# as many backups as it can to the holding disks.  In order to save
# space for unattended backups, by default, amanda will only perform
# 

a very lost changer user

[Geoff Gowey]

Not sure if I have this config correctly and would be extremely thankful 
if anyone could point my in the right direction.  What I need to do is 
back up multiple boxes at once.  The setup is what I outlined in my last 
post:
Linux (2.4.20 kernel)

ADIC Scalar 100 - 4x Quantum DLT7000 Drives
 - the picker has a barcode scanner
120 DLT IV's
 - all have bar codes
Adaptec 2944UW controller

I think chg-scsi is most appropriate due to the fact I want to be using 
more than one drive at once. Also, the unit has a reader and all 
cartridges are tagged making what I think is an ideal application for 
chg-scsi.  Thanks in advance.

Geoff
number_configs  2
eject   1   # Tapedrives need an eject command
sleep   5   # Seconds to wait until the tape gets ready
cleanmax10  # How many times could a cleaning tape get used
changerdev  /dev/sch0
debuglevel  9:0
havebarcode 1
labelfile   /usr/local/etc/amanda/inventory

#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/tape0  # the device that is used for the tapedrive 0
startuse0   # The slots associated with the drive 0
enduse  9   # 
statfile/usr/local/etc/amanda/tape5-slot  # The file where the actual slot is 
stored
cleancart   20  # the slot where the cleaningcartridge for drive 0 is located
cleanfile   /usr/local/etc/amanda/tape0-clean # The file where the cleanings are 
recorded
usagecount  /usr/local/etc/amanda/backup/totaltime

# Next comes the data for drive 1

config  1
drivenum1
dev /dev/tape1  # the device that is used for the tapedrive 0
startuse10  # The slots associated with the drive 0
enduse  19  # 
statfile/usr/local/etc/amanda/tape1-slot  # The file where the actual slot is 
stored
cleancart   21  # the slot where the cleaningcartridge for drive 0 is located
cleanfile   /usr/local/etc/amanda/tape1-clean # The file where the cleanings are 
recorded
usagecount  /usr/local/etc/amanda/backup1/totaltime
#
# This is the enda

config  2
drivenum2
dev /dev/tape2
startuse20
enduse  29
statfile/usr/local/etc/amanda/tape2-slot
cleancart   21
cleanfile   /usr/local/etc/amanda/tape2-clean
usagecount  /usr/local/etc/amanda/backup2/totaltime

config  3
drivenum3
dev /dev/tape3
startuse30
enduse  39
statfile/usr/local/etc/amanda/tape3-slot
cleancart   22
cleanfile   /usr/local/etc/amanda/tape3-clean
usagecount  /usr/local/etc/amanda/backup3/totaltime

###  !!! WARNING !!!  !!! WARNING !!!  !!! WARNING !!!  !!! WARNING !!!  ###
###  ###
###  This file is not meant to be installed "as is", and in fact, it ###
###  WILL NOT WORK!  You must go through it and make changes appropriate ###
###  to your own situation.  See the documentation in this file, in the  ###
###  "man amanda" man page, in the "docs" directory and at the Amanda###
###  web page (www.amanda.org).  ###
###  ###
###  !!! WARNING !!!  !!! WARNING !!!  !!! WARNING !!!  !!! WARNING !!!  ###

#
# amanda.conf - sample Amanda configuration file.  This started off life as
#   the actual config file in use at CS.UMD.EDU.
#
# If your configuration is called, say, "csd", then this file normally goes
# in /usr/local/etc/amanda/csd/amanda.conf.
#

org "DailySet1" # your organization name for reports
mailto "bin"# space separated list of operators at your site
dumpuser "bin"  # the user to run dumps under

inparallel 4# maximum dumpers that will run in parallel (max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
netusage  10 mbps   # maximum net bandwidth for Amanda, in KB per sec

dumpcycle 4 weeks   # the number of days in the normal dump cycle
runspercycle 20 # the number of amdump runs in dumpcycle days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 120 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle
### ### ###
# WARNING: don't use `inf' for tapecycle, it's broken!
### ### ###

bumpsize 20 Mb  # minimum savings (threshold) to bump level 1 -> 2
bumpdays 1  # minimum days at each level
bumpmult 4  # threshold = bumpsize * bumpmult^(level-1)

etimeout 300# numb

Re: First time Changer user

[Gene Heskett]

On Wednesday 05 February 2003 13:06, David Flood wrote:
>We have had a tape changer running with amanda for a while but it
> was just being used as the a single drive and the data is
> starting to exceed the size of the tape.(DLT40 - 80G compressed)
>
>I'm starting to look into utilizing the functionality of the
> changer. I've looked at the docs and have the impression that all
> I have to do is specify the chg-scsi in the amanda.conf and
> set-up the chg-scsi.conf. Here are examples of the part of
> amanda.conf and chg-scsi.conf.
>
>amanda.conf:
>tpchanger "chg-scsi"  # the tape-changer glue script
>tapedev "0"   # the no-rewind tape device to be used
>changerfile "/opt/amanda/etc/amanda/homes/chg-scsi.conf"
>
>chg-scsi.conf:
>number_configs  1
>eject 0
>sleep 60
>cleanmax  10
>changerdev/dev/rsst4
>#
># Next comes the data for drive 0
>#
>config0
>drivenum  0
>dev   /dev/rmt/0bn
>startuse  0
>enduse4
>statfile  /opt/amanda/etc/amanda/homes/tape0-slot
>cleancart 5
>cleanfile /opt/amanda/etc/amanda/homes/tape0-clean
>agecount/opt/amanda/etc/amanda/homes/totaltimef
>tapestatus  /opt/amanda/etc/amanda/homes/tape0-status
>
>
>I think I understand the contents of this file but I don't know
> what to put for the changerdev file. Up till now I've been using
> /dev/rmt/0 for backing up to a single tape so how do I find what
> this value should be for my changer.(/dev/rsst4 does not exist)

Because some changer robots are at the same bus address as the 
drive, but at a higher Logical Unit Number (lun in shorthand) there 
is a fair possibility that the changerdev may not exist if the 
kernel does not "scan all luns" at boot time.  I don't know how 
solaris does that, but you have to turn this flag on and rebuild a 
linux kernel to make it effective.  It its detected, it should be 
listed as being found in your present /var/log/dmesg (or whatever 
solaris calls it) file.  Use that device as the changerdev.  In 
linux, you'll need the sg driver (for generic scsi) in addition to 
the scsi cards driver. In linux, the dmesg files revelent lines 
are:


SCSI subsystem driver Revision: 1.00
scsi0 : AdvanSys SCSI 3.3G: PCI Ultra: IO 0xD000-0xD00F, IRQ 0xB
  Vendor: ARCHIVE   Model: 4586XX 28887-XXX  Rev: 0420
  Type:   Sequential-Access  ANSI SCSI revision: 02
  Vendor: ARCHIVE   Model: 4586XX 28887-XXX  Rev: 0420
  Type:   Medium Changer ANSI SCSI revision: 02
st: Version 20020805, bufsize 32768, wrt 30720, max init. bufs 4, 
s/g segs 16
Attached scsi tape st0 at scsi0, channel 0, id 6, lun 0
Attached scsi generic sg1 at scsi0, channel 0, id 6, lun 1,  type 8

>Also when I've got the changer working how do the tape numbers
> work? If a night's backup tape starts on homes02 and spreads 2
> tapes will amanda understand it's spread over homes02 and
> homes03? If so how does this affect restores?

Provided amanda has been given permission to use more tapes in the 
value runtapes is set to, the rest is only a problem if a single 
DLE is larger than a tape.  Amrestore, once it knows what you want, 
will give you a list of the tapes it needs, in the order that it 
needs them.

Please understand that a tapes name is just an arbitrary string to 
amanda, and that there is no binding whatsoever between a tape 
named wednesday, and that day of the week.

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

Re: new installation concerns

[Joshua Baker-LePain]

On Wed, 5 Feb 2003 at 2:49pm, Jozwiak, Paul wrote

> Not sure where to start.  I am totally new to the backup game.  I have good
> common sense but a considerable amount to learn, fast, concerning a good
> backup plan and strategies.  I have installed Amanda 2.4.3 with all the
> supporting packages and am not sure where to start.  I have a 40 tape 4
> drive library.  I have read through the readme's but there is still a
> disconnect.  Anyone care to pass on some Amanda knowledge to get me up and
> running.

A good place to start:

http://www.backupcentral.com/amanda.html

For changer specific stuff, look in docs/TAPE.CHANGERS.  Also, there have 
been some threads here concerning multi-drive libraries, so look through 
the archives.  Feel free to come back here when you hit issues (note that 
we fully expect you to ;).

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

Re: Sun L1000 and Amanda

[Brian Cuttler]

Ray,

Following advice (I can dig through my email, I can't take
credit) from amanda_users...

modify /kernel/drv/sgen.conf, add lines "like" the following
Note, my changers are on busses 5 and 6 both at SCSI id 4.

device-type-config-list="changer";
name="sgen" class="scsi" target=4 lun=0;

# devfsadm -i sgen loads the driver

my changers became availalbe at /dev/scsi/changer/c5t4d0 and
/dev/scsi/changer/c6t4d0

Note that amanda.conf will use both changerdev and tapedev
information...


ah, credit - Darin Perusich <[EMAIL PROTECTED]>
thank you Darin, my system is working beautifully.

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



> Sun solaris 8
> 5.8 Generic_108528-17 sun4u sparc
> 
> Ray Keckler
> 
> -Original Message-
> From: Brian Cuttler [mailto:[EMAIL PROTECTED]] 
> Sent: Wednesday, February 05, 2003 3:13 PM
> To: Raymond Keckler
> Cc: [EMAIL PROTECTED]
> Subject: Re: Sun L1000 and Amanda
> 
> 
> What operating system ? What version of the OS ?
> 
> > Does anybody know how to setup the Sun L1000 tape library system? I
> have
> > found some links on the web but I can not use the robot arm to load
> > tapes. 
> > 
> > I know the no rewind device is /dev/rmt/0bn but what is the device for
> > the loader? 
> > 
> >  
> > 
> > Ray Keckler
> > 
> > [EMAIL PROTECTED]
> > 
> 
> 

RE: Sun L1000 and Amanda

[Amro Radwan]

Welcome to my pain.. :-)
 
I was 
able to use the STCTL driver to get my Exb210 changer to work.. you may want to 
try downloading that and configuring it.  It will give your a dev for your 
changer /dev/rmt/stctl0.  
 
Good 
Luck!
 
http://www.cs.pdx.edu/~eric/stctl/
 
 

  -Original Message-From: Raymond Keckler 
  [mailto:[EMAIL PROTECTED]]Sent: Wednesday, February 05, 2003 11:46 
  AMTo: [EMAIL PROTECTED]Subject: Sun L1000 and 
  Amanda 
  
  Does anybody know how to setup the 
  Sun L1000 tape library system? I have found some links on the web but I can 
  not use the robot arm to load tapes. 
  I know the no rewind device is 
  /dev/rmt/0bn but what is the device for the loader? 
   
  Ray Keckler
  [EMAIL PROTECTED]

RE: Sun L1000 and Amanda

[Raymond Keckler]

Sun solaris 8
5.8 Generic_108528-17 sun4u sparc

Ray Keckler

-Original Message-
From: Brian Cuttler [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 05, 2003 3:13 PM
To: Raymond Keckler
Cc: [EMAIL PROTECTED]
Subject: Re: Sun L1000 and Amanda


What operating system ? What version of the OS ?

> Does anybody know how to setup the Sun L1000 tape library system? I
have
> found some links on the web but I can not use the robot arm to load
> tapes. 
> 
> I know the no rewind device is /dev/rmt/0bn but what is the device for
> the loader? 
> 
>  
> 
> Ray Keckler
> 
> [EMAIL PROTECTED]
> 

Re: Sun L1000 and Amanda

[Brian Cuttler]

What operating system ? What version of the OS ?

> Does anybody know how to setup the Sun L1000 tape library system? I have
> found some links on the web but I can not use the robot arm to load
> tapes. 
> 
> I know the no rewind device is /dev/rmt/0bn but what is the device for
> the loader? 
> 
>  
> 
> Ray Keckler
> 
> [EMAIL PROTECTED]
> 

new installation concerns

[Jozwiak, Paul]

Not sure where to start.  I am totally new to the backup game.  I have good
common sense but a considerable amount to learn, fast, concerning a good
backup plan and strategies.  I have installed Amanda 2.4.3 with all the
supporting packages and am not sure where to start.  I have a 40 tape 4
drive library.  I have read through the readme's but there is still a
disconnect.  Anyone care to pass on some Amanda knowledge to get me up and
running.

Many Thanks,

Paul


 NOTICE  
This email message is for the sole use of the intended recipient(s) and may
contain confidential and privileged information.  Any unauthorized review,
use, disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all copies
of the original message.
Any opinions expressed in this email are those of the individual and not
necessarily those of the company.
All liability for viruses is excluded to the fullest extent permitted by
law.

Sun L1000 and Amanda

[Raymond Keckler]

Does anybody know how to setup the Sun L1000 tape library
system? I have found some links on the web but I can not use the robot arm to
load tapes. 

I know the no rewind device is /dev/rmt/0bn but what is the
device for the loader? 

 

Ray Keckler

[EMAIL PROTECTED]

First time Changer user

[David Flood]

We have had a tape changer running with amanda for a while but it was just being used 
as the a single drive and the data is starting to exceed the size of the tape.(DLT40 - 
80G compressed)

I'm starting to look into utilizing the functionality of the changer. I've looked at 
the docs 
and have the impression that all I have to do is specify the chg-scsi in the 
amanda.conf 
and set-up the chg-scsi.conf. Here are examples of the part of amanda.conf and 
chg-scsi.conf.

amanda.conf:
tpchanger "chg-scsi"  # the tape-changer glue script
tapedev "0"   # the no-rewind tape device to be used
changerfile "/opt/amanda/etc/amanda/homes/chg-scsi.conf"

chg-scsi.conf:
number_configs  1
eject 0   
sleep 60  
cleanmax  10
changerdev/dev/rsst4
#
# Next comes the data for drive 0
#
config0
drivenum  0
dev   /dev/rmt/0bn
startuse  0   
enduse4
statfile  /opt/amanda/etc/amanda/homes/tape0-slot  
cleancart 5   
cleanfile /opt/amanda/etc/amanda/homes/tape0-clean 
agecount/opt/amanda/etc/amanda/homes/totaltimef
tapestatus  /opt/amanda/etc/amanda/homes/tape0-status


I think I understand the contents of this file but I don't know what to put for the 
changerdev file. Up till now I've been using /dev/rmt/0 for backing up to a single 
tape so 
how do I find what this value should be for my changer.(/dev/rsst4 does not exist)

Also when I've got the changer working how do the tape numbers work? If a night's 
backup tape starts on homes02 and spreads 2 tapes will amanda understand it's 
spread over homes02 and homes03? If so how does this affect restores?

David Flood
Systems Administrator

RE: Running AMANDA over the Internet

[Bort, Paul]

Actually, an SSH tunnel is one of the least easy VPNs for this because of
the many different ports AMANDA can use. Unless you have limitations on what
you can install on the boxes, a full VPN (like IPSec, as mentioned in
another post) is probably your best bet. The VPN model of point-to-point
connections suits well because AMANDA's traffic is also shaped like that,
where one of the points is always the server, and the other is a client. 

If you're really more comfortable with SSH, you could schedule a tar on each
client, and follow it with an scp to send the data to the backup server,
where it can be written to tape. This would add an extra step to any
restore, but doesn't require a VPN. 

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 05, 2003 11:34 AM
> To: Bort, Paul
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: Running AMANDA over the Internet
> 
> 
> 
> I think the easiest way would be to use an SSH tunnel. Would 
> this be easy
> to implement ? Any examples maybe or pointers on  how to 
> acheive that ?
> 
> Thanks
> Regards
> 
> 
> 
> 
>   
>   
>  
>   
>   
>  
> "Bort, Paul"  To: 
> "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, 
> [EMAIL PROTECTED] 
> <[EMAIL PROTECTED]   cc: 
>   
>  
> om>   Subject: 
> RE: Running AMANDA over the Internet  
> 
> Sent by:  
>   
>  
> owner-amanda-users@   
>   
>  
> amanda.org
>   
>  
>   
>   
>  
>   
>   
>  
> 02/05/03 04:20 PM 
>   
>  
>   
>   
>  
>   
>   
>  
> 
> 
> 
> 
> Amanda is a backup manager, not a security manager. There are no steps
> taken
> to ensure the security of the backups. Several solutions are 
> available,
> though:
> 
> - Use the Kerberos support built in to Amanda. I've never 
> played with this.
> 
> 
> - Use tar with a wrapper script on the client that encrypts the backup
> before sending it. You might be able to find samples of this 
> in the list
> archives.
> 
> - Use an encrypted VPN (CIPE, FreeSWAN, SSHTunnel) between 
> servers. This is
> the method I used, because I use the same tunnel for 
> monitoring and file
> transfers.
> 
> Search the list, think about what method fits your needs. 
> Feel free to ask
> more questions. Good Luck.
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, February 05, 2003 9:50 AM
> > To: [EMAIL PROTECTED]
> > Subject: Running AMANDA over the Internet
> >
> >
> > Hello,
> >
> > Let's take the scenario where I have got an AMANDA server
> > located at one
> > central site and have a few other servers located at various
> > places around
> > the globe which of course all need to be backed up by the
> > centraon site's
> > AMANDA server. My question is now more related about 
> security and how
> > secure it is to run backups over the internet. Is AMANA
> > secure by default
> > to run over the internet or are there any optional compiling
> > options or
> > features which I should use to make the clients itself and
> > the dump secure
> > ?
> >
> > Many thanks for your opinion
> >
> > Regards
> >
> >
> >
> >
> 
> 
> 
> 

Re: SCSI Autoloader setup

[Brian Cuttler]

Probably you've already gotten a solution on this but
I'll try anyway...

I had the same problem you are seeing, I was using
chg-zd-mtx and I was working ok on jukebox one with
tape drive 0cn but failing with the 2nd jukebox with
tape drive 1cn.

Amanda, rather tape changer, was trying to load drive
number 1 rather than drive number zero, defaulting to
value obtained by parsing drive name "1cn".

Solution for me was to specify the "optional" device
name in the chg-zd-mtx.conf file. Specified it as zero
for both jukeboxes.

> Gene (and anybody else who may be up),
> 
> I got this set up, but when running the label utility
> I get the following:
> 
> sbin]$ ./amlabel Daily Daily-01 slot 0
> amlabel: could not load slot "0": open: /dev/sg1: Bad
> file descriptor
> 
> I'm going to keep playing, but in the meantime any
> insight would be greatly appreciated...
> 
> -John
> 
> --- Gene Heskett <[EMAIL PROTECTED]> wrote:
> > On Tuesday 04 February 2003 10:33, John Cunningham
> > wrote:
> > 
> > See the attached amanda.conf, and chg-scsi.conf
> > files John.  You 
> > have to adjust the devices maybe, and the total
> > number of slots, 
> > but it should otherwise work.  Let me know how you
> > get along.
> > 
> > >Hello alll - I'm doing a first time setup (and I'm
> > new at tape
> > > drives in general) and ran in to some glitches -
> > any help would
> > > be greatly appreciated.
> > >
> > >I'm running a SCSI IBM DDS-4 120 / 240 6 tape
> > changer on a RedHat
> > > Linux 7.3 system.
> > >
> > >Here's the chain of events.  I set up the
> > configuration script
> > > using a standard chg-multi and got to the point
> > where I was
> > > labeling tapes (I'm moving through instructions in
> > O'Reily's
> > > "Unix Backup and Recovery") and realized that
> > while I could read
> > > and label the tapes, I had issues with
> > auto-changing.  When slot
> > > 1 was loaded and I attempted to run the labeling
> > command for slot
> > > 2, slot one would eject then the loader would just
> > quit,
> > > eventually resulting in an error with the amlabel
> > program.
> > >
> > >So I though perhaps the problem lies in that I'm
> > not using a
> > > chg-scsi setup.  I grabbed the example
> > chg-scsi-linux file and
> > > edited it then pointed the configuration file to
> > it.  Here's a
> > > chunk from my amanda.conf file:
> > >
> > >runtapes 1  # number of tapes to be
> > used in a single
> > > run of amdump tpchanger
> > "/dumps/amanda/chg-scsi.conf" # the
> > > tape-changer glue script tapedev "/dev/sg1"  #
> > the no-rewind
> > > tape device to be used rawtapedev "/dev/nst0"  #
> > the raw device
> > > to be used (ftape only) #changerfile
> > "/dumps/amanda/changer"
> > >#changerfile "/dumps/amanda/changer-status"
> > >#changerfile "/dumps/amanda/changer.conf"
> > >changerfile "/dumps/amanda/changer.conf"
> > >changerdev "/dev/sg2"
> > >
> > >Here's the setup from my chg-scsi file - the idea
> > is clost 1-5 for
> > > tapes and 6 for a cleaner:
> > >
> > >   UW PICO(tm) 4.2
> > File:
> > > /dumps/amanda/chg-scsi.conf
> > >
> > >#chg-scsi-linux.conf
> > >
> > >number_configs  1
> > >eject   1   # Tapedrives need an eject
> > command
> > >sleep   90  # Seconds to wait until the
> > tape gets
> > > ready cleanmax100 # How many times
> > could a cleaning
> > > tape get used changerdev  /dev/sg2
> > >#
> > ># Next comes the data for drive 0
> > >#
> > >config  0
> > >drivenum0
> > >dev /dev/nst0
> > >scsitapedev /dev/sg1
> > >startuse0   # The slots associated with
> > the drive 0
> > >enduse  5   #
> > >statfile   
> > /usr/local/etc/amanda/Daily/tape0-slot  # The file
> > > where the actual slot is stored cleancart   6 
> >  # the
> > > slot where the cleaningcartridge for drive 0 is
> > located cleanfile
> > >   /usr/local/etc/amanda/Daily/tape0-clean #
> > The file where
> > > the cleanings are recorded usagecount 
> > > /usr/local/etc/amanda/Daily/totaltime
> > >tapestatus 
> > /usr/local/etc/amanda/Daily/tapestatus # here will
> > > some status infos be stored #labelfile 
> > > /usr/local/etc/amanda/Daily/labelfile # Use this
> > if you have an
> > > barcode reader
> > >
> > >and lastly my changer.conf file
> > >
> > >
> > ># lines from chg-multi.com
> > >
> > >
> > ># For changers that need an 'mt offline' to load
> > the next tape
> > >multieject 0
> > >
> > ># Is this a gravity stacker that can't go backwards
> > or cycle ?  If
> > ># yes, set gravity to 1.
> > >gravity 0
> > >
> > ># Does this tape-changer need an explicit eject
> > command before
> > > loading # a new tape?  If you are using multiple
> > drives as a tape
> > > changer, you # don't want to do this, but if you
> > are using an
> > > auto-changer that # allows access to the slots
> > through Unix tape
> > > devices, it might block # the mount of a new slot
> > until the old
> > 

Re: Problem with stacker mode

[Chris Dahn]

> From looking at the docs and some quick googling, I don't think stacker
> mode works like this.  Yes, it will automatically load the next tape when
> it hits EOT, but I don't see any indications that the autoloader firmware
> virtualizes this and presents one contiguous tape to the OS.
>
> So you're going to have to split that big fs up (using tar).  Whether you
> stay in stacker mode or go back to random is up to you.  Myself, I'd go
> back to random.

  I have an autochanger here that is in stacker mode, and it seems that this 
is in fact (not one contiguous tape) how it appears to work, although I 
havn't done extensive testing with it. I suppose if you _really_ wanted to 
keep it in stack mode, you could try to kludge something together with 
chg-manual, where it ejects the tape, auto-loads the next then tells it to 
continue. At that rate you may as well go back to running it in random mode 
though.

RE: Running AMANDA over the Internet

[marc . bigler]

I think the easiest way would be to use an SSH tunnel. Would this be easy
to implement ? Any examples maybe or pointers on  how to acheive that ?

Thanks
Regards




   
  
   
  
"Bort, Paul"  To: "'[EMAIL PROTECTED]'" 
<[EMAIL PROTECTED]>, [EMAIL PROTECTED] 
<[EMAIL PROTECTED]   cc:  
  
om>   Subject: RE: Running AMANDA over the 
Internet  
Sent by:   
  
owner-amanda-users@
  
amanda.org 
  
   
  
   
  
02/05/03 04:20 PM  
  
   
  
   
  




Amanda is a backup manager, not a security manager. There are no steps
taken
to ensure the security of the backups. Several solutions are available,
though:

- Use the Kerberos support built in to Amanda. I've never played with this.


- Use tar with a wrapper script on the client that encrypts the backup
before sending it. You might be able to find samples of this in the list
archives.

- Use an encrypted VPN (CIPE, FreeSWAN, SSHTunnel) between servers. This is
the method I used, because I use the same tunnel for monitoring and file
transfers.

Search the list, think about what method fits your needs. Feel free to ask
more questions. Good Luck.

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 05, 2003 9:50 AM
> To: [EMAIL PROTECTED]
> Subject: Running AMANDA over the Internet
>
>
> Hello,
>
> Let's take the scenario where I have got an AMANDA server
> located at one
> central site and have a few other servers located at various
> places around
> the globe which of course all need to be backed up by the
> centraon site's
> AMANDA server. My question is now more related about security and how
> secure it is to run backups over the internet. Is AMANA
> secure by default
> to run over the internet or are there any optional compiling
> options or
> features which I should use to make the clients itself and
> the dump secure
> ?
>
> Many thanks for your opinion
>
> Regards
>
>
>
>

Re: Running AMANDA over the Internet

[Kirill Ponazdyr]

As many already sudgested: VPN is your best choice. Sometimes VPN is not
an option though, the second best option is:
http://cns.utoronto.ca/~pkern/stuff/

There is a patch which will allow the SSL encryption of the amanda dump
images. It is pretty good, since you can specify in a dumptype if you want
a encryption or not.

As for Kerberos: unless you know it well and have a infrastructure running
already it is probably the least advisable option of the three. In
addition to that we could not compile Amanda with Kerberos support on
solaris no matter what we tried.

Regards

Kirill


Kirill Ponazdyr
Technical Director
Codeangels Solutions
Tel: +41 (0)43 844 90 10
Fax: +41 (0)43 844 90 12

> Hello,
>
> Let's take the scenario where I have got an AMANDA server located at one
> central site and have a few other servers located at various places
> around the globe which of course all need to be backed up by the
> centraon site's AMANDA server. My question is now more related about
> security and how secure it is to run backups over the internet. Is AMANA
> secure by default to run over the internet or are there any optional
> compiling options or features which I should use to make the clients
> itself and the dump secure ?
>
> Many thanks for your opinion
>
> Regards

Re: Running AMANDA over the Internet

[Jon LaBadie]

On Wed, Feb 05, 2003 at 03:49:32PM +0100, [EMAIL PROTECTED] wrote:
> Hello,
> 
> Let's take the scenario where I have got an AMANDA server located at one
> central site and have a few other servers located at various places around
> the globe which of course all need to be backed up by the centraon site's
> AMANDA server. My question is now more related about security and how
> secure it is to run backups over the internet. Is AMANA secure by default
> to run over the internet or are there any optional compiling options or
> features which I should use to make the clients itself and the dump secure

Lets see, if you speak on a cell phone or transmit on the internet,
consider it public knowledge :)   Encryption, at a minimum, seems appropriate.


About a year ago, "Andrew Hall" <[EMAIL PROTECTED]>, was working on a
document describing his experience in encrypting the data stream with
gnu's gpg.  I don't recall the final status of this work.

Maybe Andrew is still reading the list and can comment,
or you might contact him.

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

Re: Running AMANDA over the Internet

[Marius Sorteberg]

On Wed, Feb 05, 2003 at 03:49:32PM +0100, [EMAIL PROTECTED] wrote:
> Hello,
> 
> Let's take the scenario where I have got an AMANDA server located at one
> central site and have a few other servers located at various places around
> the globe which of course all need to be backed up by the centraon site's
> AMANDA server. My question is now more related about security and how
> secure it is to run backups over the internet. Is AMANA secure by default
> to run over the internet or are there any optional compiling options or
> features which I should use to make the clients itself and the dump secure
> ?
>
Run Amanda thru a IPsec tunnel. I got a setup that backs up 3 servers over a 704kb/s 
cable connection.
It works fine, but take aprox. 9 hours to do a full dump (7GB, when commpressed on 
clients). 

Regards

 Marius Sorteberg

Re: Running AMANDA over the Internet

[Martin.Hepworth]

Marc

This is what VPN's are for. 

Amanda has little concept of security and relies on DNS lookups/usernames
for any sort of authentication. You can augment this with
tcp-wrapper/xinet type security, but the traffic will
still travel over the public internet in the clear (or at best
compressed!).

Beside the VPN I'd make sure there is somesort of bandwith guarantee
service between the sites - backups can be large things.

--
Martin Hepworth
Senior Systems Administrator
Solid State Logic Ltd
Phone: +44 (0)1865 842300

On Wed, 5 Feb 2003 [EMAIL PROTECTED] wrote:

> Hello,
> 
> Let's take the scenario where I have got an AMANDA server located at one
> central site and have a few other servers located at various places around
> the globe which of course all need to be backed up by the centraon site's
> AMANDA server. My question is now more related about security and how
> secure it is to run backups over the internet. Is AMANA secure by default
> to run over the internet or are there any optional compiling options or
> features which I should use to make the clients itself and the dump secure
> ?
> 
> Many thanks for your opinion
> 
> Regards
> 
> 
> 
> 
> 



**
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 also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**

Re: strange dump message

[Jon LaBadie]

On Wed, Feb 05, 2003 at 09:01:10AM -0500, Eric Sproul wrote:
> All,
> On the last few runs, I've seen some strangeness with one DLE that I
> can't figure out.  I'm using the canned 'comp-root' dumptype:
> 
> define dumptype comp-root {
> comment "Root partitions with compression"
> options compress-fast
> priority low
> }
> 
> The DLE is the root filesystem (/dev/sda1) on a Debian 3.0 box.  AMANDA
> has been trying to do both level-0 and level-1 dumps of this filesystem
> since 1/25 when the last full backup was successful.  Both client and
> server are running 2.4.3.  Below is the failure message from this
> morning's run.
> 
> 
> /-- dhcp01 sda1 lev 1 STRANGE
> sendbackup: start [dhcp01:sda1 level 1]
> sendbackup: info BACKUP=/sbin/dump
> sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... -
> sendbackup: info COMPRESS_SUFFIX=.gz
> sendbackup: info end
> |   DUMP: Date of this level 1 dump: Wed Feb  5 04:06:47 2003
> |   DUMP: Date of last level 0 dump: Sat Jan 25 04:00:08 2003
> |   DUMP: Dumping /dev/sda1 (/) to standard output
> |   DUMP: Added inode 7 to exclude list (resize inode)
> |   DUMP: Label: none
> |   DUMP: mapping (Pass I) [regular files]
> |   DUMP: mapping (Pass II) [directories]
> |   DUMP: estimated 131 tape blocks.
> |   DUMP: Volume 1 started with block 1 at: Wed Feb  5 04:06:47 2003
> |   DUMP: dumping (Pass III) [directories]
> ? /dev/sda1: EXT2 directory corrupted while converting directory #41021
> ? 
> ?   DUMP: error reading command pipe: Connection reset by peer
> ?   DUMP: error reading command pipe: Connection reset by peer
> ??error [/sbin/dump returned 3]? dumper: strange [missing size line from
> sendbackup]
> ? dumper: strange [missing end line from sendbackup]
> \
> 
> I tried looking for an explanation for the "EXT2 directory corrupted"
> dump message, but all I could find was basically "we don't know what it
> is, just fsck it and move on".  That isn't good enough for me.  ;) 
> Whatever it is, it doesn't seem to be causing grief to the server's
> normal operation, but it is preventing me from getting a backup.

Normal operation is not surprising, that area of the fs may just not
be getting used by anything.  I recall an ancient system where I could
not add things to the drives "bad block table", not something fsck deals
with.  I knew several specific blocks were bad and caused problems each
time the system tried to allocate them to a file.  I created a dummy file
"DoNotRemove" in a dummy directory "DoNotTouch".  With a disk editor, fsdb,
I "allocated" the specific block to the dummy file.  An fsck cleaned up
the mess I made with the free block list.  The fs ran fine for years then.

On your specific problem, I'm guessing the "#41021" represents an inode
number (41021).  It is also the format of the names fsck uses when it
recovers an unknown named file into the "lost+found" directory on my
Solaris systems.  Does linux/ext2 use the "lost+found" system.  There
would be a directory by that name in the root of the fs.  It would
contain recoverd files and dirs all named with an octothorpe (an #)
followed by the inode number (the name was unknown).

What I'm getting at, is if my guess is correct, 41021 is an inode num,
maybe you can find the offending file/directory and investigate.  Two
commands to assist: the ls command has a "-i" option that prints the
inode number of the entries.  Alternatively, if you don't have an idea
where the offender is, find can locate by inode number:

   find  -xdev -inum 41021

The "-xdev" keeps the search to the one fs since each fs will have its
own inode 41021.

The above syntax is for system V type commands.  I presume linux with
its gnu counterparts has the same/similar syntax.

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

Re: Problem with stacker mode

[Joshua Baker-LePain]

On Wed, 5 Feb 2003 at 10:50am, yam wrote

> I have been using amanda for over a year. Having HP SureStore Autoloader
> (9 tapes carrusel). It's been ok during that time.
> 
> Now, since I have to backup a big disk, I have decided to change the
> autoloader operation mode from random mode, to stacker mode... Thats means
> now it doesnt have a 9 tapes carrusel but a big tape (tape capacity = 9
> DLT 40/80 tapes).

>From looking at the docs and some quick googling, I don't think stacker 
mode works like this.  Yes, it will automatically load the next tape when 
it hits EOT, but I don't see any indications that the autoloader firmware 
virtualizes this and presents one contiguous tape to the OS.

So you're going to have to split that big fs up (using tar).  Whether you 
stay in stacker mode or go back to random is up to you.  Myself, I'd go 
back to random.

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

Re: strange dump message

[Martin Schwarz]

Hello Eric,

On Wed, Feb 05, 2003 at 09:01:10AM -0500, Eric Sproul wrote:
> ? /dev/sda1: EXT2 directory corrupted while converting directory #41021
[...]

> I tried looking for an explanation for the "EXT2 directory corrupted"
> dump message, but all I could find was basically "we don't know what it
> is, just fsck it and move on".  That isn't good enough for me.  ;) 
> Whatever it is, it doesn't seem to be causing grief to the server's
> normal operation, but it is preventing me from getting a backup.
> 
> Has anyone else run across this problem?  How did you solve it?

I have seen the same error message a few times (on Debian 3.0, too, but
I don't think that matters).

AFAIK (someone please correct me if I'm wrong!) this "error" is the
result of dumping an active (mounted) filesystem on which files are
being changed during the dump run. fsck checks I have run afterwards (on
the umounted fs) have shown no errors.  The incident still is very
annoying since "the ENTIRE dump is aborted" leaving me without a backup
for this DLE.

My solution was to switch from dump to gnutar. I still get messages
files that have changed during the read operation etc. but these do not
cause the whole DLE to fail.

Bye,
Martin
-- 
[EMAIL PROTECTED]   toplink-plannet GmbH
Network Operations EngineerSchönfeldstraße 8
Tel +49 [0] 721 6636-0 D-76131 Karlsruhe
Fax +49 [0] 721 6636-199  http://www.toplink-plannet.de/

Re: 2.4.4b client with 2.4.2p2 server?

[Jon LaBadie]

On Wed, Feb 05, 2003 at 09:26:30AM -0500, Richard Morse wrote:
> Hi!  I'd like to test the 2.4.4b client on a cygwin-enabled win32 machine.
> However, I have a 2.4.2p2 server, which does everything that I need to do
> for my unix boxen.  Is there any problem using the 2.4.4b client with a
> 2.4.2p2 server?

Should be compatible.
I was running a 2.4.2 server with a 2.4.3b3 cygwin client.
Unfortunately, as oft happens, the Win box needed a complete
reinstall of everything.  Cygwin and backups have not been
reinstalled as yet.

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

RE: Running AMANDA over the Internet

[Bort, Paul]

Amanda is a backup manager, not a security manager. There are no steps taken
to ensure the security of the backups. Several solutions are available,
though: 

- Use the Kerberos support built in to Amanda. I've never played with this. 

- Use tar with a wrapper script on the client that encrypts the backup
before sending it. You might be able to find samples of this in the list
archives.

- Use an encrypted VPN (CIPE, FreeSWAN, SSHTunnel) between servers. This is
the method I used, because I use the same tunnel for monitoring and file
transfers.

Search the list, think about what method fits your needs. Feel free to ask
more questions. Good Luck. 

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 05, 2003 9:50 AM
> To: [EMAIL PROTECTED]
> Subject: Running AMANDA over the Internet
> 
> 
> Hello,
> 
> Let's take the scenario where I have got an AMANDA server 
> located at one
> central site and have a few other servers located at various 
> places around
> the globe which of course all need to be backed up by the 
> centraon site's
> AMANDA server. My question is now more related about security and how
> secure it is to run backups over the internet. Is AMANA 
> secure by default
> to run over the internet or are there any optional compiling 
> options or
> features which I should use to make the clients itself and 
> the dump secure
> ?
> 
> Many thanks for your opinion
> 
> Regards
> 
> 
> 
> 

Re: strange dump message

[Joshua Baker-LePain]

On 5 Feb 2003 at 9:01am, Eric Sproul wrote

> ? /dev/sda1: EXT2 directory corrupted while converting directory #41021
> ? 
> ?   DUMP: error reading command pipe: Connection reset by peer
> ?   DUMP: error reading command pipe: Connection reset by peer
> ??error [/sbin/dump returned 3]? dumper: strange [missing size line from
> sendbackup]
> ? dumper: strange [missing end line from sendbackup]
> \
> 
> I tried looking for an explanation for the "EXT2 directory corrupted"
> dump message, but all I could find was basically "we don't know what it
> is, just fsck it and move on".  That isn't good enough for me.  ;) 
> Whatever it is, it doesn't seem to be causing grief to the server's
> normal operation, but it is preventing me from getting a backup.

This is really an ext2/Linux problem, not one with amanda.  Having looked 
around a bit, it does seem like your best option is fsck.  *Something* is 
wrong with the fs, and it may get worse which, of course, means you really 
want backups.

If you *really* can't take the server down to fsck it, you could try tar 
on that fs -- maybe it'll get by the corruption.

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

Running AMANDA over the Internet

[marc . bigler]

Hello,

Let's take the scenario where I have got an AMANDA server located at one
central site and have a few other servers located at various places around
the globe which of course all need to be backed up by the centraon site's
AMANDA server. My question is now more related about security and how
secure it is to run backups over the internet. Is AMANA secure by default
to run over the internet or are there any optional compiling options or
features which I should use to make the clients itself and the dump secure
?

Many thanks for your opinion

Regards

strange dump message

[Eric Sproul]

All,
On the last few runs, I've seen some strangeness with one DLE that I
can't figure out.  I'm using the canned 'comp-root' dumptype:

define dumptype comp-root {
comment "Root partitions with compression"
options compress-fast
priority low
}

The DLE is the root filesystem (/dev/sda1) on a Debian 3.0 box.  AMANDA
has been trying to do both level-0 and level-1 dumps of this filesystem
since 1/25 when the last full backup was successful.  Both client and
server are running 2.4.3.  Below is the failure message from this
morning's run.


/-- dhcp01 sda1 lev 1 STRANGE
sendbackup: start [dhcp01:sda1 level 1]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/sbin/restore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
|   DUMP: Date of this level 1 dump: Wed Feb  5 04:06:47 2003
|   DUMP: Date of last level 0 dump: Sat Jan 25 04:00:08 2003
|   DUMP: Dumping /dev/sda1 (/) to standard output
|   DUMP: Added inode 7 to exclude list (resize inode)
|   DUMP: Label: none
|   DUMP: mapping (Pass I) [regular files]
|   DUMP: mapping (Pass II) [directories]
|   DUMP: estimated 131 tape blocks.
|   DUMP: Volume 1 started with block 1 at: Wed Feb  5 04:06:47 2003
|   DUMP: dumping (Pass III) [directories]
? /dev/sda1: EXT2 directory corrupted while converting directory #41021
? 
?   DUMP: error reading command pipe: Connection reset by peer
?   DUMP: error reading command pipe: Connection reset by peer
??error [/sbin/dump returned 3]? dumper: strange [missing size line from
sendbackup]
? dumper: strange [missing end line from sendbackup]
\

I tried looking for an explanation for the "EXT2 directory corrupted"
dump message, but all I could find was basically "we don't know what it
is, just fsck it and move on".  That isn't good enough for me.  ;) 
Whatever it is, it doesn't seem to be causing grief to the server's
normal operation, but it is preventing me from getting a backup.

Has anyone else run across this problem?  How did you solve it?

Thanks,
Eric

2.4.4b client with 2.4.2p2 server?

[Richard Morse]

Hi!  I'd like to test the 2.4.4b client on a cygwin-enabled win32 machine.
However, I have a 2.4.2p2 server, which does everything that I need to do
for my unix boxen.  Is there any problem using the 2.4.4b client with a
2.4.2p2 server?

Thanks muchly,
Ricky Morse


Richard Morse   System Administrator
MGH Biostatistics Center 50 Staniford St. Rm 560
[EMAIL PROTECTED]617/724-9830

Re: Amflush failing silently

[Christoph Scheeder]

Hi Martin,
nope, I'm only typing the "C" itself.
It worked fine before upgrading amanda from 2.4.2p2 to 2.4.3
But you triger something in my mind.
It is possible amflush is case-significant at that point.
one more thing to try
Thanks
Christoph

Martin Schwarz schrieb:

Hi Christoph,

On Wed, Feb 05, 2003 at 10:14:35AM +0100, Christoph Scheeder wrote:


Problem if i tell amflush only to flush run named "C:", for example,
amflush does nothing, terminating without sending an e-mail.



are your literally typing "C:" including the colon? Try to use just the
letter, see if that helps.

Bye,
Martin.

Re: Amflush failing silently

[Martin Schwarz]

Hi Christoph,

On Wed, Feb 05, 2003 at 10:14:35AM +0100, Christoph Scheeder wrote:
> Problem if i tell amflush only to flush run named "C:", for example,
> amflush does nothing, terminating without sending an e-mail.

are your literally typing "C:" including the colon? Try to use just the
letter, see if that helps.

Bye,
Martin.
-- 
[EMAIL PROTECTED]   toplink-plannet GmbH
Network Operations EngineerSchönfeldstraße 8
Tel +49 [0] 721 6636-0 D-76131 Karlsruhe
Fax +49 [0] 721 6636-199  http://www.toplink-plannet.de/

RE: Full backup to tape, incrementals to disk?

[Dieter Meinert]

-BEGIN PGP SIGNED MESSAGE-

Try to set it all up for harddisk backup, and flush fulls
to tape after amanda has finished her job. Thus you also
have the fulls on disk for recovery. 

Or maybe you really want two configs, one of them an
archive run with only full backups ?

 Regards
Dieter Meinert
 


***
 * Dr. Dieter Meinert  
   *
 * c/o H. Rosen Engineering GmbHPhone +49-591-9136-493 
   *
 * Am Seitenkanal 8 Fax +49-591-9136-121   
   *
 * D-49811 Lingen (Ems) Email
[EMAIL PROTECTED] *
 * Germany 
   *


***


|=> -Original Message-
|=> From: Toralf Lund [mailto:[EMAIL PROTECTED]]
|=> Sent: Wednesday, February 05, 2003 10:01 AM
|=> To: Amanda Mailing List
|=> Subject: Full backup to tape, incrementals to disk?
|=> 
|=> 
|=> I seem to remember that something like this has been 
|=> discussed before, but 
|=> I couldn't find anything in the archives ;-/
|=> 
|=> Anyhow, I'm thinking about setting up a config with
|full  => backups to tape 
|=> and incrementals to harddisk - due to limited tape
|capacity  => (yes, I know 
|=> incrementals are usually small, but we have some 
|=> filesystems with large 
|=> files that change a lot), and to allow for faster
|recovery  => (at the expense 
|=> of security, to a certain degree.)
|=> 
|=> Is there a simple way to do that with Amanda 2.4.3? -
|Seems  => like I can 
|=> quite easily set up one config for the fulls and one
|for  => the incrementals, 
|=> but I also need some way to "link" the two, so that the
| => level returns 
|=> correctly to level 1 for the incremental when a full
|backup  => has been 
|=> executed. Also, I would really prefer to have a common 
|=> index, so separate 
|=> configs may not be quite what I want in any case.
|=> 
|=> -- 
|=> - Toralf
|=> 

-BEGIN PGP SIGNATURE-
Version: PGPfreeware 6.5.3 for non-commercial use 

iQEVAwUBPkDScrYBkYAdGmPFAQGydgf+OlM2M9sOAJK7gBHbTVDL90vFOyL3xeIV
64t0BhVPghcpYahgdxKdg4Rt2la97p5TRNc/favGGOe/UYhNYu3ssCS/XHtBhb/5
1UkEFFqIlgNbK4lS0f+wae+S7C6oC83ZmTHpercByZ5idYPV7tc0lhyPIjEkDIJh
cyBjwML4IKsPkG+EzgdW13akzXUE5E5ALGbGQR0XtSYg+RjwnuuqsMQNbPjR0EXy
cwXlnsMORtrJTT1uCuD1vKRb0za2z68m6sNkEZv2Xk6RzkmZ56+PVDpM7Awjm7RH
dGgdermnQA23BAazqVAowrrL4yWi2AyYFoD6FL2S6lMhPeX83D5ukA==
=+qcK
-END PGP SIGNATURE-

Problem with stacker mode

[yam]

Hello,

I have been using amanda for over a year. Having HP SureStore Autoloader
(9 tapes carrusel). It's been ok during that time.

Now, since I have to backup a big disk, I have decided to change the
autoloader operation mode from random mode, to stacker mode... Thats means
now it doesnt have a 9 tapes carrusel but a big tape (tape capacity = 9
DLT 40/80 tapes).

Have been trying to make it work, but no luck. After some tests, about the
same result on each one. It detects the end of the tape at first tape,
instead of detecting it at the end of the 9th tape. It is senseless since
now I have only a /dev/st0 device (and the non-rewind one), but there's no
/dev/sg0.

Any help would be appreciated Thanks...

See you.

Amflush failing silently

[Christoph Scheeder]

Hi,
i have a problem with an amanda-2.4.3 installation and amflush.
Problem
multiple amanda-runs went to disk cause of tape-errors.
only last run out of 3 shall be flushed to tape.
Problem if i tell amflush only to flush run named "C:", for example,
amflush does nothing, terminating without sending an e-mail.
after that i have to run amcleanup, and in the generated e-mail it tells me
there where no files to flush, but the tape in the drive is marked as used.
If i move the other dir's out of the holding-area and do an amflush
all works fine.

AFAIR a similar problem was reported a few month back, but i couldn't find
the messages in the mailinglist archives.
Has someone a solution to this problem?
Thanks
Christoph

Full backup to tape, incrementals to disk?

[Toralf Lund]

I seem to remember that something like this has been discussed before, but 
I couldn't find anything in the archives ;-/

Anyhow, I'm thinking about setting up a config with full backups to tape 
and incrementals to harddisk - due to limited tape capacity (yes, I know 
incrementals are usually small, but we have some filesystems with large 
files that change a lot), and to allow for faster recovery (at the expense 
of security, to a certain degree.)

Is there a simple way to do that with Amanda 2.4.3? - Seems like I can 
quite easily set up one config for the fulls and one for the incrementals, 
but I also need some way to "link" the two, so that the level returns 
correctly to level 1 for the incremental when a full backup has been 
executed. Also, I would really prefer to have a common index, so separate 
configs may not be quite what I want in any case.

--
- Toralf