Opalstack - Notice history

Opal14 is back online following the reboot and is operating normally.

The MariaDB recovery on opal9 is complete. Databases with names starting with tro through zzz are being restored from our 2 December 2023 backup.

Our plan now is to test the recovery process on a test server to determine why we were not able to import the dump files and then refine our maintenance procedures based on those findings.

The MariaDB recovery on opal9 is still in progress. We expect the recovery to be complete in around 90 minutes.

The MariaDB recovery on opal7 is complete.

The MariaDB recovery on opal9 is still in progress. We'll update with an ETA as soon as possible.

The MariaDB recovery on opal7 and opal9 is still in progress. We expect that it will take at least a couple of hours more to complete.

The MariaDB recovery on opal7 and opal9 is still in progress. We expect that it will take at least a few more hours to complete.

The MariaDB recovery on opal4 is now complete, however we were not able to use the most recent backup for about 50% of the recovered databases. The remaining databases were recovered as follows:

• Databases with names starting with lsa through shn were restored from our 2 December 2023 backup.
• Databases with names starting with sho through zzz were restored from our 1 December 2023 backup.

It seems some opal4 databases were not restored. We're restoring those databases now.

The recovery on opal7 and opal9 is still in progress.

The MariaDB recovery on opal4 is complete. Recovery on opal7 and opal9 is still in progress.

The database restore is still in progress. We expect that it will take at least a few more hours.

What happened?

We took the MariaDB database down to stop the ibdatafile from growing exponentially. The only way to do this is to dump all databases, delete the log files, update the server configuration, and restore the data.

The dump process worked without any errors. The clean up and server configuration completed without any errors. The restore process is where things failed.

Because of errors in 1 or more database(s) transactions failed to complete causing the restore to never get past a certain point. The amount of data in the mysql data directory would increase up to a certain point and then the data size would drop by half before repeating. After running the restore process twice and having errors in different spots we decided to extract each database from the monolithic backup we had taken previously. Why a monolithic backup? It's usually faster to dump and restore, except in this case.

The extraction process is painfully slow compared to just running a working dump restore. That's why this process is taking so long.

What didn't we do?

We could have restored from the latest backup which would have been 24 hours or less old, however, that option comes with the significant risk of data loss. Rather than risk losing 24 hours of data we went with the slower, safer process.

The current restore process for each server is now past the previous failure point.

We'd sincerely apologize for the downtime this has caused for your apps that use MariaDB. In the tests we performed before the actual event we did not run into any of these errors.

The data restoration process is still ongoing. There is currently no ETA we can provide.

Opal4, Opal7, Opal9: We are still restoring data to the MariaDB databases. The exact amount of time left in the restoration process is unknown but we will update every hour until all of the restores have finished.

Opal3 is back online.