From owner-freebsd-isp Fri Sep 18 12:28:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14081 for freebsd-isp-outgoing; Fri, 18 Sep 1998 12:28:38 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from aniwa.sky (pppk-15.igrin.co.nz [202.49.245.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14071 for ; Fri, 18 Sep 1998 12:28:32 -0700 (PDT) (envelope-from andrew@squiz.co.nz) Received: from localhost (andrew@localhost) by aniwa.sky (8.8.7/8.8.7) with SMTP id GAA06320; Sat, 19 Sep 1998 06:57:44 +1200 (NZST) (envelope-from andrew@squiz.co.nz) Date: Sat, 19 Sep 1998 06:57:43 +1200 (NZST) From: Andrew McNaughton X-Sender: andrew@aniwa.sky Reply-To: andrew@squiz.co.nz To: Paul Stewart cc: freebsd-isp@FreeBSD.ORG Subject: Re: Backing Up Entire Server In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 18 Sep 1998, Paul Stewart wrote: > HI there... is there a way to run "tar cvfz backup.tgz *" from the root > directory of a machine but have the backup.tgz file not build on that > server? We really need a good backup solution and this seems to be the > way. But many of the servers don't have the space needed to store a > backup file that size until we ftp it off the server. I've seen > uncompressing done something like this before and can't remember what was > used. ssh remote.host tar -czf - -C / > remote.host.tar.gz Alternatively the same thing can be accomplished with less security using socket (see ports). If you need to connect from the windows machine, it might be easier to implement something this way. On the machine you're backing up type this command from a root shell. socket -p "tar -czf - -C /" -s 12345 To retrieve the backup type socket localhost 12345 > remote.host.tar.gz Or you could write a short perl script using IO::Socket::INET to do the job, which might get around this instance of the awkwardness of using windows. Do look into other approaches. A .tar.gz file might be easier to extract files from using windows if that's important, but otherwise you'd be better to use dump so you get incremental backups. By dump'ing to stdout you can use this exactly like tar in the above examples, meaning that your windows machine doesn't need to know anything about dump. I haven't looked at Amanda (see ports), but for backing up a whole network of servers it's probably worth a look. Andrew McNaughton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message