Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bobn42855

Pages: [1]
1
First of all, your registry backup just pulled me out of another unwanted situation - thanks for that!

Regarding your reply here, I hope you were just thinking out loud and not expecting that your comments are going to help me figure out what the problem is. Some of it I only vaguely understand - the rest I don't understand at all. I take it to mean it didn't help you understand what the problem is. Let me know if there's anything else I can try or let you know that might help. Thanks!

2
Hey, Shane. Not sure how I'm supposed to reopen this topic. I have had several scheduled registry backups hang since I brought this up initially. I don't know if this helps at all, but I did notice a definite difference in the Log_vss.txt files between runs that don't hang and those that do. I'm attaching them here.

3
Hi, Shane. I wish I could verify that this does or doesn't only happen running under the system account but I cannot. All I can verify is that it was running under the system account this last time it happened. I've only noticed that's it's happened twice since I've been having Task Scheduler run it twice a day for a couple of months. I don't remember when I changed the task from running under my admin account to running under the system account. I do know that this time (when it got hung), it was running as a catch-up task after my system had been shut down and started up again. In other words, the system was not idle long enough for the task to start at its scheduled time and before the system did meet that idle condition, I shut down the system. The task then was started after I started the system and got away from it long enough for the idle condition to be met. I know it has run as a catch-up task before without shutting down the system in between without the problem. I almost never shut my system off but had to a few times lately. It seems to me that that was the case the last time the problem occurred but I'm not sure. But, I'm pretty sure that I've had it run as a catch-up task after a restart and it didn't have the problem because I was trying to get Task Scheduler to start missed tasks after a system restart and, through my testing, found that the only way I could do it was to have the task run under the system account and during that testing, your program was started as a catch-up task and I didn't notice that it didn't finish on its own (and I would have had that been the case). Don't know what the difference (if any) might be for it or the Task Scheduler between a shut down and a restart. If I'm able to notice anything else that might be applicable, I'll let you know. Thanks very much.

4
Hi, Shane. I've had Registry Backup v1.6.0 set up via Windows Task Scheduler to run twice a day, 12 hours apart, upon 10 minutes of system idle time for a couple of months. I'm using argument "-auto". I originally had it set up to run under my user account (which is administrator) but my experience has been that Task Scheduler does not pick up missed tasks after a restart for non-System user accounts. So, I changed it to run under user account "SYSTEM" and it's never missed being run when it should be (even after a restart after a missed task due to the idle condition not being met). I always have DriveGLEAM running which is wonderful for letting me easily see my CPU and physical disk usage at all times. It normally shows 0% CPU usage unless something I'm aware of is running. Twice now, I've noticed it sitting at 25% usage without anything obvious going on and when I check Task Manager I see TweakingRegistryBackup.exe running as a process using 25% CPU. When I check the backup files that it should be generating at that time, they are there and contain all the same folders and files as any of the other previous registry backups and the size of the entire backup is virtually the same as the previous one. I mean, it seems to have done its job but, for some reason, isn't ending. No other processes are showing any CPU usage whenever I look (other than Task Manager). I've let it go like this for over an hour each time and it doesn't end on its own so I kill it. I'm sure you are the one who may have an idea as to what may be going on. Thanks!

Addendum: Next time I ran the program directly after killing the process, it came up with a notice which I closed before writing it down specifically but it was something to the effect, "The last process did not end properly, would you like to revert to the fallback method?". I just answered "No" and did a backup (via VSS) which completed fine.

5
OK - thank you. Your reply led me to do some studying up on 'hives' and the listed groupings makes more sense to me now. Heck, I had always assumed that the registry was just one big file somewhere. The more I learn (about anything) the more I realize how much I don't know. Thanks again for the quick reply.

6
Seems like a dumb question to me too but the first screen that comes up listing parts of the registry to uncheck for backup causes me to ask. I know what the registry looks like via the editor and these groupings don't register with me. I just want to make sure that if everything is checked that it means that the entire registry gets backed up. And, I guess, it begs the question for me as to why one would want the option of omitting any of these groups. Or maybe I'm just not understanding what the first screen's about at all. Thanks!

Pages: [1]