Symptoms

The above error is generally a result of fixing a previous error "Target path overlap. Previous policy XXXXX from xxxxxxx has path YYYYYYYY. New policy ZZZZZ from zzzzzzz has path YYYYYYYY (unrunnable)"

Cause

On the source cluster, the source path was a target of a previous policy from an older cluster "due to migration per example"The old policy from the older cluster was still having target records on the source cluster "including the old domain id on the path"When the mirror policy created on the new target cluster, it utilizes the same domain-id from the old policy records but later on when the mirror policy run, it complains about the existence of the older target records from the older cluster. "Target path overlap. Previous policy XXXXX from xxxxxxx has path YYYYYYYY. New policy ZZZZZ from zzzzzzz has path YYYYYYYY (unrunnable)" When the admin/support tries to fix this error, he will break the association of the older policy XXXXX on the source cluster, this will result in deleting the domain-id that the mirror policy is counting on and hence cause a failure on the new mirror policy ZZZZZ later on.Please find below the simulation in the lab for demonstration: On the new_source_cluster path /ifs/target is a target from older_cluster and has a Domain ID 65537 new_source_cluster-1# isi sync target list| grep -w /ifs/targetold_policy old_cluster /ifs/target finished writes_disablednew_source_cluster-1# isi_classic domain list -wl | grep -w /ifs/target65537 | /ifs/target | SyncIQ | None | None | None | None | None | Off A newly created policy "new_policy" from new_source_cluster to new_target_clusterThe "new_policy_mirror" created and complains from target overlap new_target_cluster-1# isi sync reports list -v Policy Name: new_policy_mirror Job ID: 1 Start Time: 2021-05-30T08:27:01 End Time: 2021-05-30T08:27:03 Action: run State: failed ID: 1-new_policy_mirror Policy ID: 005056aa8bf93a4cb360d71298fdf618 Sync Type: incremental Duration: 2s Errors: Target path overlap. Previous policy old_policy from old_cluster has path /ifs/target. New policy new_policy_mirror from new_target_cluster has path /ifs/target (unrunnable) The new_policy_mirror is using the same domin id 65537 as the old_policy new_source_cluster-1# cat /ifs/.ifsvar/modules/tsm/config/target_records/005056aa8bf93a4cb360d71298fdf618.xml | grep domain-id 65537 The admin/support breaks the old_policy on the new_source_cluster which result in deleting the domain id 65537 new_source_cluster-1# isi sync target break --policy=old_policyBreaking a policy's target association will result in requiring a full synchronization of all data on the next sync.Are you sure? (yes/[no]): yesnew_source_cluster-1# isi_classic domain list -wl | grep -w /ifs/targetnew_source_cluster-1# As a result, the next run of the mirror policy will fail because the domain id 65537 got deleted new_target_cluster-1# isi sync reports list -v Policy Name: new_policy_mirror Job ID: 1 Start Time: 2021-05-30T08:27:01 End Time: 2021-05-30T08:31:03 Action: run State: failed ID: 1-new_policy_mirror Policy ID: 005056aa8bf93a4cb360d71298fdf618 Sync Type: incremental Duration: 3s Errors: Failed to get domain info for domain id 65537: No such file or directory (unrunnable)

Resolution

The fix is to manually create a new domain id using the job engine, wait till the DomainMark job to finish then update the target XML record with the new domain id and finally resume the mirror policy to success.NB: Please engage support to help updating target XML record new_source_cluster-1# isi job jobs start DomainMark --root=/ifs/target --dm-type=SyncIQ -o MediumStarted job [64]new_source_cluster-1# isi_classic domain list -wl | grep -w /ifs/target65538 | /ifs/target | SyncIQ,Writable | None | None | None | None | None | Offnew_source_cluster-1# cat /ifs/.ifsvar/modules/tsm/config/target_records/005056aa8bf93a4cb360d71298fdf618.xml | grep domain-id 65538new_target_cluster-1# isi sync reports listPolicy Name Job ID Start Time End Time Action State---------------------------------------------------------------------------------------------new_policy_mirror 1 2021-05-30T08:27:01 2021-05-30T08:34:59 run needs_attention---------------------------------------------------------------------------------------------Total: 1

Support Cases