Scribd
Upload
13 views2 pages

Incident Report

An incident occurred on July 10, 2019, involving the accidental restoration of a live database which resulted in the loss of data from the DRS and MRF projects. The MHS team collaborated with Edotco's IT team to recover the lost data, ultimately deciding to manually import backdated data to minimize risks. By July 13, 2019, the data entry was completed and the live database was restored to normal functionality.

Uploaded by

Yethu Aung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views2 pages

Incident Report

An incident occurred on July 10, 2019, involving the accidental restoration of a live database which resulted in the loss of data from the DRS and MRF projects. The MHS team collaborated with Edotco's IT team to recover the lost data, ultimately deciding to manually import backdated data to minimize risks. By July 13, 2019, the data entry was completed and the live database was restored to normal functionality.

Uploaded by

Yethu Aung
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Incident Report

Project Title: Edotco Myanmar


Incident Date: July-10-2019
Incident Time: 4 PM

Date: July-10-2019 (Morning)


Since before the live database was incidentally restored , the developer requested the testing
database to IT team because DRS project was needed to test after files have uploaded to server
by FileZilla software.

Date: July-10-2019 3:40 PM


IT team told the developer that you can use and create test database in live server.

Date: July-10-2019 3:45 PM


Firstly, it was created as “test_drs” database in live server and then selected this database that
exported data were last two weeks ago. At that time “drs” database data were incidentally lost
about two weeks because of sql file has already included host IP address and same name with
live server database.

Date: July-10-2019 4:00 PM


DRS and MRF’s data have been incidentally restored last two weeks ago.

Date: July-10-2019 5:00 PM


MHS’s Project Manager arrived at Edotco. MHS team discussed and researched to do the recover
state with IT team.

Date: July-10-2019 8:00 PM


MHS team got Rollout and Operation Stock Movement Excel sheet and also discussed MRF table
structure. The developer thought that how to insert this data. IT team would stop the live server for
maintenance on July 11 .

Date: July-11-2019 (Morning)


It had two ways to restore the data. The First one is to write backend SQL code and the second
one is to import backdate data manually from backend interface records by records. MHS team
discussed with Edotco’s IT Team to make actions. They decided to choose second option for the
low risks.
Date: July-11-2019 (Afternoon)
MHS team started data entry in the afternoon. At the first, focus on Operation Stock Movement’s
data. It is about 40 records. The MHS team added the data in local database because it was
needed to change previous date. After finished the data entry, it also need to import from local
database to live database.

Date: July-11-2019 (Evening)


MHS team stopped data entry for Operation Stock Movement because there is no stock for one
item, so MHS team started to add Rollout Movement transaction. It is about 200 records. This data
entry is too long to finish one record because rollout movement form must choose project
reference which is too many data in dropdown when user chose this ref code, it took around 1 min.
And also needed to import Inventory on Hand for Operation, Inventory on Hand for Rollout and
Site Info, so MHS team requested to Mrs. Yu Myat and received these excel sheets.

Date: July-11-2019 (Night)


MHS team also stopped data entry for Rollout Stock Movement because there has no stock for
items. They are trying to import rollout stock, operation stock and site info but it isn’t working.
Former developer added SQL trigger code in database. When Edotco’s IT team exported
database backup, it didn’t include SQL triggers. But they received this code back from former
developer at 9 PM. MHS team continued data entry at around 1 AM and finished half of data for
Rollout Stock Movement. After that MHS team tried to export data from local server and import to
live server. When they import data file to live server, faced some problems also. This was table
name upper case and lower case issue. The developer had resolved this issue at that night.

Date: July-12-2019 (Morning)


MHS team started data entry again and faced TDMS(DRS) document file name error and also
mismatch with DRS file name in both document and file tables.

Date: July-12-2019 (Afternoon/Evening/Night)

MHS team put the data entry for Rollout Stock Movement at 7 o’ clock. If they need Project Ref
and Stock on Hand, need to add and import that data to database.

Date: July-13-2019 (Morning/Afternoon)


MHS team continue to put the data entry parallel by four people.

Date: July-13-2019 (Evening)


MHS team had finished data entry at around at 4 PM and started to import the live database.
The live server was back to normal state at 6 PM.

You might also like