Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!RUDY.FAC.CS.CMU.EDU!Rudy.Nedved
From: Rudy.Nedved@RUDY.FAC.CS.CMU.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Summary: Backup via network
Message-ID: <8907300001.AA15626@ucbvax.Berkeley.EDU>
Date: 24 Jul 89 21:36:22 GMT
References: <1989Jul21.014826.19864@comp.vuw.ac.nz>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 35


CMU CS:
-------

I am working on and putting the finishing details on a 4.3BSD Unix oriented
backup system so we can change from manually running backups on 80+ machines
to automatically running backups on 500+ machines.

It takes a modified version of dump/rdump called edump and a modified version
of rshd called oprshd (uses real passwords to break system administrator
bounds) and backs the data up on tape drives.

It is a prototype system and internally very ugly. After I have gained some
experience oriented insight I will rewrite it and clean it up.

Sun file servers:
-----------------

A company called Trimachi I believed based in Stage College, PA has a system
for backing up SunOS file servers.

super saver:
------------

I saw the source code for a system from Berkeley I believe called super
saver. It had limited confiuguration options but looked workable.

Epoch:
------

There is an integrated system from a company I think is called Epoch that
uses WORM disks and other disks and automatically migrates old data to the
WORM disks for permanent archival.

-Rudy