Re: amanda tar and star again
> Related to your original post on the subject, it was suggested that > you see if star supported all the arguments and options that amanda > expected to see supported by gnutar and if it was compatible with > the formats and error messages that gnutar generates. Were you > able to do that? If star is not usable, a wrapper is of little value. as described star should be able to do all these things but i will check it again. is there a doc-file where all options of tar which are used are described or listed or do i have to look into the source code? regards claus
Re: amanda tar and star again
On Thu, Jan 27, 2005 at 02:54:34PM +0100, Claus Rosenberger wrote: > hi, > > it would be nice if amanda will be packaged with a compiled in wrapper tar > script instead of running tar from /usr/bin. perhaps it's possible to run > /usr/lib/amanda/tar-wrapper wich is calling /usr/bin/tar again. that > script could be changed then to call /usr/bin/star. > It would be nice if amanda did not use the gzip program but was packaged with a wrapper so I could replace it with zip or bzip2. It would be nice if amanda was packaged with a wrapper that called dump so I could call a different dump. Or maybe I could have it do a snapshot first. Yeah, nice, but those really are local customizations best done locally - IMHO. Related to your original post on the subject, it was suggested that you see if star supported all the arguments and options that amanda expected to see supported by gnutar and if it was compatible with the formats and error messages that gnutar generates. Were you able to do that? If star is not usable, a wrapper is of little value. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: infofile partition out of space, trashed file
Paul Bijnens <[EMAIL PROTECTED]> writes: > Kevin Dalley wrote: > >> Oops. I forgot to mention the version number >> I am using a CVS release of amanda, which is named Amanda-2.4.5b1, > > should be fine, but... > >>>Kevin Dalley wrote: >>> Last night, my amanda run had a problem. The partition on which infofile is stored ran out of space. With infofile set to /var/lib/amanda/normal/curinfo, the file: /var/lib/amanda/normal/curinfo/condor/__redbird_l$ had 0 length, which meant that all history for this partition was lost. I restored the file from backup, and things look better. Is it possible to write the new file in a way that the old file is not deleted until the new file is known to exist? > > The problem here is that, if you would do that, the file does not > contain the current info anymore. > Does it make sense to keep the old file? > On the other hand, does it make sense to have an empty file instead? > > Also the file is written to when the backup is already done. > Whatever you decide, the information is not consistent with the reality > anyway. Any good argument to prefer ancient over empty ? I think that I prefer the old file to an empty file, but I'm not sure that I understand everything this file does. An empty curinfo file gave me bad results when I typed: amadmin normal due It said: new disk condor://redbird/l$ ignored. Though: amadmin normal find condor //redbird/l\\$ works The old curinfo file would at least have showed that there were some backups of this partition, even if it didn't have the latest information. If amanda could pretend that the latest backup hadn't happened, that would be better than having no backups. -- Kevin Dalley [EMAIL PROTECTED]
Re: infofile partition out of space, trashed file
Kevin Dalley wrote: Oops. I forgot to mention the version number I am using a CVS release of amanda, which is named Amanda-2.4.5b1, should be fine, but... Kevin Dalley wrote: Last night, my amanda run had a problem. The partition on which infofile is stored ran out of space. With infofile set to /var/lib/amanda/normal/curinfo, the file: /var/lib/amanda/normal/curinfo/condor/__redbird_l$ had 0 length, which meant that all history for this partition was lost. I restored the file from backup, and things look better. Is it possible to write the new file in a way that the old file is not deleted until the new file is known to exist? The problem here is that, if you would do that, the file does not contain the current info anymore. Does it make sense to keep the old file? On the other hand, does it make sense to have an empty file instead? Also the file is written to when the backup is already done. Whatever you decide, the information is not consistent with the reality anyway. Any good argument to prefer ancient over empty ? -- 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: infofile partition out of space, trashed file
Oops. I forgot to mention the version number I am using a CVS release of amanda, which is named Amanda-2.4.5b1, with CVS date as of about Thu Nov 18 16:50:15 PST 2004 using tag amanda-245-branch, with an additional change which I made regarding the , which is probably unrelated to the problem at hand. Paul Bijnens <[EMAIL PROTECTED]> writes: > Kevin Dalley wrote: >> Last night, my amanda run had a problem. The partition on which >> infofile is stored ran out of space. With infofile set to >> /var/lib/amanda/normal/curinfo, the file: >> /var/lib/amanda/normal/curinfo/condor/__redbird_l$ >> had 0 length, which meant that all history for this partition was >> lost. I restored the file from backup, and things look better. >> Is it possible to write the new file in a way that the old file is >> not >> deleted until the new file is known to exist? >> > > Which amanda version is this? I remember going through all the > source and adding a few error checks for these conditions. > I do not remember anymore which version exactly the patches got > incorporated, but 2.4.4p4 should detect these errors. > > If not, I like to know and go through it all again... > > > -- > 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 * > *** > -- Kevin Dalley [EMAIL PROTECTED]
Re: Problems with amrestore and sparse files
Kevin Dalley wrote: I used amrestore to recover a file and received error message which look like this: Extracting from file /backup/20050125170301/condor._.5 tar: ./var/cache/apt/pkgcache.bin: invalid sparse archive member tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: ./var/cache/apt-proxy/.apt-proxy/backends/debian/packages.db: invalid sparse archive member tar: Skipping to next header I'm using GNU tar 1.14. Yes, gnutar 1.14 has this known bug when encountering a sparse file in the archive during recovery. The archive itself however is fine. You can restore the files using gnutar 1.13.25 or 1.15.1. -- 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: infofile partition out of space, trashed file
Kevin Dalley wrote: Last night, my amanda run had a problem. The partition on which infofile is stored ran out of space. With infofile set to /var/lib/amanda/normal/curinfo, the file: /var/lib/amanda/normal/curinfo/condor/__redbird_l$ had 0 length, which meant that all history for this partition was lost. I restored the file from backup, and things look better. Is it possible to write the new file in a way that the old file is not deleted until the new file is known to exist? Which amanda version is this? I remember going through all the source and adding a few error checks for these conditions. I do not remember anymore which version exactly the patches got incorporated, but 2.4.4p4 should detect these errors. If not, I like to know and go through it all again... -- 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 * ***
Problems with amrestore and sparse files
I used amrestore to recover a file and received error message which look like this: Extracting from file /backup/20050125170301/condor._.5 tar: ./var/cache/apt/pkgcache.bin: invalid sparse archive member tar: Skipping to next header tar: Archive contains obsolescent base-64 headers tar: ./var/cache/apt-proxy/.apt-proxy/backends/debian/packages.db: invalid sparse archive member tar: Skipping to next header I'm using GNU tar 1.14. I am using Amanda-2.4.5b1, with CVS as of about Thu Nov 18 16:50:15 PST 2004, with a small change unrelated to tar. I should be using the same version of tar to create the backup as I did to restore, though I updated (in the Debian sense) many packages recently. Why is the tar file being created taking advantage of sparse files, if it is being extracted without sparse files? -- Kevin Dalley [EMAIL PROTECTED]
infofile partition out of space, trashed file
Last night, my amanda run had a problem. The partition on which infofile is stored ran out of space. With infofile set to /var/lib/amanda/normal/curinfo, the file: /var/lib/amanda/normal/curinfo/condor/__redbird_l$ had 0 length, which meant that all history for this partition was lost. I restored the file from backup, and things look better. Is it possible to write the new file in a way that the old file is not deleted until the new file is known to exist? -- Kevin Dalley [EMAIL PROTECTED]
Re: Re[2]: archiving tapes?!
On Thursday 27 January 2005 14:59, Stefan G. Weichinger wrote: >Hello, Gene, > >just now (on 01/27/2005 at 20:58) you wrote: > >GH> I do hope he was able to find gainfull employment, hopefully not >GH> around computers? > >Errm, AFAIK he is some kind of admin for this, errm, big institution Hoo boy, this might get interesting in the board room if they are keeping track. >... > >It's always fun to see what jobs I could have ... That too my friend. As one who has been to quite a few places in his earlier years, and just happened by pure serendipity to be there when something of note was being done, its always sort of fun to play the 'what if' game in ones own mind. OTOH, if some of these didn't work out, guess who's head would have been on the platter for the failure if I'd actually been in a position of responsibility? Sometimes its nice to be 'just the person taking orders', even if its your ability and not theirs thats on the line because they don't know how to do the job and have delegated it to someone who does. :-) -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re[2]: archiving tapes?!
Hello, Gene, just now (on 01/27/2005 at 20:58) you wrote: GH> I do hope he was able to find gainfull employment, hopefully not GH> around computers? Errm, AFAIK he is some kind of admin for this, errm, big institution ... It's always fun to see what jobs I could have ... -- Bye, Stefan
Re: archiving tapes?!
On Thursday 27 January 2005 13:20, Stefan G. Weichinger wrote: >Hi, Eric, > >on Donnerstag, 27. Jänner 2005 at 18:23 you wrote to amanda-users: > >ES> DON'T DON'T DON'T give all your tapes the same label! > >In once had a customer who ran amlabel as part of his daily >backup-procedure. > >Change tape, run "amlabel -f ...", wait for cronjob ... everyday. > >And he wondered why there were no working indexes. I do hope he was able to find gainfull employment, hopefully not around computers? -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: amanda change ctime
Thanks folks. Now I need to learn how to configure run amanda client. Thanks again. Mike Delaney wrote: On Thu, Jan 27, 2005 at 07:01:31AM -0500, Joshua Baker-LePain wrote: On Wed, 26 Jan 2005 at 4:27pm, Nina Pham wrote The files we are backing up are resigned on more than 1 servers, and we want to store that archive on the same place. Therefore we need to mount. As other folks have mentioned, no, you don't. However, what I haven't seen clarified yet is what OS the various servers are running. If some *nix, then install the amanda client there. If 'doze, then amanda can do the backups for you using smbclient (no need for you to mount). In the origional post, she said she was using "FC2 systems", which I took to mean Fedora Core 2, i.e. Linux.
Re: Amanda and Qualstar lib with AIT-3
--On Thursday, January 27, 2005 19:32:42 +0100 Franz-Heinrich Massmann <[EMAIL PROTECTED]> wrote: > Dear Ladies and Gentlemen, > > In July 1999 we bought a Qualstar lib TLS-4220 with one AIT-2 Tape > Drive LVD. Until mid of last year we have operated this lib successfully > on a Solaris 7 platform with the Legato Networker 5.5 software. > > Last year we have updated the system from AIT-2 to AIT-3 by exchanging > the tape drive, the Executive PCBA and the Drive Bay PCB. Unfortunately > our networker version cannot handle AIT-3 tape drives. As the costs to > upgrade the Networker software are quite high, we tried to run the AMANDA > software. But we still have problems in making the system working again. What problems are you having? > > Therefore my questions: > - Does somebody have experience with the lib running with Amanda? Well, we have a TLS-4440 that was upgraded to a TLS-4480 that was then converted from AIT2 to AIT-3, and an RLS-4445 that also works exactly the same with Amanda, and I think all the Qualstar libraries use the same control interface. > - Is it correct that we should see two SCSI devices when commanding >scsi-prob-all from the server which is connected to the lib? Yes, at least 2. You should see the changer device plus one device for each tape drive. >We only see one device. Which one? One one of my changers I see: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: QUALSTAR Model: TLS-4480 Rev: 221i Type: Medium Changer ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: SONY Model: SDX-700C Rev: 0202 Type: Sequential-AccessANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 02 Lun: 00 Vendor: SONY Model: SDX-700C Rev: 0202 Type: Sequential-AccessANSI SCSI revision: 02 This is attached to a Linux box. The results are from 'cat /proc/scsi/scsi', but your scsi probe should show similar info. > - Is there anything special, we have to take care off additionally? If this was just added to the Solaris machine, you may need to 'boot -r' for it to create the devices. You mat also need to modify your st.conf and/or sgen.conf for the drivers to recognize the devices (and you will need a reconfiguration boot after making any changes). I don't work as much with Solaris anymore so someone else on the list might have a more specific answer. Frank > > Thanks in advance. > Sincerely yours > Franz-Heinrich Massmann > -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda change ctime
On Thu, Jan 27, 2005 at 07:01:31AM -0500, Joshua Baker-LePain wrote: > On Wed, 26 Jan 2005 at 4:27pm, Nina Pham wrote > > > The files we are backing up are resigned on more than 1 servers, and we > > want to store that archive on the same place. Therefore we need to mount. > > As other folks have mentioned, no, you don't. However, what I haven't > seen clarified yet is what OS the various servers are running. If some > *nix, then install the amanda client there. If 'doze, then amanda can do > the backups for you using smbclient (no need for you to mount). In the origional post, she said she was using "FC2 systems", which I took to mean Fedora Core 2, i.e. Linux.
Amanda and Qualstar lib with AIT-3
Dear Ladies and Gentlemen, In July 1999 we bought a Qualstar lib TLS-4220 with one AIT-2 Tape Drive LVD. Until mid of last year we have operated this lib successfully on a Solaris 7 platform with the Legato Networker 5.5 software. Last year we have updated the system from AIT-2 to AIT-3 by exchanging the tape drive, the Executive PCBA and the Drive Bay PCB. Unfortunately our networker version cannot handle AIT-3 tape drives. As the costs to upgrade the Networker software are quite high, we tried to run the AMANDA software. But we still have problems in making the system working again. Therefore my questions: - Does somebody have experience with the lib running with Amanda? - Is it correct that we should see two SCSI devices when commanding scsi-prob-all from the server which is connected to the lib? We only see one device. - Is there anything special, we have to take care off additionally? Thanks in advance. Sincerely yours Franz-Heinrich Massmann
Re: archiving tapes?!
Hi, Eric, on Donnerstag, 27. Jänner 2005 at 18:23 you wrote to amanda-users: ES> DON'T DON'T DON'T give all your tapes the same label! In once had a customer who ran amlabel as part of his daily backup-procedure. Change tape, run "amlabel -f ...", wait for cronjob ... everyday. And he wondered why there were no working indexes. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: archiving tapes?!
On Thu, Jan 27, 2005 at 06:08:01PM +0100, Sebastian Kösters wrote: > if I want to restore a > tape/backup older than the last one this fails. Iam only able to restore > the last Backup from tape. I wanted to use the same amlabel for every Sunday > because I dont want the tapelist file become that long. DON'T DON'T DON'T give all your tapes the same label! This will confuse Amanda, and probably you too. Your problem with restoring from old backups is merely one symptom of Amanda's confusion. A symptom of your confusion would be mounting the wrong tape (or forgetting to change tapes), and thus overwriting a backup that you wanted to keep. There are some of Amanda's features that it can sometimes make sense to work around (e.g. what I assume you're doing to force full backups on Sundays). The tape-labelling/tapelist mechanism is NOT one of them; trying to subvert that is a REALLY bad idea. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / The animal that coils in a circle is the serpent; that's why so many cults and myths of the serpent exist, because it's hard to represent the return of the sun by the coiling of a hippopotamus. - Umberto Eco, "Foucault's Pendulum"
Re: archiving tapes?!
On Thu, 27 Jan 2005 at 6:08pm, Sebastian Kösters wrote > At Sunday we want Amanda to backup on real tapes. These tapes should not be > overwritten every Sunday. We want to archive the tapes. > > Now the problem. The Backup on tape works fine. But if I want to restore a > tape/backup older than the last one this fails. Iam only able to restore > the last Backup from tape. I wanted to use the same amlabel for every Sunday > because I dont want the tapelist file become that long. > > In which way I must configure Amanda to backup on tape so I can archive the > tapes AND can restore every tape? You can always restore from any amanda tape using amrestore or plain old mt and dd. However, if you want amanda to keep track of your multiple archival tapes (thus giving you the ability to use amrecover, just how do you expect it to do so *if they all have the same label?* In short, it can't, and so you can't. > tapecycle 1 tapes # AMANDA_WEBMIN The standard archival setup is to use a dumpcycle of 0 and an arbitrarily large tapecycle. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
archiving tapes?!
Hi, i have a problem. For weekly backups we use Amanda with v-tapes. These tapes get overwritten every week. No problems. Works fine. At Sunday we want Amanda to backup on real tapes. These tapes should not be overwritten every Sunday. We want to archive the tapes. Now the problem. The Backup on tape works fine. But if I want to restore a tape/backup older than the last one this fails. Iam only able to restore the last Backup from tape. I wanted to use the same amlabel for every Sunday because I dont want the tapelist file become that long. In which way I must configure Amanda to backup on tape so I can archive the tapes AND can restore every tape? I hope someone understands my problem. Best regards, Sebastian Here is my config: # # 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 "sino" # AMANDA_WEBMIN mailto "[EMAIL PROTECTED]" # AMANDA_WEBMIN dumpuser "amanda" # AMANDA_WEBMIN inparallel 2# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h netusage 800 Kbps # maximum net bandwidth for Amanda, in KB per sec # Set to default by AMANDA_WEBMIN - runspercycle 20 # AMANDA_WEBMIN # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 1 tapes # AMANDA_WEBMIN # 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 # AMANDA_WEBMIN bumpdays 1 # AMANDA_WEBMIN bumpmult 4 # AMANDA_WEBMIN 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. dtimeout 1800 # number of idle seconds before a dump is aborted. ctimeout 30 # maximum number of seconds that amcheck waits # for each client host tapebufs 20 # AMANDA_WEBMIN # A positive integer telling taper how many 32k buffers to allocate. # WARNING! If this is set too high, taper will not be able to allocate # the memory and will die. The default is 20 (640k). # 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 1 # AMANDA_WEBMIN #tpchanger "chg-manual" # the tape-changer glue script tapedev "/dev/nst0" # AMANDA_WEBMIN # Set to default by AMANDA_WEBMIN - rawtapedev "/dev/nst0" # 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/null" tapetype DAT #tapetype HARD-DISK # AMANDA_WEBMIN labelstr "^DailySet1[0-9][0-9]*$" # AMANDA_WEBMIN # 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 m
Re: amanda tar and star again
On Thursday 27 January 2005 11:42, Claus Rosenberger wrote: >>>it would be nice if amanda will be packaged with a compiled in >>> wrapper tar script instead of running tar from /usr/bin. perhaps >>> it's possible to run /usr/lib/amanda/tar-wrapper wich is calling >>> /usr/bin/tar again. that script could be changed then to call >>> /usr/bin/star. >> >> If building it from scratch, this is no problem Claus. You just >> use a line in your config script that says >> --with-gnutar=your-wrapper-script, just like in this script I use: > >i could build from scratch but then i have a lot of work to upgrade > amanda to newer versions. i think i have to ask the debian > maintainer if that makes sense in the official debian package. but > it would be easier if amanda offer the concept. the maintainer > would include it i think. > >but if there is no other way i have to build it from scratch every > time a new version comes out > >claus I've been doing that for years with what is now the 2.4.5b1 profile. Takes about 5-6 minutes with that script, become root and install, then a run of ldconfig to freshen the ls.so.cache. Moderately speedy machine though, XP2800 Athlon. -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: amanda tar and star again
> I don't know about .debs, but with .rpms I can rebuild the source RPM > after > modifying the spec file so I get the best of both worlds...customized > build > and package management. it's the same with debs. only use apt-get source amanda and the dpkg-buildpackage with changed configure settings but if a new version comes out the step must be run again and if you change a lot of packages then an update will be a pain. claus
Re: amanda tar and star again
On Thu, Jan 27, 2005 at 05:42:27PM +0100, Claus Rosenberger enlightened us: > >>it would be nice if amanda will be packaged with a compiled in > >> wrapper tar script instead of running tar from /usr/bin. perhaps > >> it's possible to run /usr/lib/amanda/tar-wrapper wich is calling > >> /usr/bin/tar again. that script could be changed then to call > >> /usr/bin/star. > >> > > If building it from scratch, this is no problem Claus. You just use a > > line in your config script that says > > --with-gnutar=your-wrapper-script, just like in this script I use: > > i could build from scratch but then i have a lot of work to upgrade amanda > to newer versions. i think i have to ask the debian maintainer if that > makes sense in the official debian package. but it would be easier if > amanda offer the concept. the maintainer would include it i think. > > but if there is no other way i have to build it from scratch every time a > new version comes out > > claus > > I don't know about .debs, but with .rpms I can rebuild the source RPM after modifying the spec file so I get the best of both worlds...customized build and package management. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: pre- and post-script
> > I've found its best to do the pre and post stuff seperate from amanda, > as when amanda is running, it has a few file locks and those files > cannot be backed up by amanda so you lose the most vital info of the > backup, what is it and where is it. My method works without this > limitation. In my case the only 'pre' is a run of amcheck just so > the rest of my script's are looking at the correct tape as obtained > from the tapelist. My post consists of tarballing up the config and > indice containing dirs, and appending them to the end of the tape > after making sure the tapetype is set small enough to leave room on > the tape for them. In this manner the exact config and a truely > uptodate indice of all the tapes in the tapelist, is right on the end > of the tape. In my case thats about another 375 megs. On disk its a > , on tape you'll need to compensate because they really are > fixed length. To recover, I play those last two files back with dd > into tar, and the rest of it can be fairly automatic from there. > > At least thats the theory, practice occasionally differs as we all > know so well. :-) ok, i have to do some more work, i have to stop a lot of services, then i have to run "getfacl --skip-base -r mypath | gzip > myacls.gz" to backup the acls or i have to use star which backup the acl's. i would use gnutar because it's easier to restore but my getfacl command needs 50 minutes to run, thats to long. the post script only restart the services but to add the database stuff at the end of the tape is a very good idea. please could you send me your pre and post script? then i can see which files you're appending at the end of the tape. claus
Re: amanda tar and star again
>>it would be nice if amanda will be packaged with a compiled in >> wrapper tar script instead of running tar from /usr/bin. perhaps >> it's possible to run /usr/lib/amanda/tar-wrapper wich is calling >> /usr/bin/tar again. that script could be changed then to call >> /usr/bin/star. >> > If building it from scratch, this is no problem Claus. You just use a > line in your config script that says > --with-gnutar=your-wrapper-script, just like in this script I use: i could build from scratch but then i have a lot of work to upgrade amanda to newer versions. i think i have to ask the debian maintainer if that makes sense in the official debian package. but it would be easier if amanda offer the concept. the maintainer would include it i think. but if there is no other way i have to build it from scratch every time a new version comes out claus
Re: pre- and post-script
On Thursday 27 January 2005 08:59, Claus Rosenberger wrote: >hi, > >as the response at this mailinglist i set up a script now which do > some pre stuff then start the backup and do some post stuff after > the backup. but the besser way would be an integration of these > scripts into the backup process because the logfiles will be at one > single place. > >the solution could be two parameters in amanda.conf, i.e. >prescript=/path/to/script and postscript=/path/to/script > >if the script returns 0 the process will be continued, all stdout > will be logged into the central logfile of the backup job. > >regards > >claus I've found its best to do the pre and post stuff seperate from amanda, as when amanda is running, it has a few file locks and those files cannot be backed up by amanda so you lose the most vital info of the backup, what is it and where is it. My method works without this limitation. In my case the only 'pre' is a run of amcheck just so the rest of my script's are looking at the correct tape as obtained from the tapelist. My post consists of tarballing up the config and indice containing dirs, and appending them to the end of the tape after making sure the tapetype is set small enough to leave room on the tape for them. In this manner the exact config and a truely uptodate indice of all the tapes in the tapelist, is right on the end of the tape. In my case thats about another 375 megs. On disk its a , on tape you'll need to compensate because they really are fixed length. To recover, I play those last two files back with dd into tar, and the rest of it can be fairly automatic from there. At least thats the theory, practice occasionally differs as we all know so well. :-) -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: amanda tar and star again
On Thursday 27 January 2005 08:54, Claus Rosenberger wrote: >hi, > >it would be nice if amanda will be packaged with a compiled in > wrapper tar script instead of running tar from /usr/bin. perhaps > it's possible to run /usr/lib/amanda/tar-wrapper wich is calling > /usr/bin/tar again. that script could be changed then to call > /usr/bin/star. > If building it from scratch, this is no problem Claus. You just use a line in your config script that says --with-gnutar=your-wrapper-script, just like in this script I use: #!/bin/sh # since I'm always forgetting to su amanda... if [ `whoami` == 'root' ]; then echo echo " Warning " echo "Amanda needs to be configured and built by the user amanda," echo "but must be installed by user root." echo exit 1 fi make clean rm -f config.status config.cache ./configure --with-user=amanda \ --with-group=disk \ --with-owner=amanda \ --with-gnu-ld \ --prefix=/usr/local \ --with-tapedev="FILE:/amandatapes" \ --with-debugging=/tmp/amanda-dbg/ \ --with-tape-server=coyote \ --with-amandahosts \ --with-configdir=/usr/local/etc/amanda \ --with-config=Daily \ --with-gnutar=/usr/local/bin/tar make - One could even point it at star itself unless you need to parse the command line and adjust it for star in your wrapper. That last line is how I converted mine from using /bin/gtar to using a self-compiled version of tar-1.15-1 for testing. It apparently works just fine. >regards > >claus -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
pre- and post-script
hi, as the response at this mailinglist i set up a script now which do some pre stuff then start the backup and do some post stuff after the backup. but the besser way would be an integration of these scripts into the backup process because the logfiles will be at one single place. the solution could be two parameters in amanda.conf, i.e. prescript=/path/to/script and postscript=/path/to/script if the script returns 0 the process will be continued, all stdout will be logged into the central logfile of the backup job. regards claus
amanda tar and star again
hi, it would be nice if amanda will be packaged with a compiled in wrapper tar script instead of running tar from /usr/bin. perhaps it's possible to run /usr/lib/amanda/tar-wrapper wich is calling /usr/bin/tar again. that script could be changed then to call /usr/bin/star. regards claus
RE: Amanda can back up open files?
Actually, if it's on a windows 2003 server it is possible with the standard "Microsoft Windows Backup", as the Windows 2003 version of NTBACKUP will use shadow copies to do the backup. Any other Windows OS (XP, 2000, etc...) it is not standard. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens > Sent: Thursday, January 27, 2005 5:13 AM > To: Leire Cristobo > Cc: amanda-users@amanda.org > Subject: Re: Amanda can back up open files? > > Leire Cristobo wrote: > > Hello, > > I'm new in that list, and I'm looking for a good backup > system for my > > net, with windows clients, I need to back up files although if they > > are open and been used by the user. It's possible with Amanda? > > No. > It not even possible with the standard "Microsoft Windows Backup" > program... > > > -- > 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: amanda change ctime
On Wed, 26 Jan 2005 at 4:27pm, Nina Pham wrote > The files we are backing up are resigned on more than 1 servers, and we > want to store that archive on the same place. Therefore we need to mount. As other folks have mentioned, no, you don't. However, what I haven't seen clarified yet is what OS the various servers are running. If some *nix, then install the amanda client there. If 'doze, then amanda can do the backups for you using smbclient (no need for you to mount). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Amanda can back up open files?
As an aside, it's considered bad from to "respond" to a list email (and then change the subject) when starting a new thread. Your question gets buried in an unrelated thread (for those of us using threaded mail readers) which a) annoys people, and b) makes it less likely to get answered. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Samba and single-file DLE
Dnia 2005-01-27 11:10, Paul Bijnens napisał: Filip Rembiałkowski wrote: This DLE: amandahost //NTSERVER/D$/important.bkf nocomp-user-gnutar expands to whole "D$" volume while estimating and dumping. Surprise for me. Is there any way to create a single-file DLE while using Samba? Not that I know. There is a trick with gnutar and includes, but that does not work for smbclient. I just wanted to know if it's possible. If possible, why don't you put the "important.bkf" file (which seems to be a backup file generated on the PC with windows software) in a separate directory? So I did. Thanks. -- Filip Rembiałkowski
Re: Amanda can back up open files?
Leire Cristobo wrote: Hello, I'm new in that list, and I'm looking for a good backup system for my net, with windows clients, I need to back up files although if they are open and been used by the user. It's possible with Amanda? No. It not even possible with the standard "Microsoft Windows Backup" program... -- 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: Samba and single-file DLE
Filip Rembiałkowski wrote: This DLE: amandahost //NTSERVER/D$/important.bkf nocomp-user-gnutar expands to whole "D$" volume while estimating and dumping. Surprise for me. Is there any way to create a single-file DLE while using Samba? Not that I know. There is a trick with gnutar and includes, but that does not work for smbclient. If possible, why don't you put the "important.bkf" file (which seems to be a backup file generated on the PC with windows software) in a separate directory? -- 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: Reiserfs?
Gene Heskett schrieb: On Thursday 27 January 2005 03:48, Christoph Scheeder wrote: Hi, your exclude-list has wrong syntax. it has to be relative to the root of the filesystem you backup. it should read like this ./media ./tmp ./var/spool/postfix Actually, I don't think the last line is correct either. It should either be a plain ./postfix if thats all you want it to skip, or a ./spool to skip all levels beyond including postfix, or even a ./var to skip all of /var, which probably isn't what you want. This syntax prevents tar from entering the named dir, and *all* dirs beyond it in the tree. I'm not sure of the exact results the above line would give, but I'd suspect it skip all of /var. Nope definitly not. It will only exclude the "/var/spool/postfix" directory from the root-filesystem. Trust me, i have these lines in my exclude-list since many years, and they do what i want Christoph
Re: Reiserfs?
Jon LaBadie wrote:
On Wed, Jan 26, 2005 at 03:51:33PM +0100, Paul Bijnens wrote:
Jon LaBadie wrote:
It has been a couple of years since I looked at tar,
but IIRC two things that give a return code of 2 are
"file changed as we backed it up"
"file disappeared after we made the list of what to backup"
These conditions are common on active file systems.
Both cause the error message
"error exit delayed from previous errors"
which is a return code of 2.
Consulting sources of gnutar 1.13.25:
"file changed..." would set exit(2) but is neutralized
when given the --ignore-failed-read option to tar.
I believe you are correct on a "failed read", i.e. permissions
type changes, but I don't think "file changed ..."is affected
by the --ignore-failed-read option. I think it still prints
the message, and exits 2 with the "error exit delayed" message.
I *did* consult the source :-) :
Here are some checks when dumping a file:
tar-1.13.15/src/misc.c:
# an IO error while reading a file
1378 count = safe_read (f, start->buffer, bufsize);
1379 if (count < 0)
1380 {
1381 (ignore_failed_read_option
1382 ? read_warn_details
1383 : read_error_details)
1384 (p, current_stat.st_size - sizeleft, bufsize);
1385 goto padit;
1386 }
...
# file shrank while reading
1394 if (count != bufsize)
1395 {
1396 char buf[UINTMAX_STRSIZE_BOUND];
1397 memset (start->buffer + count, 0, bufsize - count);
1398 WARN ((0, 0,
1399_("%s: File shrank by %s bytes; padding with
zeros"),
1400quotearg_colon (p),
1401STRINGIFY_BIGINT (sizeleft, buf)));
1402 if (! ignore_failed_read_option)
1403 exit_status = TAREXIT_FAILURE;
1404 goto padit; /* short read */
1405 }
...
# when at end of file, it can be disappeared already
1414 if (fstat (f, &final_stat) != 0)
1415 {
1416 if (ignore_failed_read_option)
1417 stat_warn (p);
1418 else
1419 stat_error (p);
1420 }
# ctime changed: someone wrote to it, or chmod it etc
1421 else if (final_stat.st_ctime != original_ctime)
1422 {
1423 char const *qp = quotearg_colon (p);
1424 WARN ((0, 0, _("%s: file changed as we read it"), qp));
1425 if (! ignore_failed_read_option)
1426 exit_status = TAREXIT_FAILURE;
1427 }
# even an IO error detected while closing
1428 if (close (f) != 0)
1429 {
1430 if (ignore_failed_read_option)
1431 close_warn (p);
1432 else
1433 close_error (p);
1434 }
In 1.15.1 the code is rearranged -- looks clearer -- but still does
the same.
As far as I can see in the sources, the --ignore-failed-read
option really avoids exit with a failure for all errors
involved on the reading side.
Sources of gnutar 1.15.1:
"file changed" is never triggering an exit-code different
from zero (but warning is printed nevertheless).
"file shrank ..." however still needs --ignore-failed-read flag
to be neutralized.
Looks like the RE's ignored need to be revisited.
The "file disappeared..." is diagnosed as
"Warning: Cannot stat: No such file or directory", and that
one neither sets a exitcode different from zero (in 1.13.25
and 1.15.1).
With the --ignored-failed-read I'm sure you are correct.
Yes, indeed.
The "error exit delayed" situation can be set to be considered
"normal" in sendbackup-gnutar.c or it and a few others ignored
by defining "IGNORE_TAR_ERRORS" in amanda.h.
Amanda does pass the --ignore-failed-read option, and thus you
normally should not need to compile with IGNORE_TAR_ERRORS defined.
The last one classifies the printed warnings as "normal" instead
of "strange" and suppresses the STRANGE section in the amanda report.
And maybe it would ignore other more serious errors too?
These are the 3 messages added by the IGNORE_TAR_ERRORS macro.
"File .* shrunk by [0-9][0-9]* bytes, padding with zeros"
"Cannot add file .*: No such file or directory"
"Error exit delayed from previous errors"
Seem to be directly related to the current discussion.
Tar always prints a message for the problems, but --ignore-failed-read
option just inhibits setting the exit failure code 2 for some
of them.
When tar returns with 2, amanda trows away the archive.
Amanda classifies the messages in "NORMAL", "ERROR" and all
the rest as "STRANGE".
The IGNORE_TAR_ERRORS macro just classifies those three as NORMAL
instead of STRANGE.
But the macro also makes amanda change the gnutar exit code 2 into 0.
Because you can have other real errors, defining that macro is not
very wise, I believe. I strongly think about adding the first
two
Re: Reiserfs?
On Thursday 27 January 2005 03:48, Christoph Scheeder wrote: >Hi, >your exclude-list has wrong syntax. >it has to be relative to the root of the filesystem you backup. >it should read like this > >./media >./tmp >./var/spool/postfix Actually, I don't think the last line is correct either. It should either be a plain ./postfix if thats all you want it to skip, or a ./spool to skip all levels beyond including postfix, or even a ./var to skip all of /var, which probably isn't what you want. This syntax prevents tar from entering the named dir, and *all* dirs beyond it in the tree. I'm not sure of the exact results the above line would give, but I'd suspect it skip all of /var. >Christoph > >Nick Danger schrieb: >[snip] > >> Oddly, the sendbackup...exclude tells it to exclude the >> /var/spool/postfix so Im not sure they are even in the error list. >> The man page for tar says it should be '--exclude-from=file', so >> maybe there needs to be an '=' in the argument list above? >> >>[EMAIL PROTECTED]:/tmp/amanda> more >> sendbackup._.20050126203414.exclude /media >>/tmp >>/var/spool/postfix -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: Samba and single-file DLE
On Thursday 27 January 2005 03:30, Filip RembiaÅkowski wrote: >Hello, > >This DLE: > >amandahost //NTSERVER/D$/important.bkf nocomp-user-gnutar > >expands to whole "D$" volume while estimating and dumping. Surprise > for me. > >Is there any way to create a single-file DLE while using Samba? > > >TIA, That doesn't make sense unless you are using dump, which does only whole filesystems. For individual files, you must use tar/gtar/gnutar, of one of 3 versions, 1.13-19, 1.13-25, or 1.15-1. 1.14 appears to be broken, as does 1.13 with no minor revision. -- 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.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Amanda can back up open files?
Hello, I'm new in that list, and I'm looking for a good backup system for my net, with windows clients, I need to back up files although if they are open and been used by the user. It's possible with Amanda? Thanks __ Renovamos el Correo Yahoo!: ¡250 MB GRATIS! Nuevos servicios, más seguridad http://correo.yahoo.es
Re: Reiserfs?
Hi, your exclude-list has wrong syntax. it has to be relative to the root of the filesystem you backup. it should read like this ./media ./tmp ./var/spool/postfix Christoph Nick Danger schrieb: [snip] Oddly, the sendbackup...exclude tells it to exclude the /var/spool/postfix so Im not sure they are even in the error list. The man page for tar says it should be '--exclude-from=file', so maybe there needs to be an '=' in the argument list above? [EMAIL PROTECTED]:/tmp/amanda> more sendbackup._.20050126203414.exclude /media /tmp /var/spool/postfix
Samba and single-file DLE
Hello, This DLE: amandahost //NTSERVER/D$/important.bkf nocomp-user-gnutar expands to whole "D$" volume while estimating and dumping. Surprise for me. Is there any way to create a single-file DLE while using Samba? TIA, -- Filip Rembiałkowski
