When using Ivanti EPM Content Replication, a variety of diverse sources can be created, managed and replicated to a variety of Preferred servers. A source can be a UNC or HTTP share that can be accessed by the configured user. A source can also be configured to use mirroring in order to maintain the Preferred servers up-to-date. If a source is across a very slow link, a Source Representative can also be configured.
- Name: This can be any name used to identify the source. It does not need to match any server or share name
- Description: A description or more information about the source
- UNC or http path: This is the full path to the location of the files that will be managed as a single source. This path can be an entire share (\\Server\Share1) or a particular folder inside a share (\\Server\Share1\Software\Microsoft).
- Connect as user: This is the user that will be used to connect to the share. The share must allow the user to authenticate and grant read access. This user can be a read-only user to increase security
- Password: The password for the above user
- Test credentials: This will attempt to connect to the share and path as the indicated user.
Preferred servers (Targets)
- This will show available Preferred servers and Preferred servers that are currently assigned to be replicated from this Source.
- The top pane shows all Preferred servers and the assigned Replicators that are NOT configured to be replicated from this Source.
- The lower pane shows the Preferred servers and associated Replicators that are currently assigned to be replicated from this Source.
- For more information on configuring a Preferred server see: How to How to configure the Preferred Server (Target) for Ivanti EPM Content Replication
- By default, when a replication job is run, the Replicator will only identify files that are missing from the Preferred server, it will not remove files from the Preferred server. This can lead to a preferred server having a large amount of excess data.
- When mirroring is enabled, when a replication job is run, the Replicator will make the Preferred server match the source EXACTLY. If a file is no longer on the Source it will be removed from the Preferred server.
- Be careful with mirroring if "nested" sources are used. If Source 1 is set to \\FileServer\Software with mirroring enabled and Source 2 is set to \\FileServer\Software\Microsoft with mirroring disabled, there may be unexpected results. When the replication job for Source 2 runs on PreferredServer, files will NOT be deleted. However, when the replication job for Source 1 runs on PreferredServer files will still be removed from \\PreferredServer\Software\Microsoft because Source1 will include all subdirectories and mirroring is enabled.
- Important Note: If mirroring is enabled and a file is deleted from a Source, the next replication job will remove it from the Preferred servers. This may cause the file to be deleted from the entire enterprise.
- When a replication job is run, the Replicator must verify all the files on the Source and check the hash of each file to determine if it has been changed. This can be a bandwidth intensive process. The impact in a LAN or high-speed network is essentially zero, but on a slow link, this part of the process can cause problems as it cannot be throttled. To help in these situations a Source representative can be configured
- The Source representative should be local to the Source. It should have a fast connection to the Source
- The Source representative will periodically check the files on the source, determine the hash and write that information to an XML file
- When a Replicator gets a list of files at the start of a replication job, it will be re-directed to the Source representative (if configured). The Source representative will provide the XML file for the Replicator to use for comparisons between the Preferred server and the Source
- A Source representative should NOT be used if the Replicator is local (fast network) to the Source.
- A Source representative should ONLY be configured if the Replicator is connected to the Source with a slow link. In this case, the Replicator should be connected to the Preferred server with a fast (or at least faster) connection that is available to the Source.
For more information on Content Replication and Preferred servers see: