Moving NATS4

From TMM Wiki
Revision as of 11:40, 9 September 2009 by Tmmcho (talk | contribs)
Jump to navigationJump to search
NATS 4
NATS Setup
Post-Installation Steps
Apache Configuration
MySQL Settings
Creating Admin Accounts
Multiple Server Setup
Using Memcached for Caching
File Upload Setup
Link Domain
HTTPS Setup
NATS4 Files and Directories
NATS4 Go Live Checklist
NATS3 to NATS4 Going Live Checklist
Moving NATS4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers

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.

Set up NATS on the New Server

Please check the following wiki for mysql setup: NATS4_MySQL_Settings

- MySQL must also be accessible from the CLI, which may require changes to the my.cnf file

- Ensure that NO_UNSIGNED_SUBTRACTION is enabled

  • Copy the NATS files to the new server. You can use the program rsync
  • Please be sure to check to make sure all the correct symbolic links are set up in the nats/www/ directory. These symbolic links should be:
track
strack
qtrack
ttrack
gallery
banner
include
  • If any of these symbolic links are not available or not set up correctly in your nats/www/ directory, please put in a support ticket
  • 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 file 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

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.