Migrating HQ/DVS to new Server Hardware With existing IP Address

This an application note on how to migrate an existing HQ server to a new hardware platform using the existing IP address.

Pre migration Tasks

  • Make sure that the customer provides you a temporary IP address for each location where you are migrating the hardware. This will allow you to change the old server to the temp IP address during the migration.
  • Have the customer put the new servers online with their new IP address.
    • This address will eventually be changed to the old servers IP address once the migration has started.
  • Verify that you have remote access to the new servers
  • Make sure or verify that the operating system and hardware meets the specifications of the version of software you are going to install.
  • With remote access ensure that all the features and roles have been turned on and installed on the new system
    • Ensure that you have Telnet client installed on the new server for remote Telnet access to the switches.
  • Ensure that you have set up the SMTP relay on the new servers
  • Create a shared folder on the new servers with read/write access. You are going to use this share from the old platforms to copy the old information over.
  • Create a local administrator account on the systems to match our company wide logins
  • Download the exact same version of software as on the old server. You can copy the install folder over to the new server using the shared drive you just created.
  • Copy or download the Install folder off our FTP site and put it on the new server

Pre Migration backup

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 servers.

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.

Start of Migration

Since we are migration the HQ server and DVS servers to new hardware the following will have to occur:

  • The old servers will require backups to be performed and have that data moved to the new server(s)
  •  The old servers will need their ShoreTel services stopped and once stopped they will need to have their IP address changed to the temporary IP address provided by the customer
  • Verify that you still have remote access on the old server after changing its IP address
  • The new servers will then have their IP addresses changed to the corresponding IP address in Shoreware Director
  • Then run a Fresh install of the Shoreware Server or Remote server software
  • Stop all the ShoreTel services on the old server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
    • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directoryScript> and run the hq-shoretel-stop-svcs.bat
  • Change the IP address of the old server to the temp IP address that the customer provided.
  • Change the IP address of the new server to the actual IP address of the HQ server in Shoreware Director
  • Run a fresh install of the ShoreTel software on the server(s) starting with HQ
  • Once the install has completed, stop all the ShoreTel services
  • Stop all the ShoreTel services on the old server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
    • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directory Script> and run the hq-shoretel-stop-svcs.bat
  • Using SQLyog connect to the new Shoreware DB on the new server (root/shorewaredba port 4308)
    • Import the ConfigSQL.sql into the ShoreTel DB
    • Import the ShorewareBridge.sql into the ShoreTel DB
  • Using SQLyog connect to the ShorewareCDR db an import the ShorewareCDR.sql dump file into the db
  • Then in the Shoreware Backup folder copy and paste the following directories over the existing ones in the C:Shoreware Data folder
    • Prompts
    • User Data
    • VMS
  • Once all the folders have been copied over and the DB has been imported, restart the ShoreTel services
    • Start all the ShoreTel services on the new server. This can be accomplished by running quickinstall –startall in the C:program files (x86)Shoreline CommunicationsShoreware Server directory.
      • You can also navigate to the C:program files (x86)Shoreline CommunicationsShoreware Server directory Script> and run the hq-shoretel-start-svcs.bat
  • You may be able to start services and be okay, but you may have to reboot the server to ensure that the services do come back up.
  • Login to the system and verify that the new servers Shoreware Director appears to have the configuration of the old server.

DVS locations

The migration of the remote servers is similar to that of the HQ server.

If the DVS software is not running distributed Databases then you will not have to run DB backups on the DVS servers.

  •  Stop all the ShoreTel services on the old server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline CommunicationsShoreware Remote Server directory.
    • You can also navigate to the C:program files (x86)Shoreline Communications Shoreware Remote Shoreware Server directory Script> and run the hq-shoretel-stop-svcs.bat
  • Change the IP address of the old server to the temp IP address that the customer provided.
  • Change the IP address of the new server to the actual IP address of the HQ server in Shoreware Director
  • Run a fresh install of the ShoreTel software on the server(s) starting with HQ
  • Once the install has completed, stop all the ShoreTel services
  • Stop all the ShoreTel services on the old server. This can be accomplished by running quickinstall –stopall in the C:program files (x86)Shoreline Communications Shoreware Remote Shoreware Server directory.
    • You can also navigate to the C:program files (x86)Shoreline Communications Shoreware Remote Server directory Script> and run the hq-shoretel-stop-svcs.bat
  • Then in the Shoreware Backup folder copy and paste the following directories over the existing ones in the C:Shoreware Data folder
    • Prompts
    • User Data
    • VMS
  • Once all the folders have been copied over restart the ShoreTel services
    • Start all the ShoreTel services on the new server. This can be accomplished by running quickinstall –startall in the C:program files (x86)Shoreline Communications Shoreware Remote Server directory.
      • You can also navigate to the C:program files (x86)Shoreline Communications Shoreware Remote Server directory Script> and run the hq-shoretel-start-svcs.bat
  • You may be able to start services and be okay, but you may have to reboot the server to ensure that the services do come back up.

Post Migration tasks

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:

  • Have customer test voice mail on their phones, can they login
  • Dial into the main numbers at each site to ensure that the local Auto Attendants and greetings play
  • Check the Quick Look and Connectivity screens to ensure that everything is green and has reconnected
  • Make sure the SMTP relay address have been added to the server
  • Using the Trunk Test tool make outbound calls out of each set of customer trunks to verify that both outbound and inbound (calling the AA’s step from above) is working.
  • Call a few DID numbers to ensure they are going to the correct person and that person’s voice mail