Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!sgi!jmb@patton.SGI.COM
From: jmb@patton.SGI.COM (Jim Barton)
Newsgroups: comp.sys.sgi
Subject: Re: Experiences with 4D/2xx as timesharing systems?
Message-ID: <30483@sgi.SGI.COM>
Date: 12 Apr 89 00:11:30 GMT
References: <89Apr9.160219edt.38129@neat.ai.toronto.edu> <89Apr11.122420edt.38132@neat.ai.toronto.edu>
Sender: daemon@sgi.SGI.COM
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 17

In article <89Apr11.122420edt.38132@neat.ai.toronto.edu>, lamy@ai.utoronto.ca (Jean-Francois Lamy) writes:
> How does one dump/restore an SGI server with about 4Gigs?
> (we currently have essentially unattended dumps at night over the network,
> using the Berkeley rdump/rrestore combo, to a pair of Exabytes).  Is
> anything remotely similar possible with SGI machines?

You can buy officially supported Exabyte-style drives from SGI, and put your
own 2Gb tapes in them.  The 'bru' command should support dump/restore
to this device, as well as tar and cpio.  One of my personal favorites to
save tape and speed the backup is to compress the data, for example:

	find . -newer lastbackup -print | cpio -oc | compress -v -f |\
		rsh remote "dd bs=16k of=/dev/tape"

Compression is slow, but Exabyte tape drives are slower, so there you are ...

-- jmb