From owner-freebsd-questions Sat Jan 3 12:41:20 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA02085 for questions-outgoing; Sat, 3 Jan 1998 12:41:20 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from www.dancooks.com (www.dancooks.com [204.180.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA02070 for ; Sat, 3 Jan 1998 12:41:09 -0800 (PST) (envelope-from jasonh@cei.net) Received: from thanatosis (max3-26.cei.net [204.180.118.122]) by www.dancooks.com (8.8.8/8.8.7) with SMTP id OAA03521 for ; Sat, 3 Jan 1998 14:45:51 -0600 (CST) (envelope-from jasonh@cei.net) Message-ID: <005401bd1887$d6308ec0$7a76b4cc@thanatosis> From: "Jason Hudgins" To: Subject: Good backup hardware for FreeBsd? Date: Sat, 3 Jan 1998 14:39:55 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I'm in a similar situation. What happens for you is that the tape has >reached the end (my guess; I get write errors when I reach >end-of-tapes), and is trying to tell you this on the tty; "fopen on >/dev/tty" means that it cannot talk to a console, probably because >you're running it from cron, or detached the dump process from the >tty. I don't think this is the case, because some of the time it actually works, just not often. And it dies at random times, sometimes at say 25% sometimes at 85%, ...etc...etc. >AFAIK, you can't run dump from cron, at least not directly. (I'd like to >hear from you folks! How do you make automated dumps?) Dump needs >user interaction when an error or end-of-tape occurs, or it will get >suspended or fail. Again, I've gotten it to work from cron, though I've never tried to call dump from cron directly. My cronjob calls a perlscript that first rewinds the tape, and then does a dump of /usr to /dev/nrst0. The perl script redirects the output of dump and logs it into a PostgresSQL database, which I then can examine from some web pages.. Its a pretty nice setup, but then again, I only get a successful backup about 15% of the time. When I originally had it setup, for the first two weeks, it was working 100% everyday, but then it started failing, and now it hardly ever works. I use a different tape every day of the week, and they are 4 gig cartridges. My whole /usr filesystem maybe has about 2 gigs of data on it.. >What does your dump command look like? If your tape can swallow no more >than 2GB, you've reached the end-of-tape. Using the B option, yuo can >tell dump about the tape lenght, and get "tape-end" instead of >"write-error". If you expect hardware compression, are you sure it is >switched on? Probably not? something like this, (from memory) dump -0uf /dev/nrst0 /usr I'm not opposed to purchasing new backup hardware if anyone has any solid suggestions. Of course I still haven't completely determined if its a hardware failure, but that my best guess.. Jason