Sanovi's customised DRM solutions for banking ind

by CXOtoday Staff    Apr 27, 2010

Sanovi Technologies has announced an effective solution for the treasury departments of banks that use Kondor application from Reuters. Kondor from Reuters is a popular application for treasury departments of different banks. By its very nature, a treasury application is a complex implementation, with multiple data bases, multiple application processes on multiple servers and multiple start/stop scripts, using off the shelf host or storage based replication.

Kondor treasury application uses Sybase as its database. The business process requires the use of non-logged operations on the database. Any replication technology that makes use of Sybase transaction logs to replicate data from the primary database to the DR server is not suitable when non-logged operations are in use.
 
Sanovi DR solution for Kondor solves this problem in a unique manner. When normal database operations are in force, Sanovi’s in-built file replication copies the database transaction logs from the primary database to the DR server, where the logs are applied to the DR database.
 
"DR drill is a very manual and people intensive process. With the implementation of Sanovi DRM for the treasury application, the banks are able to implement various kinds of test scenarios. Fail over Drill can be done without shutting down the production server; taking a backup of the DR database before the drill does this. Switch over and switchback drills tests the complete scenario of providing application services from the DR side and then resuming services from the primary site to mimic the scenario where primary comes back after an outage", said Chandra Sekhar Pulamarasetti, founder & CTO, Sanovi Technologies..

Sanovi DRM software is able to detect when non-logged operations on the database commence. The software stops replicating the transaction logs once transaction logs operations are detected. After the completion of non-logged operations, Sanovi DRM makes a complete backup of the primary database. The complete database is copied to the DR server and recovered. All of these operations are completely automated and do not require user intervention.