Yesterday I successfully replicated my Exchange server to a repository on the local SAN. Then I launched a replication to the remote (Disaster Recovery) host over the WAN. That job is still "processing" after 14 hours, although it has only processed 0.0 KB.
What is the best way to stop this job?
Why I'm asking is: Last week I launched a replication to the same remote replica, but I had forgotten that I had launched a Consolidation on that replica that was still running. So I stopped the job. Then since it didn't want to stop for a long time, I rebooted the Veeam B & R server.
Then I consolidated the snapshots on that replica, and on the vm itself. And since then, I haven't been able to replicate to that replica.
Maybe my question is, "How can I repair a replica that seems to be 'broken'"?