Date: Mon, 13 May 2002 14:09:20 -0400 From: "Gray, David" <David_W_Gray@tvratings.com> To: "'Mike Meyer'" <mwm@mired.org> Cc: "'FreeBSD Chat List'" <freebsd-chat@freebsd.org> Subject: RE: Backups and such Message-ID: <0BC5187E59E2D411A81000508BB0956901E33CC1@nmrusdunsx6.nielsenmedia.com>
next in thread | raw e-mail | index | archive | help
Yeah, thats pretty much the way I do that. Its a bear though, when the machine in question needs a complete restore from tape... Between tcp wrappers, rsh being turned off (by default) *and* living in /usr, etc, etc, it was an all day (ok, night) affair the last time I lost a drive (5 1/4", 9G Seagate, did NOT like the amt. of ventilation in that cabinet.) -----Original Message----- From: Mike Meyer [mailto:mwm@mired.org] Sent: Monday, May 13, 2002 1:43 PM To: Gray, David Cc: 'FreeBSD Chat List' Subject: Re: Backups and such In <0BC5187E59E2D411A81000508BB0956901E33CBB@nmrusdunsx6.nielsenmedia.com>, Gray, David <David_W_Gray@tvratings.com> typed: > A multivolume dump to tape works, and is the current > solution - but its slow over the network - the speed > of the tape and the speed of the net don't match well, > causing the tape to go to stop-start mode. Just out of curiosity, have you tried not using the rmt protocol, but using rsh (or ssh) to copy the data over? Some work done at stanford in the early nineties showed that rmt was *very* slow, and simply doing "rsh <hostname> dump | dd <reblock it out to tape>" was faster. I confirmed that result going to a disk buffer. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0BC5187E59E2D411A81000508BB0956901E33CC1>