This an application note on how to migrate an existing HQ server to a new hardware platform with a new IP address change
Allow yourself about 1 hour prior to the migration to run a backup. This will accommodate for large systems and will prevent you from missing the start time of the maintenance window.
Run the Lantelligence Backup Scripts for the appropriate version of software they are running. This will create a C;Shoreware Backup folder on the older server.
Once you have the MySql ShoreTel config file, open this file up in a text editor. Search for SOFTSWITCH and change the old IP address to the new server IP address and save the file.
Once completed copy over the folders via the shared folder you create or upload to LANtelligence FTP site. This may take some time so allow yourself the time for the backup and for the moving of the files.
Since we are migration the HQ server and changing the IP address the following will have to occur:
Remote into the remote locations and uninstall the Remote Sever Software on all their DVS systems. You can run all the uninstalls concurrently.
To avoid later reboots, if possible you should leave the switches with their new server address saved on the switch but do not reboot until the DVS servers are back online. If you do because the customer needs some functionality, you will eventually have to reboot the switches and the DVS' later on in the process to ensure they are communicating.
Once the DVS servers have finished their unistalls, reboot the machines.
When the DVS servers have come back online, run the installation of the remote software on the server. You will be prompted to enter the new HQ server IP address.
Once the software finishes, reboot the DVS one last time.
Once all the DVS servers have come back online it is time to reboot any switches that have the new server address and update the remaining switches with the new server address.
Once the switches have reconnected, you will need to remotely reboot all the IP phones on the new system. The phones will not come up unless they grab the new DHCP scope with the new server address.
As with any upgrade or migration we need to test to ensure that all the settings have taken and that the system is fully operational as it was prior to the migration: