Mover Moving Files In Use

I know this is not supposed to happen but some how the mover is moving my Macrium image file while it's still in progress of being created; thus making my image creation fail.  I thought about making the Macrium image creation write straight to the array but I fear the slower parity speeds will make it take way too long.  I have 5 machines that get new system images created weekly and all run fine and average about 300gigs.  However, my son's image (below) is around 700gigs and takes longer to create and the mover starts before finishing.

I have tried to adjust when the image creation starts to the earliest point to when my son can no longer use the computer to adjust the mover schedule.  I felt 4am is the latest I could start the mover without it affecting performance on the users in the morning.

Any suggestions?  I was hoping there would be some type of custom schedule I could set for the mover by each day but don't see that as an option.

Oct 1 04:00:01 unRaid root: mover: started
Oct 1 04:00:01 unRaid move: move: file /mnt/cache/Data/System Images/Evan/backup_running
Oct 1 04:00:01 unRaid move: move: file /mnt/cache/Data/System Images/Evan/Evan-Desktop-00-00.mrimg.tmp