Main Forum > Tweaking.com Support & Help
Registry Backup Beta
Shane:
--- Quote ---This work now in 0.9.1!!!
The first time I open "Registry backup" there is only 3 "user registry files", then if I Close and open the program again there is 7 "User registry files"
--- End quote ---
This was an odd bug. While it got better in 0.9.1 I think I have it fully fixed in 0.9.2.
The program loads an API to get a folder list. For some odd reason at random times the API gets stuck and keeps returning the same folder name. I made my own code to handle it if it does it again. So far so good :-)
--- Quote ---It took about 70 sec to backup for me then I backup manually! Thats just an observation, nothing wrong with that time!
--- End quote ---
Backup times will vary per machine because it is waiting for the volume shadow copy service to make a snapshot.
--- Quote ---These three things are rather unimportant but:
Under "Backup Location" if I have checked "Change backup location" and clicked on the button "Choose folder to store backups" I would like it to start at the latest folder that I have choosen.
Under "Backup Location" again if I have checked "Change backup location" and I have clicked on the text and the text cursor are blinking I also would like to write the backup location and be able to create a folder from there not having to go thru the "Explorer".
In "Check for updates" under settings it says, "Check for program updates at startup", you mean at startup of this program (Registry Backup) not Windows startup (so that you add something to run in the registry)?
--- End quote ---
All fixed for you in v0.9.2 :wink:
--- Quote ---If I create a schedule in "scheduling options" and close the option, then I open the "Task scheduler" and change "configure for" from: "Windows server 2003, Windows Xp or Windows 2000" to "Windows 7, Windows Server 2008 R2", then in Scheduling options under settings in registry backup I tried to click on edit it says: Couldn't find Schedule. Maybe I shouldn't change "configure for" to windows 7?
--- End quote ---
Just leave it the default and it will still work fine.
--- Quote ---This work now in 0.9.1!
Backup by using "Task scheduler" doesn't work for me. Then I look in "Process explorer" under taskeng.exe the TweakingRegistryBackup.exe start but it doesn't do anything. I have tried to change options in Task scheduler but nothing helps. I can do a backup manually and "Volume Shadow Copy" works.
--- End quote ---
That was a spelling mistake that I have fixed. I had the program set to use "/silent" and in the schedule I had it "\silent"
I changed the program to support "/silent", "\silent" and "-silent"
--- Quote ---This works then I restart the computer!!!
I have noticed when Task schedueler are finished with the backup so I see in Process explorer that the cpu on " TweakingRegistryBackup.exe" are at 25% and vss_start.exe at 0.1% and it doesn't stop.
--- End quote ---
The program taking up that much is one of 2 things. 1. its doing the file copy, which wont take long. 2. it could have been the bug that is hopefully fixed where it would get stuck in a loop trying to search for folders.
--- Quote ---In "Log_VSS" I see that then I do a backup it deletes all shadow copies:
(Option: Delete all shadow copies)
This will delete all shadow copies in the system. Are you sure? [Y/N]
- Setting the VSS context to: 0xffffffff
- Deleting shadow copy {b312b803-f794-4726-980f-2ddbc21f47a2} on \\?\Volume{ac49bd0f-c993-11e0-a094-806e6f6e6963}\ from provider {b5946137-7b9f-4925-af80-51abd60b20d5} [0x0042000d]...
--- End quote ---
I have it do this by default for 2 reasons.
1. If a backup failed we want to get rid of the old snapshot.
2. We dont want to use any old snap shots or we may get older files.
0.9.2 is out :cheesy:
v0.9.2
Small bug fix where the program would sometimes get stuck in a loop when loading the treeview.
The backup location setting can now be typed in instead of just using the browse button.
The backup location browse button will now default to what ever backup location is currently set.
Spelling changes.
Shane
Tomas_Sweden:
Ok I have tried 0.9.2 now!
Is there any possibility of choosing whether I want to keep the old files in the shadow copies, because I've been saved by it several times when I have deleted files by mistake.
--- Quote ---"The backup location setting can now be typed in instead of just using the browse button."
--- End quote ---
It doesn't create any folder then I type there.
--- Quote ---"The backup location browse button will now default to what ever backup location is currently set."
--- End quote ---
This works!
--- Quote ---"Small bug fix where the program would sometimes get stuck in a loop when loading the treeview."
--- End quote ---
This seems to work (all the time I have tested)
I have deleted the old schedule and created a new, and then I go to Task Scheduler and run Registry Backup( I haven't rebooted yet) if Registry Backup program is open the vss_start.exe, cmd.exe, vss_7_64.exe, cmd.exe and vss_pause.exe don't use so much cpu, around 0.25%, it makes o backup, but it doesn't stop. And the vss_start.exe isn't under taskeng.exe. If I close Registry Backup vss_start.exe disappears.
If I go to Task Scheduler after closing Registry backup and run Registry Backup the TweakingRegistryBackup.exe starts under taskeng.exe with vss_start.exe, cmd.exe and vss_7_64.exe and vss_7_64.exe uses around 25% cpu but all of them disapperars then they are finished.
Tomas
Shane:
--- Quote ---It doesn't create any folder then I type there.
--- End quote ---
It will create it when you do a backup :wink:
--- Quote ---I have deleted the old schedule and created a new, and then I go to Task Scheduler and run Registry Backup( I haven't rebooted yet) if Registry Backup program is open the vss_start.exe, cmd.exe, vss_7_64.exe, cmd.exe and vss_pause.exe don't use so much cpu, around 0.25%, it makes o backup, but it doesn't stop. And the vss_start.exe isn't under taskeng.exe. If I close Registry Backup vss_start.exe disappears.
If I go to Task Scheduler after closing Registry backup and run Registry Backup the TweakingRegistryBackup.exe starts under taskeng.exe with vss_start.exe, cmd.exe and vss_7_64.exe and vss_7_64.exe uses around 25% cpu but all of them disapperars then they are finished.
--- End quote ---
When you start the program and click backup the program will run vss_start.exe. This then runs the vss exe for the system. When the snapshot is made the vss_pause.exe runs. This keeps the snap shot.
The vss_start.exe looks if the Registry backup program is running. If it isnt it closes the vss_pause. Which then allows the snap shot to close and be done. At which point you see the rest of the exe's close and vss_start closes itself.
The vss exe that is making the snap shot will uses some cpu as it is building the snap shot.
Once the snap shot is made the program starts copying the files from the snap shot, so you will see the program use as much cpu as it can as it copies the files as fast as it can.
Once everything is done you see everything go back to normal. The vss_start stays running until the backup program is closed. So if you clicked backup again without restarting it the backup would be very fast as the snapshot is still made. :wink:
Shane
Tomas_Sweden:
--- Quote ---
--- Quote ---It doesn't create any folder then I type there.
--- End quote ---
--- Quote ---It will create it when you do a backup
--- End quote ---
--- End quote ---
It didn't work. I tried to do a backup after I changed the pathway, but it did a backup in the previous one(C:\Reg_Backup\) not in C:\Reg_Backup2\ that I tried.
The next time I open the Registry Backup program it didn't remeber that I wrote in "change backup location".
--- Quote ---When you start the program and click backup the program will run vss_start.exe. This then runs the vss exe for the system. When the snapshot is made the vss_pause.exe runs. This keeps the snap shot.
The vss_start.exe looks if the Registry backup program is running. If it isnt it closes the vss_pause. Which then allows the snap shot to close and be done. At which point you see the rest of the exe's close and vss_start closes itself.
The vss exe that is making the snap shot will uses some cpu as it is building the snap shot.
Once the snap shot is made the program starts copying the files from the snap shot, so you will see the program use as much cpu as it can as it copies the files as fast as it can.
Once everything is done you see everything go back to normal. The vss_start stays running until the backup program is closed. So if you clicked backup again without restarting it the backup would be very fast as the snapshot is still made.
--- End quote ---
Ok I see that now! :smiley:
Tomas
Shane:
--- Quote ---It didn't work. I tried to do a backup after I changed the pathway, but it did a backup in the previous one(C:\Reg_Backup\) not in C:\Reg_Backup2\ that I tried.
The next time I open the Registry Backup program it didn't remeber that I wrote in "change backup location".
--- End quote ---
That is because I am a dork lol
Thats what I get for programming before coffee. As soon as I woke up and read your post I started making the changes.
I forgot to put any code behind the text box being typed into. I updated the exe, just redownload it. Still the same version.
I also found the bug Ztruker said he had. The browse button didnt have the flag to set the backup path variable in the program. But when you restarted the program it worked fine.
I fixed that as well. Just had to add this to the browse button, and of course it is also added to the textbox when typing :-)
If Trim$(TextBackupPath.Text) = "" Then
sBackupPath = App.Path & "\Backups\"
Else
sBackupPath = TextBackupPath.Text
End If
Shane
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version