How to verify MySQL database?
Hello all,
Could someone from IBM please explain what checks are done to verify a database when Build Forge starts? We are trying to find ways to do "live" backups of a Build Forge MySQL database. Our current implementation uses the following command: mysqldump -u %mysqlUsername% -p%mysqlPassword% -v --single-transaction %mysqlDB% > %backupFileName%.sql But, we have no current way to verify that the resulting file is good and will work if restored to a Build Forge installation. When Build Forge starts, how is it verifying that the database is OK? I've seen some cases where the Build Forge service dies after starting and a system reboot or the restarting of MySQL resolves the issue. So, there are some checks being done to ensure the database is usable by Build Forge. We'd like to find a way to run the same checks as part of backup/restore verification. Thank you, Eric |
5 answers
|
Tap, tap, tap - is this thing on?
IBM has asked us to use this form as a place to ask questions and get answers, but I haven't seen any response. |
Well, here's a response - BF doesn't ask much from its database on startup. The services layer validates every new connection to the database by doing a cheap existence check for the root user and reads in the translated string templates from the bf_strings at startup. I think your problem about service startup is more likely to revolve around mysql's table verification at start rather than something BF does or doesn't need - hard data from the problem you're referencing would go a long way in getting a faster and more definitive answer.
-steve Tap, tap, tap - is this thing on? |
|
Thanks Steve,
What we are looking for is a way to reproduce exactly what Build Forge does at startup to verify a database. We need to integrate this process into our daily database verification process and need to ensure that a backup would pass Build Forge validation. Thanks, Eric |
Thanks Steve, the validation query steve is referring to is "SELECT bf_id FROM bf_users WHERE bf_id='1'" there isn't any validation of data on startup. we leave that to the database. all the data is written transactionally, and there are data constraints in place. If you'd like to discuss automated install of buildforge as part of your backup verification process, I'd be happy to discuss our build verification process with you. At the 10K foot level, it breaks off a copy of a VM template that has mysql server installed, does an automated install of BF, and then manipulates the UI to make sure it all still works as it should. You might want to look into that kind of process in your backup validation. |
Depending on your license, what about pointing another console at your
backed up DB as a validation test? BF doesn't take very long to install if it doesn't have to create the schema. With a little bit of help from a test tool like Selenium and a valid response file the whole validation could be fairly easily automated. Regards, K --
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.