In a policy run, a policy is enforced separately for each of the pairs associated with the policy. A policy can run on demand or when it is scheduled. Each policy is associated to a schedule. Multiple policies can be scheduled to run at the same time. Scheduled and unscheduled policies can be run manually.
Run a single policy at a time on a pair to enforce the policy’s rules for moving data. A file is moved if it meets all of the filter options specified in the rule.
Configure multiple policies to run at the same time on a pair to enforce alternative rules for moving data. When the group of policies moves files in both directions, the primary-to-secondary policies are grouped and enforced, then the secondary-to-primary policies are grouped and enforced. A file is moved if it meets the rules for any one of the policies that are run together.
For example, a policy run for a standard pair might move all files with extensions of .mp3 from the primary location to the secondary location.
For a retention pair, policies move data only from primary to a repository on the secondary. A folder is created and named with “PolicyRun” a time stamp, such as PolicyRun_20110815_10.35. Files are moved to the folder, keeping the data structure relatve to the root of the primary location.