GOALS AND OBJECTIVES
To optimize and improve the reliability of the automated banking system (ABS).
To separate and migrate operational and analytical data to different storage sites.
- A Parallel Migration Scenarios
- Oracle Certified Master
ABS downtime of no more than three hours could be tolerated, therefore the separation and migration procedure was thoroughly developed and tested several times. During the course of the project, changes were constantly made to application software, and the version of the database itself was radically changed requiring several adjustments to separation and migration mechanisms.
Data separation and migration were performed strictly during dedicated timeslots for technical work. Thanks to this approach, as well as the joint efforts of the bank's developers and Jet Infosystems experts, including Oracle Certified Master, the array reorganization did not affect user work.
Each stage included a plan for rollback to the original state, and migration mechanisms accounted for the relationships between shared databases: small-size tables were migrated in a single stream, while parallel migration scenarios were used for tables of several terabytes. After database division, the complex continues to function as an integral whole, serving all incoming requests just as it did previously.
In addition, the backup time has been significantly reduced, the efficiency of hardware use has increased, data recovery in the event of a failure is now almost eight times faster, and it has become possible to optimize the costs of data storage and systems backup.
Replication of the ABS to the backup site now requires lower bandwidth channels, and analytical data is stored in less expensive, Midrange arrays. This has freed up Hi-End disk space which can therefore be used for further expansion of the bank’s systems.
Size of the entire database
Includes the bank network
Faster is now the data recovery in case of failures
Private clients are served by the bank