Hello guys!
I have a problem with my backups: jobs that were in running state when i performed my backup process remain running when I restore it. It’s quite annoying because these jobs are automatically respawned. Which is not the expected behaviour.
How would you manage that? The question (and the answer) may be obvious but is not so simple as it appears.
Many thanks.
UP!
I can’t believe that nobody do awx database backup 
I have the same issue as you do, we backup and restore to a different AWX instance nightly, and we were receiving alerts of job failures for jobs that happened to be running during the backup upon restore to the secondary.
I was interested to see if anyone who had more knowledge would’ve replied to you as this’d help me out too. The closest I could come to finding a solution on my own was Add ability to exclude job event and job data from backup · Issue #958 · ansible/awx-operator · GitHub but excluding the tables just made the restore fail. So my crappy solution was to have my automation disable notifications for the one frequently-running job, back up AWX, then re-enable notifications on it.
Hopefully someone has the right answer out here.
Same issue. Due to me additionally having the porblem that these exact running jobs deadlocked my AWX in such a wayy that I cannot cancel these jobs, Its really annyoing.
As a workaround I am currently trying to manually restore AWX using the awx.awx.export and awx.awx.import modules, but I cannot get the import to work.