Migrate from Legacy to MySQL for Webserve service

On this page:


Overview

Notes:
  • The legacy MySQL server was shut down August 1, 2018, and you can no longer manually migrate your legacy MySQL schemas. If you still need your data, the group account owner will need to create a MySQL for Webserve account, and then contact Web Services Support sct2@iu.edu for more information about their data recovery options. Both the account creation and email must come from the account owner.
  • The term 'database' has been changed to 'schema' in new versions of MySQL. Although 'database' and 'schema' can be used interchangeably, the term 'database' will be phased out by developers. To reduce confusion and maintain continuity with documentation hosted at IU and elsewhere, this document and future MySQL documents will use the new term exclusively.

The MySQL for Webserve service at Indiana University is designed to provide better MySQL support for Webserve users and eliminate the need for individual administration of MySQL database instances. IU group account owners can create and manage MySQL accounts automatically and get nearly instant access to the new environment.

The migration process takes place from the new environment using stored procedures that were developed for that purpose. It is imperative that users be familiar with how the new environment works and what tools are available for data and user management.

For more about the MySQL for Webserve environment, including recommended connection methods and guidelines using stored procedures, see:

Note:

WordPress users:

For help navigating the special challenges you will face in this migration, see Migrate your Legacy MySQL-based WordPress site to New MySQL.

You may need to familiarize yourself with your site's code and identify any MySQL connection strings as well as schema (database) names and users that may exist in your chosen schema. Webserve administrators have created a shell script you can run via SSH in Webserve and Webtest to find code references in your site to the Legacy MySQL for Webserve service. To use this script, run the following command at the prompt:

  show_mylegacy_refs
Note:
For best results, you may need to run this command from the www and wwws folders.

This command will return a list of all files and locations where the Legacy MySQL for Webserve servers are referenced in your site's code. Review all the indicated files for updates you need to make to successfully migrate to the new environment.

For instructions on SSHing into Webserve using the most common clients, see:

You should also be aware of the following:

  • All your current schemas will be renamed according to the new prefix_schema naming convention, where prefix is the name of your group account. For more, see MySQL for Webserve account naming conventions.
  • The names of users will also need to conform to the new prefix_suffix naming convention. If the new user name is longer than 32 characters, it will be shortened. The new name is provided in the output of migrationGetSchemaInfo API procedure.

Reconnect a WordPress site

Note:
Until you edit your wp-config file, your site will be inaccessible.

After your WordPress schema has been migrated, you will need to need to edit your wp-config.php file:

  1. Choose an SFTP client such as WinSCP or Cyberduck.
  2. In the editing, you will need to change your DB_Name to yourGroupName_dbnameYouPreviouslyUsedforWP.
  3. Change your DB_USER to yourGroupName_PreviousDbUsername.
  4. Change your DB_HOST to mysql-test.uits.iu.edu:3306 (Test) or mysql.uits.iu.edu:3306 (Production).
  5. Save changes to the server.

This is document apjp in the Knowledge Base.
Last modified on 2018-08-15 09:10:33.

Contact us

For help or to comment, email the UITS Support Center.