In today’s business world, consistent access to real-time, online transactional data is a competitive advantage. To realize this advantage, this data must be current and available across the enterprise at all times. Otherwise, the inability to access or update, or the loss of this data carries significant potential business cost: up to thousands of dollars per second loss of brand reputation, regulatory fines, and other unforeseen consequences that could be prevented.
Solution Brief: Shadowbase Zero Data Loss (ZDL)
Figure 1 states the numerous costs per hour of downtime by industry (in USD): healthcare $636K, retail $1.1M, financial $1.5M, manufacturing $1.6M, and communications/media/entertainment $2M, with the average of $1.4M. In some cases, absolutely no data loss can be tolerated:
|Table 1 — Estimated Cost of Lost Data Across Various Industries in USD
(i.e., 500 transactions per second)
|Technology Architecture||Recovery Point Objective||Retail||Credit/Debit Card||EFT||Stock Trade|
|Active/Passive and Sizzling-Hot-Takeover5||~1 sec||$47.5K||$35.6K||$688K||$31.6M|
|Average Transaction Value||N/A||~$95
2Source: European Central Bank
3Source: Canadian Payments Association
4Source: London Stock Exchange
Most other data replication software uses asynchronous replication that leads to the possibility of data loss for unplanned outages. For this reason, companies must consider a zero data loss solution to protect their invaluable data. Shadowbase ZDL guarantees that all committed data changes made on one system are replicated to a backup system. Therefore, unplanned system outages never result in lost data, and the business will never face these costs or the headache of trying to recover lost data.
Shadowbase ZDL uses synchronous replication, which avoids data loss for active/passive architectures, and eliminates all possibility of data loss, as explained in these definitions:
Shadowbase ZDL support for active/active architectures is called Shadowbase ZDL+ and will be available in a future release. In active/active architectures, data collisions can occur when using asynchronous replication. By their very nature, active/active architectures run multiple application copies, with each application maintaining its own database copy. If two requests are routed to different application environments for processing, and they both act on the same account’s data, different values may result in each database. This result is referred to as a data collision. Data collisions cannot arise when using Shadowbase ZDL+ because the replication engine automatically avoids them.
Table 2 compares the benefits of synchronous replication to asynchronous replication.
|Table 2 — The Benefits of Synchronous Replication by Replication Mode|
|Attribute||Asynchronous Active/Passive||Synchronous Active/Passive||Asynchronous Sizzling-Hot-Takeover||Synchronous Sizzling-Hot-Takeover||Asynchronous Active/Active||Synchronous Active/Active|
|Data Collisions||Not possible||Not possible||Not possible||Not possible||Possible||Not possible4|
|Data/Request Partitioning||Not required2||Not required2||Not required||Not required||Possible||Not possible|
|1All users affected, but takeover time is the same as Active/Active modes.
2“Required” if run in Reciprocal Mode. (Reciprocal Mode allows each system to be active for a separate data set.)
3“Yes” if run Reciprocal Mode.
4By using ZDL+. Collisions may be avoided in both asynchronous and synchronous architectures by using a partitioned database or data dependent routing.
Use Shadowbase ZDL to significantly reduce outage costs by avoiding any data loss, eliminating data collisions (ZDL+), and applying active/active architecture benefits to any application. Shadowbase ZDL is the pinnacle of replication solutions for business continuity and data integration, providing the ultimate protection level against unplanned service outage costs.
Specifications are subject to change without notice, and delivery dates/timeframes are not guaranteed. Purchasing decisions should not be made based on this material without first verifying that the desired features are available on the desired platforms and environments.