SyncIQ resync-prep fails to start. Error "Target path overlap"

SyncIQ resync prep job fails to start with the following error:

"Target path overlap. Don't allow change target path  to sub-folder /ifs/source. Please use "source-include-directories" or break target then re-create policy "

A similar error is observed in the isi_papi_d.log:

SOURCE-CLUSTER-1(id1) isi_papi_d[4699]: STACK Target path overlap. Don't allow change target path  to sub-folder /ifs/source. Please use "source-include-directories" or break target then re-create policy.

A target record exists on the source cluster with an empty target directory entry. Or the source cluster name <src-cluster-name> is the local, not target, cluster.

Example 1:

<?xml version="1.0" encoding="utf-8"?>
<target-status>
  <policy>
    <id>xxxxxxxxxxxxxxxxxxxxxxxxxxxxx</id>
    <policy-name></policy-name>
    <src-cluster-name></src-cluster-name>
    <src-cluster-id>xxxxxxxxxxxxxxxxxxxxxxxxxx</src-cluster-id>
    <target-dir></target-dir> <<-------------------------------------------Target directory entry is empty
    <last-src-coord-ip></last-src-coord-ip>

Example 2:

<?xml version="1.0" encoding="utf-8"?>
<target-status>
  <policy>
    <id>xxxxxxxxxxxxxxxxxxxxxxxxxxxxx</id>
    <policy-name></policy-name>
    <src-cluster-name>source1</src-cluster-name> <<-----------------------Source cluster is the local cluster not the target cluster
    <src-cluster-id>xxxxxxxxxxxxxxxxxxxxxxxxxx</src-cluster-id>
    <target-dir>/ifs/source/path</target-dir>
    <last-src-coord-ip></last-src-coord-ip>

On older OneFS versions, a SyncIQ policy with Accelerated Failback set, leaves behind a target record xml file.
OneFS 9.10 introduced a check for the resync-prep job that fails when the target record file has an empty target directory value, "<target-dir>."

Workaround:

Remove the target record xml file with empty directory entries which is present on the source cluster. 

On newer OneFS versions, DomainMark jobs run by Accelerated Failback, do not leave a target record xml file behind.
However, previously created target records are not removed.

Steps to remove the target record xml file with an empty directory on the source cluster:

1) Create a directory with the Service Request (SR) number under /ifs/data/Isilon_Support/.
Example:

mkdir /ifs/data/Isilon_Support/123456789

2) Move the affected xml file with an empty target directory to /ifs/data/Isilon_Support/<SR>.
Example:

mv /ifs/.ifsvar/modules/tsm/config/target_records/xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.xml  /ifs/data/Isilon_Support/<SR>

Fixed versions:
9.12.0.0
9.10.1.3
9.7.1.9