![Hitachi HiCommand Replication Monitor [EOL] vs. NetApp SnapMirror report](https://www.peerspot.com/assets/media/images/icons/pdf-c33db68f.svg){kind=icon}
![Hitachi HiCommand Replication Monitor [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_64/oz2tnjdteedru28f6d6m695iggdh.jpeg?_a=BACAGSGT)
![Hitachi HiCommand Replication Monitor [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_30/oz2tnjdteedru28f6d6m695iggdh.jpeg?_a=BACAGSGT){kind=small}
![Hitachi HiCommand Replication Monitor [EOL] Logo](https://images.peerspot.com/image/upload/c_scale,dpr_3.0,f_auto,q_100,w_40/oz2tnjdteedru28f6d6m695iggdh.jpeg?_a=BACAGSGT){kind=small}
The features of NetApp SnapMirror that I have found most valuable include the possibility to stop synchronization in case of high network latency and to limit the bandwidth throttle. This means limiting bandwidth when less connectivity occurs or opening wide the throttling to use the full speed of network connectivity, which we can adjust according to our needs or the needs of our customers. All of this is done without limiting business continuity, so business continuity is always guaranteed. NetApp SnapMirror's data replication feature supports disaster recovery strategies, as it is incorporated into the business continuity feature. SnapMirror is strictly related to snapshot features, a core part of ONTAP, so it's very flexible. It allows us to start with just two snapshots as a simple backup and then use them as a replication point or base for both backup and business continuity. There is no right or wrong answer, it just depends on how it works for specific needs.
