FinanceServersMigrationPlan: Difference between revisions
From Newroco Tech Docs
Jump to navigationJump to search
(A migration plan for Finance servers that will help during the down time or for the next time it needs to be done) |
|||
| Line 2: | Line 2: | ||
== Steps before down time== | == Steps before down time== | ||
* Create the VMs according to their needs | |||
* Install all packages required | |||
* Take full DB dumps from the old VMs | |||
* Restore dumps to new VMs | |||
* Edit /etc/hosts and add names and IPs to all VMs involved so they can be addressed by DNS rather than IPs: | |||
<pre> | |||
10.0.10.49 finance.thehumanjourney.net | |||
10.0.10.24 timesheets.thehumanjourney.net | |||
10.0.10.43 hrdb.thehumanjourney.net | |||
10.0.10.180 tenders.thehumanjourney.net | |||
</pre> | |||
== Steps during down time== | == Steps during down time== | ||
Revision as of 11:12, 18 May 2017
Overview
Steps before down time
- Create the VMs according to their needs
- Install all packages required
- Take full DB dumps from the old VMs
- Restore dumps to new VMs
- Edit /etc/hosts and add names and IPs to all VMs involved so they can be addressed by DNS rather than IPs:
10.0.10.49 finance.thehumanjourney.net 10.0.10.24 timesheets.thehumanjourney.net 10.0.10.43 hrdb.thehumanjourney.net 10.0.10.180 tenders.thehumanjourney.net
Steps during down time
Steps after down time
- Test all interfaces work well
- Test special functions that might no longer work
- Make staff changes in HRDB and check if the change was propagated to TRS, Finance, Admin DB on Finance VM, Tenders, Archives
- Make project changes on Finance and see if the change was propagated to Archives - this checks if RabbitMQ worked well
- Monitor any support tickets related to any of these services and first find a cause in the migration done.
