Webserver Migration

Migration rundown

Hereunder you can find a rundown of what's about to happen.


  • Server A: Production server
  • Server B: Temporary server to facilitate staging of new server OS
  • Server C: Temporary server to provide uptime during the migration


Everything will happen in the following order

Phase 1

Server B basic config will be finished during this phase.
  1. Server B will be created with equal hardware specifications conform with server A.
  2. After hardware and OS install finalization, nginx config files will be copied and webserver will be tested.
  3. Migration only continues when webserver is evaluated as functional.

Phase 2

Infrastructure will be running both old and new webserver, ready to transition into the next phase.
  1. Website root directory and onther files will be copied over to server B and website functionality is tested.
  2. DNS records are updated as required.
  3. Haproxy config will be edited and tested to use Server B as primary and Server A as secondary backend.
  4. This will ensure fucntionality should something still be defective with server B.
  5. During the update to the Haproxy config, DR team will be on standby.

Phase 3

During phase 3 preprations will be made to transfer data from temporary server B to server A
  1. Server C is created with equal hardware conform with Server A.
  2. OS disk of Server A is copied to server C and booted.
  3. DNS records are updated as required.
  4. Haproxy config is updated and tested again to set Server C as primary and server B as secondary.

Phase 4

Last phase will migration of server OS and cleanup of temporary machines
  1. OS Disk of Server B is moved to Server A.
  2. Server A is tested.
  3. Haproxy config is updated to use Server A as Primary and Server B as secondary.
  4. Server B is removed from inventory.
  5. Infrastructure is tested and haproxy config will be updated to only use Primary Server A.
  6. Server C is shutdown and kept on standby during grace period.


Updates will be reported on the top of this page after every phase.
Because uptime is the #1 priority, the status will be viewable during the entire migration process.