The "Inside Baseball" of E-Discovery
Everyone has baseball on the brain these days. At the new EDD Update blog, Craig Ball is no exception, only his focus is the "inside baseball" of e-discovery. In other words, if you're not an EDD geek, feel free to log off. But, as Ball says, if you can't talk at an insider's level about e-discovery at a blog devoted to e-discovery, then what's the point.
In his post, Acting on a WIM for SIS, Ball makes a pitch for something called WIM, or Windows Imaging Format. But before he explains why, he first explains something called SIS, for Single Instance Storage. "It's a de-duplication mechanism that rather smartly eliminates multiple identical instances of files in favor of pointers to a single instance of the target file," he says. "It's implemented to save backup storage space, and it's a great idea."
Now back to WIM, which Ball describes as a file-based system for creating a ghost image of a hard drive. Because it uses SIS, WIM is highly efficient, Ball says.
One of the uber-cool things about WIM is that, once a machine is imaged in WIM, the WIM image can be mounted as a virtual drive in the Windows environment. Plus, it can be mounted read only. That just seems to create so many possibilities for great desktop tools for e-discovery in small- and mid-volume cases (where vendors and budgets have left everyone to pretty much fend for themselves).
Problem is, Ball is unaware of anyone using WIM for e-discovery. Thus his post, all of which is to set the stage for his question: "Is anyone aware of folks using WIM in an e-discovery setting? Anyone see any problems with it?" If you have answers, head over here and share them with Ball.
Posted by Robert J. Ambrogi on October 30, 2007 at 02:42 PM | Permalink
| Comments (1)