Creating Replication Rules

This section outlines how replication rules are created. Replication rules define which files get replicated, from where, to where, and when. These rules are checked when a file is downloaded from a vault server (this happens when users get or view a file), when a file is uploaded to a vault server (this happens when users add or modify a file), and when requested programmatically. Replication rules are created for each vault server, and can be written to move files to another vault server or copy files to multiple vault servers. User Default Vault and Read Priority settings, as mentioned in the prior chapter, interact with Replication rules, so care must be taken in defining both to work together to give the desired results.

Replication rules are checked by the Aras Innovator Server, and any match causes the creation of replication transaction record(s) for the specified file and source vault to each target vault specified in the rule. These transaction records are regularly checked by the Aras Innovator Server based on the settings determined in how the Replication Transaction thread was configured (in Section Creating and Configuring Replicated Vaults), and sent to and executed by the vault servers per the date/time the transaction is due to execute.