This is a one-way process. Once the data has been moved to MySQL, there is no process for switching back to the default Hypersonic database. You should only perform the transfer if you are willing to abandon the default database.
Before getting started with the transfer from Hypersonic to MySQL, please follow the ScrumWorks Pro backup procedure.
Please read the MySQL Requirements and Configuration guide before transferring data from Hypersonic to MySQL.
Please note that specific MySQL-related components must be obtained directly from the MySQL web site for licensing reasons. ScrumWorks Pro does not bundle or automatically download MySQL components. For a complete list of needed components, please see the MySQL Requirements section of the documentation.
mysql-transfer.exe.
You can download the mysql-transfer.exe package from the
ScrumWorks Upgrade website.
mysql-transfer.exe. Note that the transfer tool takes some time to start up since it has to extract the files necessary for it to run.
The mysql-transfer.exe program will perform the transfer, create the necessary files, and configure the ScrumWorks Pro Server to run with MySQL.
Note: The transfer process may run for several hours depending on the size of your database.
To abort the transfer process, use CTRL-C
If anything goes wrong with the data transfer, the process will abort and you will have a
scrumworks-transfer.log file. Your existing data has not been modified and it
is safe to restart the ScrumWorks Pro Server with the old database. The scrumworks-transfer.log file may contain relevant information about the reason your transfer failed.
scrumworks-{version}-mysql-transfer.tar.bz2.
You can download the package from the ScrumWorks Upgrade website.
Extract the package:
tar jxvf scrumworks-{version}-mysql-transfer.tar.bz2
Change to the scrumworks-transfer directory:
cd scrumworks-transfer
Run the transfer tool:
./mysql-transfer.sh
The installation will perform the transfer, create the necessary files, and configure the ScrumWorks Pro Server to run with MySQL.
Note: The transfer process may run for several hours depending on the size of your database.
To abort the transfer process, use CTRL-C
If anything goes wrong with the data transfer, the process will abort and you will have a
scrumworks-transfer.log file. Your existing data has not been modified and it
is safe to restart the ScrumWorks Pro Server with the old database. The scrumworks-transfer.log file may contain relevant information about the reason your transfer failed.