Thoughts for Tomorrow's Innovation

Follow Us on

Current Case Studies
Client environment The client is a preeminent global financial services company with presence in more than 100 countries. It provided customers a broad range of financial products and services, such as consumer banking and credit, corporate and investment banking and asset management.
Client Requirement Interruption of services and support to their customers even during uncontrollable events of great severity like, hurricane, total blackout or sabotage could cause serious long term damage to its business and reputation.

We were asked to develop and maintain the business continuity system for its central Europe and Middle East Asia business. This system is functioning on Oracle Enterprise Edition and databases running on Superdome server with HP-Unix 11.11 as Operating System.
Our Solution What was needed was a disaster recovery system that will allow close-to-normal business operations even in case of entire-site-failure. We implemented the setup using Oracle's standby database feature.

Oracle Standby databases were setup at two geographically widely separated locations. This would satisfy the objective of disaster recovery. The standby setup will, in normal times take the load of ad hoc requests (like report generation) away from production setup. We developed shell scripts and UNIX cron daemons which will help a smooth switchover to the DR setup.

Client's security policies mandated a secure transfer of archived redo logs from primary production site to fail-over site since the logs contain very sensitive and confidential business data. We recommended use of Connect Direct for encrypting data over the network. We deployed the Connect Direct and automated the movement of large archive redo logs across the sites. Mock drills were performed to test the reliability of system and every time the disaster recovery system proved itself as a business continuity solution.
Client Benefits In mock drills, our client was able to restore services and support to customers within three hours of total destruction of its primary site. Data recovery time was reduced (from 36 hours) to 3 hours. Confidentiality of data being transferred was ensured.

A fringe benefit was load reduction on production database by diversion of low priority jobs to standby setup.