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.

At 04:11 PM 3/24/98 -0500, the prophet wrote:
>I am trying to work on multilevel backup for coda.  I have been trying to
>play with regular full dumps to see how they work so far, but I've been
>having trouble.
>
>I have two volumes, coda.root and u.edaniel, with id's 2a000001 and
>2a000002 respectively.  I can get volutil to do info and lookup on both
>volumes successfully, but when I try to dump:
>
>[root_at_triffid dumps]# volutil dump 2a000002 u.edaniel.dump
>V_BindToServer: binding to host triffid.je.yale.edu
>VolDump failed with Unknown RPC2 return code 200
>
>The same thing happens with my other volume.  For what it's worth, if I
>try to call volutil dump with a non-existant volume ID, it returns with a
>different (but still "Unknown") RPC2 return code.
>
>I am running coda 4.4.0 on a 2.0.30 kernel.  Any suggestions?
>
>The other seemingly important thing that I have not yet figured out is the
>format of the dump file.  Assuming that I can get dump to work, I
>could probably reverse-engineer it, but it would be nicer to have someone
>tell me...
>
>Thanks for your help.
>
>-Eli Daniel
>
>      0
>        0
>\  /\ 0
> \/ o\ 0 
> /\  /
>/  \/
>
>
>