There is no automated check to determine if the policies associated with a pair are moving files back and forth in the same or different runs. When you plan policies for a pair, consider the file extensions and types that occur in the pair and how the filter options are enforced. Ensure that the policies assigned to a pair move files where you expect them to be moved, and that they are not counter-productive.
For example, if one policy moves files to the secondary path based on the file extension, and another policy moves files to the primary path based on the last modified time, some files might move both ways.
You can use the following methods to understand what files are moved during a policy run:
Preview Now: You can use the Section 9.9, Previewing a Policy Run.option to view the files that would be moved in a run without actually moving any files. For information, see
Policy Execution History: You can inspect the Policy Execution History for a pair to examine lists that show what files were moved in the last several runs. For information, see Section 13.2, Viewing the Policy Execution History for a Pair.
Use this information to refine the policies as needed to achieve your storage goals.