Offers stable performance even with a single node failure and manages everything with just two nodes.The only drawback is that it takes a bit of time during initial synchronization, especially after restarting the environment. This is a potential area of improvement. There's a synchronization time, but it takes time. Initially, when we start the first environment deployment, it starts synchronizing between the storage. So, it is taking time. One thing is that even when you restart. Let's assume that the synchronization is completed and the storage is synchronized. Both storages are fully synchronized, and it is in sync mode. Now, if we want to restart both nodes, there is a case for maintenance purposes. You took both nodes for maintenance, and we rebooted it. Then, it should not synchronize again. It should be a checksum. And if there is a checksum match, there should be no synchronization again. So, one thing that should be taken care of. Another thing is that I used freeware- the community version, free license, which we deployed using PowerShare. In that case, it was very difficult to bring back another node when one node was faulty. Let's assume that both the nodes are working fine. And we found one node faulty. And we destroyed all the volumes in that and tried to bring it back. So that was a difficult factor. The final solution is that we were not able to bring back the failed node. So, we reconstructed a new data source for that. That is another drawback. In future releases, I would like to see the integration with VMware or some other things as a plugin model for VMware.
