SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Cheeky Kid who wrote (75659)6/7/2011 7:52:23 AM
From: PMS Witch  Read Replies (1) of 110645
 
I find the Volume Shadow Copy issue intriguing.

When I run my imaging software from within Windows, I'm copying a running Windows system. When I restore my system from that image, this work is NOT done from within Windows; hence, when the restoration is finished, my system boots. In this case, I'm booting Windows from a disk that contains data from a running Windows. Normally, when Windows boots, it expects the disk to contain data from a Windows session that has gone through the process of an orderly Windows Shut Down. Sometimes, Windows doesn't like this.

Volume Shadow Copy enables a running Windows system to make an exact duplicate of its system -- even those files being used (and altered) at the time. It's easy to see why imaging software would need to deal with Windows Volume Shadow Copy to work properly. It's also easy to see how this would make tricky code even more complex.

A few people have recommended running imaging software from a CD instead of through Windows. This would solve the issue of restoring a shut-down system with a running system's data. It would also eliminate much of the necessity for using Volume Shadow Copy. This could augment the reliability of both image creation and system restoration.

Cheers, PW.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext