Simplify, enhance, and reduce operational costs of your storage environment with data storage software that works well with the VMware, Citrix, and Microsoft virtualization platforms.
Article
Date: Jan 30, 2017
A Cluster-in-a-Box system houses two servers and a common set of direct attached hard drives within one server enclosure. This system simplifies the physical setup and deployment of a two-node High Availability storage cluster since all necessary connections are pre-configured between the inner components.
Article EOL
Date: Jun 16, 2015
The Avago Syncro™ technology is a solution for businesses of all sizes that require high available storage for high performance, high capacity or hybrid system. The Syncro™ CS solution is a hardware based, high-available DAS which is shared between two head-nodes. In combination with Open-E DSS V7 software, it is possible to create a customized solution for any need, from a high performance SSD storage to high capacity 3,5” HDD server with SDD caching.
Article EOL
Date: Jun 16, 2015
The Avago Syncro™ technology is a solution for businesses of all sizes that require high available storage for high performance, high capacity or hybrid system. The Syncro™ CS solution is a hardware based, high-available DAS which is shared between two head-nodes. In combination with Open-E DSS V7 software, it is possible to create a customized solution for any need, from a high performance SSD storage to high capacity 3,5” HDD server with SDD caching.
Article
Date: Jun 16, 2015
The Failover feature provides High Availability of data. In an iSCSI Failover setup of two servers, data is saved on both servers simultaneously. When one system fails, its processes and all resources are being relocated to and restarted on the second node. The Active-Passive setup allows having all volumes active on one node (the primary node), while the other node has all passive copies and takes over the tasks in case of an emergency (the secondary node). A load-balanced Active-Active Failover on the other hand, doesn’t have a primary or secondary node. It adds extra performance by enabling the user to decide which volumes are active on which node. The failover process is the same, but the servers are able to utilize their full network performance and eliminate the unnecessary cost of idle hardware.
Article
Date: Jun 16, 2015
High Availability through Failover is crucial for many companies. Despite using high-quality hardware and superior connections, still any server can crash, leading to data loss. Providing High Availability can be tricky, but fortunately Open-E DSS V7 is able to work with a second node. It keeps data redundant and when aware of the original node’s failure, the redundant node continues serving clients; effectively replacing the missing node. This process is commonly known as Failover.
Article
Date: Dec 21, 2012
Having a highly available storage is one thing, but what about its overall performance? Learn how you can achieve both, using Open-E DSS V7 with iSCSI Active-Active Feature Pack.
Article EOL
Date: Jul 25, 2011
Failover is an excellent way to implement <strong>High Availability</strong>. It is a work mode that uses two Open-E Data Storage Software V6 servers (primary and secondary). The secondary server, which has a full up-to-date copy of the data, takes over as the file server in the event of a primary server failure.
Article EOL
Date: Jul 25, 2011
High availability is crucial to many applications. Despite using high-quality hardware and superior connection, any node (network, server, storage equipment, etc) is still subject to crashes due to power shortages, communication and equipment faults, fire incidents, maintenance problems or a human factor. These crashes result in a loss of all active connections and data transactions, as well as service termination. The main goal of Failover is to protect company server against such cases.
Article EOL
Date: Jul 25, 2011
Failover Cluster allows multiple computers work together in order to provide high availability of some services. In case of a situation when a node responsible for a service fails, the second one is able to take over this service and prevents from an unexpected downtime.