Closed
Bug 838292
Opened 12 years ago
Closed 12 years ago
Please restore the Mozillians staging database
Categories
(Data & BI Services Team :: DB: MySQL, task)
Data & BI Services Team
DB: MySQL
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hoosteeno, Assigned: scabral)
Details
We pushed a bad migration to staging on Feb 01 2013 06:42:25. Could you restore the Mozillians staging database to sometime earlier that day or late the previous day?
I did not give this an extreme severity, but there are a few of us really hoping that we can get it done today. TIA!
Assignee | ||
Comment 1•12 years ago
|
||
Will start this now, thanx for the heads-up on IRC.
Assignee: server-ops-database → scabral
Assignee | ||
Comment 2•12 years ago
|
||
Imported to the mozillians_stage database. Please verify or reopen as needed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 4•12 years ago
|
||
Can you please drop all tables and re-import the same backup? Tables introduced by the bad migration still exist and are blocking us from pushing to stage.
Thanks!
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 5•12 years ago
|
||
Done. For my records:
[root@dev1.db.phx1 ~]# mysql -e "drop database mozillians_stage; create database mozillians_stage;"
[root@dev1.db.phx1 ~]# mysql mozillians_stage < /home/scabral/mozillians_stage.2013.02.02.sql
[root@dev1.db.phx1 ~]#
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•12 years ago
|
||
will the 2/2/13 backup be early enough? the bad migration was on 2/1...
Assignee | ||
Comment 7•12 years ago
|
||
Just updating with the final info - the 2/2 backup actually is the 1/30 backup - we had a replication problems.
also kudos to :sancus who pointed out that that backup had myisam tables. I fixed the export to have only innodb tables and dropped & reacreated & reimported the data.
All is well!
Updated•11 years ago
|
Product: mozilla.org → Data & BI Services Team
You need to log in
before you can comment on or make changes to this bug.
Description
•