[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number : 10818 Date : 2005-03-18 Author : des4212001 Subject : Re: How does xxclone copy the registry? Size(KB) : 3
--- In xxcopy@yahoogroups.com, "des4212001" wrote: > > --- In xxcopy@yahoogroups.com, "Garry Deane" wrote: > > > > --- In xxcopy@yahoogroups.com, "des4212001" wrote: > > > > > > Does it shutdown Windows first & copy the files? > > > > > > I'm reasonbly sure ERUNT writes out memory which at least > > > gets 99.9%. (There are some minor settings pieces not captured > > > this way.) Volume Shadow Copy Service can copy the files with > > > Win32 running (if you've got the time to wait) but this is > > > insufficient as any app data changes aren't in the files until > > > Windows shuts down. > > > > > > I may be ignoring the best way to do it!? > > > > > > Thanks: DES > > > > This from a google search: > > > > "ERUNT uses the Windows API function RegSaveKey (or RegSaveKeyEx > > on Windows XP and Server 2003) to stream the registry data out > > into a new file. So it is not a direct "file copy". REGBACK and > > REGREST tools from the Windows Resource Kit use the same method." > > > > I'm pretty sure that xxclone uses the same technique but also > > has a few fail safe techniques if there's a problem. One of > > these is the triple boot method but I don't think that there's > > been any reports of xxcopy needing to resort to this in recent > > times. > > > > I wouldn't worry too much about the fact that ERUNT/Xxclone/ > > Shadow Copy etc don't have the "latest" data. The registry is > > updated constantly. If you're concerned that a program may > > not have written data to the registry when you do a clone, > > shut down the application in question before doing the clone. > > > > Garry > > Yes Garry, that confirms what I only suspected. I currently use > ERUNT and know for a fact though that some minor pieces of the > registry aren't complete until Windows closes. Specifically, the > Quick Launch Tool Bar is never present on either a copy or restored > registry via ERUNT. Trivial to fix, but always makes me wonder "what > else"? > > I still can't be sure from Kan's reply exactly what's going on? > Rephrasing the question... "Does xxclone copy the registry After > Windows has Closed and written every last detail?" Reading > his "trade secrets" there only convinced me my manual method isn't > that complicated after all! > > Yesterday playing around I had built a SyncBack Profile to copy just > the 7 necessary conponents (no logs or LocalService & NetworkService > (other user) parts). SyncBack and stores it's data in the registry, > so this very act changed the registry. (It copies the Locked files > via VSS.) But running the profile said there were no differences. > And there weren't... in the files. But, I don't think I'd closed > SyncBack prior to the test (which could have updated the files)! > I'll continue the test today & verify whether or not I can get as > current a registry that way as with ERUNT. It's slower but easier > (and less prone to mistakes). > > DES And answering my own question... Closing SyncBack doesn't write the registry capturing the data change. Apparently only closing Windows does that. Not good (wonder how much other stuff falls in this catagory?). I had already asked about an option to store the program data in an .ini instead, and that's... coming. Just trying understand all this. And apparently the only way get a "complete" registry is stop Windows & copy the files. DES
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.