Difference between revisions of "Moving NATS3"

From TMM Wiki
Jump to navigationJump to search
m
 
Line 22: Line 22:
 
* Change the paths in the ''includes/config.php'' and ''includes/run_mailer_now.sh'' files to be correct on the new server.
 
* Change the paths in the ''includes/config.php'' and ''includes/run_mailer_now.sh'' files to be correct on the new server.
 
* Change the MySQL connection information for the ''includes/config.php'' file on the new server so it can connect to the database on the original server. Test that NATS is working correctly using the IP address of the new server
 
* Change the MySQL connection information for the ''includes/config.php'' file on the new server so it can connect to the database on the original server. Test that NATS is working correctly using the IP address of the new server
 
+
* If you're including ''helper.php'' (located in <tt>includes/helper.php</tt> in NATS) in one of your pages, you'll need to update the include of header.php to the path on the new server.
 
At this point, NATS should work correctly on both servers and will use the database on the original server.
 
At this point, NATS should work correctly on both servers and will use the database on the original server.
  

Revision as of 17:29, 16 July 2009

NATS 3
Setup
Apache Configuration
MySQL Settings
Creating Admin Accounts
File Upload Setup
Link Domain
NATS3 Files and Directories
NATS Go Live Checklist
Moving NATS3

Too Much Media will move your NATS installation to a new server for $300. We recommend you use this service. The following steps describe moving NATS on your own. Note: these steps require some down time, but they guarantee database consistency and consistent service during the DNS switch-over.

Note: if you just want to change your NATS domain, please see the PROJECT_HOSTNAME configuration setting.

Set up NATS on the New Server

  • Copy the NATS files to the new server. You can use the program rsync
  • Get a NATS license for your new server. Please open a new ticket and tell us with the zendid if you are using Zend, or the MAC address if you are using IonCube
  • If you have Zend, you may need to set up the path to the zend license in the php.ini by adding the following line:
zend_optimizer.license_path=/path to nats/licenses/
  • Change the paths in the includes/config.php and includes/run_mailer_now.sh files to be correct on the new server.
  • Change the MySQL connection information for the includes/config.php file on the new server so it can connect to the database on the original server. Test that NATS is working correctly using the IP address of the new server
  • If you're including helper.php (located in includes/helper.php in NATS) in one of your pages, you'll need to update the include of header.php to the path on the new server.

At this point, NATS should work correctly on both servers and will use the database on the original server.

Moving the Database to the New Server

Your NATS program will be down during these steps.

  • Shut down the database on the original server. This makes NATS stop working.
  • Copy the database to the new server.
  • Change the config.php file on the new server to use the new database and check that nats is working correctly.
  • Change the config.php file on the original server to connect to the new server's database.

At this point, NATS should work correctly on both servers and will use the database on the new server.

Set up Crons and Billers

  • Remove the NATS cron from the old server
  • Set up a new cron on the new server; use the correct paths to nats and php
  • Tell your billers about your new IP address

Switch the DNS

  • Have your host switch the DNS name to the new server. Please open a new ticket when the DNS change is complete so we can update your NATS license.