Difference between revisions of "ITrack/Migrating a server"

From ISoft Wiki
Jump to navigationJump to search
 
(27 intermediate revisions by 6 users not shown)
Line 3: Line 3:
*To stop the MySQL service from the command line: '''net stop mysql''' or '''net stop mysql5'''
*To stop the MySQL service from the command line: '''net stop mysql''' or '''net stop mysql5'''


'''Note:''' Before making the switch, warn customer/users that ITrack will not work while the move is happening.
'''Note:''' Before making the switch, warn customer/users that ITrack will not work while the migration is happening.
 


==Server Side==
==Server Side==
===Preferred Method===
This walk-through requires [http://en.wikipedia.org/wiki/Sqlyog SQLyog].  Alternatively, you can use the MySQL command line utility if you're that 1337.
#Use SQLyog create a dump of the users ITrack database
##Right click on the database in the left pane and select '''"Backup database as SQL dump"'''
##Make sure the '''"Structure and data"''' [[ITrack/Control Types#Radio_Button|radio]] is selected
##Make sure the '''Include "USE database" statement''' and '''Include "CREATE database" statement''' check-boxes are checked.
##Click export
#Copy the .sql file to the new server
#Install MySQL on the new server
#Import the .sql dump script with SQLyog
##Select '''Tools''' from the top menu
##Choose '''Restore from SQL dump'''
#Check the results, make sure it imported properly
===2nd Method===
*Note: This method is not recommended and should only be used if you can't use the 1st method.
#Stop the MySQL service on the "old ITrack server"
#Stop the MySQL service on the "old ITrack server"
#Set it to not start on "automatically"
#Create a share on the old ITrack server
#Create a share on the old ITrack server
#Copy the ITrack database from '''C:\Program Files\MySQL\MySQL Server 5.0\data''' to the share you just created
#Copy the ITrack database from '''C:\Program Files\MySQL\MySQL Server 5.0\data''' to the share you just created
##('''Be careful''' to make sure you have the correct data. If the customer still has MySQL version 4 installed then it will be in the MySQL directory, but if the customer has MySQL version 5 then the data will be in a sub-directory called MySQL 5.0; otherwise you might delete their up-to-date database and only have the crappy old outdated one to work with)
#On the new ITrack server, install MySQL server
#On the new ITrack server, install MySQL server
##If you are doing a MySQL reinstall then you may need to uninstall MySQL a few times. It's a little silly, but just because you uninstall the service, the regular files may not have been removed (or vice versa).
#Stop the MySQL service on the new server
#Stop the MySQL service on the new server
#Use explorer to navigate to the share on the old server
#Use explorer to navigate to the share on the old server
Line 16: Line 36:
#Start the MySQL service on the new server.
#Start the MySQL service on the new server.
#Install SQLYog
#Install SQLYog
===Additional Server Changes===
#Create a new user in the mysql database that ITrack will use to connect to the server
#Create a new user in the mysql database that ITrack will use to connect to the server
#Change all client machines to be pointed to the new server's name/IP
#Create an ITrack share on the new server, make sure the "Everyone" group has read and write privileges(for images and attachments).
#Create an ITrack share on the new server, make sure "everyone" has read and write privileges(for images and attachments).
#Move the reports, images, attachments directories from the old server to the share on the new server
#Move the reports, images, attachments directories from the old server to the share on the new server
#On the old server, set its MySQL service to not start on "automatically"
#Set the Replikwando Service on the old server to "Disabled" and make sure it's not still running.
#Disable the Windows Scheduled Task for Image Synch.


==Client Side==
==Client Side==
#Change the "hostname" in all clients host.ini to be the name/IP of the new server.
#Change the "hostname" in all clients host.ini to be the name/IP of the new server.
#Change the "server" in the ODBC to the name/IP of the new server.
#Change the "server" in the ODBC to the name/IP of the new server.
#Change the reports, images, attachments to point to the share on the new server.
#''Change the reports, images, attachments to point to the share on the new server.'' (This should no longer be necessary after database images.)
#Double check to make sure everything is working properly.
#Double check with the customer to make sure everything is working properly.
 
== To consider with older Operating Systems ==
Windows Server 2003: MySQL 5.6.22 is the highest compatible MySQL version with this OS
[https://bugs.mysql.com/bug.php?id=80399 https://bugs.mysql.com/bug.php?id=80399]
 
On Big 3, we encountered a situation where Symantec was half-installed on their system, causing it to try to install the software any time the user right-clicked an icon. We found this article to fix that issue
[https://support.symantec.com/en_US/article.TECH101706.html https://support.symantec.com/en_US/article.TECH101706.html]
 
Related case: [https://isoftdata.fogbugz.com/f/cases/30422/Chelsey-at-Big-3-pictures-errors 30422]
 


[[Category:ITrack/Support]]
[[Category:ITrack/Support]]

Latest revision as of 13:42, 9 March 2018

  • To access services in the UI, go to Start > Control Panel > Administrative Tools > Services
  • To start the MySQL service from the command line: net start mysql or net start mysql5
  • To stop the MySQL service from the command line: net stop mysql or net stop mysql5

Note: Before making the switch, warn customer/users that ITrack will not work while the migration is happening.


Server Side

Preferred Method

This walk-through requires SQLyog. Alternatively, you can use the MySQL command line utility if you're that 1337.

  1. Use SQLyog create a dump of the users ITrack database
    1. Right click on the database in the left pane and select "Backup database as SQL dump"
    2. Make sure the "Structure and data" radio is selected
    3. Make sure the Include "USE database" statement and Include "CREATE database" statement check-boxes are checked.
    4. Click export
  2. Copy the .sql file to the new server
  3. Install MySQL on the new server
  4. Import the .sql dump script with SQLyog
    1. Select Tools from the top menu
    2. Choose Restore from SQL dump
  5. Check the results, make sure it imported properly

2nd Method

  • Note: This method is not recommended and should only be used if you can't use the 1st method.
  1. Stop the MySQL service on the "old ITrack server"
  2. Create a share on the old ITrack server
  3. Copy the ITrack database from C:\Program Files\MySQL\MySQL Server 5.0\data to the share you just created
    1. (Be careful to make sure you have the correct data. If the customer still has MySQL version 4 installed then it will be in the MySQL directory, but if the customer has MySQL version 5 then the data will be in a sub-directory called MySQL 5.0; otherwise you might delete their up-to-date database and only have the crappy old outdated one to work with)
  4. On the new ITrack server, install MySQL server
    1. If you are doing a MySQL reinstall then you may need to uninstall MySQL a few times. It's a little silly, but just because you uninstall the service, the regular files may not have been removed (or vice versa).
  5. Stop the MySQL service on the new server
  6. Use explorer to navigate to the share on the old server
  7. Copy the ITrack database directory to the MySQL data directory on the new server
  8. Start the MySQL service on the new server.
  9. Install SQLYog

Additional Server Changes

  1. Create a new user in the mysql database that ITrack will use to connect to the server
  2. Create an ITrack share on the new server, make sure the "Everyone" group has read and write privileges(for images and attachments).
  3. Move the reports, images, attachments directories from the old server to the share on the new server
  4. On the old server, set its MySQL service to not start on "automatically"
  5. Set the Replikwando Service on the old server to "Disabled" and make sure it's not still running.
  6. Disable the Windows Scheduled Task for Image Synch.

Client Side

  1. Change the "hostname" in all clients host.ini to be the name/IP of the new server.
  2. Change the "server" in the ODBC to the name/IP of the new server.
  3. Change the reports, images, attachments to point to the share on the new server. (This should no longer be necessary after database images.)
  4. Double check with the customer to make sure everything is working properly.

To consider with older Operating Systems

Windows Server 2003: MySQL 5.6.22 is the highest compatible MySQL version with this OS https://bugs.mysql.com/bug.php?id=80399

On Big 3, we encountered a situation where Symantec was half-installed on their system, causing it to try to install the software any time the user right-clicked an icon. We found this article to fix that issue https://support.symantec.com/en_US/article.TECH101706.html

Related case: 30422

Retrieved from "https://wikido.isoftdata.com//index.php?title=ITrack/Migrating_a_server&oldid=10342"