Jump to category:

How to move a Daisy installation to another machine?

[ This article applies from Daisy version 2.0 to version any ]

Just as a reminder, Daisy keeps application and data completely separated, so you have:

  1. The Daisy application
  2. Your Daisy data, which is spread over:
    1. the repository data directory
    2. the MySQL databases: for the Daisy repository and the ActiveMQ system
    3. the wiki data directory

See the Daisy installation instructions for a nice figure showing all this.

Steps to move Daisy

0. Stop Daisy on the old machine

1. Put the Daisy application on the target machine

You can either copy the Daisy installation directory from the current machine or download the Daisy archive again. In the last case, use the same Daisy version (see notes below) and do not use the Windows installer (see notes below). Just extract the archive.

If Java is not yet installed on the target machine (try executing java -version), do so.

2. Copy the data directories

Copy the repository data directory and the wiki data directory to the target machines. You will probably want to zip them to move them over as that will be more efficient and less error-prone.

3. Move the MySQL data

If necessary, install MySQL on the target machine.

Move over the daisyrepository and activemq databases. This can be done using the mysqldump and mysql commands.

(on the source machine)
mysqldump -uroot daisyrepository > daisyrepository.sql
mysqldump -uroot activemq > activemq.sql

(on the target machine)
mysqladmin -uroot create daisyrepository
mysql -uroot daisyrepository < daisyrepository.sql
mysqladmin -uroot create activemq
mysql -uroot activemq < activemq.sql

On the target machine, create the necessary access grants. For this, start the mysql tool on the command line:

mysql -uroot

And execute (change the statements accordingly if you did not use the default passwords, you can find the passwords Daisy expects in the myconfig.xml file located the repository data directory):

GRANT ALL ON daisyrepository.* TO daisy@'%' IDENTIFIED BY 'daisy';
GRANT ALL ON daisyrepository.* TO daisy@localhost IDENTIFIED BY 'daisy';
GRANT ALL ON activemq.* TO activemq@'%' IDENTIFIED BY 'activemq';
GRANT ALL ON activemq.* TO activemq@localhost IDENTIFIED BY 'activemq';

4. Start Daisy on the target machine and verify it all runs

See the Daisy documentation.


Do not try to upgrade Daisy as part of the move

Moving Daisy to another machine and performing a Daisy upgrade are two different tasks. If you want to upgrade Daisy, either do it before the move or after the move.

Verify that the task at hand (either the upgrade or the move) succeeded before moving on to the next task.

Do not run the installation utilities or the Windows installer on the target machine

Daisy does not require any real installation, the application is runnable just by extracting the zip or tar.gz file. What the installation utilities (or the automated Windows installer) does additionally is initializing a data set. In the case of moving Daisy, you have already a data set, so you don't need to create a fresh one. It will only get in your way and complicate things.