Installation point replication is based on installation point reporting. Therefore, it is necessary to understand the main concept of the reporting before implementing the replication. See About installation point reporting for more information.
If you understand the concept of installation point reporting, implement the installation point replication according to the provided step-by-step guide to automatically keep the files at installation points synchronized with the media master installation point.
Before continuing to the step-by-step guide to implementing installation point replication, make sure that you have installed your installation points and they have an asset configuration item in Miradore. See setting up an installation point if you need more help about this topic.
Notice that installation point replication doesn't work if data deduplication is enabled on the server.
Also make sure that you understand the concept of file management on installation points in Miradore.
Step-by-step guide to implementing installation point reporting and replication
Step |
Task |
How to... |
Select one installation point as a media master installation point. |
At the top level of the installation point hierarchy, there is always the media master installation point, where all new files, installation media, patches, and drivers are uploaded. From the media master installation point, the files are then automatically replicated to 1st level slave installation points, where the files are replicated onwards to 2nd level slave installation points and so on.
|
|
Add an installation point to the installation point replication hierarchy. |
To optimize the performance and reliability of installation point replication, it is advisable to organize installation points in a hierarchical topology, which is based on the physical location or quality of the network connections of the installation points. Therefore, the media master installation point should not be a direct parent for all other installation points, but instead it is recommended to form replication chains that are based on the properties of an installation point.
|
|
Configure installation point reporting and replication settings |
Installation point media reporting schedule determines how often Miradore checks whether the files on the installation point are up-to-date and synchronized with the media master installation point or not. If the files are out-of-date and replication is enabled for the installation point, Miradore will automatically replicate the changed files from the media master installation to the particular installation point. If the replication enabled = No, then the configurations affect only to the installation point reporting.
See Installation point item attributes for field descriptions. |
|
Enable installation point replication. |
Installation point replication duplicates the files from the parent installation point to the installation point in question.
|
|
Make sure that replication is enabled for the whole replication chain |
It is possible that the replication feature is enabled for an installation point, but not for it's parent. Therefore, it is advisable to make sure that the replication is enabled for all installation points that belong to the same replication chain if there are more than two levels in the installation point hierarchy.
Notice that replication can be disabled for a parent installation point if some other method (e.g. Robocopy) is used for performing the replication. |
|
Repeat the steps 2-5 to add more slave installation points to the replication hierarchy. |
Additional installation points can be added to installation point hierarchy by repeating the steps 2-5. |
Related to