Server Migrations
Revision as of 10:39, 12 July 2022 by Shieldstromme (talk | contribs) (→Summary of a server migration)
PTS server migrations are not that different to fresh installations of the PTS server software. The crucial difference, of course, is the use of a database backup from your existing PTS database server so your data carries over.
This document aims to briefly summarise the steps involved in a PTS server migration.
Summary of a server migration
In reality a TMSi technician will take the lead on many of these steps but they are included here for the sake of completeness.
- Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.
- Take a backup of the existing PTS database. This backup is for rolling back the update if the need arises.
- Update PTS on the existing server to the latest release.
- Test that the update was successful.
- Take another backup of the existing PTS database from the old database server. This backup will be used for the migration.
- Install PTS on the new application and database server/s. This will manifest a vanilla instance of the latest version of the software on the new server/s.
- Replace the newly installed vanilla database with the latest backup from the old server.
- On each PC hosting PTS barcode scanners, uninstall the PTS Comms Client software, and then download and re-install the appropriate PTS Comms version, being sure to enter the new URL when prompted.
- Re-map any networked label printers onto the new server.
- Update desktop and intranet shortcuts with the new PTS URL.