Quicky
If I change tapetypes (ie, from a 30G config to a 20G one), can I expect Catastrophy to occur? -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Running out of tape due to full dumps
Hi all, I've got amanda running successfully here for some time, but periodically I have a problem where the tape runs out of space. This generally happens when 2 of the larger partitions I have have a full dump run on them at the same time. Is there any way to tell Amanda to try not to do a full dump of certain file systems at the same time? Thanks, Brad -- +=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+ |Brad Marshall| Plugged In Software| |Senior Systems Administrator | http://www.pisoftware.com| |mailto:[EMAIL PROTECTED] | GPG Key Id: 47951BD0 / 1024b| +-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=+ Fingerprint: BAE3 4794 E627 2EAF 7EC0 4763 7884 4BE8 4795 1BD0
RE: amrecover: No index records for disk for specified date
Hello,
> -Original Message-
> From: Jon LaBadie [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 27, 2002 8:35 PM
> To: Simas Cepaitis
> Subject: Re: amrecover: No index records for disk for specified date
>
>
>
> Any chance your disklist uses localhost rather than a hostname?
No, I use full hostname. For example,
sunny.5ci.lt /usr {
always-full
exclude list "/usr/local/etc/amanda/test/.exclude"
compress server fast
} -1 local
> If using tar, maybe a bad release of tar. gunzip one of the
> indexs. See if each line begins with a long number. That is
> one sign of a bad tar.
I tried using both gnutar (version 1.13.25) and native FreeBSD tar.
# pwd
/usr/local/etc/amanda/test/index/sunny.5ci.lt/_usr
#zmore 20020527_0.gz
/
/bin/
/bin/cu
/bin/uucp
/bin/uulog
/bin/uuname
/bin/uupick
/bin/uusched
...
...
I don't think that is a tar problem. Somehow I believe that rather
directory with indexes is not found. Is there any option to enable
debug mode or something to see more in logs? Because now
they aren't providing much use (amrecover for example)... :(
Simas Cepaitis
[EMAIL PROTECTED]
Re: Deleting a backup from Amanda's database
On Mon, May 27, 2002 at 11:31:57PM +0200, Bernhard R. Erdmann wrote: > > I just had a problem with a backup shown up by amverify - the second last > > filesystem wasn't dumped correctly and the last one not at all. I'd like to > > make amanda delete the records of those dumps from its database so I won't > > be offered them as choices if ever I need to restore a file from them. Is > > there any way of doing that ? I know I can remove a tape altogether (and > > hence all of its backups) with amrmtape, and amadmin delete wil remove all > > records of a particular disk from the database, but I can't see any way to > > remove the record of one disk's backup on one day. Is it possible ? > > Force a full dump using "amadmin force ". That doesn't do what I want - of course it makes a full backup of the affected filesystems but that's not what I want - I want to remove the record of the failed backup so that if at some future stage I look for a file which was in that backup, I won't be offered that backup as one of the recover possibilities (because it won't work). Regards, Niall O Broin
Re: EZ17 trials and tribul.. [data timeout]
On Mon, 27 May 2002 at 7:41pm, Kenny MacPherson wrote > Can anyone provide some guidance? I am experiencing data timeout errors on > AMANDA from a Linux file server "toronto" when trying to backup big > filesystems. When it's a small fs on "toronto" there is no problem but the > big ones keep running out of tape. Apart from the obvious (too much data and > not enough tape) can any shed some light? > Are your filesystems bigger than an individual tape? If so, you need to split them up via tar. Amanda doesn't yet span filesystems across tapes. Also, if you're signature *must* be that exceedingly long, please put sigdashes in to separate it from the message body. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Linux DUMP
Ya, but didnt someone post that "DUMP" on linux can fail - if the conditions are right? I think is was suggested that SMP systems can demonstrate the failure sooner. I think that Mr. Torvolds ( sorry is i mis-spelled) made that comment or conclusion. Are there some caveats that need to be added here ? /gat "Bernhard R. Erdmann" wrote: > > > Which backup program is best? dump, says some people. Elizabeth D. Zwicky > > torture tested lots of backup programs. The clear choice for preserving > > all your data and all the peculiarities of Unix filesystems is dump, she > > stated. Elizabeth created filesystems containing a large variety of > > unusual conditions (and some not so unusual ones) and tested each program > > by do a backup and restore of that filesystems. The peculiarities > > included: files with holes, files with holes and a block of nulls, files > > with funny characters in their names, unreadable and unwriteable files, > > devices, files that change size during the backup, files that are > > created/deleted during the backup and more. She presented the results at > > LISA V in Oct. 1991. > > This article is archived here: > http://berdmann.dyndns.org/doc/dump/zwicky/testdump.doc.html
Re: GNU tar's --atime-preserve switch
> I am needing to make use of last access time for some of the files on > our system. Currently, Amanda/GNU Tar is modifying it. According to > tar's man page, there is a --atime-preserve switch that will stop tar > from modifying the access time. > > How would I make Amanda pass this switch to GNU Tar and what > consequences, if any, would doing this have on recovery? Using --atime-preserve alters the ctime, which may be not an option for you.
Re: Deleting a backup from Amanda's database
> I just had a problem with a backup shown up by amverify - the second last > filesystem wasn't dumped correctly and the last one not at all. I'd like to > make amanda delete the records of those dumps from its database so I won't > be offered them as choices if ever I need to restore a file from them. Is > there any way of doing that ? I know I can remove a tape altogether (and > hence all of its backups) with amrmtape, and amadmin delete wil remove all > records of a particular disk from the database, but I can't see any way to > remove the record of one disk's backup on one day. Is it possible ? Force a full dump using "amadmin force ".
Re: making 2.4.3p3 on octane running 6.5.12
> To add a datum to the context, I have no trouble building and installing > amanda on IRIX with the MIPSpro toolchain. I have not ever had > occasion to try the gcc route. If you access to MIPSpro compilers you > might try them. IRIX' cc wanted to have a licence password. So I installed gcc.
Re: Linux DUMP
> Which backup program is best? dump, says some people. Elizabeth D. Zwicky > torture tested lots of backup programs. The clear choice for preserving > all your data and all the peculiarities of Unix filesystems is dump, she > stated. Elizabeth created filesystems containing a large variety of > unusual conditions (and some not so unusual ones) and tested each program > by do a backup and restore of that filesystems. The peculiarities > included: files with holes, files with holes and a block of nulls, files > with funny characters in their names, unreadable and unwriteable files, > devices, files that change size during the backup, files that are > created/deleted during the backup and more. She presented the results at > LISA V in Oct. 1991. This article is archived here: http://berdmann.dyndns.org/doc/dump/zwicky/testdump.doc.html
Re: Any automagic exclusion of filesystems?
On Mon, May 27, 2002 at 03:05:12PM +0200, Jens Rohde wrote: > Hi > > I'm changing the dump-method on some of my filesystems from ufsdump to > gtar (so I can restore these filesystems on non-Sun hardware/OS). > > I used to backup via the mount-point, and that worked ok, but will I get > double amount of data now? > > Hmm... how the do I explain this... :) > amanda backups with tar does not branch to other file systems through the mount points. each fs must be backed up individually with tar you can specify multiple starting points within a single file system. this would be done with multiple disklist entries. in this case, duplication of data in the backup is possible as is omission of a complete fs backup. depends on your choice of starting points -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
EZ17 trials and tribul.. [data timeout]
Hi Can anyone provide some guidance? I am experiencing data timeout errors on AMANDA from a Linux file server "toronto" when trying to backup big filesystems. When it's a small fs on "toronto" there is no problem but the big ones keep running out of tape. Apart from the obvious (too much data and not enough tape) can any shed some light? Kenny Wolfson Microelectronics Ltd. http://www.wolfsonmicro.com t: +44 131 272-7000 f: +44 131 272-7001 Registered in Scotland 89839 This message may contain confidential or proprietary information. If you receive this message in error, please immediately delete it, destroy all copies of it and notify the sender. You must not use or disclose any part of this message if you are not the intended recipient. We may monitor all Email communication through our networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise. We take reasonable precautions to ensure our Emails are virus free. However, we cannot accept responsibility for any virus transmitted by us and recommend that you subject any incoming Email to your own virus checking procedures. Wolfson Microelectronics Limited is a company incorporated in Scotland having its Registered Office at 20 Bernard Terrace, Edinburgh EH8 9NX
Re: Any automagic exclusion of filesystems?
Jens Rohde wrote: > > Hi > I suppose that the disk/fs that will/might be restored to, that is to be recognized by SUN, will be done on a machine that can create the (unofficial) sun partition correctly? > I'm changing the dump-method on some of my filesystems from ufsdump to > gtar (so I can restore these filesystems on non-Sun hardware/OS). >
Any automagic exclusion of filesystems?
Hi I'm changing the dump-method on some of my filesystems from ufsdump to gtar (so I can restore these filesystems on non-Sun hardware/OS). I used to backup via the mount-point, and that worked ok, but will I get double amount of data now? Hmm... how the do I explain this... :) I have the following filesystems on the box: / /data /usr /var . . In the disklist i have /, /data, /usr and /var defined as seperat disks, using gtar as dump-method. So the question is, will the backup of / also include /data, /usr and /var, or will amanda exclude these by default? Hope it makes sence :) Kind regards... -- Jens Rohde, System Administrator --- Eastfork Object Space (EOS), Margrethepladsen 3, 8000 Aarhus C, Denmark Tel: +45 8732 8787 / Fax: +45 8732 8788
Re: Clarification of Bugtraq info
On Mon, May 27, 2002 at 12:03:48PM -0400, John Cartwright wrote: > I'm sure I'm not alone in my request for clarification regarding the > recent BugTraq announcements... are we to expect a stable release with > these fixes soon? Or, (having re-read the advisory), what I *should* have said is: Are these issues solved in 2.4.2x releases? Thanks :) - John
Re: Reducing the amount of output from amverify
On Fri, 24 May 2002, Niall O Broin wrote: > On Fri, May 24, 2002 at 03:23:02PM +0200, Ulrik Sandberg wrote: > > > > What happens if you eject and then forget to switch tapes? Like in: > > > > amdump && amverify ; mt -f /dev/rmt/1n offline > > > > I think amverify prompts for a tape and then just sits there. This might > > affect the following amdump in a bad way. Processes already running and > > such. > > Indeed it does. I had a situation (public holiday) where the tape wasn't put > in for the backup. So the dumps happened to the holding disk - no problems > so far. But then amverify was run (from my backup script). It found no tape > and just sat there. The next day I inserted a tape to run amflush. Of course > amverify saw the tape but knew that it wasn't what it wanted so exited with > an error and then the script ejected the tape. Then of course amflush failed > because there was not tape in the drive when it went looking for it :-) You state above that amverify exited with an error. It probably didn't fail because it was the wrong tape. As has been pointed out to me in private mail: amverify will happily verify old tapes as well, of course. All it does is check that the tape and its contents is readable, not that it is "the right tape". > I normally manage the office in question from > 1000 km away - fortunately I > was present when all this rigmarole happened, otherwise it might have been > quite confusing. Next thing was to edit my script to do an 'mt status' and > check the return code and only run amverify if it appears that there is a > tape. Yes. So my point still remains: If you eject the tape and forget to put in an new tape, then amverify will "hang" forever, waiting for a tape. It will most likely affect the following amdump. It could be solved with a wrapper around amverify, as Niall did. Another solution would be to build the check into amverify and enable it with a flag, like --exit-if-no-tape. -- Ulrik Sandberg
Clarification of Bugtraq info
Hi I'm sure I'm not alone in my request for clarification regarding the recent BugTraq announcements... are we to expect a stable release with these fixes soon? Thanks - John
gnutar-lists folder problem
Hello, I have a problem when I back up my NT share files. My server will not make an incremental backup of it. I found that the gnutar-lists folder is empty and I don't understand why. Of my Linux hosts, It works well. At what moment, the amanda program create the files in the gnutar-lists folder ? Thank you for your help Ben ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
amrecover: No index records for disk for specified date
Hello, I know this problem is described in FAQ-O-MATIC section , but it didn't help. I also searched google couple of days, still haven't found an answer. My configuration is called test. In amanda.conf I have these entries: infofile "/usr/local/etc/amanda/test/curinfo"# database DIRECTORY logdir "/usr/local/etc/amanda/test/log" # log directory indexdir "/usr/local/etc/amanda/test/index" # index directory In dumptype there is entry "index yes", and when doing backup I get zipped index file in directory $indexdir/host/_mountpoint/ . For example, 20020527_0.gz Everything seems ok, but when runing amrecover I get 200 Working date set to 2002-05-27. 200 Config set to test. 200 Dump host set to sunny.5ci.lt. Trying disk /usr ... $CWD '/usr/home/simas' is on disk '/usr' mounted at '/usr'. Scanning /usr/amanda... 200 Disk set to /usr. No index records for disk for specified date If date correct, notify system administrator Runing history on amrecover prompt gives empty list for disk... Also I tried compiling amanda without gnutar support, but it didn't help either. Amanda is runing on FreeBSD 4.5-RELEASE-p4, amanda's version - 2.4.3b2. Any ideas? Simas Cepaitis [EMAIL PROTECTED]
dump dir
Hi http://www.easywarez.com/ When there is stuff left in the temporarly dump directory I set up, and the backups went according to plan (according to the report), can I just delete everything thats left over in the dump directory? kind regards Tom Van de Wiele
RE: Reducing the amount of output from amverify
>Date: Fri, 24 May 2002 15:23:02 +0200 > (=?ISO-8859-1?Q?V=E4steuropa=2C_sommartid?=) >From: Ulrik Sandberg <[EMAIL PROTECTED]> > Subject: RE: Reducing the amount of output from amverify > > On Fri, 24 May 2002, C R Ritson wrote: > > > I use (as a cron job) for both the backup and its following amverify > > run:- > > > > /usr/local/amanda/current/sbin/amdump ncl && \ > > /usr/local/amanda/current/sbin/amverify ncl \ > > >/tmp/amanda/amverify.debug 2>&1 > > What happens if you eject and then forget to switch tapes? Like in: > > amdump && amverify ; mt -f /dev/rmt/1n offline > > I think amverify prompts for a tape and then just sits there. > This might > affect the following amdump in a bad way. Processes already > running and > such. > > What happens if you DON'T eject and then forget to switch tapes? > > Will amverify find the wrong label and then exit with a failure? I am using a tape changer, and a very cautious approach in cron (I have split the longer crontab line for readability):- 02 11,16 * * 1-5 /usr/local/amanda/current/sbin/amcheck -ms ncl 50 23 * * 1-5 /usr/local/amanda/current/sbin/amdump ncl && \ /usr/local/amanda/current/sbin/amverify ncl \ >/tmp/amanda/amverify.debug 2>&1 Ulrik is right, there could be a problem here, but even during a holiday, the subsequent amcheck runs will attempt to do the right thing for us. The problem would arise if an amdump run somehow left a tape offline but still in the drive, not back in its slot in the tape changer. For us, I think it would take a hardware fault (not just a tape error) to cause that. In that state, amverify will get into a loop, made worse by the fact that our "mt -f /dev/nst0 status" (used by amverify to see if the tape is ready) returns success (0) when the tape is in the drive housing, but not online. The subsequent rewind attempt gets into an infinite loop returning a tape error. In this state, our first attempt to run amcheck will get us a race condition, with the amverify running to completion eventually, although it may well not examine that tape most recently written. The second amcheck run will then load the correct next tape if it is in the changer. It looks a little as if amverify could do with checking over, but first, I will need to switch from using a non-standard tape changer glue script to chg-zd-mtx, then if I can still cause problems I will try and look into them. Chris Ritson.
