====== Migration Responsibility ====== 1. Data transfer and Application Configuration - Syed 2. Data validation - Uday 3. DNS and network configuration - Murali ===== Data Transfer steps ===== 1. Customer data has to be replicated from NA1 to NA3. We Prefer Tarred copy of Customer data to be sent over Internet from NA1 to NA3. Shared folders to be copied; 1. Streams 2. System 3. Assets 4. log (Data can be ignored - Optional). We have around 160Gb of customer data, we tested data transfer rate and it takes at-least 48Hrs to transfer 160Gb. 2. Once we have the copy of customer data we shall perform Rsync after untaring files to maintain consistent updates. 3. Making sure that application configuration files are properly configured. 4. Once we have complete copy of data, then we shall start the process of database migration Database is approx. 1 GB and transfer will take 30 mins. Total ETA - 3hrs. **Tar and Rsync will be used for Data transfer - Backup and incremental restore.** ===== Application Configuration steps ===== Configuration files will be replicated from NA1 to NA3 for reference 1. Make sure the hostnames and system is configured properly. 2. Following files will be modified; * database.yml * steams.yml * recoder.yml * bigbluebutton.yml * newrelic.yml (need to change hostnames) * juggernaut.yml * sunspot.yml 3. God configuration and environment will be changed to production. 4. Apache-Phusion configuration will be changed to production (RAILSENV). 5. NA1 - Data base will imported. 6. Deploy scripts will be tested and verified. ===== DNS and network configuration ===== LoadBalancer - na3chat.learnexa.com - 162.212.1.188 (for sub-site) - na3mtchat.learnexa.com - 162.212.3.238 (for Multi-tenant) - learnexa.com - 162.212.1.188 (currently na3.learnexa.com) Application Server 01 - app1.learnexa.com - 162.212.1.189 Prodcollab (streamer) - streamer01.learnexa.com - 162.212.3.134 Prodcollab (recorder) - recorder01.learnexa.com - 162.212.3.135 ====== In-case of Failure (Reverting) ====== We have images of the app server on NA3 and also we shall not decommision the servers on NA1 (production) until we have Application configurations and data set correctly.