Re: OnStream DI-30, amrecover not working
On Wed, Jan 23, 2002 at 06:11:11PM -0500, John R Jackson wrote: I found I had to rewind the tape before running amrecover extract Otherwise I get a can't read file header error Is this normal? OnStream drives are evil It's my understanding they cannot do file marks properly, so what you're seeing is not surprising There was some discussion of this recently in this group so you might take a look at the archives Bah I was considering an Onstream drive, but I do like using Amanda, and I want to get something that works well with it The problem is that I'm on a university budget (and not a university tech budget, but a university student newspaper budget :) Other solutions seem to be a lot more expensive than Onstream, so if it really does work OK with Amanda, I'd like to go with it (the SC30e, specifically) On the other hand, if they really are terrible drives, could I get some recommendations? I'd like something about that size (15GB uncompressed), and I could go with either internal IDE or external SCSI (probably better for various reasons) The idea is to get something we can actually buyI'm not worried about winning any speed competitions, I'd just like to have money left over to fix the printer, and have tapes that will last for a while :) -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: [Amanda-users] Re: Linux and dump
On Sun, May 20, 2001 at 04:45:52PM +1000, Jason Thomas wrote: On Fri, May 18, 2001 at 12:18:30AM -0400, Ray Shaw wrote: On Thu, May 17, 2001 at 09:53:59PM -0300, Alexandre Oliva wrote: clip I can also tell from personal experience that I haven't had trouble with GNU tar 1.13.17 on GNU/Linux/x86, but I still haven't been able to do backups reliably with 1.13.19 (it will generally abort part-way through the back-up; I suspect a network problem, but a bug in GNU tar still isn't ruled out) My systems (Debian potato): media:~$ tar --version tar (GNU tar) 1.13.17 media:~$ gcc --version 2.95.2 No problems here, except that the kernel isn't best friends with my ATA tape drive sometimes. The joys of an academic budget! :) when you say no problems have you tested using amverify. No, but I've tried restoring random files from tapes. And I've also had to do some actual restores when another server went down (couldn't simply move the disk over thanks to cursed proprietary CompaQ SCSI disk interface...) I'm running the debian potato, and tar does not seem todo the right thing, the archives are corrupt. I'm about to start testing with a newer version of tar taken from sid most probably. Well, at least now your bzip2 option will be l instead of I :) -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: Linux and dump
On Thu, May 17, 2001 at 09:53:59PM -0300, Alexandre Oliva wrote: clip I can also tell from personal experience that I haven't had trouble with GNU tar 1.13.17 on GNU/Linux/x86, but I still haven't been able to do backups reliably with 1.13.19 (it will generally abort part-way through the back-up; I suspect a network problem, but a bug in GNU tar still isn't ruled out) My systems (Debian potato): media:~$ tar --version tar (GNU tar) 1.13.17 media:~$ gcc --version 2.95.2 No problems here, except that the kernel isn't best friends with my ATA tape drive sometimes. The joys of an academic budget! :) I've never tried amanda on anything but Linux, so I can't speak about that. sunfreeware.com might have a good version of gcc. -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: missing files
On Mon, May 14, 2001 at 08:57:02AM +0200, Bernhard R. Erdmann wrote: dump 0.4b16-1 on a debian potato system. Go get a newer version of Linux dump (0.4b22, http://dump.sourceforge.net/) as many bugfixes have been applied. Probably the best way to do this is to temporarily change the potato to woody in your /etc/apt/sources file, apt-get update, install dump, then change it back. The new version of apt can keep track of things like this without having to shuffle config lines, but you wouldn't have the new version with potato :) Woody has 0.4b21-4 (likely with some of the later fixes backported). -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: tar question
On Fri, May 11, 2001 at 12:51:43AM -0400, Jon LaBadie wrote: On Thu, May 10, 2001 at 08:41:24PM -0400, Ray Shaw wrote: On that note, it is annoying that if I have an exclude file, say /etc/amanda/exclude.home, running amanda with that file produces different results than: tar cvf /dev/null /home -X /etc/amanda/exclude.home I don't think amanda tar's /home, I think it cd's to /home and tar's . (current dir). Thus your exclude file should be relative to ., not /home. Ah, yes, that's correct. Thanks for pointing that out; it was the first step in creating the Tower of Globbing in my last post :) For testing, I now use: cd /home tar cvf /dev/null . -X /root/exclude moo and then look at the contents of moo. -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
Re: tar question
On Thu, May 10, 2001 at 08:36:07PM -0500, John R. Jackson wrote: ... I'd like to back up at least their mail, and probably web directories. ... I've been trying to do this with exclude lists, but I haven't hit the solution yet. ... Wow! I wouldn't have had the guts to try this with exclude lists. They give me (real :-) headaches just trying to do normal things :-). Brave or stupid, I've gotten it working with some help from a LUG member on my sh globbing. If you have a line like so in your disklist: myhost /home myhost-home and the myhost-home dumptype is calling /etc/amanda/exclude.myhost-home, which contains this: ./*/? ./*/?? ./*/??? ./*/?* ./*/[!mM]??? ./*/[Mm][!a]?? ./*/[Mm]a[!i]? ./*/[Mm]ai[!l] Then /home/*/Mail and /home/*/mail will be backed up. This creation of evil could easily be extended to back up /home/*/public_html, too, or whatever else you wanted. Maybe you could do it with inclusion instead of exclusion? Take a look at: ftp://gandalf.cc.purdue.edu/pub/amanda/gtar-wrapper.* During the pre_estimate you could run find to gather a list of what you want to back up, squirrel that away and then pass it to gtar for both the estimate and the real run. Yes, but that's a compile-time option, right? As I'm a university student and will be replaced in a few years, I don't want my successor to be confused when apt-get dist-upgrade breaks the /home backup :) Of course, I hope we have a bigger tape drive by then... -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
tar question
I'm using amanda 2.4.1p1 (the version included in Debian potato). Currently, the /home partition on our main user system is too large to back up fully (we have only a small tape drive). Rather than completely leave users out in the cold, I'd like to back up at least their mail, and probably web directories. So: /home/*/[M,m]ail /home/*/public_html I've been trying to do this with exclude lists, but I haven't hit the solution yet. This: [^*/public_html] at least, does not work. On that note, it is annoying that if I have an exclude file, say /etc/amanda/exclude.home, running amanda with that file produces different results than: tar cvf /dev/null /home -X /etc/amanda/exclude.home Why is this? Thanks for any help, -- --Ray - Sotto la panca la capra crepa sopra la panca la capra campa
