Child pages
  • How to Migrate to Variations 6.0 - New Install

This space has moved to IU's Confluence.
It is located at https://uisapp2.iu.edu/confluence-prd/display/iulV3/

Skip to end of metadata
Go to start of metadata

How to Migrate to Variations 6.0 - New Install

This page covers the special instructions for setting up a new installation of Variations 6.0 server using the content and configuration from a pre-existing Variations 5.0.* server. These instructions assume one of the following:

  1. You can afford to have Variations offline while performing the migration and that you can require users to install new clients. For a more gradual approach to upgrading, see How to Migrate to Variations 6.0 - In Place.
  2. You are moving to new server hardware and can keep the old server running until you've updated everyone's client application.

If you have any questions about or problems with the update process, please email the Variations support list, variations-discuss@lists.sourceforge.net, or if necessary contact Chris Colvard directly (812-856-0026, cjcolvar@indiana.edu).

Important things to note about this migration:

  • The 6.0 server requires 6.0 clients. Previous clients will NOT work with the 6.0 server. 6.0 clients are not compatible with pre-6.0 servers. You will need to migrate your users to the new client at the same time that you migrate to the new server.
  • The old cataloging server's data will be loaded into the new production server. EXAMPLE_CATALOGING will become EXAMPLE.
  • When your migration is complete, you will just have one server rather than two: the cataloging/production split disappears in 6.0. This simplifies Variations setup for new sites and reduces the complexity of managing Variations.
  • 6.0 will run in a subdirectory underneath /home/dmlserv.
  • This upgrade will also move your implementation from MySQL 4 to MySQL 5 and Java 1.4 to Java 1.6, if you haven't moved already.

Important things to backup before attempting to upgrade on the same machine currently running 5.0:

  • Dmlserv's home directory
    • You may want to backup the content directory separately due to its large size:
      • tar cvzf content-backup.tar.gz content/
      • tar cvzf variations-backup.tar.gz bin/ conf/ COPYING data/ lib/ log/ public_html/ server.jar VERSION
    • Do this using the preferred method for your institution
  • Full-system filesystem
    • Do this using the preferred method for your institution
  • All MySQL Databases
    • Run mysqldump -A --allow-keywords --create-options -r dump.sql

Step 1. Preparing Content and Data

  1. Dump databases:
    mysqldump -ntq -r EXAMPLE_CATALOGING.dump.sql EXAMPLE_CATALOGING
    mysqldump -ntq -r DMLLIB.dump.sql DMLLIB
    
  2. Make archives of Variations files to be copied
    tar cvzf content-backup.tar.gz content/
    tar cvzf variations-backup.tar.gz bin/ conf/ COPYING data/ lib/ log/ public_html/ server.jar VERSION
    
  3. If you're reinstalling on the same machine, transfer the database dumps and Variations archives to another system before starting the fresh install of the operating system.

Step 2. OS and Variations Installation

  1. Perform a fresh install of the operating system by following the directions for Server OS and Third Party Software Setup - 6.*.
  2. Create a directory as dmlserv: mkdir /home/dmlserv/old-data
  3. Transfer the database dumps and Variations archive to this new directory and extract the Variations backup: tar xvzf variations-backup.tar.gz
  4. Continue by doing a fresh installation of the Variations server with the directions for Installing the Variations Server Software - 6.*, but stop before the step entitled "Start, stop, and check the Variations Servers," returning to the instructions on this page at that point. When editing configuration files, look at your old configuration files in /home/dmlserv/old-data/ for reference.

Step 3. Loading Data and Content

  1. Copy over your vocabulary files from the old data: cp /home/dmlserv/old-data/data/vocab/* /home/dmlserv/Variations-6.0/data/vocab/
  2. After setting up databases, but before starting Variations, do the following:
    1. Extract content archive in dmlserv's home directory: tar -xvz -C /home/dmlserv -f /home/dmlserv/old-data/content-backup.tar.gz
    2. Create indexes: mysql -u dmlserv library_name_METADATA < /home/dmlserv/Variations-6.0/bin/createMySqlIndex.sql
    3. Load sql dumps:
      mysql -u dmlserv library_name_DMLLIB < /home/dmlserv/old-data/DMLLIB.dump.sql
      mysql -u dmlserv library_name_METADATA < /home/dmlserv/old-data/library_name_CATALOGING.dump.sql
      
    4. Run DB stats update script: mysql -u dmlserv library_name_METADATA < /home/dmlserv/Variations-6.0/bin/runstats-mysql.sql
  3. Start Variations: Variations-6.0/bin/startVariations.sh
  4. Install crontab: crontab Variations-6.0/bin/crontab

What's Next?

At this point, go to the Administrator's Guide and work through the client configuration and building instructions to create a 6.0 client installer. Use the 6.0 client to test the new server.

  • No labels