I apologize for being late in responding.  The backup code is much
the same as it was when you wrote David.  It indeed causes the
read-only copy-on-write volumes to be created, and then the read-only
volume is dumped to local disk.

regards,
henry m. pierce


------------------------
Henry M. Pierce
Research Programmer
Department of Computer Science
Carnegie Mellon University
5000 Forbes Avenue
Pittsbugh, PA


hmpierce_at_cs.cmu.edu	hmp_at_infomagic.com

On Tue, 24 Mar 1998, the prophet wrote:

> Date: Tue, 24 Mar 1998 20:05:50 -0500 (EST)
> From: the prophet <elijah.daniel_at_yale.edu>
> Reply-To: linux-coda_at_TELEMANN.CODA.CS.CMU.EDU
> To: linux-coda_at_TELEMANN.CODA.CS.CMU.EDU
> Subject: Re: dumping volumes
> Resent-Date: Tue, 24 Mar 1998 20:08:31 -0500
> Resent-From: linux-coda_at_TELEMANN.CODA.CS.CMU.EDU
> 
> Thanks so much.  I've been beating myself over the head about this one for
> days.
> 
> -Eli Daniel
> 
> On Tue, 24 Mar 1998, David C. Steere wrote:
> 
> > I wrote the backup code eons ago, and this info may be out of date.
> > 
> > As I recall, you could only dump a read-only volume. To create a read-only
> > copy use the volutil clone command. The advantage of this approach is that
> > it's much quicker to create a clone than a dump, and hence the volume is
> > offline for less time (if one were really slick one could log updates to
> > the volume while the clone was being made and not have to take the volume
> > offline at all). Also, you can leave the cloned volume online to handle
> > silly restore requests like "I deleted this file by mistake, can I get
> > yesterday's version?"
> > 
> > One creates clones by "volutil clone <volid>", I think.
> > 
> > Hope this helps!
> > 
> > david.
> > 
> 
>       0
>         0
> \  /\ 0
>  \/ o\ 0 
>  /\  /
> /  \/
>