Application Migration for application owners with own server. (CrossmarX External)

Definitions

Application <APPLICATION> is to be migrated at <PLANNED DATE AND TIME>. This time is called DDAY

• The new server: <NEW_SERVER_DOMAIN_NAME>
• The new IP address is: <NEW_IP>
• The moved domains: <LIST OF DOMAIN NAMES> 

OWNER: the owner of the application and server and domains.
CX: CrossmarX

Preparations

P1) OWNER and CX: Set a date and time for the migration   DDAY

P2) OWNER: Add new IP to SPF record(s) if any

P3) OWNER: Two days before DDAY set DNS TTL cache to 300 seconds (or as low as possible if 300 seconds is not allowed) for all domains concerned.

P4) OWNER:  Three days before DDAY copy databases (use mysqldump), private blobs, public blobs and application files to the new server.

P5) OWNER: disable mail functionalitity and jobs. To prevent mailing and ftp processes during the test phase.
Add the following lines to $ENGINE_HOME/etc/environment.properties

allow.batches.<APPLICATION>=false
email.override.address.<APPLICATION>=<YOUR_EMAIL_ADDRESS> 
email.override.<APPLICATION>=true

P6) OWNER: Reload the environment properties (see /engine/system menu item environment properties) and perform beta tests

DDAY

D1) CX: Disable application on old server in the studio. OWNER: Disable application or shutdown engine on old server 

D2) Perform DNS change(s)

D3) Migrate databases to new server. (use mysqldump)

D4) After database restore on new server. Unset the changes in $ENGINE_HOME/etc/environment.properties and 

reload the environment properties (see /engine/system menu item environment properties)

D5) Add domain names in the domain names list of the applications (blueprint editor)