As members would know, CF had a database crash on 25 January caused by the wrong setting in a config file - I fixed it in about 12 hours with no data loss.
Well, I didn't learn my lesson and kept modifying the database config to try to optimize the database so I could put our "find member's posts" feature back in.
It worked but because of the way I recoded things, the database was cacheing a lot of disk writes into RAM, and this caused occasional writes not to be written - leading to another database corruption.
This database corruption affected the WHOLE database - I had to restore our backups 3 times but they ended up being corrupted, and in the end decided to try to fix up the corrupted database. Took about 12 ours again...
Praise God, I fixed it, with minimal or no data loss whatsoever.
So now CF is back.
I promise I won't try to be too smart now. I'll leave things alone!
Well, I didn't learn my lesson and kept modifying the database config to try to optimize the database so I could put our "find member's posts" feature back in.
It worked but because of the way I recoded things, the database was cacheing a lot of disk writes into RAM, and this caused occasional writes not to be written - leading to another database corruption.
This database corruption affected the WHOLE database - I had to restore our backups 3 times but they ended up being corrupted, and in the end decided to try to fix up the corrupted database. Took about 12 ours again...
Praise God, I fixed it, with minimal or no data loss whatsoever.
So now CF is back.
I promise I won't try to be too smart now. I'll leave things alone!