Extracting amanda tapes without amanda ...
all, When you want to extract tapes from a tape WITHOUT using amanda how do you know which file a particular archive is located? Wouldnt it be a good idea to have a "table of content" located in the second BLOCk? Ie: when amanda starts writing it writes a zero filled 32k block to the second file and when its finshed doing all the work put a file in there containing archive_name1 directory1 FILEMARK1 archive_name2 directory2 FILEMARK2 archive_name3 directory3 FILEMARK3 This way you would only need to look up the block and could blindly restore JUST by looking at the content of the seocnd block. Or is there already a way existing and I didnt know about it? jobst -- The email address in this email is used for Mailing Lists Only. Please reply ONLY to the list email address, do not reply to the email directly, it ends up in /dev/null. File not found! Do you want me to fake it? __, Jobst Schmalenbach, Technical Director _ _.--'-n_/ Barrett Consulting Group P/L & The Meditation Room P/L -(_)--(_)= +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia
Re: This is a test message
On Thursday 22 January 2004 15:48, Kent L. Nasveschuk wrote: >I just joined this mailing list and I'm not clear at what address to >post messages.Hopefully this is it. > >Thanks You got it right :) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
This is a test message
I just joined this mailing list and I'm not clear at what address to post messages.Hopefully this is it. Thanks -- Kent L. Nasveschuk <[EMAIL PROTECTED]>
Re: concurrancy
Gene, > I would hope that the backups are being done as an unprivileged user, > bin has quite high rights on most systems. OTOH, the mailto: here is > root. As a matter of site policy all new installations are being configured to run as "amanda". > Thats why most of us have added a user 'amanda' and made amanda a > member of the group disk or bin, whichever works for your distro. > Unless you have an exclude list file in comp-root that > specifies ./maildb, ./maildb2 and ./home (on separete lines) you are > doing the whole of the last 3 filesystems twice each, once for / and > once per subdir listing. The last entry will also make you require a > seperate disklist entry for /home that doesn't specify the exclude > file. > > Thats of course unless the last 3 are in fact different disks > entirely, in which case you should append a 1, a 2, a 3, or a 4 in > order to define to amanda that they are separate physical disks and > can therefore be done concurrently. One should not attempt to backup > 2 different partitions on the same disk concurrently as that will > thrash the seeks, slowing things down a bit, or potentially > overheating the seek drivers and damaging the drive, but that would > be a very extreme result and something I've not seen in at least 5 > years. Yes, these are different disks. Mirrored too (should provide some read performance benifits as well as HW redundancy). Its a Lotus Notes server, many large files. BTW we are using native dump, not tar (not gnutar nor other). # df -kl Filesystemkbytesused avail capacity Mounted on /dev/md/dsk/d10 7789512 2510143 520147433%/ /proc 0 0 0 0%/proc fd 0 0 0 0%/dev/fd mnttab 0 0 0 0%/etc/mnttab swap 7670968 16 7670952 1%/var/run swap 8588192 917240 767095211%/tmp /dev/md/dsk/d40 52421967 36894141 1500360772%/maildb /dev/md/dsk/d60 70555171 27397902 4245171840%/maildb2 /dev/md/dsk/d30 17408538 7022817 1021163641%/export/home /dev/dsk/c1t4d0s070554178 9 69848628 1%/amanda/work > I have the situation in my /usr dir that there are a couple of the > subdirs that are more than a tapefull, so my /usr is broken down into > a /usr/subdir per disklist entry. The is no entry for / in my > disklist. > > There are also good reasons to use a non-compressing dumptype for some > dirs as they will grow rather than compress if they contain mostly > executable binaries. Likewise for dirs that contain already > compressed archives & rpms. Its a waste of gzips time to try and > compress them further. A good argument for a bit of reason in the > directory layouts :) Compression on these disks is pretty successful. Using SW rather than HW compression. > You can see which ones you are wasting compression efforts (and cpu > horsepower) on by looking at the reported compression achieved, in > the email from amanda, and switching those entrys that only get 5 or > 10% to a non-compressing dumptype, there by saveing a lot of useless > wheel-spinning by gzip. > It doesn't seem to be at all sensitive to whitespace here. I use tabs > liberally for formatting in mine, but an equal amount of spaces is > also just fine. That at least is good news. Too bad there isn't really a syntax checker for amanda.conf - would potentially have saved me from making myself crazy over the typo I had in the columnspec param last month. > The use of spindle numbers in the dle perhaps. Nope, default (blank) doesn't do any blocking. Thanks Gene, Brian
RE: multiple disklists
Thanks for the info... I'll check it out.
-Rob
> -Original Message-
> From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 22, 2004 11:14 AM
> To: Amanda List
> Subject: Re: multiple disklists
>
>
> Hi, Dege, Robert C.,
>
> on Donnerstag, 22. Jänner 2004 at 17:06 you wrote to amanda-users:
>
>
> DRC> Is there a way to have multiple disklists per config? I
> plan is to
> DRC> alternate the amdump cycles with the different
> disklists. I'm running into
> DRC> a tape space issue, and am trying to split my disklist
> into 2 disklists; one
> DRC> with lower priority backups & one with higher priority
> backups. The one
> DRC> with the lower priority would run like twice a week,
> while the higher
> DRC> priority disklist would run 5 times a week.
>
> Seems to be the strange-questions-day ;) ...
>
> Why not use two dumptypes?
>
> For example:
>
> > define dumptype important {
> > dumpcycle 2
> > priority high
> > }
>
> > define dumptype unimportant {
> > dumpcycle 5
> > priority low
> > }
>
> You get less lev0 for the "unimportant" stuff so you save space for
> the important ones.
>
> Let AMANDA schedule!
> --
> best regards,
> Stefan
>
> Stefan G. Weichinger
> mailto:[EMAIL PROTECTED]
>
>
>
Re: concurrancy
Brian Cuttler wrote: Unfortunately my amanda run didn't run any more quickly. Now you'll have to find out where the bottleneck is. in the ~amanda directory, there is a directory with the same name as the config, and in it you find files named "amdump.xx". Look at the last one (amdump.1), and locate the lines starting with: driver: state ... These lines end in a string indicating why driver was not able to add more concurrency, like: ... driver-idle: client-constraint ... driver-idle: no-dumpers ... driver-idle: no-diskspace etc, or even: ... driver-idle: not-idle :-) You may send me the file to analyze if you like . -- 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: amrecover with file: driver
Stefan, The settape section of the man page for amrecover says: "settape [[server]:][tapedev|default] If you want amrecover to use your changer, the tapedev must be equal to the amrecover_changer setting on the server." I used this setting in amanda.conf: amrecover_changer chg-disk then, in amrecover: settape chg-disk and the extract invokes the chg-disk script and sets the "./data" sym-link to the correct slot automatically. Very nice! Marc. It appears that using "settape chg-disk" in amrecover On Thu, 2004-01-22 at 09:17, Stefan G. Weichinger wrote: > Hi, Marc, > > on Donnerstag, 22. JÃnner 2004 at 16:59 you wrote to amanda-users: > > ML> I'm using the chg-disk changer. Does amrecover use the changer script? > > Good question. There is the parameter amrecover_changer which > explicitly sets the changer used. Maybe you try to set this in your > conf. > > ML> And would it be possible to modify the script to choose the correct > ML> slot? > > As soon as I know it I will tell you ;) > Practically YES, it is possible.
Re: concurrancy
On Thursday 22 January 2004 10:11, Brian Cuttler wrote: >Stefan, >Gene, >Paul, > >Unfortunately my amanda run didn't run any more quickly. > >From amanda.conf - I can send more if you want to see more. > >org "NOTES_DLT" # your organization name for reports >mailto "[EMAIL PROTECTED]"# the mailing list > for operators at your site >dumpuser "bin" # the user to run dumps under I would hope that the backups are being done as an unprivileged user, bin has quite high rights on most systems. OTOH, the mailto: here is root. Thats why most of us have added a user 'amanda' and made amanda a member of the group disk or bin, whichever works for your distro. ># changed from 8 to 4... can't explain excessive time to backup 4 > partitions -ck inparallel 4# maximum dumpers that will > run in parallel # maxdumps, added 21-jan-2004 BRC >maxdumps 2# max (concurrent) to be run on any > individual "client" > >disklist > ># Notes server backup >wcnotes / comp-root >wcnotes /maildb comp-user >wcnotes /maildb2 comp-user >wcnotes /export/home comp-user Unless you have an exclude list file in comp-root that specifies ./maildb, ./maildb2 and ./home (on separete lines) you are doing the whole of the last 3 filesystems twice each, once for / and once per subdir listing. The last entry will also make you require a seperate disklist entry for /home that doesn't specify the exclude file. Thats of course unless the last 3 are in fact different disks entirely, in which case you should append a 1, a 2, a 3, or a 4 in order to define to amanda that they are separate physical disks and can therefore be done concurrently. One should not attempt to backup 2 different partitions on the same disk concurrently as that will thrash the seeks, slowing things down a bit, or potentially overheating the seek drivers and damaging the drive, but that would be a very extreme result and something I've not seen in at least 5 years. I have the situation in my /usr dir that there are a couple of the subdirs that are more than a tapefull, so my /usr is broken down into a /usr/subdir per disklist entry. The is no entry for / in my disklist. There are also good reasons to use a non-compressing dumptype for some dirs as they will grow rather than compress if they contain mostly executable binaries. Likewise for dirs that contain already compressed archives & rpms. Its a waste of gzips time to try and compress them further. A good argument for a bit of reason in the directory layouts :) You can see which ones you are wasting compression efforts (and cpu horsepower) on by looking at the reported compression achieved, in the email from amanda, and switching those entrys that only get 5 or 10% to a non-compressing dumptype, there by saveing a lot of useless wheel-spinning by gzip. >that is it, just the one client. Suppose I can set maxdumps to 4, > anyway no sense in having inparallel != maxdumps with only a single > client. > >How sensitive is amanda.conf (disklist or others) to white space ? >I've notices that its often It doesn't seem to be at all sensitive to whitespace here. I use tabs liberally for formatting in mine, but an equal amount of spaces is also just fine. >keyword value # comment > >Just to be paraniod I changed the space to a tab. > >Am I missing some other parameter that controls parallelism ? The use of spindle numbers in the dle perhaps. Here are a few entrys from mine to illustrate: --- coyote /varcomp-root-tar 1 local coyote /usr/binroot-tar1 local gene/boot root-tar2 le0 gene/home comp-root-tar 2 le0 --- where the final local or le0 tells anamda that the disk is local or out on the network. Also, the /etc/hosts files on both machine contain the alias<->FQDN of the machines, hence the shortand here is usable. >I was thinking of running amstatus from cron very 15 minutes >to watch it but that still isn't much of a diagnostic, more to >confirm lack of parallelism. > > thanks, > > 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 -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: Editing disklist
Hi, [EMAIL PROTECTED], on Donnerstag, 22. Jänner 2004 at 18:34 you wrote to amanda-users: papc> How does one 'add an excludelist to the dle' ? (also, what is dle?) DLE = Disk List Entry Read the example disklist-file in your amanda-tarball for details on excluding. example/disklist example/amanda.conf docs/EXCLUDE papc> I currently have my dumptype definitions which 'exclude-list' option. papc> Do I add these "smalldirs" to this existing list, or is there a way to papc> specify on a per-disk basis? You can specify exclusions in the DLE so it is kind of per-disk. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: Editing disklist
> On Tue, 23 Sep 2003, "Stefan" == Stefan G. Weichinger wrote: Stefan> I want to change some DLEs from Stefan> /mydisk/bigdir Stefan> to Stefan> /mydisk/bigdir/smalldir1 Stefan> /mydisk/bigdir/smalldir2 Stefan> /mydisk/bigdir/smalldir3 > On Tue, 23 Sep 2003, "CScheeder" == C.Scheeder wrote: CScheeder> i would do the following: add an excludelist to the dle CScheeder> "/mydisk/bigdir" excluding "/mydsik/bigdir/smalldir[1-n]" CScheeder> and leave it in the disklist. How does one 'add an excludelist to the dle' ? (also, what is dle?) I currently have my dumptype definitions which 'exclude-list' option. Do I add these "smalldirs" to this existing list, or is there a way to specify on a per-disk basis? Thanks, -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
amflush stuck
Hi Guys, I am trying to use amflush to get some stuff from the holding disk onto tape. Anytime I do that, I get the following (running: amflush -f DailySet1) Are you sure you want to do this [yN]? y amflush: datestamp 20040122 driver: pid 30616 executable driver version 2.4.3 taper: pid 30617 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400db000 taper: buffer[01] at 0x400e3000 taper: buffer[02] at 0x400eb000 taper: buffer[03] at 0x400f3000 taper: buffer[04] at 0x400fb000 taper: buffer[05] at 0x40103000 taper: buffer[06] at 0x4010b000 taper: buffer[07] at 0x40113000 taper: buffer[08] at 0x4011b000 taper: buffer[09] at 0x40123000 taper: buffer[10] at 0x4012b000 taper: buffer[11] at 0x40133000 taper: buffer[12] at 0x4013b000 taper: buffer[13] at 0x40143000 taper: buffer[14] at 0x4014b000 taper: buffer[15] at 0x40153000 taper: buffer[16] at 0x4015b000 taper: buffer[17] at 0x40163000 taper: buffer[18] at 0x4016b000 taper: buffer[19] at 0x40173000 taper: buffer structures at 0x4017b000 for 240 bytes driver: send-cmd time 0.020 to taper: START-TAPER 20040122 driver: adding holding disk 0 dir /data/amanda size 3145728 reserving 3145728 out of 3145728 for degraded-mode dumps taper: read label `DMP05' date `20031227' taper: wrote label `DMP05' date `20040122' here it hangs and hangs and hangs. Nothing is writen to the /tmp/amanda log directory. Any ideas? Axel Axel Haenssen Department of Ecology and Evolutionary Biology Princeton University Princeton, NJ 08544 phone: (609)258-6999 http://www.eeb.princeton.edu/~axel
Re: amrecover with file: driver
Hi, Marc, on Donnerstag, 22. Jänner 2004 at 16:59 you wrote to amanda-users: ML> I'm using the chg-disk changer. Does amrecover use the changer script? Good question. There is the parameter amrecover_changer which explicitly sets the changer used. Maybe you try to set this in your conf. ML> And would it be possible to modify the script to choose the correct ML> slot? As soon as I know it I will tell you ;) Practically YES, it is possible. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: multiple disklists
Hi, Dege, Robert C.,
on Donnerstag, 22. Jänner 2004 at 17:06 you wrote to amanda-users:
DRC> Is there a way to have multiple disklists per config? I plan is to
DRC> alternate the amdump cycles with the different disklists. I'm running into
DRC> a tape space issue, and am trying to split my disklist into 2 disklists; one
DRC> with lower priority backups & one with higher priority backups. The one
DRC> with the lower priority would run like twice a week, while the higher
DRC> priority disklist would run 5 times a week.
Seems to be the strange-questions-day ;) ...
Why not use two dumptypes?
For example:
> define dumptype important {
> dumpcycle 2
> priority high
> }
> define dumptype unimportant {
> dumpcycle 5
> priority low
> }
You get less lev0 for the "unimportant" stuff so you save space for
the important ones.
Let AMANDA schedule!
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
multiple disklists
Is there a way to have multiple disklists per config? I plan is to alternate the amdump cycles with the different disklists. I'm running into a tape space issue, and am trying to split my disklist into 2 disklists; one with lower priority backups & one with higher priority backups. The one with the lower priority would run like twice a week, while the higher priority disklist would run 5 times a week. -Rob
Re: suggestions for a backup scheme?
Jon LaBadie wrote: With such a structured, non-amanda-like requirement, what benefits do you feel you would experience from using amanda? It will not be doing the scheduling, you will. It will not specify the tapes to be used, you will. It will track the backups (what is on what tape from what date), but you would know that already. What are you looking for amanda to do for you that you could not do with cron entries and shell scripts? I chose amanda, because I needed to do backups in a heterogenous *nix machine network. The other requirements are not of my own design. I would have been happy with whatever scheme Amanda would have suggested. The people I'm working for use Backup Exec, and a specific rigid schedule for their Windows machines. I'm not going to argue with them (it's not worth it, I'll rather quit). (Sorry for venting my frustration; I seem to have needed that).
Re: amrecover with file: driver
Stefan, The "settape" command in amrecover is what I was looking for (thanks Toomas!). I'm using the chg-disk changer. Does amrecover use the changer script? And would it be possible to modify the script to choose the correct slot? Marc. On Thu, 2004-01-22 at 03:19, Stefan G. Weichinger wrote: > Hi, Marc, > > on Mittwoch, 21. JÃnner 2004 at 19:41 you wrote to amanda-users: > > ML> Hello, > > ML> I'm using amanda 2.4.4p2 on Redhat 8, with the "file" output driver > ML> (i.e. writing to disk instead of tapes). The config is working great, > ML> but using amrecover is a little clunky since the current "tape" slot > ML> (directory) is usually set to the next available tape, and not the slot > ML> required for the recovery. > > Do you use chg-disk or chg-multi as changer?
Re: suggestions for a backup scheme?
In cron, dependent on day of week/month amadmin force the level you want ? If you config the dumptype as "always-1" or "never-full", I don't recall cause I've never seen it used, can you override with a force command ? > Stefan G. Weichinger wrote: > > > Please don't do that. > > In case I wasn't quite clear: This is not what I want to do. > This is what I *have* to do. > > Again: I have to deal with people who want me to do insane > things. On a daily basis. > > > At least don't try to do that with AMANDA. > > The question is: can I force amanda to do it? > > > AMANDA is NOT DESIGNED to do what you describe above. > > > > AMANDA is designed to schedule your backups in a way to successfully > > meet your goals. > > > > You don't say: Do a full backup of DLE host/disk on Monday. > > You say: I want at least one full backup of DLE host/disk in X days. > > You must be lucky. You're living in a rational universe. > > > You could FORCE AMANDA into doing it the old way but it is like > > tightening screws with a hammer. Not a good solution. > > It doesn't matter. My days with the company are counted, largely because > I'm getting tired of incompetent people telling me how to do my job. > > > -- > > > > This is a topic that appears very often on the list. > > You can browse the archives to find all the discussions ... > > > > It's definitely a FAQ. > > > > Also maybe consult: http://amanda.sourceforge.net/fom-serve/cache/28.html >
Re: concurrancy
Hi, Brian,
on Donnerstag, 22. Jänner 2004 at 16:44 you wrote to amanda-users:
BC> er, global-dumptype ?
BC> I extracted a few, I can send the complete list but I'm not
BC> seeing a default prototype.
Have you ever looked at a current amanda.conf (2.4.4p2-tarball for
example) ?
BC> From amanda.conf
BC> diskdir "/amanda/work" # where the holding disk is
BC> disksize 7 MB # we have a 36g disk for amanda -ck
BC> # 01-15-04 added 72 gb disk -ck
What are these parameters? I don't know them ...
A working holdingdisk section would be:
> holdingdisk hd1 {
> comment "main holding disk"
> directory "/home/amanda/work"
> use 70Gb
> chunksize 1Gb
> }
To use a [global]-section you have to create one:
> define dumptype global {
> index yes
> holdingdisk yes
> maxdumps 4 # < added the maxdumps to global !
> program "GNUTAR"
> }
Where did you add the maxdumps?
Then you can refer to the global-dumptype in your other dumptypes:
BC> define dumptype comp-user {
BC> global
BC> comment "Non-root partitions on reasonably fast machines"
BC> options compress-fast
BC> priority medium
BC> }
BC> define dumptype comp-root {
BC> global
BC> comment "Root partitions with compression"
BC> options compress-fast
BC> priority low
BC> }
Should work out.
Please read a current amanda.conf and adjust your settings.
It's definitely worth the effort.
Seems you have a pretty old one ...
--
best regards,
Stefan
Stefan G. Weichinger
mailto:[EMAIL PROTECTED]
Re: suggestions for a backup scheme?
Stefan G. Weichinger wrote: Please don't do that. In case I wasn't quite clear: This is not what I want to do. This is what I *have* to do. Again: I have to deal with people who want me to do insane things. On a daily basis. At least don't try to do that with AMANDA. The question is: can I force amanda to do it? AMANDA is NOT DESIGNED to do what you describe above. AMANDA is designed to schedule your backups in a way to successfully meet your goals. You don't say: Do a full backup of DLE host/disk on Monday. You say: I want at least one full backup of DLE host/disk in X days. You must be lucky. You're living in a rational universe. You could FORCE AMANDA into doing it the old way but it is like tightening screws with a hammer. Not a good solution. It doesn't matter. My days with the company are counted, largely because I'm getting tired of incompetent people telling me how to do my job. -- This is a topic that appears very often on the list. You can browse the archives to find all the discussions ... It's definitely a FAQ. Also maybe consult: http://amanda.sourceforge.net/fom-serve/cache/28.html
Re: concurrancy
Stefan,
Will append the dumptypes information at the end of this email
er, global-dumptype ?
I extracted a few, I can send the complete list but I'm not
seeing a default prototype.
> BC> # changed from 8 to 4... can't explain excessive time to backup 4 partitions -ck
> BC> inparallel 4# maximum dumpers that will run in parallel
> BC> # maxdumps, added 21-jan-2004 BRC
> BC> maxdumps 2# max (concurrent) to be run on any individual "client"
>
> Please let us see your dumptypes plus the [global]-dumptype.
[stuff removed]
>From amanda.conf
tapedev "/dev/rmt/0hn" # hmm go up one level of drive and up 2 in description!!
-ck
tapetype SDLT220# what kind of tape it is (see tapetypes below)
labelstr "^NOTES_DLT[0-9][0-9]*$" # label constraint regex: all tapes must
match
diskdir "/amanda/work" # where the holding disk is
disksize 7 MB # we have a 36g disk for amanda -ck
# 01-15-04 added 72 gb disk -ck
# added 26-Nov-2003 BRC
# Numbers from amanda.org faq-o-matic, remember, most of these
# numbers aren't used for anything, only the length is really important.
define tapetype SDLT220 {
comment "Super Differential Digital 220"
length 101444 mbytes
filemark 496 kbytes
speed 2165 kbytes
}
define dumptype comp-user {
comment "Non-root partitions on reasonably fast machines"
options compress-fast
priority medium
}
define dumptype holding-disk {
comment "The master-host holding disk itself"
options no-hold
priority medium
}
define dumptype comp-root {
comment "Root partitions with compression"
options compress-fast
priority low
}
Re: suggestions for a backup scheme?
On Thu, Jan 22, 2004 at 04:19:38PM +0100, Eugen Leitl wrote: > First: thanks for all the people who answered my previous questions. > Very much appreciated. > > I'm stuck (i.e. regardless of whether this makes sense, or no, sounds > familiar?) > with the following set of requirements: > > * 5 machines (it's good: 5 days/week, one overnight run/machine) > * one full backup of all machines/month > * four incremental backups/month, relative to above full dumps > * two months sliding window, after which incremental backup tapes are reused > * storage depth of one year > > So I'm going to use a tape/day, labeled DailyMachineWeekdayNumber, > e.g. u03Monday01,u03Monday02, u03Monday03, u03Monday04. Is it possible to > promote > a full dump, say, Monday for u01, Tuesday for u02, etc., and store diffs > relative > to it? > > How do I do that? With such a structured, non-amanda-like requirement, what benefits do you feel you would experience from using amanda? It will not be doing the scheduling, you will. It will not specify the tapes to be used, you will. It will track the backups (what is on what tape from what date), but you would know that already. What are you looking for amanda to do for you that you could not do with cron entries and shell scripts? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: suggestions for a backup scheme?
Hi, Eugen, on Donnerstag, 22. Jänner 2004 at 16:19 you wrote to amanda-users: EL> I'm stuck (i.e. regardless of whether this makes sense, or no, sounds familiar?) EL> with the following set of requirements: EL> * 5 machines (it's good: 5 days/week, one overnight run/machine) EL> * one full backup of all machines/month EL> * four incremental backups/month, relative to above full dumps EL> * two months sliding window, after which incremental backup tapes are reused EL> * storage depth of one year EL> So I'm going to use a tape/day, labeled DailyMachineWeekdayNumber, EL> e.g. u03Monday01,u03Monday02, u03Monday03, u03Monday04. Is it possible to promote EL> a full dump, say, Monday for u01, Tuesday for u02, etc., and store diffs relative EL> to it? EL> How do I do that? Please don't do that. At least don't try to do that with AMANDA. AMANDA is NOT DESIGNED to do what you describe above. AMANDA is designed to schedule your backups in a way to successfully meet your goals. You don't say: Do a full backup of DLE host/disk on Monday. You say: I want at least one full backup of DLE host/disk in X days. You could FORCE AMANDA into doing it the old way but it is like tightening screws with a hammer. Not a good solution. -- This is a topic that appears very often on the list. You can browse the archives to find all the discussions ... It's definitely a FAQ. Also maybe consult: http://amanda.sourceforge.net/fom-serve/cache/28.html -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: concurrancy
Hi, Brian, on Donnerstag, 22. Jänner 2004 at 16:11 you wrote to amanda-users: BC> Stefan, BC> Gene, BC> Paul, BC> Unfortunately my amanda run didn't run any more quickly. :( BC> # changed from 8 to 4... can't explain excessive time to backup 4 partitions -ck BC> inparallel 4# maximum dumpers that will run in parallel BC> # maxdumps, added 21-jan-2004 BRC BC> maxdumps 2# max (concurrent) to be run on any individual "client" Please let us see your dumptypes plus the [global]-dumptype. BC> How sensitive is amanda.conf (disklist or others) to white space ? BC> I've notices that its often BC> keyword value # comment BC> Just to be paraniod I changed the space to a tab. Should not matter. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: suggestions for a backup scheme?
On Thursday, 22.01.2004 at 16:19 +0100, Eugen Leitl wrote: > So I'm going to use a tape/day, labeled DailyMachineWeekdayNumber, > e.g. u03Monday01,u03Monday02, u03Monday03, u03Monday04. Is it possible > to promote a full dump, say, Monday for u01, Tuesday for u02, etc., > and store diffs relative to it? Without answering your other questions, can I say that using 'day of the week' names for your tapes is probably a bad idea. If you get out of sequence, it'll be confusing. We currently have day-of-the-week tapes, but in setting up a new rotation scheme on a new server shortly, the plan will NOT to do that. Dave. -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
suggestions for a backup scheme?
First: thanks for all the people who answered my previous questions. Very much appreciated. I'm stuck (i.e. regardless of whether this makes sense, or no, sounds familiar?) with the following set of requirements: * 5 machines (it's good: 5 days/week, one overnight run/machine) * one full backup of all machines/month * four incremental backups/month, relative to above full dumps * two months sliding window, after which incremental backup tapes are reused * storage depth of one year So I'm going to use a tape/day, labeled DailyMachineWeekdayNumber, e.g. u03Monday01,u03Monday02, u03Monday03, u03Monday04. Is it possible to promote a full dump, say, Monday for u01, Tuesday for u02, etc., and store diffs relative to it? How do I do that? TIA, Eugen Leitl
Re: concurrancy
Stefan, Gene, Paul, Unfortunately my amanda run didn't run any more quickly. >From amanda.conf - I can send more if you want to see more. org "NOTES_DLT" # your organization name for reports mailto "[EMAIL PROTECTED]"# the mailing list for operators at your site dumpuser "bin" # the user to run dumps under # changed from 8 to 4... can't explain excessive time to backup 4 partitions -ck inparallel 4# maximum dumpers that will run in parallel # maxdumps, added 21-jan-2004 BRC maxdumps 2# max (concurrent) to be run on any individual "client" disklist # Notes server backup wcnotes / comp-root wcnotes /maildb comp-user wcnotes /maildb2 comp-user wcnotes /export/home comp-user that is it, just the one client. Suppose I can set maxdumps to 4, anyway no sense in having inparallel != maxdumps with only a single client. How sensitive is amanda.conf (disklist or others) to white space ? I've notices that its often keyword value # comment Just to be paraniod I changed the space to a tab. Am I missing some other parameter that controls parallelism ? I was thinking of running amstatus from cron very 15 minutes to watch it but that still isn't much of a diagnostic, more to confirm lack of parallelism. thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: Level 1 dumps acting like level 0 dumps
> On Sat, 17 Jan 2004, "Steve" == Steve Manuel wrote: Steve> The man page for amanda can be more explict about what backup Steve> programs can be used and where they record the time-stamp. If Amanda is going to modular such that it can use different backup programs, it's probably a lot easier to say: # record - record the dump timestamp in the time-stamp-database of the # backup program. Check the documentation for the # backup program you are using for more information. rather than try to keep track of all the different versions of backup programs and their corresponding time-stamp db files. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: Level 1 dumps acting like level 0 dumps
In a message dated: Sat, 17 Jan 2004 20:15:19 +0100 "Stefan G. Weichinger" said: >It says: > >> record - record the dump in /etc/dumpdates. Default: [record yes] > >which may lead to assume it doesn´t matter for GNUtar as has happened >for Steve in this case. Not only that, but: Jon> Tar is the odd man out; I doubt it was ever intended to be a Jon> system-wide backup program. It doesn't have the capability to Jon> record its own backup dates file. So amanda fudges a dumpdates Jon> file, by default using /etc/amandates. yet, I can't find a *date* file on any of my clients which is touched by amanda. I'm using gnutar exclusively for backups, and have 2 sets (daily incrementals and weekly archivals) of backups running. No where do I have 'record no' being used. This leads me to believe that there's something monumentally wrong with my config, gnutar doesn't require a date file of any kind, or, amanda keeps track of gnutar backup dates elsewhere. Btw, Debian/stable, amanda-2.4.4p1, tar 1.13.25-2. -- Seeya, Paul GPG Key fingerprint = 1660 FECC 5D21 D286 F853 E808 BB07 9239 53F1 28EE If you're not having fun, you're not doing it right!
Re: amrecover with file: driver
Hi, Marc, on Mittwoch, 21. Jänner 2004 at 19:41 you wrote to amanda-users: ML> Hello, ML> I'm using amanda 2.4.4p2 on Redhat 8, with the "file" output driver ML> (i.e. writing to disk instead of tapes). The config is working great, ML> but using amrecover is a little clunky since the current "tape" slot ML> (directory) is usually set to the next available tape, and not the slot ML> required for the recovery. Do you use chg-disk or chg-multi as changer? -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amrecover with file: driver
Hi! > I'm using amanda 2.4.4p2 on Redhat 8, with the "file" output driver > (i.e. writing to disk instead of tapes). The config is working great, > but using amrecover is a little clunky since the current "tape" slot > (directory) is usually set to the next available tape, and not the slot > required for the recovery. > > I've got around this by using the command: > > amtape slot > > to re-set the "./data" sym-link in the tape directory, but it has to be > done outside of amrecover after the required label is displayed, > Is there a simpler way to change the current tape directory, especially > for non-unix-guru users? I use the 'settape' command in amrecover, e.g. (typing from memory): settape name.of.tape.server:file:/mountpoint/SLOT Seems to work. -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * When you are in it up to your ears, keep your mouth shut.
Re: Restore problem
On Wed, 21 Jan 2004 at 7:57am, Dege, Robert C. wrote > I've appeared to run into a restore problem. I've been backing up several > directories on a nightly basis using amanda for the past several months. > Today, I had to restore a fairly large directory. About 1/3 through the > restore, and error message appeared: > > tar: Skipping to next header > tar: Archive contains obsolescent base-64 headers > > and the restore is no longer continuing. > > An added note, of all the times that I ran amdump, I never had any tar > related errors in the email report. > here are my specs: > > Linux: 2.4.22 > Flavor: Redhat 9.0 > Tar: 1.13.25 > amanda: 2.4.4p1 I've never seen that error, but some googling points to either not giving tar the 'z' flag for a compressed tarball (in which case it probably should have bombed out immediately) or a corrupted tarball. Check for the first case, and then check the 2nd by restoring some other archives from that and other tapes. How did your test restores go when you first got things working? Did you do any this big? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
