4.1 Linux to Linux

  1. Disable all archive and deletion jobs and stop Tomcat on the Retain server.

  2. Perform a dump of the database.

  3. Download MySQL onto the new server and un-tar it. Retain only needs the client and the server RPM's, but it is simpler to download one bundle file then two separate files.

  4. Install MySQL and configure the retain database on the new server.

    At this point, you may want to configure MySQL memory allocation in the /etc/my.cnf file. Your retain database uses the innoDB storage engine. The following should be researched and considered:

    innodb_buffer_pool_size
    innodb_innodb_additional_mem_pool_size
    innodb_log_file_size
    innodb_log_buffer_size

    If done correctly, this can enhance the performance of MySQL and Retain. You might want to research this and experiment with those settings to find what works best for your system. OpenText support cannot answer questions about or help customer's with their databases. That is the customer's responsibility.

    If you decide to change the innodb_log_file_size setting, you must take the following steps first:

    1. Log into MySQL: mysql -u root -p

    2. From the MySQL prompt, type: SET GLOBAL innodb_fast_shutdown=0;

      Then type "quit" to log out of MySQL.

    3. Shut down MySQL: rcmysql stop

    4. Rename the ib_logfile0 and ib_logfile1 files.

    5. Edit the /etc/my.cnf and change the logfile size.

    6. Start up MySQL: rcmysql start

      If you do not take these steps when changing the logfile size, MySQL doesn’t load. You can re-enable the innodb_fast_shutdown (...=1) afterwards if there is a need, but average size systems do not seem to experience any significant delay in MySQL shutdowns by leaving fast shutdowns disabled.

  5. Import the dump into the new retain database.

    mysql -u root -p retain < /[path to dump file]/[dump filename] To watch the progress of the import, use this command: watch "mysqladmin -u root -p[mysql root user pw] processlist"

  6. (Optional) Reboot the server to clear the memory. 7. Start up Tomcat and re-enable archive jobs; and if used, re-enable deletion jobs.