jeharlan
Comments
-
Also you could write out to the window event log. Currently all I ever see is this:
So if you fix this and let say ID 0 is good and ID 1 is not then we could monitor the event log instead.
The description for Event …
-
This is all we get in the file. There is no way to figure out easily if the backup succededed. Just add the word Failure or Success in the top part of the log. Like I show below and you can now manage this from all kinds of RMM software.
Yes but I do not want to do this manually..... I want a system to do it for me. So what would it take for you to just add a status to the log file you create at backup?
And either create a new file each day deleting the old one or just append to the exisiting file.
Sorry for the delay.. Yes what I am saying is that there is no way to parse through your current log file to determine if the backup completed successfully. What would be great is a single line at the end stating that the job was SUCCESSFULL or F…
Rebooted the server and now it is working fine.
I second that!! One quick way would be to just output a txt file that had the word "success" or "failure". We use N-able and could just read for the output and set a warning if the job failed or the file did not update in 24 hours.
So back to task scheduler then I suppose...