This is just the knd of thing vendor specific commands are designed for. We
can also implement mode sense and log pages to return information about the
snapshot(s)
VSS allows for the concept of multiple snapshots. Do we need this?
Most of the VSS negotiations take place in the operating system. VSS
cordinates with VSS aware applications so thay can flush their buffers and
caches, give a windows for a snapshot and then release that window.
I suspect at minimum we need a snap and unsnap CDB. I also recommend some
sort of log or mode page to return statistics about the snapshot (space
used, etc...)
To be honest, I have not studied the architecture of the target this list is
developing. I will get up to speed this weekend and will be able to
contribute at a higher level next week.
Jamey
----- Original Message -----
From: "Brian Wolfe" <brianw@xxxxxxxxxxxx>
To: "Ming Zhang" <mingz@xxxxxxxxxxx>
Cc: "Pasi Kärkkäinen" <pasik@xxxxxx>; "iet-dev"
<iscsitarget-devel@xxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, July 14, 2005 1:32 PM
Subject: Re: [Iscsitarget-devel] Developing VSS hardware providers
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
|
