Specifies a description of the replication policy. Sorts output by directories that have been explicitly excluded in replication. Specify as a replication policy name or a replication policy ID. In this example, you could include both the Run the policy on all nodes in this cluster. If a SyncIQ license becomes inactive, you cannot create, run, or manage replication policies. Displays the status of the job. Useful for things like the newsyslog-on-ifs crontab entry, which wants to be in each nodes' crontab but should only be run once per cluster. Configuring file-criteria statements can cause the associated jobs to run slowly. After a replication policy is reset, SyncIQ performs a full or differential replication the next time the policy is run. For example, you can specify "Every 1st month". Use Live Chat for fast, direct access to EMC Customer Service Professionals to resolve your support questions. The POSIX timestamp of when the item was last accessed. movies and Copy policies enable you to remove files from the source cluster without losing those files on the target cluster. If changelists are enabled for a policy, SyncIQ does not automatically delete the repstate files generated by the policy; if changelists are not enabled for a policy, SyncIQ automatically deletes the repstate files after the corresponding replication jobs complete. OneFS isi commands A through C This chapter contains documentation of the OneFS CLI commands isi antivirus policies create through isi config . For example, if the target directory is a compliance directory, the source must also be a compliance directory. iprange int-a Adds an IP range to the int-a internal network. 172. OneFS enables you to replicate data from one Isilon cluster to another through the SyncIQ software module. The number of bytes between the start of the changelist entry structure and the path, relative to the root path, of the file or directory that was modified or removed. /ifs/data/media/file to be deleted from the target cluster. Displays a subreport about a completed replication job targeting the local cluster. If no options are specified, displays current default replication report settings. If a SnapshotIQ license has been activated on the target cluster, you can configure a replication policy to generate additional snapshots that remain on the target cluster even as subsequent replication jobs run. If you are unable to fix the issue, you can reset the replication policy. For example, consider a policy with the following settings: In this example, the setting that excludes the Removes the specified directory from the list of included directories. Specify as any directory path contained in the root directory. You cannot specify the The cluster that data is being replicated to is the target cluster. 10. Assessment appears. You can prevent a large replication job from overwhelming the system by limiting the amount of cluster resources and network bandwidth that data synchronization is allowed to consume. OneFS does not limit the number of replication policies that you can create. This procedure is available only through the command-line interface (CLI). You can replicate any number of files and directories with a single replication job. cars and The following replication policy fields are available only through the OneFS command-line interface. Determines whether replication jobs connect only to nodes in a given SmartConnect zone. When a job is created for a replication policy, SyncIQ checks whether it is the first job created for the policy. The following command configures SyncIQ to delete replication reports that are older than 2 years: SyncIQ does not support dynamically allocated IP address pools. You can view a changelist that describes what data was modified by a replication job. Connect policies to all nodes on a source cluster. The following types of items might have been modified: A first-in-first-out (FIFO) queue was modified. /ifs/data/media/temp. 162, and Selects files that were created after the specified time. Delete all files that are not committed to a WORM state from the target directory. You cannot replicate data according to snapshots generated by SyncIQ. Specify Failover is performed per replication policy; to migrate data that is spread across multiple replication policies, you must initiate failover for each replication policy. For example, For example, Metadata such as access control lists (ACLs) and alternate data streams (ADS) are replicated along with data. The following command creates a report about how much data will be transferred when weeklySync is run: The following command displays the assessment report for weeklySync: The following command replicates the source directory of weeklySync according to the snapshot HourlyBackup_07-15-2013_23:00: The following command resumes weeklySync: The following command cancels weeklySync: The following command displays detailed information about a replication job created by weeklySync: The following command fails over data for weeklySync: The following command sets newPolicy to run only manually: For example, the following command reverts a failover operation for newPolicy: The following command creates a mirror policy for weeklySync: SyncIQ names mirror policies according to the following pattern: You can replicate data either by manually starting the mirror policies or by modifying the mirror policies and specifying a schedule. Displays a sub report about the specified replication policy. Disable Policy appears, verify that a replication job is not running for the policy. For assessed policies, You can create replication policies that determine when data is replicated with SyncIQ. Isilon Version 8 Cheat Sheet Commands.