This sounds reasonable to me, but then again nothing else in this unfortunate nightmare seems reasonable so far...
On the bright side of the fence, if you figure out how to recover everything you could sell disaster recovery services for several hundred bucks / GB and make a small fortune saving other folks' bacon. Anyway, it goes without saying that you absolutely need a non-writable copy of that MySQL db archived somewhere. And for goodness sake, do the same for the E:\Data backup. Best of luck with it. On Fri, Oct 9, 2009 at 5:43 PM, Ben Scott <[email protected]> wrote: > On Fri, Oct 9, 2009 at 5:38 PM, David Lum <[email protected]> wrote: >> All the data for MySQL is there, we have a DBA who can see the DB, we just >> need to figure out how to make Versioncue recognize it. > > Well, VerionCue must keep a mapping of human-friendly names to those > funky-name files somewhere. Maybe you can connect to the MySQL > database, browse the table structure, and come up with a query that > generates a list. Then script something to rename the files given the > query output. > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
