System Restore erases restore set points about once a day.

1. My system (XP-Pro) erases restore set points about once a day. I have set the registry for 12 hour restore points and 30 day retention. The only restore points left are the ones made that day. Overnight, I defrag the disks (the Windows Defrag) and the computer goes into the hibernate mode, as it is supposed to. Any suggestions on how to prevent removal of the restore points would be appreciated.

2. Is there any way to automate establishing restore points (other than using the registry settings) so that they are set at the same time each day?

Thanks, SN

 

No idea why your points are not being retained, but this script will create a one-click restore point. It can be set up as a scheduled task to make a point at the same time each day:
http://www.dougknox.com/xp/scripts_desc/xp_sysrestorepoint.htm

 

System Restore

Abraxas: Thanks. I will try this later today. If it works (probably will) the other questions become moot since there will be a daily restore point created. Thanks, again, and especially for the prompt reply. SteveN

 

It could be caused by the amount of disk space System Restore is allowed to use for your restore points. Restore points use a large amount of disk space and when the space is filled the oldest restore points are discarded. This is my understanding at any rate (someone correct me if I'm wrong... I have system restore turned off. I prefer 'images'.) HTH

B

 

B: I checked that first, I am allowing maximum space. I have about 42 gig on the "C" drive and about 32 gig are unused. So . . there should be plenty of room. Thanks for the suggestion. SN

 

Abraxas: I tried using xp_sysrestorepoint.vbs and it seems to work like a charm. I set it up for two restores/day until I see what happens to the old restore points, then one/day should suffice. I still haven't any clues as to why the older ones disappear. Thanks again, SN

 

Abraxas and Mr. B, and others:

I noticed that the old system restore points are erased when the registry program restore points are created, but NOT when the automatic restore points are created. Is there some setting that controls this? Thanks again.

 

Abraxas and Mr. B, and others:

I noticed that the old system restore points are erased when the registry program restore points are created, but NOT when the automatic restore points are created. Is there some setting that controls this? Thanks again.
__________________
SN

 

System Restore Point erasure

Previous System Restore points are erased when the registry ordered restore points are written but NOT when a restore point is written from a scheduled task command (see previous posting).

Edit by PeteC Thread merged - Please don't start a new thread which is the continuation of an existing thread - gets confusing and will lose you attention as previous posters to the thread will NOT receive email notification of the new thread. Better if you stick with black text - easier on the eyes!

Here are the registry entries:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore]
"DisableSR "=dword:00000000
"CreateFirstRunRp "=dword:00000001
"DSMin "=dword:000000c8
"DSMax "=dword:00000190
"RPSessionInterval "=dword:00000000
"RPGlobalInterval "=dword:00005460
"RPLifeInterval "=dword:00278d00
"CompressionBurst "=dword:0000003c
"TimerInterval "=dword:00000078
"DiskPercent "=dword:0000000c
"ThawInterval "=dword:00000384
"RestoreDiskSpaceError "=dword:00000000
"RestoreStatus "=dword:00000001
"RestoreSafeModeStatus "=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\Cfg]
"DiskPercent "=dword:0000000c
"MachineGuid "= "{92D5A1BB-9FD9-4B1E-B90B-D1809D855025} "

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRestore\SnapshotCallbacks]
@=" "

Here is the comands from the scheduled settings:

'Unattended System Restore Point
'sysrestorepoint.vbs
'© Doug Knox - rev 02/11/2002
'Downloaded from www.dougknox.com
'Extracted from original code by Bill James - www.billsway.com

Set sr = getobject( "winmgmts:\\.\root\default:Systemrestore ")

msg = "New Restore Point successfully created." & vbCR
msg = msg & "It is listed as: " & vbCR
msg = msg & "Automatic Restore Point " & Date & " " & Time

'Put a ' in front of the next five lines to disable the Success Failed Prompt.
If (sr.createrestorepoint( "Automatic Restore Point ", 0, 100)) = 0 Then
MsgBox msg
Else
MsgBox "Restore Point creation Failed! "
End If

'Remove the ' from the next 3 lines to only alert you if the process failed
'If (sr.createrestorepoint( "Automatic Restore Point ", 0, 100)) <> 0 Then
' MsgBox "Restore Point creation Failed! "
'End If


The old restore points are erased when a new registry controlled restore point is written. Is there some setting that I am missing?

Thanks for all the previous help and looking for more help.

Regards,

 

Solution found

I was using XCOPY once a day to backup my data files on Drives D, E, F to a spare drive. When XCOPY ran, all previous restore points were erased. Disabling the XCOPY command (in Task Scheduler) fixed the problem and the restore points are left alone. I guess I missed this in looking at several resources on restore problems. This may be of help to others. Regards, SN

 

BTW, I wondered why you needed to defrag every single night in XP?

Glad you found the conflict with your SR points, and thank you for posting your solution. Since your Restore Points are very important to you, have you considered an Imaging program, which will protect more than your Windows System Files?

Also, since you have XP Pro, check out ASR, if you haven't done so already. Could be a useful tool for you, depending on your needs, but it must be set up in advance.
HTH
Johanna

 

Johanna and PeteC:

I only Defrag twice a week and that does not seem to cause the problem. It was the daily XCOPY of Drives D, E, F, to a spare drive that seemed to cause the problem. I have tried Executive Software defragger but did find it to be significantly better (for my purposes) than the version included with XP. Does XCOPY also Defrag????? In any case, all seems to be working fine now. I am using Norton Ghost to make copies of the drives -- if only I can remember to do it on a regular basis.

Thanks for the reply,

 

JMO, but XP defrags on the fly, and other drefragger software is in constant conflict with XP. A once a month check to see if defragging is even warranted should be sufficient in most cases, even on a busy computer. XP's native utility is the best defrag for XP. YMMV, of course.

Also, is there a specific reason the comp needs to go into hibernation? XP doesn't need it, and neither does modern computer hardware. It's a space hogger that has outlived its purpose, because the hardware technology has advanced so far. Remember when screensavers were necessary to prevent burning an image on a monitor? Now they are a lark! Anachronisms from Win9X still exist on XP, but they are superfluous. You can disable Hibernation in the Control Panel under Power Options.

Best regards,
Johanna

 

Hi Johanna,

XP's auto defrag works only if the Task Schedular service is enabled. I'm fairly certain that TS comes enabled by default and wouldn't be an issue unless turned off.

TS also needed for auto System Restore points.

Regards - Charles

 

Charles, I understand that Task Scheduler must be enabled for the actual defrag program to run at a specified time. I should have been more clear. XP is always rearranging data (defragging) while you are working. If your disk somehow becomes such a mess that you need to do a manual defrag, XP will inform you, but I have only seen that on older hardware, if the user is doing video or music editing. So, if you are using SpeedDisk by Norton, for example, then both softwares are trying to rearrange data to where they think is best. This creates conflicts. I have heard great things about DiskKeeper, but I have not tried it, so I can't comment. "Defragging" is getting more redundant anyway, as technology improves. More experienced XP users are placing less emphasis on manual defragging, and someday Defrag will just be a memory from the Win9X days.

btw, for anyone interested, if you set the task scheduler, and XP "analyzes" the drive and determines there are not enough fragmented files to warrant a defrag, it will just skip the task. I'm sure many of you have seen the "You don't need to defrag this drive" message on a manual analysis.

Johanna