Script to handle Hargrove's vacation responder
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2004-05-03 19:35]:
> Hello, and thank you for your email.
>
> I shall be out of the office until Tuesday 4th May. Should your email
> require urgent attention, the please contact David Adams or email
> [EMAIL PROTECTED]
For dealing with Mr. Hargrove's vacation responder, I wrote the
following script, which might be useful to procmail users:
SPC="[ ]"
FROM_="(From${SPC}|(Old-|X-)?(Resent-)?\
(From|Reply-To|Sender):)(.*\<)?"
SENDER_ML=(owner-(\
[EMAIL PROTECTED]
|[EMAIL PROTECTED]
|[EMAIL PROTECTED](lne|ssz).com\
|[EMAIL PROTECTED]))
# Sender is owner mailing lists
#
:0
*$ ^Sender:.*$SENDER_ML
* ^Sender:.*owner-\/[a-z0-9.-]+@
* MATCH ?? ()\/[EMAIL PROTECTED]
{
LISTNAME=$MATCH
:0 :
*$ [EMAIL PROTECTED]
* B ?? out.of.the.office
/dev/null
:0 E:
mailing_lists/${LISTNAME}
}
I have not tested this with the Hargrove auto-responder code, but the
code is pretty simple and should work.
Re: New to Amanda- discouraged by some absurd limitations..
Mail-Followup-To: [EMAIL PROTECTED] * Jon LaBadie <[EMAIL PROTECTED]> [2004-05-02 12:44]: > On Sun, May 02, 2004 at 12:44:16PM -0600, Justin Gombos wrote: > > > > > IMHO this was rather rude way to bring up the issue, > > > > First of all, I did not know whether this was an issue, that's why I > > posted here. It was certainly proper to raise an Amanda > > issue/question to the amanda-users mailing list. > > The rude part was not your posting a question about the design of > amanda to this list. The rudeness came when you described an aspect > of amanda as "incredibly stupid" in your first posting to a list > that contains among it membership several people who have > contributed to amanda's development. Few people like to hear their > work described as stupid. It seemed like an incredibly stupid limitation to me. That is my opinion. Opinions are often welcome on mailing lists, even if they are offensive. It was not an ad hominem, or a flame. It was a remark about the functionality of a tool, and should be accepted. If you disagree, you are welcome to state your opinion that it would be stupid for Amanda to support such functionality. > Particularly by someone who doesn't know what they are talking > about. Exactly. For me to state that a certain functionality or lack thereof is "stupid," it's not just a statement about the subject, but it's also (intentionally) a statement about the author. This way, you know where I'm coming from, and what kind of user you're dealing with. Specifically, you're dealing with a user who is accustomed to tools that can put multiple volumes on a single media, and has never encountered this type of limitation. > > OTOH-- if you want to talk about etiquette, you should try not to > > ignore the mail-followup-to header on mailing list posts. > > I just looked back at your original post. I see no header directing > followups anywhere. Jonathan knows that many posters, particularly > new posters, do not subscribe to the list. It is not a requirement > for posting. Thus as a courtesy to you he sent a copy to you as well > as to the list. I just verified that I sent a Mail-Followup-To header. It seems the mailing list software is stripping out the Mail-Followup-To headers. So you are correct, Jonathan did not fail to honor the header, but rather the list software. I'll have to come up with alternatives. Maybe a mutt hook that will automatically append a signature with the Mail-Followup-To preferences. As a test, I'm adding a Mail-Followup-To line to the body and a X-Mail-Followup-To header to see if the list strips that too.
Re: New to Amanda- discouraged by some absurd limitations..
* Jonathan Dill <[EMAIL PROTECTED]> [2004-05-02 12:44]: > As others have pointed out, 700 MB CD-R is probably not going to be > adequate for backing up multiple clients across the network anyway. I'll have to figure that out. I'm having trouble realizing how Amanda behaves. So far it doesn't look like I can reasonably predict when each file gets backed up. It seems it can't do a full backup, and then small incrementals that include only changed files. > By "GNU" do you mean "covered under the terms of the Gnu Public > License"? Are you opposed to other free, or "free to use but > restricted" licensing? Is the point that you want something free or > very cheap, hence would not consider something like Arkeia? I subscribe to the Richard Stallman FSF.org philosophies, and prefer software that is no only free of charge, but also open source and with freedom to alter. I don't necessarily need those features in this case, but I try to support the movement whenever practical. This is what attracts me to Amanda.
Re: New to Amanda- discouraged by some absurd limitations..
* Stephen Carville <[EMAIL PROTECTED]> [2004-05-02 10:11]: > > What does a CD-R cost these days? About 35-40 cents apiece? The price is not the biggest issue here. I have a plastic tub full of hundreds of CDRs that were free after MIR. What I don't like is: 1) the effort of swapping the media daily (automation should reduce interaction) and the constant labelling, 2) the physical management.. having 350 CDs/year taking up physical space, and having more CDs to have to handle and account for in the event of recovery, 3) making unnecessary contributions to my local landfill.
Help: could not connect to HOST
Hello! I have a problem. My amanda mail report returns: FAILURE AND STRANGE DUMP SUMMARY: mailman /usr/local/etc lev 0 FAILED 20040503[could not connect to mailman] webserver2 /home/diegob lev 0 FAILED 20040503[could not connect to webserver2] mercurio /usr/local/apache lev 0 FAILED 20040503[could not connect to mercurio] ... DUMP SUMMARY: mailman -cal/uvscan 0 FAILED --- mercurio /boot 0 FAILED --- ... Any ideia? Thanks all!!! Taffarel
Re: Monthly Backup Problem
On Mon, May 03, 2004 at 10:01:47AM +0200, Paul Bijnens wrote: > Kianusch Sayah Karadji wrote: > > > [...] the plan was to not put in a > > tape, and have amanda backup everything to the dumps Partition. After that > > use amflush to move the data from the partition to tapes in several runs. > > Why so complicated? > Let it dump to one tape, and flush the rest in the morning to the other > tape(s). I do our all-level-0 configurations this way, but for a different reason: it more fully packs the first tape. Since taping doesn't start until all of the DLEs have been dumped, the largestfit algorithm has all the data it needs to fill the tape as full as possible. If instead we let amdump write the first tape, largestfit would pick the optimum DLE from among those available at the moment the drive became free, which would be suboptimal for minimizing tape usage. I'm not sure whether this applies to 2.4.3, since I don't know what (hardwired) tape algorithm it used. > runtapes 1 > maxdumpsize 90g That's what I did, but in 2.4.3, I presume one could get the same effect by increasing runtapes instead. In this situation, runtapes doesn't seem to have any direct effect on the actual number of tapes used :-/ > reserve 0 > taperalgo largestfit That's what we have. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau
Re: New to Amanda- discouraged by some absurd limitations..
On Monday May 03 2004 09:45 am, Jonathan Dill wrote: > Jon LaBadie wrote: > >One of the concerns I have about disk-only based backup schemes is the > >total loss of data. If you encounter a 2-disk failure you lose not only > >your most recent, but all your backups. If a tape drive fails the data > >can be read on another drive. If a single tape goes bad, that is the > >only set of backups lost. > > If you're using multiple removable hard drives as tapes, I think that > would mitigate the risk somewhat vs. disks that are "online" all the > time, although spin-up seems to be THE most crucial moment in the life > of any disk drive. I think disks still aren't as reliable as tapes in > terms of failure rates, but would expect a removable hard drive solution > to fall somewhere between full-time disk drives and tapes. I've been considering a backup to drive with daily copies made to tapes. I already use BackuoExec to backuop my Windoze boxes to a Samba share and then use Amanda to back those files up to tape. That works well so I don't see how a hybrid setup would be less robust than tapes alone. It means a lt lot of disk space -- in my case about 300 - 400 GB for a weeks worth -- but drives are getting real cheap. -- Stephen Carville http://www.heronforge.net/~stephen/gnupgkey.txt -- Right wing socialists hate privacy as much as left wing socialists hate guns.
Re: New to Amanda- discouraged by some absurd limitations..
Jon LaBadie wrote: One of the concerns I have about disk-only based backup schemes is the total loss of data. If you encounter a 2-disk failure you lose not only your most recent, but all your backups. If a tape drive fails the data can be read on another drive. If a single tape goes bad, that is the only set of backups lost. If you're using multiple removable hard drives as tapes, I think that would mitigate the risk somewhat vs. disks that are "online" all the time, although spin-up seems to be THE most crucial moment in the life of any disk drive. I think disks still aren't as reliable as tapes in terms of failure rates, but would expect a removable hard drive solution to fall somewhere between full-time disk drives and tapes. --jonathan
Re: New to Amanda- discouraged by some absurd limitations..
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: New to Amanda- discouraged by some absurd limitations..
On Mon, May 03, 2004 at 10:45:26AM -0400, Jonathan Dill wrote: > Which reminds me...If cost is a factor, now that FILE-DRIVER is an > option, RAID or removable hard drives may give you a better $/GB ratio > than tapes, and much more capacity than CD-R. I think this is a very > good option for a single computer or small network like Justin described > in his original e-mail. If you use removable drives or a RAID-1, you > might not need anything else, though it would be a good idea to still > dump more important files to tape or writable DVD media occasionally. I > haven't investigated it, but I have heard of hot-swap external SATA and > firewire options which would be very good indeed. > > 250 GB removable drives could be a great option if you are backing up > large partitions, say up to 500 GB uncompressed, so that you could get > around dumps not fitting on a single tape without having to use RAIT > with multiple tape drives, or very expensive tape drives and media, or > split up dumps with (IMHO inefficient and CPU/IO intensive) GNUTAR. > > In my case, I am using a 1 TB Snap Server 4500 in a RAID-5 configuration > and flushing mostly just the full dumps to 200/100 GB LTO (Ultrium-1). > Since RAID-5 has less redundancy than RAID-1, I am more concerned about > having at least some dumps on tape since a 2-disk failure would mean > that all of the data on the RAID-5 would be gone. > One of the concerns I have about disk-only based backup schemes is the total loss of data. If you encounter a 2-disk failure you lose not only your most recent, but all your backups. If a tape drive fails the data can be read on another drive. If a single tape goes bad, that is the only set of backups lost. Disk-based schemes seem to violate the amanda principle of never appending to a tape. All that negativity, yet I think I would setup a disk-based scheme for ease and speed of recovery but as Jonathan does, I would do some backups to tape also. That is why I've been wondering about a RAIT scheme where the backup is mirrored to disk and tape. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amdump searchs for log file
Hi list! I get no errors with amcheck Diaria but amdump doesnt work. *** THE DUMPS DID NOT FINISH PROPERLY! The next tape Amanda expects to use is: a new tape. The next new tape already labelled is: Diaria2. FAILURE AND STRANGE DUMP SUMMARY: amreport: ERROR could not open log /usr/adm/amanda/Diaria/log: No such file or directory irixoa06.d /amanda RESULTS MISSING I create a file called log in /usr/adm/amanda/Diaria/ as user amanda, but every time I run amdump its erased. And what about the tape expected? Is this message correct? Thanks _ Horóscopo, tarot, numerología... Escucha lo que te dicen los astros. http://astrocentro.msn.es/
Re: New to Amanda- discouraged by some absurd limitations..
Which reminds me...If cost is a factor, now that FILE-DRIVER is an option, RAID or removable hard drives may give you a better $/GB ratio than tapes, and much more capacity than CD-R. I think this is a very good option for a single computer or small network like Justin described in his original e-mail. If you use removable drives or a RAID-1, you might not need anything else, though it would be a good idea to still dump more important files to tape or writable DVD media occasionally. I haven't investigated it, but I have heard of hot-swap external SATA and firewire options which would be very good indeed. 250 GB removable drives could be a great option if you are backing up large partitions, say up to 500 GB uncompressed, so that you could get around dumps not fitting on a single tape without having to use RAIT with multiple tape drives, or very expensive tape drives and media, or split up dumps with (IMHO inefficient and CPU/IO intensive) GNUTAR. In my case, I am using a 1 TB Snap Server 4500 in a RAID-5 configuration and flushing mostly just the full dumps to 200/100 GB LTO (Ultrium-1). Since RAID-5 has less redundancy than RAID-1, I am more concerned about having at least some dumps on tape since a 2-disk failure would mean that all of the data on the RAID-5 would be gone. On Sun, 2004-05-02 at 20:53, [EMAIL PROTECTED] wrote: > In my Amanda experience, I was lucky enough to have a > large holding disk area and a tape drive which failed > spectacularly before even one backup was flushed. It gave > me the opportunity to see how Amanda works. The most > wonderful aspect was how happy "she" was to restore > from the holding disk. --jonathan
Re: Monthly Backup Problem
> maxdumpsize 90g > taperalgo largestfit Those are 2.4.4 options ... I run 2.4.3 ,,, But I got the idea :) Kianusch
Re: Q: tapeless Amanda
Raúl Wild-Spain wrote: I'm trying to configure a tapeless amanda ... I'm trying to understand the setup by your vague description. Please don't leave out the essential details while summarizing your setup. I've configured many directories as the amanda tapeless HowTo said ( Which HowTo? The one I find is called "HOWTO-FILE-DRIVER", all uppercase, and no mixed case. /backup/amanda/GARBI[01..11] -> 11 directories for 11 "slots"). I want And did you create the data symlink and info file too? And what did you specify as "taperdev" From the description below, I assume you use "chg-multi" as changer. Since amanda 2.4.4p2, there is a much simpler chg-disk, which doesn't even need a configuration file. amtape returns "amtape: could not load slot 1: file:/backup/amanda/GARBI01: not a device file". The same with amlabel. Your probably forgot to specify you're using a changer in amanda.conf: tpchanger "chg-multi" Or you're using an amanda pre 2.4.3 which does not know about the file driver. About config: * Debian Woody That's a little hint, but more imporant; what amanda version is installed? * /backup/amanda and /backup/amanda/GARBI* -> chmod 770 and chown backup:backup applied * created GARBI*/data directories And also done "chown backup:backup data"? * changer.conf -> "file:/backup/amanda/GARBI[01..11]" for each slot descriptor So you are using chg-multi? In that case do you have a in amanda.conf: changerfile "/the/path/to/changer.conf" But as said above, if you use "chg-disk" as changer than you don't even need a changer.conf file. * amanda.conf -> using a HARD-DISK device (5 mbytes) and hard-disk-tar descriptor Not really relevant for your problem, but 50 Gbyte for each of your 11 vtapes indicates you have a huge disk of 550 Gbyte? Or did you mean 4500 mbyte (4.5Gb * 11 < 50 Gbyte). What about the really relevant parameters "tpchanger" and "tapedev"? * Must I have an "chg-multi" script on my Debian? (I don't found it) If you want to use it, yes, you must. :-) It is sitting next to al the other changers in libexec (wherever that may be installed in Debian Woody.) -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Q: tapeless Amanda
Hello, and thank you for your email. I shall be out of the office until Tuesday 4th May. Should your email require urgent attention, the please contact David Adams or email [EMAIL PROTECTED] Regards, William Hargrove
Re: Q: tapeless Amanda
Hi, Raúl, on Montag, 03. Mai 2004 at 12:50 you wrote to amanda-users: RWS> Hi, RWS> I'm trying to configure a tapeless amanda ... RWS> I've configured many directories as the amanda tapeless RWS> HowTo said ( /backup/amanda/GARBI[01..11] -> 11 directories for RWS> 11 "slots"). I want to label each slot, but when I do: RWS> $amtape slot 1 RWS> $amlabel slot 1 RWS> amtape returns "amtape: could not load slot 1: RWS> file:/backup/amanda/GARBI01: not a device file". The same with RWS> amlabel. RWS> About config: RWS> * Debian Woody RWS> * /backup/amanda and /backup/amanda/GARBI* -> chmod 770 and chown backup:backup applied RWS> * created GARBI*/data directories * changer.conf ->> "file:/backup/amanda/GARBI[01..11]" * changer.conf ->> for each slot descriptor * amanda.conf ->> using a HARD-DISK device (5 * amanda.conf ->> mbytes) and hard-disk-tar descriptor RWS> * Must I have an "chg-multi" script on my Debian? (I don't found it) RWS> Any idea? Please consult the HOWTO-FILE-DRIVER in the docs-directory in your amanda-tarball. You need the line tpchanger "chg-disk" in your config, for example. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Q: tapeless Amanda
Hi, I'm trying to configure a tapeless amanda ... I've configured many directories as the amanda tapeless HowTo said ( /backup/amanda/GARBI[01..11] -> 11 directories for 11 "slots"). I want to label each slot, but when I do: $amtape slot 1 $amlabel slot 1 amtape returns "amtape: could not load slot 1: file:/backup/amanda/GARBI01: not a device file". The same with amlabel. About config: * Debian Woody * /backup/amanda and /backup/amanda/GARBI* -> chmod 770 and chown backup:backup applied * created GARBI*/data directories * changer.conf -> "file:/backup/amanda/GARBI[01..11]" for each slot descriptor * amanda.conf -> using a HARD-DISK device (5 mbytes) and hard-disk-tar descriptor * Must I have an "chg-multi" script on my Debian? (I don't found it) Any idea? thanks in advance, -- Raúl Cruz Tech Manager, Wild-Spain.com Tel/Fax (+34) 925 867636 www.wild-spain.com - Information on Nature and Outdoor travel in Spain -
Re: which partition in level 0 for next dump
BRINER Cedric wrote: I'm thinking to breaking down some of my _BIG_ partition, by using tar on their respective subdirectories. but when I will do this, amanda will perform a dump level 0. So I'd rather prefer to break down the ones who are going to be dumped at level 0 at the next amdump. any idea how to do this ? amadmin Config due -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
which partition in level 0 for next dump
Hi, I'm thinking to breaking down some of my _BIG_ partition, by using tar on their respective subdirectories. but when I will do this, amanda will perform a dump level 0. So I'd rather prefer to break down the ones who are going to be dumped at level 0 at the next amdump. any idea how to do this ? Regards Cédric BRINER
Re: Monthly Backup Problem
Hi! > Not needed, just change maxdumpsize (or runtapes). Thanks ... that's what I was looking for. > Why so complicated? Let it dump to one tape, and flush the rest in the > morning to the other tape(s). Just configure Amanda a little bit more, > to allow her to schedule all backups. Because at that time the Daily Backup-Tape is in the drive ... and as the tapes are changed by persons who do not know anything about what's going on - I want to avoid that they have to think! :) Regards Kianusch
Re: Monthly Backup Problem
Kianusch Sayah Karadji wrote: My Monthly Backup is designed to make a "level 0" from all available Data - which will not fit to one tape anyway - so the plan was to not put in a tape, and have amanda backup everything to the dumps Partition. After that use amflush to move the data from the partition to tapes in several runs. Why so complicated? Let it dump to one tape, and flush the rest in the morning to the other tape(s). Just configure Amanda a little bit more, to allow her to schedule all backups. Some parameters you'll need to set: # you may set runtapes to more if you like, amanda # will not find them all, and continue to disk runtapes 1 # Even with runtapes 1, you can let amanda plan # for a lot more gigabytes than fit on one tape maxdumpsize 90g # When dumping to holdingdisk because tapes are full # you need to lower the reserved-for-incremental space # Setting it to 0 percent lets all the space be used # for level0 backups. (Or set it to some low value.) reserve 0 # You can get amanda to optimize tape usage too. # See for an extended explanation: # http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2 taperalgo largestfit What i do now ist using a "dummy" tape definition with the following entry "length 9 mbytes", so that the backup is done in any case ... and changing the setup back to the correct value for tape operation. Not needed, just change maxdumpsize (or runtapes). -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
