Re: amanda - my way ?
Hi, if i had to decide what to do, i would do both, a) and b). Why? you won't beleave it, but a few weeks ago at one of our customers 2 of 3 drives in a scsi raid5-array died in a periode of half an hour. They where more then happy having all their data on tape, and back on a replacement-disk in about 4 hours. Amanda rocks But it was a hard fight to convince them to do backups parallel to their raid-5 array. Their argument: why backup, we have raid Christoph Gene Heskett wrote: > On Monday 13 May 2002 06:08 pm, John Koenig wrote: > >>I recommend either: >> >>a) spend REAL BIG money on adequate tape library with at least >>10 8mm tapes (AIT-2, for example). >> >>or >> >>b) spend much smaller amount of money on large RAID-5 array of >>many many gigabytes using 3ware IDE card and cheap IDE disks... >>then back up to disk and forget the tapes. >> > > Thats essentially what we did. We built a machine with 4 160 gig > drives on 2 promise controllers in a software raid that gives us > 320 gigs of recoverable if only one drive at a time dies, storage. > > We're using rsync to do the actual data movement, gradually > adding the rest of the house to its list. All run by cron of > course. Over a 100mbps circuit it only takes a few minutes. > Anytime we need a file recovered, its a simple search of that > machine name and path to find it, and a simple copyback. > > >>Now go ride! >> > > And you won't get so many bugs on your teeth if you wear a > full-face helmet. Thats the observations of a nearly 50 year > rider, estimated at half a million miles, down twice, one ankle, > one rib. But the reflexes are going so I sold the last ride 2 > years ago. But I still miss it... > >
Re: amanda - my way ?
On Monday 13 May 2002 06:08 pm, John Koenig wrote: >I recommend either: > > a) spend REAL BIG money on adequate tape library with at least > 10 8mm tapes (AIT-2, for example). > >or > > b) spend much smaller amount of money on large RAID-5 array of > many many gigabytes using 3ware IDE card and cheap IDE disks... > then back up to disk and forget the tapes. Thats essentially what we did. We built a machine with 4 160 gig drives on 2 promise controllers in a software raid that gives us 320 gigs of recoverable if only one drive at a time dies, storage. We're using rsync to do the actual data movement, gradually adding the rest of the house to its list. All run by cron of course. Over a 100mbps circuit it only takes a few minutes. Anytime we need a file recovered, its a simple search of that machine name and path to find it, and a simple copyback. >Now go ride! And you won't get so many bugs on your teeth if you wear a full-face helmet. Thats the observations of a nearly 50 year rider, estimated at half a million miles, down twice, one ankle, one rib. But the reflexes are going so I sold the last ride 2 years ago. But I still miss it... -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 98.89+% setiathome rank, not too shabby for a hillbilly
Re: I need help getting amanda working
Is '0' a valid number for runspercycle (that's a rhetorical question for the developers on the list)? You're telling planner that Amanda is run 0 times during the 5 days of your dumpcycle. It might not be the reason you get no output, but if you're trying to do what I think you are (i.e. run Amanda 5 days a week), you should have a dumpcycle of 7 and a runspercycle of 5. You probably also want a larger tapecycle, since with 5 tapes for 5 runs you will be overwriting the only level 0 of some of your filesystems each day, and if it should fail you will not be able to restore all of your disks. Frank --On Monday, May 13, 2002 15:35:32 -0700 Doug Silver <[EMAIL PROTECTED]> wrote: > On Mon, 13 May 2002, Andrew Falanga wrote: > >> >> That's just it. I'm not getting any error's. Nothing. I'm not getting >> any mail sent to user amanda. I've thined out the comments from my conf >> file, and I'm pasting that in to this message. I don't get it. >> >> Andy >> >> org "TestSet1" # your organization name for reports >> mailto "afalanga" # space separated list of operators at your site >> dumpuser "amanda" # 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 5 days# the number of days in the normal dump cycle >> runspercycle 0 # the same as dumpcyle >> tapecycle 5 tapes # the number of tapes in rotation >> >> >> 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 est. >> >> runtapes 1 # number of tapes to be used in a single run of >> amdump >> > [snip] >> logdir "/var/amanda/log" # log directory >> infofile "/var/amanda/log/TestSet1/curinfo" # database filename >> indexdir "/var/amanda/log/TestSet1/index" # index directory > [snip] > > Well your configuration looks okay. So when you run 'amcheck TestSet1' > it checks out okay and 'amdump TestSet1' nothing happens?? > > I'd look in the various configuration areas, i.e. /tmp/Amanda and > /var/amanda/log/TestSet1 for information as to what Amanda is doing -- or > not doing. > > > -- > ~~ > Doug Silver > Network Manager > Urchin Corporationhttp://www.urchin.com > ~~ > -- Frank Smith[EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: I need help getting amanda working
On Mon, 13 May 2002, Andrew Falanga wrote: > > That's just it. I'm not getting any error's. Nothing. I'm not getting > any mail sent to user amanda. I've thined out the comments from my conf > file, and I'm pasting that in to this message. I don't get it. > > Andy > > org "TestSet1" # your organization name for reports > mailto "afalanga" # space separated list of operators at your site > dumpuser "amanda" # 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 5 days# the number of days in the normal dump cycle > runspercycle 0 # the same as dumpcyle > tapecycle 5 tapes # the number of tapes in rotation > > > 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 est. > > runtapes 1 # number of tapes to be used in a single run of > amdump > [snip] >logdir "/var/amanda/log" # log directory >infofile "/var/amanda/log/TestSet1/curinfo" # database filename >indexdir "/var/amanda/log/TestSet1/index" # index directory [snip] Well your configuration looks okay. So when you run 'amcheck TestSet1' it checks out okay and 'amdump TestSet1' nothing happens?? I'd look in the various configuration areas, i.e. /tmp/Amanda and /var/amanda/log/TestSet1 for information as to what Amanda is doing -- or not doing. -- ~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~
Re: amanda - my way ?
I recommend either: a) spend REAL BIG money on adequate tape library with at least 10 8mm tapes (AIT-2, for example). or b) spend much smaller amount of money on large RAID-5 array of many many gigabytes using 3ware IDE card and cheap IDE disks... then back up to disk and forget the tapes. :) Now go ride! ## PS: To the amanda-users list... I could have sent my response via private e-mail however I thought by posting this opinion I would get some other opinions... This is my opinion after working with amanda for a while... however I am far from an expert.
Re: I need help getting amanda working
>
> It sounds like you're in a testing mode right now. It would also help us
> to figure out the exact problem if you included the error message and what
> your dumpcycle and tapecycle are in your amanda.conf file. If you want to
> remove the tape in a brute force manner, you could remove it out of the
> tapelist file. However, keep in mind that the strategy with Amanda is to
> tell it how many tapes you're going to use over a time period and once
> those tapes are properly labeled, Amanda will tell you which tape it wants
> next.
>
> e.g. I'm on a 15 tape, 3 week cycle, labeled 'VOL[1-3][1-5]' (1st Monday
> is VOL11). If I try to put in VOL 22 on a Monday, Amanda will not dump it
> to the tape but it will dump it to the holding disk.
>
> Time for some coffee ...
>
>
That's just it. I'm not getting any error's. Nothing. I'm not getting
any mail sent to user amanda. I've thined out the comments from my conf
file, and I'm pasting that in to this message. I don't get it.
Andy
org "TestSet1" # your organization name for reports
mailto "afalanga" # space separated list of operators at your site
dumpuser "amanda" # 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 5 days# the number of days in the normal dump cycle
runspercycle 0 # the same as dumpcyle
tapecycle 5 tapes # the number of tapes in rotation
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 est.
runtapes 1 # number of tapes to be used in a single run of
amdump
# Tape dev info
tapedev "/dev/nst0" # non-rewinding tape device block name
tapetype DEC-DLT2000# what kind of tape it is (see tapetypes below)
labelstr "^TestSet1[0-9][0-9]*$"# label constraint regex: all
tapes must match
holdingdisk hd2 {
comment "main holding disk"
directory "/mnt/holding-tank" # mount point of holding disk
use 17 Gb
}
logdir "/var/amanda/log" # log directory
infofile "/var/amanda/log/TestSet1/curinfo" # database filename
indexdir "/var/amanda/log/TestSet1/index" # index directory
# tapetypes
define tapetype DEC-DLT2000 {
comment "DEC Differential Digital Linear Tape 2000"
length 15000 mbytes
filemark 8 kbytes
speed 1250 kbytes
}
define dumptype global {
index yes
record no
}
define dumptype comp-test {
comment "test dump with compression, no /etc/dumpdates recording"
compress client fast
}
define dumptype local {
comment "dump of local file systems"
compress server best
}
# network interfaces
define interface local {
comment "a local disk"
use 1000 kbps
}
define interface eth0 {
comment "100 Mbps ethernet"
use 400 kbps
}
amanda - my way ?
Hi, I am not shure, I understood, what amanda is able to do: in the company I have 2 Win NT Server 4 SP6 1 Novell 3.12 1 Digital Alpha DEC/OSF 1 Win NT 4 Workstation (is to be changed to SUSE 7.3) 1 SuSE e-Mail Server II Most of them have a tape drive and do their backups. But most of these tape drives are on there bounds, I mean, they would need a second tape to backup all theier datas. i solved the problem now, by doing a complete backup about once a month, and then only backing up the datas beeing changed since the "monthly" backup. It is horrible, because I have would like to have the backups performed when noone is working to keep the datas consistent, so I have an other weekend job changing tapes. The horror is increased, because it is growing spring/summer and my motobikes are waiting for me ;-) ! So I have the idea (and my boss is willing to spend some money - not because of the motobikes- ): I install a PC with about 160GB space on IDE-HD and a tape-autoloader. It is getting Linux and amanda. My dream would be, I have amanda do a complete copy from (most of) the other servers to the HD and then (maybe during day) do a backup on mutliple tapes of the autoloader. So I change 4 or 5 tapes once a day and have an actual copy of all my datas on the HDs and on the tapes the yesterdays copy. Can this work? Is this normal function or something special hardly to configure, only with direkt mental help from a amanda-guru and some special rare herbs growing in the upmost peaks of himalaya, working only when gathered in deepest night with golden sickle, ... ? Thanks for any hints. Martin Schmidt [EMAIL PROTECTED]
Re: Amanda dump level policy
On Mon, 13 May 2002 at 8:29pm, Niall O Broin wrote > So if I want to persuade amanda to use more tape I should shorten the dump > cycle, correct ? But I have a DDS-3 with native capacity of 12 GB and no > changer. What happens if in a dump cycle there's more to be backed up than > can fit on the tape e.g. if a lot happens to change on a couple of > filesystems and level 1s get large ? What falls off the edge of the world ? > The biggest danger is overwriting the only level 0 you have of a particular filesystem. Amanda will try *very* hard not to do this, and will warn you when it's about to happen, and when it has. This danger is mitigated if you have a tapecycle significantly longer (>2X, e.g.) than your dumpcycle*runtapes. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda dump level policy
On Mon, May 13, 2002 at 02:07:28PM -0400, Joshua Baker-LePain wrote: > On Mon, 13 May 2002 at 6:55pm, Niall O Broin wrote > > > It would seem to me that amanda should use the tape as much as it can and > > promote as many dumps as necessary to do that but it doesn't seem to do so > > from what I've seen. Is there a minimum number of runs before amanda will > > repeat a level 0 for a disk ? > > Amanda promotes and bumps dumps (within the parameters you set, e.g. > dumpcycle, bumpsize, etc) with the goal of equalizing (not maximizing) > tape usage. I.e., the goal is to have each night's run use the same > amount of tape. So if I want to persuade amanda to use more tape I should shorten the dump cycle, correct ? But I have a DDS-3 with native capacity of 12 GB and no changer. What happens if in a dump cycle there's more to be backed up than can fit on the tape e.g. if a lot happens to change on a couple of filesystems and level 1s get large ? What falls off the edge of the world ? Regards, Niall O Broin
Re: Amanda dump level policy
On Mon, 13 May 2002 at 6:55pm, Niall O Broin wrote > It would seem to me that amanda should use the tape as much as it can and > promote as many dumps as necessary to do that but it doesn't seem to do so > from what I've seen. Is there a minimum number of runs before amanda will > repeat a level 0 for a disk ? Amanda promotes and bumps dumps (within the parameters you set, e.g. dumpcycle, bumpsize, etc) with the goal of equalizing (not maximizing) tape usage. I.e., the goal is to have each night's run use the same amount of tape. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Question in case of disaster
On Mon, 13 May 2002, Anthony A. D. Talltree wrote: > There's a lot to be said for printing tape labels or case inserts that > document the contents of each tape -- or for printing each day's results > and keeping them in a binder. Definitely. I enabled that from day one. After I fixed up the templates, as described a few weeks ago in this list, they print nicely. Each morning I pick up a new case insert in the printer, cut a little, fold a little and it's done. Makes the stack of tapes look really professional. -- Ulrik Sandberg
Amanda dump level policy
How does Amanda decide what it's going to do, dump-level wise. From the POV of ease of restoration, level 0 every day is the easiest way to go. From the POV of minimising tape usage, bumping the dump level every day is the way to go. Between these two extremes, depending on your tape capacity and the capacity of the disks in your disklist, is the optimum strategy for amanda. I know that amanda tries to make sure that each disk in the disklist has as level 0 dump at least once in the cycle, and also that it will bump a dump of a disk to a higher level when it can save X MB (a configurable amount based on the bump variables), and also that it sometimes promotes a level 0 dump to earlier in the cycle when it has space. But exactly how does it decide this ? It would seem to me that amanda should use the tape as much as it can and promote as many dumps as necessary to do that but it doesn't seem to do so from what I've seen. Is there a minimum number of runs before amanda will repeat a level 0 for a disk ? Kindest regards, Niall O Broin
Re: I need help getting amanda working
On Mon, 13 May 2002, Andrew Falanga wrote: > Ok, > > I don't quite understand things I guess. The week before last, I > couldn't get amanda to work because it didn't want to overwrite the tape > I had used to run amcheck with. So, I relabeled the tape, and set > things up to run again. This time, I get back in to work today and go > through the log files generated (for some reason I can't get them with > amreport this time, but that's not part of this). > > This time is says, it can't overwrite an active tape. Why not? > Aren't they supposed to be active? What is going wrong here? > > Andy > It sounds like you're in a testing mode right now. It would also help us to figure out the exact problem if you included the error message and what your dumpcycle and tapecycle are in your amanda.conf file. If you want to remove the tape in a brute force manner, you could remove it out of the tapelist file. However, keep in mind that the strategy with Amanda is to tell it how many tapes you're going to use over a time period and once those tapes are properly labeled, Amanda will tell you which tape it wants next. e.g. I'm on a 15 tape, 3 week cycle, labeled 'VOL[1-3][1-5]' (1st Monday is VOL11). If I try to put in VOL 22 on a Monday, Amanda will not dump it to the tape but it will dump it to the holding disk. Time for some coffee ... -- ~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~
Re: Question in case of disaster
There's a lot to be said for printing tape labels or case inserts that document the contents of each tape -- or for printing each day's results and keeping them in a binder.
Re: Amanda I/O error!
On Mon, 13 May 2002 at 6:23pm, Alexander Belik wrote > I have Input/output error. But I have cleaned my device. Dirty tapes aren't the only source of I/O errors. Look in your system logs for what type of I/O error the kernel reported. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Amanda I/O error!
I have Input/output error. But I have cleaned my device.
P.S. I have red FAQ
--
[EMAIL PROTECTED]ICQ: 41776461
2:465/207@Fidonet Alexander Belik
http://www.vnet.dn.ua[EMAIL PROTECTED]
-- Forwarded message --
These dumps were to tape AUTH5.
*** A TAPE ERROR OCCURRED: [[writing file: Input/output error]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: AUTH6.
FAILURE AND STRANGE DUMP SUMMARY:
wwwsda5 lev 1 FAILED [out of tape]
wwwsda2 lev 1 STRANGE
auth hda4 lev 0 FAILED [no more holding disk space]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:03
Run Time (hrs:min) 0:41
Dump Time (hrs:min)0:47 0:00 0:47
Output Size (meg) 682.80.0 682.8
Original Size (meg) 1708.40.0 1708.4
Avg Compressed Size (%)24.1--24.1 (level:#disks ...)
Filesystems Dumped 12 0 12 (1:10 2:2)
Avg Dump Rate (k/s) 248.8-- 248.8
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 1.20.01.2
Tape Used (%) 0.10.00.1 (level:#disks ...)
Filesystems Taped 8 0 8 (1:8)
Avg Tp Write Rate (k/s) 2696.2-- 2696.2
FAILED AND STRANGE DUMP DETAILS:
/-- wwwsda2 lev 1 STRANGE
sendbackup: start [www:sda2 level 1]
sendbackup: info BACKUP=/bin/gtar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/gtar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
? gtar: ./httpd/noc/cfg/sirius93.cfg_l: Warning: Cannot stat: No such file or directory
? gtar: ./httpd/noc/cfg/sirius93.cfg_l_32123: Warning: Cannot stat: No such file or
directory
| Total bytes written: 206530560 (197MB, 565kB/s)
sendbackup: size 201690
sendbackup: end
\
NOTES:
planner: Last full dump of auth:hda4 on tape overwritten in 1 run.
planner: Incremental of ultra:hda1 bumped to level 2.
taper: tape AUTH5 kb 6560 fm 9 writing file: Input/output error
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
auth hda21 25 64 256.0 0:01 0.0 0:002604.0
auth hda40 FAILED ---
mail sda111171192 16.4 0:09 17.9 0:003023.4
mail sda22 366610 366610 --6:27 948.3 N/A N/A
mail sdb21 532 64 12.0 0:07 2.6 0:002656.2
news sda11 17 64 376.5 0:00 0.0 0:002345.7
news sda311030128 12.4 0:04 21.3 0:003193.1
news sda511244480 38.6 0:02 239.3 0:002475.8
ultrahda12 1062569 226822 21.3 31:20 120.7 N/A N/A
www sda11 830 96 11.6 0:14 4.2 0:002614.7
www sda21 201690 91418 45.3 5:57 255.9 N/A N/A
www sda31 420128 30.5 0:18 3.6 0:002876.5
www sda51 113270 13570 12.0 2:12 102.5 FAILED
(brought to you by Amanda version 2.4.3b3)
I need help getting amanda working
Ok, I don't quite understand things I guess. The week before last, I couldn't get amanda to work because it didn't want to overwrite the tape I had used to run amcheck with. So, I relabeled the tape, and set things up to run again. This time, I get back in to work today and go through the log files generated (for some reason I can't get them with amreport this time, but that's not part of this). This time is says, it can't overwrite an active tape. Why not? Aren't they supposed to be active? What is going wrong here? Andy
Re: forcing a degraded backup
On Tue, May 07, 2002 at 07:52:10AM -0400, Jean-Louis Martineau wrote: > > > That's BAD, you can't use the same logdir for two configurations, logfile > > > will get erased. You will get the same problem with indexdir if you have > > > a disk in both config. > > > > I don't understand why ... note that both configs won't run at the same day > > (one day for backup to tape, next day a degraded backup). > > When I use 'history' in amrecover I get all the backups in the list, > > with the proper tapes. Also the log files are all there. > > It works now because it's a new config, After tapecycle days, one config > will erase the log and index of the other config. Ha OK. Hum, I can see a problem even with one config then: I think I should have dumpcycle=2 weeks and runspercycle=14, (one run per day) but I'll have only have half the expected tapes (as one run out of 2 will go to holding disk and will be flushed with the dump of the next run). I'm not sure how amanda will handle it. I already planned to have 14 tapes to have 2 cycles of tapes, so it should be OK. > > > > Why not use one config and edit your amanda.conf everyday, that could > > > be easily done by cron. > > > > I though at this, but I prefer static config files. This avoids problems > > in case the server goes down in the middle of a backup. > > I think that running a small sed script to patch a static config > file template before every amdump run is easier than using two configs. OK, I'll look at this. My problem with this approach is that if the server crashes in the middle of a degraded dump, then the wrong config will be in place until the next run, and amtape won't work (for use with amrecover for example). I agree this would be very bad luck. Also it has to be changed for amcheck too. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
Re: Question in case of disaster
On Sun, 12 May 2002, Jon LaBadie wrote: > 2. dump/restore are generic names for a type of backup and recovery pair > of programs found on many unix systems. The dump/restore pair have to > be specific for the "type" of file system they were written for. > > On linux "I think" you have programs named dump and restore. I do not, > I have ufsdump and ufsrestore. UFS is the type of file system on Solaris. > You might also have ext2dump or reiserfsdump. I could also have vxfsdump > (veritas fs). > > If you are like me, and not using dump/restore, but using tar, tar is both > your dump and your restore. > > 1. dd will recover the dump image. That could be a tar file or a dump file > depending on your backup program. Thank you (and the others) for the answers to my questions. Now I have a question for Amanda developers: is there any plan for Amanda to backup also on tape the backup index? I read about this feature on a commercial page on BRU, so maybe it will be possible to add this feature in Amanda too, smewhere in the future. Ave, Radu -- Radu Filip Network Administrator @ Technical University of Iasi [EMAIL PROTECTED] Information Technology and Communication Center http://socrate.tuiasi.ro/ [EMAIL PROTECTED] | http://ccti.tuiasi.ro/
