In an online meeting on December 21, 2023, representatives from CS and Ukrainian banks discussed the specifics of working with the 'Archiving Policies' module.
Bank databases require significant disk space to store information from the CBS B2. Large tables are filled daily with substantial amounts of data, which over time lose their relevance but still require storage space, affecting system performance and increasing the time needed for end-of-day (EOD) processes.
The 'Archiving Policies' module addresses this issue by defining a set of rules and automating the archiving (transferring to a separate server or storage medium) or deletion of data that has lost its relevance.
The implementation of the module is always accompanied by collaborative work between CS specialists and the bank on preliminary analysis and identifying the unique features of the specific institution's database. Priority archiving policies and the bank's needs are determined, and requirements for the depth of archiving and data deletion are agreed upon.
At the meeting, Sergey Belozorov, a representative from Sense Bank, shared his experience with implementing the 'Archiving Policies' module at Sense Bank. He discussed the nuances of preliminary preparation and the phased implementation. Sergey highlighted that the bank aimed not only to launch archiving policies per se but also to ensure timely archiving of all accumulated outdated data. Both objectives were successfully achieved.
Serhiy Belozyorov, Director of the Department for the Development of Centralized Information Systems of the Information Technology Block at Sense Bank:
'By implementing archiving policies, we have freed up 25 terabytes in the productive environment of the B2 ABS system. We are saving on database sizes and servers. We see savings in infrastructure, and we also notice improvements in performance. Reducing the database size positively impacts the system's overall performance.'
The practical experience of using the module at Sense Bank was also discussed during the question and answer session. Representatives from other banks showed interest in specific cases where data recovery was required, as well as the nuances of setting the depth of archiving.
The CS team has already developed 38 active policies for different entities, such as change logs of documents, reserves, account balances, etc.
Six of these, used for clearing logs and journals, can be utilized by banks on a free basis. In this case, journal information is deleted and is not recoverable. These policies are only executed synchronously, as part of end-of-day (EOD) task procedures.
The paid functionality of the module allows a bank to use all developed archiving policies and choose between manual, EOD, and automatic launching in asynchronous mode at a specified time. In this case, the archived data can be restored.
For additional materials and individual consultation regarding the 'Archiving Policies' module, please send your inquiry to the following email address: [email protected].
(all fields are required)
We will be in touch shortly to continue the conversation.
Thank you for your interest!