From owner-freebsd-questions Mon Jan 15 16:26:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 65D9237B6AC for ; Mon, 15 Jan 2001 16:26:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0G0PhR82618; Mon, 15 Jan 2001 18:25:43 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101160025.f0G0PhR82618@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Dave VanAuken" Cc: freebsd-questions@FreeBSD.ORG From: David Kelly Subject: Re: Poor mans backup solution required In-reply-to: Message from "Dave VanAuken" of "Mon, 15 Jan 2001 09:46:38 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jan 2001 18:25:43 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Dave VanAuken" writes: > Have a couple of low end servers... 10GB IDE drives. > > Wish to offer backup as an extra bit of value, but these particular > systems (nor the data for that matter) are really worth installing > tape, upgrading to SCSI, or installing IDE RAID. > > Any recommendations for perhaps tar-ing the directory tree to a second > IDE drive each night, or other solutions involving the cost of adding > another $100 IDE drive. You could NFS mount space off another machine and write the tar file(s) there. Or if you enable the Sun RPC commands (rsh, rlogin, etc.) and make the holes for rlogin w/o password, you can have tar write directly without NFS. "tar -cvzf user@hostname:full-path.tar.gz files... " Notice closely, "make the holes for rlogin w/o password." Make sure you understand the risks. Am not good enough with ssh to know how to completely replace the Sun RPC utilities with ssh. Or how to run tar thru ssh. You would probably want the encrypted authentication exchange but not a fully encrypted link. Something else to consider: don't leave the .tar files laying around where anybody can read them. If you tar the user files as root so that tar can read them, and later a user can read the tar file, then that user can read anything that has been backed up. Such as the master password file. Or other user's private information. So, set your umask to 77 before running the backup. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message