mistakenly deleted database but recovery takes time while the company is still running -
my friend mistakenly added update clause , changed company's database. thing backup everyday @ time. trying recover. recovery takes several hours, , company still producing products , running 24/7 has run production table/database (probably understanding?) current use during recovery time. problem is, during recovery hours new data still being produced. after recovery finishes, how deal these new data during these several hours?
i not know if such kind of questions can asked here. story happens friend in non english country, country without site him ask here. worried.
do guys have basic thought or idea it? wonder normal solution since imagine kind of things might happen in modern life sometimes.
update: told me company produces important things , shutting down several hours cause huge loss
even though questions seems broad still try answer it.
determine how many tables affected
for each table determine records changed , columns changed
determine if current transactions, stored procedures , functions or other software has changed of records/rows step 2. , how being run (they might changing records read this)
determine if operations step 3 inconsisten because of changes made incorret update. (money or other calculation comes mind)
after should able determine if best keep running database altered incorrectly , allow user , other sofware continue updating records after manually altered or if best let people know urgent maintenance needed, agree them on maintenance window , fix problem before updated records , information propagated , used take importan decisions
my personal advice. determine plan recover affected data point in time records made sense , try re-run transactions happend after exact moment. try determine how time take , agree on urgent maintenance window users , other software might acceess database.
a database set maintenance mode, no users or other software can acccess it, runs faster , allows recover or undo damage faster if try keep accesable user , fix damaged records.
other approach be..(even if not sound professional)...let time pass , if no user complains updated records old or not accesed or important user, case , is best accept , fix problem "hoping best"
i have "reposted" question on serverfault
Comments
Post a Comment