Many-to-one topologies should be used only where absolutely necessary. These topologies allow data from multiple nodes to be stored on a single destination node. For example, two or more source nodes replicate to a common backup server.
Consider whether the source nodes should be treated as a cohesive node group rather than individually.
If the source nodes are not functionally related then consider drawing separate data flows for each one; this will allow rules activation/deactivation for each flow to be decoupled.
Note: Many-to-one policies preclude the use of the
Mount operation (for proxy back-up or re-purpose) on a destination
Hitachi Block device. A Mount operation is only valid when one replication is applied to the
destination node.
Figure. Many-to-one data flow
