We are looking forward to being able to use the “vos copy” / ”vos shadow” and “vos clone” commands of OpenAFS 1.3.x to perform incremental, disk-based remote backups of our file servers in order to move away from tape-based backup storage.  Since we would use the “vos copy” command on R/W volumes to create pseudo-backup volumes, we would also like to be able to use the “-readonly” parameter to mark the newly copied volumes as RO. 

 

We also would like to use the “vos clone” command to create snapshots of a copied volume before it is over-written by the “vos shadow” command.  Unfortunately, the current code prohibits one from making a clone of a RO volume.  Does anybody know of an underlying structural reason why one cannot clone a RO volume? 

 

Jason A. Dillaman

__________________

ITCS

University of Michigan

 

Reply via email to