Re: Scheduler stupidity
Hello Mike, I have determined the scheduler function is stupid. I have it set to make an incremental back-up every night at 2 AM and send me an e-mail when it is done. Last night, I intentionally deleted the back-up file/location. When I woke up, I had an error message (file not found) and cancelled the back-up, so it was never done. Guess what? Got an e-mail that said the back-up was complete. Now what happens when I automatically compress folders, do folder maintenance etc. and there is an error that I don't see or the process doesn't really complete? I will still get an e-mail that says it's complete? This is false and and can lead to problems down the line. Comments? Thoughts? Write a BT. Bug must be in a code, the boolean (that triggers the email sent to you) is set true too early to signal the success of the backup. I think, it is easy to fix. -- Vili Current beta is 3.62.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
Re[2]: Scheduler stupidity
TBBETA, On 11/1/2005, 10:18 AM, you scribbled: V Write a BT. Bug must be in a code, the boolean (that triggers the V email sent to you) is set true too early to signal the success of the V backup. I think, it is easy to fix. Here's the BT link... https://www.ritlabs.com/bt/view.php?id=5277 -- Sawadee, Mike :flag-us-tx: :flag-thailand: Using TB! 3.62.08 Home on Windows XP SP2 Current beta is 3.62.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
Re[3]: Scheduler stupidity
Hello Mike, V Write a BT. Bug must be in a code, the boolean (that triggers the V email sent to you) is set true too early to signal the success of the V backup. I think, it is easy to fix. Here's the BT link... https://www.ritlabs.com/bt/view.php?id=5277 I read the BT, and I started to think about it, just before I wrote that Confirmed. There is an event scheduled. At the start, you make a backup, at the finish, you generate the email. But that email will ALWAYS say that it was successful, as you made the template saying that it was a successful backup, right? So, I think the real solution somewhere would be the possibility to evaluate the result of the start action. Because now you set a mail to be set when the EVENT FINISHED, not when the START ACTION WAS SUCCESSFUL. Do you see the difference? So, for a 2nd thought, it is not really a bug, as the faulty email is not because of bad evaluation (my mistake), but the lack of evaluation... Maybe, there should be some: 'Run this action if the Start action was successful...' between the start and the finish actions... -- Vili Current beta is 3.62.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
Re[4]: Scheduler stupidity
TBBETA, On 11/1/2005, 12:59 PM, you scribbled: V Hello Mike, V Write a BT. Bug must be in a code, the boolean (that triggers the V email sent to you) is set true too early to signal the success of the V backup. I think, it is easy to fix. Here's the BT link... https://www.ritlabs.com/bt/view.php?id=5277 V I read the BT, and I started to think about it, just before I wrote V that Confirmed. V There is an event scheduled. At the start, you make a backup, at the V finish, you generate the email. But that email will ALWAYS say that it V was successful, as you made the template saying that it was a V successful backup, right? V So, I think the real solution somewhere would be the possibility to V evaluate the result of the start action. Because now you set a mail to V be set when the EVENT FINISHED, not when the START ACTION WAS V SUCCESSFUL. V Do you see the difference? V So, for a 2nd thought, it is not really a bug, as the faulty email is V not because of bad evaluation (my mistake), but the lack of V evaluation... V Maybe, there should be some: V 'Run this action if the Start action was successful...' between the V start and the finish actions... I agree, there are two different conditions. Unfortunately the success/failure of the scheduled function is irrelevant. I agree this may not be an actual bug, but I believe it is bad form. Imagine thinking all of your e-mails have been backed up for the last month, then one day you need them. Or the maintenance that wasn't really done until one day your mail file becomes inaccessible. -- Sawadee, Mike :flag-us-tx: :flag-thailand: Using TB! 3.62.09 Home on Windows XP SP2 Current beta is 3.62.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
Re[5]: Scheduler stupidity
Hello Mike, V Maybe, there should be some: V 'Run this action if the Start action was successful...' between the V start and the finish actions... I agree, there are two different conditions. Unfortunately the success/failure of the scheduled function is irrelevant. I agree this may not be an actual bug, but I believe it is bad form. Imagine thinking all of your e-mails have been backed up for the last month, then one day you need them. Or the maintenance that wasn't really done until one day your mail file becomes inaccessible. I totally understand you. Ok, lets be constructive: go to the BT, close the issue, and send a new WISH. I will support that, as e.g. it is possible to return a result value (0 or 1) from the start action for the next one, so that can be evaluated... Hmm... Thinking further: there should be a %STARTACTIONRESULT or something macro, so: Dear Mike, IF %STARTACTIONRESULT=0 Then Sorry, backup failed IF %STARTACTIONRESULT=0 Then Sorry, backup failed Cheers, Mike's TB! (Ok, I did not use the %IF macro the right way, but something similar). All we need is a %STARTACTIONRESULT macro, and its result should be updated by TB! depending on the success of the start action, if possible... This way we dont need a 'Run this action if the Start action was successful...' type action between the start and the finish actions... Any thought? -- Vili Current beta is 3.62.07 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
