HPE Shadowbase A/P uni-directional replication is used for classic disaster recovery configurations. It supports applications that must be highly available but where some small data loss is tolerable. Customer relationship management (CRM) and human resources (HR) corporate applications are examples of this class of application, as are ATM transactions, which have a low value. If the ATM machine is down, the customer can go to a different ATM machine serviced by a different bank.
Solution Brief & Video: HPE Shadowbase Business Continuity Solutions
An HPE Shadowbase asynchronous uni-directional A/P system has a Recovery Point Objective (RPO) of greater than zero (it depends upon the replication latency of the data replication channel). If Shadowbase synchronous replication is used, no data is lost following a source node failure, and an RPO of zero is achieved. The Recovery Time Objective (RTO) of an A/P system is measured in minutes or longer as applications are started following a failure of the active node, the databases are mounted, and the network is reconfigured. Additional recovery time is typically required for the management decision time to failover to the backup system and for testing to ensure that the backup is performing properly.
Figure 1 shows clients posting transactions to an active system, with either Shadowbase synchronous or asynchronous uni-directional data replication keeping the passive, standby, disaster recovery system up-to-date.
In an A/P configuration, the passive system is typically idle as far as update-processing is concerned. However, applications may also be up and running in read-only mode in the standby node, and the standby database may be actively used for query and reporting purposes. Shadowbase replication provides for the target database to be a consistent copy of the source database, though delayed by the replication latency. If the active node fails, the applications at the backup node can remount the database for read/write access and take over the role of the original active node. This process typically takes only a few minutes, leading to RTOs measured in minutes. Therefore, uni-directional architectures provide high availability — RTOs measured in minutes and RPOs measured in subseconds (or zero if synchronous replication is used).