Active/Active Systems — Why Choose HPE Shadowbase?

Active-Active-Systems-Why-Choose-ShadowbaseHPE Shadowbase technology is a leader in data replication for active/active systems. Its avoidance of disk queuing points makes it fast and highly efficient, able to scale and handle the most demanding workloads. Fast replication means fewer data collisions and less potential data loss following a node failure. Its efficient replication path also means less utilization of computing resources for replication.

Shadowbase software is easy to manage and is itself fault tolerant. Of utmost importance is attention to referential integrity; it ensures that database updates are consistent and correct. Aiding this is Shadowbase technology’s superior capabilities to automatically detect and resolve data collisions.

The Shadowbase high-speed SOLV utility allows an active database to be copied while it is being actively updated. Any portion of the database that has been copied is immediately consistent and correct and can be used for application processing. These utilities simplify the implementation of an active/active architecture, moving either from an existing standalone or active/passive system configuration.

The Shadowbase technology is fully heterogeneous. Its active/active technology can be used on today’s popular systems including UNIX, Linux, and Windows running Oracle, SQL Server, and Sybase databases, as well as HPE NonStop servers using NonStop SQL (/MP and /MX) and Enscribe databases. Nodes in the Shadowbase active/active network can be similar, or completely different. There is no need for each node to be configured the same and to run the same software versions, as Shadowbase handles interconnecting differing versions. Contact us for the availability of additional commercial offerings, such as MySQL and DB2.

In summary, an active/active HPE Shadowbase architecture’s key benefits include:

  • Extremely high system availability with uptimes measured in centuries
  • Only a subset of users, rather than all, affected upon a node failure
  • Restoration of service to users connected to a failed node in seconds
  • Little data loss, if any, as the result of a failure
  • Elimination of planned downtime
  • Greatly improved disaster tolerance
  • Support for dynamic load balancing (expandable)
  • Utilization of all purchased system capacity for productive work (no idle standby systems needed)
  • Elimination of the uncertainty and indecision associated with passive backup systems at takeover time (if the primary fails, will the backup system take over and work properly?)
  • Accomplishment of all these benefits at little or no additional cost

Related Solutions:
Related White Paper:
Related Case Study: