hi,
thanks for your answer but, i still have problems....
i change some couple of parameter in /etc/stinit.def .
the tonight's backup seems to be stalled...
here is the "ps -u amandabackup"
31331 ? 00:00:00 amdump
31342 ? 00:00:00 driver
31351 ? 00:04:37 taper
31352 ? 00:04:59 dumper
31353 ? 00:00:00 dumper
31354 ? 00:00:00 dumper
31355 ? 00:00:00 dumper
31356 ? 00:01:05 taper
31929 ? 00:06:39 amandad
31989 ? 00:00:00 sendbackup
31991 ? 00:04:40 sendbackup
31992 ? 00:00:00 sh
31994 ? 00:00:00 gzip
31995 ? 00:01:49 tar
31996 ? 00:00:01 sed
31997 ? 00:00:00 sh <defunct>
the amstatus DailySet1 always show :
Using /etc/amanda/DailySet1/amdump from Tue Feb 13 01:45:01 CET 2007
calys:/home 0 13011769k wait for dumping
lesia01:/Data 0263299570k dumping to tape (1:47:13)
lesia01:/home 2 145480k finished (1:47:00)
mesopl:/home 1 34940k finished (1:47:13)
secchirh:/home 2 39720k finished (1:47:08)
soleil:/home 1 40700k finished (1:47:04)
soljuke:/home 1 210k finished (1:46:55)
SUMMARY part real estimated
size size
partition : 7
estimated : 7 276572296k
flush : 0 0k
failed : 0 0k ( 0.00%)
wait for dumping: 1 13011769k ( 4.70%)
dumping to tape : 1 263299570k ( 95.20%)
dumping : 0 0k 0k ( 0.00%) ( 0.00%)
dumped : 6 261050k 263560527k ( 0.10%) ( 0.09%)
wait for writing: 0 0k 0k ( 0.00%) ( 0.00%)
wait to flush : 0 0k 0k (100.00%) ( 0.00%)
writing to tape : 0 0k 0k ( 0.00%) ( 0.00%)
failed to tape : 0 0k 0k ( 0.00%) ( 0.00%)
taped : 5 261050k 260957k (100.04%) ( 0.09%)
tape 1 : 5 261050k 260957k ( 0.07%) DailySet1-70
3 dumpers idle : not-idle
taper writing, tapeq: 0
network free kps: 4294937496
holding space : 7168000k (100.00%)
chunker0 busy : 0:00:00 ( 0.00%)
chunker1 busy : 0:00:00 ( 0.00%)
chunker2 busy : 0:00:00 ( 0.00%)
chunker3 busy : 0:00:00 ( 0.08%)
dumper0 busy : 0:00:10 ( 8.10%)
dumper1 busy : 0:00:02 ( 2.21%)
dumper2 busy : 0:00:09 ( 7.36%)
dumper3 busy : 0:00:13 ( 9.86%)
taper busy : 0:00:24 ( 18.31%)
0 dumpers busy : 0:00:14 ( 10.68%) no-diskspace: 0:00:13 ( 93.10%)
1 dumper busy : 0:00:05 ( 3.98%) no-diskspace: 0:00:03 ( 62.77%)
no-bandwidth: 0:00:01 ( 37.23%)
2 dumpers busy : 0:00:00 ( 0.00%)
3 dumpers busy : 0:00:07 ( 5.88%) no-diskspace: 0:00:07 (100.00%)
4 dumpers busy : 0:00:00 ( 0.00%)
i have attach the disklist and amanda.conf
so i asking myself if my failure was due to a scsi timeout.....because of the
sh defunct process on the client. (/Data from the backup server itself)
thanks to help me to understand what's going on....;
julien
Le mercredi 7 février 2007 17:35, Julien Brulé a écrit :
> hi all,
>
> i am trying to backup big filesystem and i get this errors
>
> ----------------------------------------------
> mptscsi: ioc2: attempting task abort! (sc=0000010272788040)
> scsi22 : destination target 6, lun 0
> command = Move medium/play audio(12) 00 00 00 00 f0 00 07 00 00 00
> 00 mptscsi: ioc2: task abort: SUCCESS (sc=0000010272788040)
> mptscsi: ioc2: attempting bus reset! (sc=0000010272788040)
> scsi22 : destination target 6, lun 0
> command = Move medium/play audio(12) 00 00 00 00 f0 00 07 00 00 00
> 00 mptbase: ioc2: IOCStatus(0x0048): SCSI Task Terminated
> mptscsi: ioc2: bus reset: SUCCESS (sc=0000010272788040)
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> mptscsi: ioc2: Attempting host reset! (sc=0000010272788040)
> mptbase: Initiating ioc2 recovery
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> scsi: Device offlined - not ready after error recovery: host 22 channel 0
> id 6 lun 0
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
> st0: Error on write filemark.
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
> mptbase: ioc2: IOCStatus(0x0043): SCSI Device Not There
> ----------------------------------------------
>
>
> I don't know if this is a hardware or a config problem. I doesn't cut out
> the filesystem.
>
> the scsi card is a SCSI storage controller: LSI Logic / Symbios Logic
> 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 07)
>
> and the library is :
>
> scsi26 : ioc2: LSI53C1030, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=233
> Vendor: HP Model: Ultrium 3-SCSI Rev: G25H
> Type: Sequential-Access ANSI SCSI revision: 03
> st: Version 20040403, fixed bufsize 32768, s/g segs 256
> Attached scsi tape st0 at scsi26, channel 0, id 4, lun 0
> st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA
> 3145727 Vendor: OVERLAND Model: LXB Rev: 0107
> Type: Medium Changer ANSI SCSI revision: 02
>
>
> I am using this packages :
>
> amanda-client-2.4.4p3-1
> amanda-server-2.4.4p3-1
> amanda-2.4.4p3-1
>
> This error comes when the taper is at the end of the tape. I should do a
> reset on the library to see the lto3 reader again, and then the tape is
> shown as slot 1: not an amanda tape (Input/output error).
>
> the amanda report show :
>
> /-- lesia01 /Data lev 0 FAILED [data write: Connection reset by peer]
> sendbackup: start [lesia01:/Data level 0]
> sendbackup: info BACKUP=/sbin/dump
> sendbackup: info RECOVER_CMD=/sbin/restore -f - ...
> sendbackup: info end
>
> | DUMP: Date of this level 0 dump: Wed Feb 7 01:51:33 2007
> | DUMP: Dumping /dev/cciss/c0d0p8 (/Data) to standard output
> | DUMP: Label: none
> | DUMP: Writing 10 Kilobyte records
> | DUMP: mapping (Pass I) [regular files]
> | DUMP: mapping (Pass II) [directories]
> | DUMP: estimated 266810611 blocks.
> | DUMP: Volume 1 started with block 1 at: Wed Feb 7 01:54:19 2007
> | DUMP: dumping (Pass III) [directories]
> | DUMP: dumping (Pass IV) [regular files]
> | DUMP: 3.39% done at 30136 kB/s, finished in 2:22
> | DUMP: 7.08% done at 31474 kB/s, finished in 2:11
> | DUMP: 10.94% done at 32446 kB/s, finished in 2:02
> | DUMP: 14.53% done at 32310 kB/s, finished in 1:57
> | DUMP: 18.18% done at 32337 kB/s, finished in 1:52
> | DUMP: 21.82% done at 32344 kB/s, finished in 1:47
> | DUMP: 25.65% done at 32590 kB/s, finished in 1:41
>
> \--------
>
> thanks for your help
>
> (sorry for my poor english..)
>
>
> julien brulé
#
# 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 /etc/amanda/csd/amanda.conf.
#
org "DailySet1" # your organization name for reports
mailto "[EMAIL PROTECTED]" # space separated list of operators at
your site
dumpuser "amandabackup" # the user to run dumps under
inparallel 4 # maximum dumpers that will run in parallel
netusage 600 Kbps # 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
tapecycle 25 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 # number of seconds per filesystem for estimates.
#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.
# Specify tape device and/or tape changer. If you don't have a tape
# changer, and you don't want to use more than one tape per run of
# amdump, just comment out the definition of tpchanger.
# Some tape changers require tapedev to be defined; others will use
# their own tape device selection mechanism. Some use a separate tape
# changer device (changerdev), others will simply ignore this
# parameter. Some rely on a configuration file (changerfile) to
# obtain more information about tape devices, number of slots, etc;
# others just need to store some data in files, whose names will start
# with changerfile. For more information about individual tape
# changers, read docs/TAPE.CHANGERS.
# At most one changerfile entry must be defined; select the most
# appropriate one for your configuration. If you select man-changer,
# keep the first one; if you decide not to use a tape changer, you may
# comment them all out.
runtapes 2 # number of tapes to be used in a single run of amdump
tpchanger "chg-zd-mtx" # the tape-changer glue script
tapedev "/dev/nst0" # the no-rewind tape device to be used
#rawtapedev "/dev/null" # the raw device to be used (ftape only)
#changerfile "/var/lib/amanda/DailySet1/changer"
#changerfile "/var/lib/amanda/DailySet1/changer-status"
changerfile "/etc/amanda/DailySet1/changer.conf"
changerdev "/dev/sg1"
tapetype HP-LTO3 # what kind of tape it is (see tapetypes below)
labelstr "^DailySet1-[0-9][0-9]*$" # label constraint regex: all tapes
must match
# Specify holding disks. These are used as a temporary staging area for
# dumps before they are written to tape and are recommended for most sites.
# The advantages include: tape drive is more likely to operate in streaming
# mode (which reduces tape and drive wear, reduces total dump time); multiple
# dumps can be done in parallel (which can dramatically reduce total dump time.
# The main disadvantage is that dumps on the holding disk need to be flushed
# (with amflush) to tape after an operating system crash or a tape failure.
# If no holding disks are specified then all dumps will be written directly
# to tape. If a dump is too big to fit on the holding disk than it will be
# written directly to tape. If more than one holding disk is specified then
# they will all be used round-robin.
#
#holdingdisk hd1 {
# comment "main holding disk"
# directory "/var/tmp/amanda-holding" # where the holding disk is
# use 3000 Mb # how much space can we use on it
# # a negative value mean:
# # use all space except that value
## chunksize 2 Gb # size of chunk if you want big dump to be
# # dumped on multiple files on holding disks
# # N Kb/Mb/Gb split disks in chunks of size N
# # 0 split disks in INT_MAX/1024 Kb chunks
# # -N Kb/Mb/Gb dont split, dump larger
# # filesystems directly to tape
# # (example: -2 Gb)
#}
#
holdingdisk hd2 {
directory "/tmp/amanda-hold1"
use 4000 Mb
chunksize 2 Gb
}
holdingdisk hd3 {
directory "/usr/local/tmp/amanda-hold2"
use 3000 Mb
chunksize 2 Gb
}
# 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
# incremental backups in this case, i.e., it will reserve 100% of the
# holding disk space for the so-called degraded mode backups.
# However, if you specify a different value for the `reserve'
# parameter, amanda will not degrade backups if they will fit in the
# non-reserved portion of the holding disk.
# reserve 30 # percent
# This means save at least 30% of the holding disk space for degraded
# mode backups.
# Amanda needs a few Mb of diskspace for the log and debug files,
# as well as a database. This stuff can grow large, so the conf directory
# isn't usually appropriate. Some sites use /usr/local/var and some /usr/adm.
# Create an amanda directory under there. You need a separate infofile and
# logdir for each configuration, so create subdirectories for each conf and
# put the files there. Specify the locations below.
infofile "/etc/amanda/DailySet1/curinfo" # database filename
logdir "/etc/amanda/DailySet1" # log directory
indexdir "/etc/amanda/DailySet1/index" # index directory
tapelist "/etc/amanda/DailySet1/tapelist" # list of used tapes
# tapelist is stored, by default, in the directory that contains amanda.conf
# tapetypes
# Define the type of tape you use here, and use it in "tapetype"
# above. Some typical types of tapes are included here. The tapetype
# tells amanda how many MB will fit on the tape, how big the filemarks
# are, and how fast the tape device is.
# A filemark is the amount of wasted space every time a tape section
# ends. If you run `make tapetype' in tape-src, you'll get a program
# that generates tapetype entries, but it is slow as hell, use it only
# if you really must and, if you do, make sure you post the data to
# the amanda mailing list, so that others can use what you found out
# by searching the archives.
# For completeness Amanda should calculate the inter-record gaps too,
# but it doesn't. For EXABYTE and DAT tapes this is ok. Anyone using
# 9 tracks for amanda and need IRG calculations? Drop me a note if
# so.
# If you want amanda to print postscript paper tape labels
# add a line after the comment in the tapetype of the form
# lbl-templ "/path/to/postscript/template/label.ps"
# if you want the label to go to a printer other than the default
# for your system, you can also add a line above for a different
# printer. (i usually add that line after the dumpuser specification)
# dumpuser "operator" # the user to run dumps under
# printer "mypostscript" # printer to print paper label on
# here is an example of my definition for an EXB-8500
# define tapetype EXB-8500 {
# ...
# lbl-templ "/usr/local/amanda/config/lbl.exabyte.ps"
# }
##
#define tapetype QIC-60 {
# comment "Archive Viper"
# length 60 mbytes
# filemark 100 kbytes # don't know a better value
# speed 100 kbytes # dito
#}
#
#define tapetype DEC-DLT2000 {
# comment "DEC Differential Digital Linear Tape 2000"
# length 15000 mbytes
# filemark 8 kbytes
# speed 1250 kbytes
#}
#
## [EMAIL PROTECTED]
## in amanda-users (Thu Dec 26 01:55:38 MEZ 1996)
#define tapetype DLT {
# comment "DLT tape drives"
# length 20000 mbytes # 20 Gig tapes
# filemark 2000 kbytes # I don't know what this means
# speed 1536 kbytes # 1.5 Mb/s
#}
#
#define tapetype SURESTORE-1200E {
# comment "HP AutoLoader"
# length 3900 mbytes
# filemark 100 kbytes
# speed 500 kbytes
#}
#
#define tapetype EXB-8500 {
# comment "Exabyte EXB-8500 drive on decent machine"
# length 4200 mbytes
# filemark 48 kbytes
# speed 474 kbytes
#}
#
#define tapetype EXB-8200 {
# comment "Exabyte EXB-8200 drive on decent machine"
# length 2200 mbytes
# filemark 2130 kbytes
# speed 240 kbytes
#}
#
#define tapetype HP-DAT {
# comment "DAT tape drives"
# # data provided by Rob Browning <[EMAIL PROTECTED]>
# length 1930 mbytes
# filemark 111 kbytes
# speed 468 kbytes
#}
#
#define tapetype DAT {
# comment "DAT tape drives"
# length 1000 mbytes # these numbers are not accurate
# filemark 100 kbytes # but you get the idea
# speed 100 kbytes
#}
#
#define tapetype MIMSY-MEGATAPE {
# comment "Megatape (Exabyte based) drive through Emulex on Vax 8600"
# length 2200 mbytes
# filemark 2130 kbytes
# speed 170 kbytes # limited by the Emulex bus interface, ugh
#}
#
#http://wiki.zmanda.com/index.php/Tapetype_definitions#LTO_Ultrium_3_with_400.2F800_Gbyte_tapes
define tapetype LTO3-400 {
comment "LTO Ultrium 3 400/800, compression off"
length 402432 mbytes
filemark 0 kbytes
speed 71702 kps
}
define tapetype LTO3-400-HWC {
comment "LTO Ultrium 3 400/800, compression on"
length 401408 mbytes
filemark 0 kbytes
speed 74343 kps
}
define tapetype HP-LTO3 {
comment "just produced by tapetype prog (hardware compression on)"
length 386048 mbytes
filemark 0 kbytes
speed 67921 kps
}
# dumptypes
#
# These are referred to by the disklist file. The dumptype specifies
# certain parameters for dumping including:
# auth - authentication scheme to use between server and client.
# Valid values are "bsd" and "krb4". Default: [auth bsd]
# comment - just a comment string
# comprate - set default compression rate. Should be followed by one or
# two numbers, optionally separated by a comma. The 1st is
# the full compression rate; the 2nd is the incremental rate.
# If the second is omitted, it is assumed equal to the first.
# The numbers represent the amount of the original file the
# compressed file is expected to take up.
# Default: [comprate 0.50, 0.50]
# compress - specify compression of the backed up data. Valid values are:
# "none" - don't compress the dump output.
# "client best" - compress on the client using the best (and
# probably slowest) algorithm.
# "client fast" - compress on the client using fast algorithm.
# "server best" - compress on the tape host using the best (and
# probably slowest) algorithm.
# "server fast" - compress on the tape host using a fast
# algorithm. This may be useful when a fast
# tape host is backing up slow clients.
# Default: [compress client fast]
# dumpcycle - set the number of days in the dump cycle, ie, set how often a
# full dump should be performed. Default: from DUMPCYCLE above
# exclude - specify files and directories to be excluded from the dump.
# Useful with gnutar only; silently ignored by dump and samba.
# Valid values are:
# "pattern" - a shell glob pattern defining which files
# to exclude.
# gnutar gets --exclude="pattern"
# list "filename" - a file (on the client!) containing patterns
# re's (1 per line) defining which files to
# exclude.
# gnutar gets --exclude-from="filename"
# Note that the `full pathname' of a file within its
# filesystem starts with `./', because of the way amanda runs
# gnutar: `tar -C $mountpoint -cf - --lots-of-options .' (note
# the final dot!) Thus, if you're backing up `/usr' with a
# diskfile entry like ``host /usr gnutar-root', but you don't
# want to backup /usr/tmp, your exclude list should contain
# the pattern `./tmp', as this is relative to the `/usr' above.
# Please refer to the man-page of gnutar for more information.
# Default: include all files
# holdingdisk - should the holding disk be used for this dump. Useful for
# dumping the holding disk itself. Default: [holdingdisk yes]
# ignore - do not back this filesystem up. Useful for sharing a single
# disklist in several configurations.
# index - keep an index of the files backed up. Default: [index no]
# kencrypt - encrypt the data stream between the client and server.
# Default: [kencrypt no]
# maxdumps - max number of concurrent dumps to run on the client.
# Default: [maxdumps 1]
# priority - priority level of the dump. Valid levels are "low", "medium"
# or "high". These are really only used when Amanda has no
# tape to write to because of some error. In that "degraded
# mode", as many incrementals as will fit on the holding disk
# are done, higher priority first, to insure the important
# disks are at least dumped. Default: [priority medium]
# program - specify the dump system to use. Valid values are "DUMP" and
# "GNUTAR". Default: [program "DUMP"].
# record - record the dump in /etc/dumpdates. Default: [record yes]
# skip-full - skip the disk when a level 0 is due, to allow full backups
# outside Amanda, eg when the machine is in single-user mode.
# skip-incr - skip the disk when the level 0 is NOT due. This is used in
# archive configurations, where only full dumps are done and
# the tapes saved.
# starttime - delay the start of the dump? Default: no delay
# strategy - set the dump strategy. Valid strategies are currently:
# "standard" - the standard one.
# "nofull" - do level 1 dumps every time. This can be used,
# for example, for small root filesystems that
# only change slightly relative to a site-wide
# prototype. Amanda then backs up just the
# changes.
# "noinc" - do level 0 dumps every time.
# Unfortunately, this is not currently
# implemented. Use `dumpcycle 0'
# instead.
# "skip" - skip all dumps. Useful for sharing a single
# disklist in several configurations.
# Default: [strategy standard]
#
# Note that you may specify previously defined dumptypes as a shorthand way
# of defining parameters.
#
# Paramètres globaux pour sauvegarde ----->> index=yes et record=yes
#
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere. All dumptype definitions in this sample file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
index yes
record yes
}
define dumptype always-full {
global
comment "Full dump of this filesystem always"
compress none
priority high
dumpcycle 0
}
#
# Pour les partitions "/"
#
define dumptype comp-root {
global
comment "Root partitions with compression"
compress client fast
priority low
}
define dumptype nocomp-root {
comp-root
comment "Root partitions without compression"
compress none
}
define dumptype nocomp-root-index {
comp-root
comment "Root partitions without compression"
compress none
index yes
}
define dumptype nocomp-root-index-nohold {
comp-root
comment "Root partitions without compression"
compress none
index yes
holdingdisk no
}
define dumptype root-tar {
global
program "GNUTAR"
comment "root partitions dumped with tar"
compress none
index
exclude list "/usr/local/lib/amanda/exclude.gtar"
priority low
}
define dumptype comp-root-tar {
root-tar
comment "Root partitions with compression"
compress client fast
}
define dumptype high-tar {
root-tar
comment "partitions dumped with tar"
priority high
}
#
# Pour les autres partitions
#
define dumptype user-tar {
root-tar
comment "user partitions dumped with tar"
priority medium
}
define dumptype comp-user-tar {
user-tar
compress client fast
}
define dumptype comp-user {
global
comment "Non-root partitions on reasonably fast machines"
compress client fast
priority medium
}
define dumptype nocomp-user {
comp-user
comment "Non-root partitions on slow machines"
compress none
}
#
# Pour les espaces temporaires de sauvegarde
#
define dumptype holding-disk {
global
comment "The master-host holding disk itself"
holdingdisk no # do not use the holding disk
priority medium
}
#
# Pour grands espaces disque
#
define dumptype comp-high {
global
comment "very important partitions on fast machines"
compress client best
priority high
}
define dumptype nocomp-high {
comp-high
comment "very important partitions on slow machines"
compress none
}
#
# Pour grands espaces disque découpé tape_splitsize
#
define dumptype comp-high-split {
global
tape_splitsize 40 gb
comment "very important partitions to split on fast machines"
compress client best
}
define dumptype nocomp-high-split {
comp-high-split
tape_splitsize 40 gb
comment "very important partitions to split on slow machines"
compress none
}
#
#
# Pour grands espaces disque avec tar découpé tape_splitsize
#
define dumptype comp-high-tar-split {
global
program "GNUTAR"
tape_splitsize 40 gb
comment "very important partitions to split on fast machines"
compress client best
}
define dumptype nocomp-high-tar-split {
comp-high-split
program "GNUTAR"
tape_splitsize 40 gb
comment "very important partitions to split on slow machines"
compress none
}
# Pour test --->> record=no
#
define dumptype nocomp-test {
global
comment "test dump without compression, no /etc/dumpdates recording"
compress none
record no
priority medium
}
define dumptype comp-test {
nocomp-test
comment "test dump with compression, no /etc/dumpdates recording"
compress client fast
}
# network interfaces
#
# These are referred to by the disklist file. They define the attributes
# of the network interface that the remote machine is accessed through.
# Notes: - netusage above defines the attributes that are used when the
# disklist entry doesn't specify otherwise.
# - the values below are only samples.
# - specifying an interface does not force the traffic to pass
# through that interface. Your OS routing tables do that. This
# is just a mechanism to stop Amanda trashing your network.
# Attributes are:
# use - bandwidth above which amanda won't start
# backups using this interface. Note that if
# a single backup will take more than that,
# amanda won't try to make it run slower!
define interface local {
comment "a local disk"
use 1000 kbps
}
#define interface eth0 {
# comment "10 Mbps ethernet"
# use 400 kbps
#}
#
define interface bond0 {
comment "100 Mbps ethernet"
use 400 kbps
}
# You may include other amanda configuration files, so you can share
# dumptypes, tapetypes and interface definitions among several
# configurations.
#includefile "/usr/local/amanda.conf.main"
#fichier disklist
#---------------------------------------------------------
# Serveur calys
#--------------------------------------------------------
calys /home nocomp-user
#calys /var/lib/mysql nocomp-user
#---------------------------------------------------------
# Serveur lesia01
#--------------------------------------------------------
#partition root
#lesia01 / nocomp-root-index -1 local
#partition home
lesia01 /home nocomp-root-index -1 local
#partition Data
lesia01 /Data nocomp-high-tar-split -1 local
#---------------------------------------------------------
# Serveur mesopl
#--------------------------------------------------------
mesopl /home nocomp-user
#---------------------------------------------------------
# Serveur secchirh
#--------------------------------------------------------
secchirh /home nocomp-user
#secchirh /data_raid nocomp-user
#---------------------------------------------------------
# Serveur soleil
#--------------------------------------------------------
soleil /home nocomp-user
#soleil /data1 nocomp-user
#soleil /data2 nocomp-user
#soleil /data3 nocomp-user
#soleil /data4 nocomp-user
#soleil /raid0 nocomp-user
#---------------------------------------------------------
# Serveur soljuke
#--------------------------------------------------------
soljuke /home nocomp-user
#soljuke /juke nocomp-user
#soljuke /data nocomp-user
#---------------------------------------------------------
# Serveur venus
#---------------------------------------------------------
#venus /home nocomp-user
#venus /data nocomp-user
#---------------------------------------------------------
# Autres Machines
#partition home
#pcspajb sda4 nocomp-user -1 bond0
