Running same script on two servers for redundancy

Less a coding question, and I guess more of a methodology question.

I Have a pretty lengthy (4-5 hours) script that absolutely must run nightly.

To achieve this, I have two servers in different geographic locations that will run the script each night.

My plan is to have each script write to an azure table when it starts, when it ends and when it has created csv files.

Whichever script finishes first, can check that the second script has started.
Whichever script finishes second can then check that both scripts ran, and that the csv files are the same (via MD5 hash or just file size).
If either script didn’t run, or the files are not the same, an alert would be generated.

Does this sound too convoluted? I like Azure Tables as an easy way to keep track of scripts, but I am curious if anyone has suggestions for improvements…

when you crosspost the same question at the same time to different forums you should at least post links to the other forums along with your question to avoid people willing to you help making their work twice or more.