Move a Triofox installation to a New Server

There are times when Triofox admins need to move the Triofox installation to another server for one reason or another. It is crucial that proper procedure and steps are taken to move the installation to a new server.

Triofox installation consists of persistent and non-persistent data. Triofox database contains persistent/static information such as the username, email, storage configuration, files and folders sharing information and others. It is recommended to have daily backup of the database, since it contains configuration information for the service to run properly. The database is a critical component for the smooth operation of the Triofox server farm. Local database with latency less than 10 milliseconds is recommended.

There are two pieces of persistent information:

1. Database
2. Storage

To move the Triofox installation to a new server:

1. If your database is already on a separate server and you don't need to move it, skip the step.
2. If you need to move the database, you can use Triofox's own database migration tool. To use the database migration tool, make sure the new server and the current Triofox server can communicate with each other directly. It is not required to keep using the same type of database on the new server. Can choose a new database software on the new server. For example, if the old Triofox server is using SQL Express, can take the opportunity to switch to MySQL or PostgreSQL which don't have size limit.
   
   If the new server plans to use the same database, can use the database's own export/import function.
3. Install the database software on the new server.
   
   If you want to use MySQL:
   
   • Use 'Legacy Authentication Method', which is MySQL 5.x Compatibile
   • Make sure MySQL table name is case insensitive, if the server runs on Unix/Linux server
4. Make sure the old Triofox server can access the database on the new server. You can use SQL Management Studio (for SQL Server/Express)/MySQL Workbench (for MySQL)/pgAdmin (for postgreSQL) on the old server to connect to the database on the new server.
5. Once the database connection is verified, on old server, follow the KB article here to migrate the database to the new server. 
   
   https://support.triofox.com/hc/en-us/articles/27995004464407-Migrate-Triofox-Database-Using-Triofox-Migration-Tool
   
   After the migration, the Triofox software still runs on the old server, while the database is on the new server. To test it, create a new user and it should show under the new database server, on xaf_user table.
6. If you use the same type of database on the new server, you can also export the Triofox database on the old server and import it on the new server directly.
7. If the shares Triofox manages are cloud share, ensure the new server can access the cloud storage.
   
   If the shares are local file share, ensure the new server can access the file share the same way as the old server. 
8. Install Triofox on the new server. When prompt for database, choose to use the existing database. Type in the DB connection information, to connect to the new Triofox database.
9. Login to the admin. It will prompt you to configure the new worker node. Make sure the external URL is defined correctly
10. As Admin on web portal, go to System Info, Worker Node Count, Cluster Worker Nodes, unpublish the old worker node
    
11. From Settings, Personal Home Drive, check whether personal home drive has been enabled. If so, make sure the storage is either accessible on the new server, or copy the folder from the old server to the new server.
    
    
    
12. Import SSL certificate on the new server. Use it to bind port 443
13. Change your DNS to point to the new server

Now Triofox is moved to the new server. You can test web portal and native clients operations.