just a moment ago I've discussed your issue with Dieter.
We now have a hypothesis what happened and what is causing the problems.
You probably didn't shut down the server first and pulled a backup of the database afterwards, but more vice versa.
During your backup (or just after the backup and before you shut down the server) some jobs finished.
The finish of those jobs isn't part of your backup.
Thus after starting the new server, it thinks that those jobs are still running (that's what the database tells it).
What has to be done is to simply repeat the messages from the jobservers to the scheduling server.
ALTER JOB xyz WITH STATE = FINISHED, EXIT CODE = 4711; /* or 0 or whatever */
(instead of xyz you enter the JOBID of the jobs to finish of course).
I hope our hypothesis is correct.
the contents of the database is kept in sync with the contents of the server's memory.
This guarantees that if the database is safe, your entire system is safe.
This means that if you're going to manipulate the database (moving it to another instance is a kind of manipulation), ALWAYS shut down the scheduling server first!
And never ever use SQL to manipulate the data within the database, unless we say so.