From owner-freebsd-questions Fri Jan 8 08:32:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15751 for freebsd-questions-outgoing; Fri, 8 Jan 1999 08:32:14 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15746 for ; Fri, 8 Jan 1999 08:32:12 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.2/8.9.2) with SMTP id LAA44844 for ; Fri, 8 Jan 1999 11:32:26 -0500 (EST) Message-Id: <4.1.19990108112719.0097e590@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Fri, 08 Jan 1999 11:31:09 -0500 To: freebsd-questions@FreeBSD.ORG From: Forrest Aldrich Subject: Backup solutions Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We've looked into some DLT tape libraries recently.. due to our need to come up with a decent system-wide backup solution. I wondered what other people's experience was in this area. Generally, I've always used good ol' reliable "dump" and "restore" from individual machines. However, as your server farm grows, that approach isn't feasible (unless you love switching little 4mm tapes or can spend $$ for lots of DLT drives). Add to that, multi-platforms such as Solaris, Windoze, ... Some commercial products, like ADSM, run a daemon on a given machine which will dump its disk drive (or what you specify) to a remote disk drive -- then, in turn, the tape system writes that to tape. But for a large enterprise system, you'd need a backend network at least for that. I'd appreciate suggestions in this area. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message