After adding a remote DMA (DMP) we need to create replicated elements to display the data from the remote site on the DMS.
You can however also create replicated elements from a DMA that has not been added as a remote DMA (DMP).
I know of one advantage for adding the DMA as a remote DMA. When it's added as a remote DMA, and you do an upgrade the cluster, the remote DMA will also be upgraded.
Is this the only reason for adding a remote DMA to the cluster, or are there other advantages?
In that light, is the only difference between a DMP and a DMA the number of licensed elements?
Hi Jeroen, by adding a DMP in System Center, you get visibility on 'linked' DMPs, but main advantage is that you can manage these from a central point (e.g. upgrade action as you mentioned).
What's the difference between DMA and DMP? DMP stands for DataMiner Probe. It’s a stand-alone limited functionality unit, typically installed at remote sites (such as transmitter sites). It serves then as an interface between the local managed devices and the central DataMiner System. DataMiner Probes enable operators to bring the power and intelligence of DataMiner to the most remote and isolated locations, and to embed intelligent self-sustaining network management pockets within the operation.
DMP and DMA licenses are a lot similar, providing many of the same features, however DMPs present some limitations when compared to DMAs: e.g. cannot be integrated in the DMS cluster, limited capacity licenses, …
Replication functionality will manage the buffering in case of connection loss. I don’t expect different behavior in case of DMP-DMA or DMA-DMA.
Is the DMP capable of buffering data in case the link with the destination DataMiner system gets interrupted? If so, is this also possible with regular replication, using a standard DMA at the remote site?