Typical Replication Configurations

This section provides examples of typical types of replication configurations. These can be used as is, or may be modified for your special circumstances. A combination of these configurations may be used.

These replication rule configurations interact with the Read Vaults Priority and Default Vaults you assign to each user. In most cases, it is recommended to set the user’s Read Priority vaults to give them the best performance at their usual location for reading the files.

There are two options for setting the User’s Default Vault. The first is to assign it to the Vault which gives them the best performance, often the same one as the highest Read Priority. The second is to assign it to a ‘Master’ vault. There are tradeoffs for each approach. The first approach allows you to use the ‘onDemand’ replication rules to place files onto their local vault when they first view them, the second approach puts files immediately onto a master vault.

This configuration allows users to almost always access files from their Read Priority vaults, unless a file has not yet been replicated (because it is claimed, or because the scheduled replication has not yet executed). Usually, you would want to set this type of replication to run immediately or to be scheduled to occur during off hours, to capitalize on periods with low server use and lower network traffic.

For this configuration, one replication rule must be set for each vault -

• Initiator Type – onChange
• Filter Method – none (blank)
• Replication Mode – Immediate or Scheduled
• Replication Type – Copy
• Is Active – checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule -

• File Types – should be blank.
• Target Vaults – each other vault.

This configuration is good for an organization where there is one main location with many users, and smaller satellite locations, or where you want to maintain a backup repository, and you don’t want to assign the master vault as every user’s Default Vault. Often this would be combined with onDemand rules to copy files to user’s highest priority Read Vault (or Default Vault if there are none) from the master vault when they first open a file.

Usually, you would want to set this type of replication to run immediately or to be scheduled to occur during off hours, to capitalize on periods with low server use and lower network traffic.

For this configuration, one replication rule must be set for each vault except the master vault.

• Initiator Type – onChange
• Filter Method – none (blank)
• Replication Mode – Immediate or Scheduled
• Replication Type – Copy
• Is Active – checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule -

• File Types – should be blank.
• Target Vaults – only the master vault.

This configuration is especially useful for cases where files of certain types are either exceptionally large and that vault is specially configured to handle them, or are regularly accessed by another server-based application at that vault site, or for special backup or security reasons.

For this configuration, one replication rule should be set for each vault which is configured as the Default Vault for any user who might save that type of file, except the specific vault to which the files are to be moved.

• Initiator Type – onChange
• Filter Method – none, or configured based on the business need. Remember, the filter method is checked before the replication transaction for a file is executed.
• Replication Mode – Scheduled, Delayed, or Immediate, depending on the file type and business need
• Replication Type – Move
• Is Active – checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point. Large files may require longer Timeout values.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule -

• File Types – select the type(s) of files to move.
• Target Vaults – the selected vault (only one should be selected for a Move replication type).

This configuration provides Released Document Files to users at remote sites. It requires writing a method which is specified to run on a Lifecycle Transition to the Released state. See Programming Notes – Document Release Transition onEvent Method for an example of that code.

For this configuration, a master vault would typically be used as the main repository, and one replication rule must be set for the master vault, or otherwise for all vaults which might have the only copy of a ‘released’ document file.

• Initiator Type - onEvent
• Filter Method – none, or configured based on the business need. Remember, the filter method is checked before the replication transaction for a file is executed.
• Replication Mode – Scheduled, Delayed, or Immediate, depending on the file type and business need
• Replication Type - Copy
• Is Active - checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point. Large files may require longer Timeout values.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule -

• File Types – select the type(s) of files to move.
• Target Vaults – the selected vault(s).

This configuration allows copies of files to be local to a user so that subsequent access (for anyone else at their site) is faster. It is useful for files that need repeated access, but may not be needed by users at all sites. It minimizes access times, and reduces site-to-site data traffic and storage requirements at the sites.

For this configuration, one replication rule should be set for each vault:

• Initiator Type - onDemand
• Filter Method – none, or configured based on the business need. Remember, the filter method is checked before the replication transaction for a file is executed.
• Replication Mode – Scheduled, Delayed, or Immediate, depending on the file type and business need.
• Replication Type - Copy
• Is Active - checked
• Replication Time – If Scheduled, set to an off hour. You should consider staggering the replication times for the different rules, so excessive replication transactions are not set to execute all at the same time.
• Timeout – depends on the installation, but a default value of 0100 (one hour) is a good starting point. Large files may require longer Timeout values.
• Label – a unique name for each rule.

And for the two relationships made in the Replication Rule:

• File Types – None, or select the type(s) of files to copy.
• Target Vaults – None (blank). The user’s highest Read Priority vault is automatically used.