Versant Asynchronous Replication (VAR) add-on module for Versant Object Database supports both master-slave and peer-to-peer asynchronous replication between multiple object servers. This can be used to replicate data to a distributed recovery site or to replicate data between multiple local object servers for increased performance and reliability.
In many applications, there is a need to replicate data, typically to improve availability, to improve performance by geographically co-locating databases with the applications that access the databases, to isolate decision support systems from online production systems, and to help in recovery from failures using warm-standby systems.
Replication can be achieved in two ways - synchronous, where consistency of data between replicas is strictly maintained, and asynchronous, where data consistency is loosely maintained. Synchronous replication increases the duration of application transactions and cannot be completed until all the replicas have been brought to the same state. Asynchronous replication does not prolong the transaction much, as it updates the replicas in a separate transaction from the application transaction. Therefore, asynchronous replication is most suitable where certain latency before achieving consistency among replicas is permissible.
The add-on module Versant Asynchronous Replication provides two modes of replication for Versant Object Database, Default and Advanced.
The Default mode uses Versant APIs for replication and supports only Master-Slave configuration. This mode is suitable for LAN and WAN based replication where network is fast and reliable.
The Advanced mode provides snapshot-based replication and supports peer-to-peer and Master-Slave configurations. This mode is suitable for WAN based replication where the network is slow and unreliable. The Advanced mode provides customizable messaging, transport mechanism and conflict detection and resolution.
Versant Asynchronous Replication offers the following core features that are provided by Default as well as Advanced mode:
The architecture allows for various Master-Slave configurations such as:
Objects created using any of the Versant language interfaces, that is, C++/Versant, J/Versant or C/Versant, can be replicated to and from Versant databases.
Databases can be partitioned logically for replication. The partitioning is based on a class, a set of classes, a set of objects, or a predicated extent of a class that is specified using a query.
Objects that have been created, modified or deleted are replicated. Versant event notification is used to register the updates, deletions and create events on classes of objects specified by the user. An event daemon in the database at each site monitors changes and creates requests for replication.
With batch replication, objects changed in a batch of user transactions are replicated in a single replication transaction. Irrespective of whether a replication is transactional or batch based only the part of the transaction that is of interest to that site is applied at the receiving site.
Two methods are provided for automatic or explicit replication. The first method uses Versant event notification to monitor updates to database objects, and automatically creates replication requests. The set of objects to be monitored can be specified in various ways. In the second method, applications use Java or C++ API to create replication requests explicitly.
The second method, therefore, has more control over specifying the set of objects to be replicated and the timing of replication.
All the objects representing meta data used by Versant Asynchronous Replication are stored persistently to facilitate recovery and synchronization after network or machine failures.
The product includes a set of command line utilities to help administer the replication sites and to check and fix corrupted meta data.
Logging facility is provided to report errors and status of replication. To preserve application events, events are raised irrespective of whether the updates occurred due to replication from other sites or due to an application. However, it is guaranteed that changes are replicated only once to all the target sites.
Besides supporting different Master-Slave configurations, Advanced replication supports N-way peer-to-peer or symmetric replication with mechanisms for update conflict detection and resolution.
You can avoid update conflicts by allowing changes to objects to occur at a single designated site. In applications where this restriction cannot be supported, Versant Asynchronous Replication allows update conflicts to be detected and resolved. In order to detect update conflicts, an administrator can assign ownership of database objects to primary sites. Updates made to objects at non-primary sites are propagated to the primary site for replication. The primary site is then a single point where update conflicts can be detected and resolved regardless of where the update actually occurred. The target sites receive their updates only from the owner site. Versant Asynchronous Replication provides a default mechanism for detecting conflicts. You can optionally customize the detection and resolution of conflicts by implementing the interfaces specified for conflict detection and resolution.
Mechanisms are provided for preventing conflicts by synchronously replicating to the owner sites, from where replication is carried out asynchronously to the other sites. Conflict avoidance is supported by enabling the administrator to assign ownership of database objects to their primary sites, and avoiding updates to those objects at the other sites.
Interfaces are provided to customize the transport mechanism used. Default implementation uses Java sockets. Versant connections are not used to communicate from one site to another. The default supports replication over a LAN as well as a WAN.
Message formats can be customized to support replication of parts of database objects instead of replicating objects (Java-serialized) in their entirety as default.
In Explicit mode, replication operates in two states, active and passive. In active state, replication requests are only consolidated without actually replicating the data. Whenever the state is changed from active to passive, objects specified by the consolidated requests are replicated first and then processing of replication requests is started.
Technische Fragen:
Developer Center Message Boards
Preisanfragen:
Versant Object Database
FastObjects .NET
Allgemeine Fragen:
Quick Message Form
Für Hausadressen, e-Mail-Adressen, Wegbeschreibungen etc:
Kostenlose 60-Tage-Test-Vollversionen: Jetzt die Versant Object Database oder FastObjects .NET testen! Downloads sind im Versant Developer Center verfügbar:
Using Versant Vitness provides you with a basic tool for all fundamental administration operations and decisions.
In today's fast paced world you want to be part of a company that is on the leading edge of technology? Join Versant!
The Versant Developer Center (VDC) provides all the essential information and valuable resources needed for developers, just like
Database Company supports Masters students enrolling in Databases / Information Systems through 2-year Scholarship
www.versant.com | Copyright © 2003-2008 Versant Corp. All rights reserved.
For questions about this site please contact webmaster@versant.com
Versant, Vitness, Vorkout, Vildcard, Vhistle, Vhisper, Varehouse, Vedding, reVind and FastObjects are either registered trademarks or trademarks of Versant Corporation in the United States and/or other countries. All other products might be a registered trademark or trademark of their respective company in the United States and/or other countries.
Add-on Modules for the Versant Object Database.
If mission critical deployments are a part of your business or if you need to access data through SQL, Versant provides Enterprise-class Add-on Modules for the Versant Object Database.
The observation of a production system is a cornerstone to the proper establishment of an adequate System & Network Management policy.
Using Versant Vitness for the advanced monitoring of your entire Versant Object Database environment provides you with a fundamental tool for all database administration operations and decisions.
The Vitness add-on module delivers real-time views of performance data and analytical information about the Versant Object Database at the push of a button. Proactive database monitoring prevents potential faults that could be unexpectedly generated by an unobserved system - Versant Vitness alerts administrators before database availability is affected. Can life get any easier?
Versant Vorkout is a Database Reorganizer Tool for applications that delete large numbers of objects. It lets you reclaim unused space in your database while it is in normal operation, increasing available free space and improving database performance. Last but not least Vorkout is tightly integrated and can be used through Versant Vitness.
Over time as objects grow or are deleted, empty holes are created in the tightly packed database resulting in fragmentation of data segments. Thus, performance starts degrading and disk usage is also increased.
Versant has addressed this issue by introducing Vorkout - the enhanced tool provides the user the ability to analyze a database for wasted space and reorganizes the data for reduced fragmentation and restored performance.
Vedding is an add-on software module for the Versant Object Database enabling automatic fail-over and recovery in the case of hardware or software failure. This is commonly known as a Fault Tolerance environment.
Vedding uses synchronous replication between two database instances and supports transparent re-synchronization in the event of a failure. Synchronous database replication mirrors the contents of one database to another in a predictable and orderly manner. This provides either local or geographically remote redundancy, which protects against the unavailability of data.
The Vhistle add-on module for Asynchronous Replication supports both master-slave and peer-to-peer asynchronous replication between multiple Versant Object Database servers. This can be used to replicate data to a distributed recovery site or to replicate data between multiple local object servers for increased performance and reliability.
In many applications, there is a need to replicate data, typically to improve availability, to improve performance by geographically co-locating databases with the applications that access the databases, to isolate decision support systems from online production systems, and to help in recovery from failures using warm-standby systems.
Vhisper provides Warm Standby capabilities to a Versant Object Database. The add-on module is used as an incremental rollforward recovery. It is designed to minimize the downtime in an emergency event.
With Vhisper, an up-to-date copy of the primary database is maintained - this is a Warm Standby database. In case of an emergency, the Vhisper's Warm Standby database can be updated very quickly to the state of the primary database. Instead of starting a full database restore that may take a considerable time with large databases, you just need to apply the last roll forward archive plus the logical.log of the primary database to the Warm Standby database - and you are ready for anything.
Varehouse is an add-on software module that enables the Versant Object Database to use the disk mirroring features of EMC Symmetrix or other enterprise storage systems to take an online backup of very large data volumes without impacting availability (High Availability Backup, HAbackup).
Varehouse, Versant's High Availability Backup solution, is a generic way of achieving continuous online backup of the Versant Object Database. It exploits the capabilities of special storage devices. It allows the user to execute certain operations such as, splitting a mirrored device, after bringing the database to a consistent state.
Vildcard enables you to run a discounted standby server in parallel to your initial Versant Object Database server.
Most likely, Vildcard is used for generic cold standby environments where backups are accomplished manually in certain periods.
reVind is an Add-on module for the Versant Object Database. The Versant/SQL suite of software modules permits you to use conventional Structured Query Language (SQL) semantics to access data that resides in a Versant Object Database.
The resulting application architecture can offer the strengths of both the relational and the object database models, such as the openness and interconnectivity of relational tables along with the expressiveness and performance of object collections.