Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!sdrc!crgabb From: crgabb@sdrc.UUCP (Rob Gabbard) Newsgroups: comp.sys.apollo Subject: Re: more SR10 questions Summary: rbak/wbak writing to a file at SR10 Message-ID: <463@sdrc.UUCP> Date: 6 Dec 88 14:47:46 GMT References: <8812051455.AA06261@richter.mit.edu> <5627@sdcsvax.UCSD.EDU> Organization: Structural Dynamics Research Corp., Cincinnati Lines: 25 In article <5627@sdcsvax.UCSD.EDU>, markley@celece.ucsd.edu (Mike Markley) writes: > In article <8812051455.AA06261@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes: > I have read in the SR10 documentation that rbak/wbak will > write to a file so it would be possible to create a backup > directory on every node and then run wbak as a server that > writes to the backup directory. You could set it up so This would be a nice solution except for the fact that you would have to have as much free space on each disk as you have used space (for a complete) or be sure that you have as much free space as what has been changed since the last backup (for an incremental). At the ADUS conference I sat through a VERY interesting talk on NBS, the Apollo Network Backup System. With NBS Apollo seems to be addressing all of these backup complaints and much more. It has its own scheduling language and is designed to live in a heterogeneous world. I'm not sure about release info. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rob Gabbard (uunet!sdrc!crgabb) _ /| Workstation Systems Programmer \'o.O' Structural Dynamics Research Corporation =(___)= U =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=