This is just about the only reason that you would do this with a host-based 
volume manager.  Making a volume snapshot doesn't allow you to mount it on 
another system, so about the only benefit you get it is available for an 
immediate restore.  It's a pity they're not taking advantage of that.

At 06:14 AM 7/11/2001 -0700, Roger B.A. Klorese wrote:
>On Wed, 11 Jul 2001, W. Curtis Preston wrote:
> > The biggest example of this is that snapshots (copy on
> > write) can't protect you against a large disk failure on the primary, where
> > copies can.
>
>But, in fact, without serious tweaking of their semantics -- playing with
>their state in non-supported ways -- volume snapshots do not, either.
>Their command model is designed to support use for backup, not as a
>recovery platform.

---
W. Curtis Preston
Principal Consultant for Storage Designs,   your storage experts
Voice: 760 710 7017                            Fax: 760 710 7019
Webmaster: http://www.backupcentral.com curtis AT backupcentral DOT com