![]() This means that Bvckup2 process is killed by your operating system rather than being given a chance to exit gracefully. I mean, not only there was no interruption's reasons mentioned in the log, but the interruptions themselves aren't mentioned neither. So, I'm wondering which is the expected behavior from Bvckup when dealing with interruptions, according to which one was the interruption, the amount of files, its kind and size, etc., in order it will determine to start from scratch or resume interrupted jobs? But other times, I saw that it did resume the interrupted job exactly when it was left off, but the files in that test weren't the same ones. I mean, not only there was no interruption's reasons mentioned in the log, but the interruptions themselves aren't mentioned neither.Īnd what about the jobs' specific status while an interruption affect them? I mean, in my tests, there were sometimes when after a sleep interruption, Bvckup just initiated it again, but from scratch, re-processing the already completed (copied) files. " message you mention, is when I manually stop a job through the program's itself there is nothing in the jobs' log telling me what happened between two different executions, which I'm able to notice by looking at the time lapse gap. Jan 26, 2018I see, but take note that the only time when I see that "Cancelling. In my test, I started to copy 3 files, two of 439MB and one from ~1GB, and after every interruption, Bvckup will resume the full job, even if it already had copied fully one of the three files.īy the way, I saw the job's log but there where no signal of what really happened between each newly started copying process, I mean, I didn't see any kind of messages informing about the process being interrupted anytime, neither because what reason (system was logged off, etc.). I noticed that although Bvckup will always resume the interrupted jobs, it will not resume exactly from where it left off, but start from scratch. I did some additional simple tests to see how Bvckup behaves when some currently active job is interrupted by a restart, a logging off or a shutdown. But in case of reboots or shutdowns, I bet I will still need to look at Bvckup's current state before doing it. Normally, I just put the system to sleep by myself or via a third-party timer, and if jobs will resume correctly each time, there is no problem. Jan 16, 2018Alright, thanks for your explanation. ![]() ![]() "Reboot" is a full system reset, so all programs are shut down with some being restarted after a reboot. All running programs just freeze until the machine is awoken. I did notice that in the case of "standbys", after turning on the PC again, the interrupted job resumed its activity from its last state but I doubt whether that will be always the case or a reliable practice.īasically, "sleep" is a non-intrusive system pause. Would you like to proceed anyway?" or something similar. When one is in place, it _will_ block a reboot and if you (or a system) is trying to reboot the machine, you will see a message saying "Program X is blocking a reboot for THIS reason. Reboot prevention is done by creating a similar request, but it is of a stronger nature and it's called a "reboot block". This is a request for Windows, but Windows may or may not act on it. Sleep prevention is done by tagging an active execution thread (that's doing a backup) as needing a system to be up. A sleep is a non-intrusive, state-preserving operation, so it doesn't have a strict veto'ing mechanism like reboots have. Jan 16, 2018Reboots and sleeps are handled by Windows differently. And although I didn't tried it, I think that in the case of reboots and shutdowns, it would get considerably complicated, since I don't know if Bvckup will just resume the jobs next time without any consequent problems. ![]() I did notice that in the case of "standbys", after turning on the PC again, the interrupted job resumed its activity from its last state but I doubt whether that will be always the case or a reliable practice. Is there a way Bvckup intercepts and delays such kind of requests, so currently active jobs or those with a few seconds to start, don't get abruptly stopped? But then I thought of this feature for those cases, when a user or even a scheduled third-party program reboots or put the PC to sleep. ![]() Let's say I want to put to sleep or reboot the machine, in such cases I never stop for a while to see Bvckup's jobs' condition, but rather just do it. My Windows' power options keep the PC always active, with no kind of active idleness timers. Jan 16, 2018I see, but I was referring to user initiated sleeps, reboots and shutdowns. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |