Difference between revisions of "Server Migrations"
Jump to navigation
Jump to search
(Created page with "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 summarise the steps involved.") |
|||
| Line 1: | Line 1: | ||
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. | 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 summarise the steps involved. | 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. | |||
<ol> | |||
<li>Review the High Level Design Document for the recommended server specs and required server software components for the latest version of PTS.</li> | |||
<li>Take a backup of the existing PTS database. This backup is for rolling back the update if the need arises.</li> | |||
<li>Update PTS on the existing server to the latest release.</li> | |||
<li>Test that the update was successful.</li> | |||
<li>Take another backup of the existing PTS database from the old database server. This backup will be used for the migration.</li> | |||
<li>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.</li> | |||
<li>Replace the newly installed vanilla database with the latest backup from the old server.</li> | |||
<li>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.</li> | |||
<li>Re-map any networked label printers onto the new server.</li> | |||
<li>Update desktop and intranet shortcuts with the new PTS URL.</li> | |||
</ol> | |||
Revision as of 10:33, 12 July 2022
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.