Support #12371
[SCP ID :##5991##] : KFHOnline DR readiness - 11/Oct/2021
| Status: | Closed - End of life cycle | Start date: | September 29, 2021 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zahir Abd Latif | % Done: | 100% | |
| Category: | DR Activity | Spent time: | - | |
| Target version: | - |
Description
Hi,
Kindly attend below request:-
1. 1) KFHOnline DR on 11/Oct/2021 – standby onsite/offsite
2. 2) To ensure that , KFHOnline in DR in good condition .
History
#1
Updated by Zahir Abd Latif almost 3 years ago
- Status changed from New - Begin Life Cycle to Closed - End of life cycle
- Assignee changed from Hafizudin MD to Zahir Abd Latif
- % Done changed from 0 to 100
Hafiz, Mon, 15 Nov :-
Summary as below:
0000 - IT Security disable IB connection from external
0055 - All IB Production services has down
0100 - Backup dB(Daily BAU Process) Completed
0110 - restoring dB to DR Site
0140 - DR DB up
0147 - System Admin start all services IB at DR
0230 - ESB not working
0345 - ESB status is prepare. change status to active
0347 - User started testing
0355 - KFH Online able to login
0401 - KFH Online cannot received TAC
0409 - CMS cannot login kt IB
0610 - SMS - connection sms server to DB success . connection to mk failed.
0620 - SMS - KFH Online - able to send TAC.
0630 - CMS login issue - deploy bib from prod and replace upass config from prod
0700 - epay n jompay issue (Unable to received succesful transactions and loading so long)
0707 - KFH decide to revert back to production
0740 - All services IB prod up
0757 - User started testing at IB prod
0830 - IBG - w1 and w2 used same record because DB DR is not restore to DB prod when w1 execute
1000 - IBG - execute w2 after db has been restore
Conclusion:
DR failed.
Issue and resolutions:
1) KFH online - tac not received - Resolved by allowing connection sms to db and sms to mk
2) CMS - cannot login - Resolved by updating upass.cfg in /bin/ folder and restart jboss
*3) cannot perform JomPAY and ePay transactions - No error in logs, not able to identify the root cause
4) ESB status prepare at console - Resolved by changing status to active
Issue closed in SCP.