Should Protection Settings Be On for all HD's?

apd2


Hay forum,
Hope everyone had a cool 4th... Soo
 
Should Protection Settings be on for all HD's when you create a System Restore piont ? By default it's just the Windows7 C drive. Sorry for the basic ? I'm just transfering and updating to a new machine and have been out of the loop for awhile and I wasnt sure if its bad for the sample/audio drive?  Looking forward to Sonor 8.5
 
Thanks everyone,
 
Scott
 

I don't use built-in system restore at all but that's just me.

System Restore is most helpful on the drives where the data is constantly changing, so certainly your system drive should be selected also where you keep your works in progress would give you protection on the files you last worked on.

Any drives where the data stays constant would be less critical as the information wont have changed between the last restore point and the system going belly up.

Once the System Restore service is running in the background anyway I don't think there is much overhead between having one drive protected and having say 4 drives protected so I'd be tempted to have them all turned on.  You never know.

The only real exception to this would be if you had a dual boot set-up where you'd turn off System Restore for the drive that contained the alternative OS so that the System Restore didn't mess with that OS.

Scott,

I do not believe that System Restore will help protect and restore any of your music files, no matter which disk they are on.

According to Microsoft, the following features ARE restored when using System Restore:

    * Windows Registry
    * Local Profiles
    * COM+ DB
    * WFP.dll cache
    * WMI DB
    * IIS Metabase

According to Microsoft, the following ARE NOT restored when using the System Restore feature:

    * DRM settings
    * Passwords in the SAM hive
    * WPA settings (Windows authentication information is not restored)
    * Specific directories/files listed in the Monitored File Extensions list in the System Restore section of the Platform SDK e.g. 'My Documents' folder.
    * Any file types not monitored by System Restore like personal data files (e.g. .doc, .jpg, .txt etc.)
    * Items listed in both Filesnottobackup and KeysnottoRestore (HKLM\System\Controlset001\Control\Backuprestore\Filesnottobackup and Keysnottorestore) in the registry.
    * User-created data stored in the user profile
    * Contents of redirected folders

I don't find System restore to be a resource hogger, and it is a useful, practical tool within its limitations.

System restore does check-points only at certain times, and does not normally interfere with anything one is doing.

But my main use for it is to create a MANUAL system restore point, typically BEFORE I install some software, specially free ones that affect the registry. It only takes a few seconds.

VST's do not, as far as I know affect registry. Unless there were some malware.

I also use Acronis, as a backup. Typically I only back up the C: partition, which I keep on purpose rather small..All data is in a different partition. That partition can be a reliable external drive. I use a firewire drive for that.

Larrymcg is correct on what he posted. On "being a hog for resources", I'd appreciate a reference being cited, applicable to the current state of the art (or technology).

By the way, Acronis also runs as a process, and it does not consume CPU or anything that I can detect, to it affecting performance or results.

One reason why files of Mac or Linux don't always backup right is because some characters in Unix/Linux/BSD are not valid in Windows, and viceversa, for filenames...Using usual filenames is not a problem, though.