Differences

This shows you the differences between two versions of the page.

--- tutorials:server:moving_installation [2011/12/30 19:05]
james
+++ tutorials:server:moving_installation [2014/09/25 16:55] (current)
@@ Line 1: / Line 1: @@
-====== Moving Installation to New Server ======
+====== Moving Installation to New Server (MOVED) ======
-<tip c n>This tutorial will also work when creating a duplicate installation for staging or testing purposes.  Note though that you are creating two separate and autonomous installations.  This means two separate file locations and two separate databases.  Each file set connecting to it's own database.  This is irrespective of whether the test installation is on a different server, the same server and/or the same domain than the live installation.  Each is a standalone copy of the other installation when finished.  Just note NOT to delete the original installation if you are just creating the copy for development purposes.
+Instructions have moved.  **See [[tutorials:server:migration:start]]**
-If you choose to create an exact copy of your live installation in your testing location make sure to disable all notification emails sent by the system to your clients or they could be getting duplicate expiration notifications for anything expiring in the testing installation the same time it is expiring in the live installation.  You can disable all of those within the following admin tool:
-  EMAIL SETUP > NOTIFICATION EMAIL SETTINGS
-</tip>
-When moving the software from one server/location to another (aka Server Migration) there are five things to consider. The actual files (php, images, etc...), the database, admin settings, html and license.
-) Files:
-This is the easiest step. With respect to the software, you will simply need to transfer all of the files of the software including subdirectories and the files in the subdirectories from your old server to your new server.  You would basically copy the Geo files in your old location down to your local computer.  You could then copy them to your new location.  This also creates a file backup locally if anything happens in either the old or new locations.  Before you begin copying you should turn off caching within the old installation.  You do not need to copy the contents of the /templates_c directory from your old location.  Those contain specific file paths that most likely will not exist on the new server.  The new server location does need to have /_geocache and /templates_c folders and they do need to be "writable" but their contents in the old location are useless in the new location.
-) The database:
-Most hosts provide a program called phpMyAdmin for administering your MySQL databases of your hosting account. You will first want to use phpMyAdmin to create a backup of the database of the old installation in sql format.  Many times hosts have built in "database backup" features but the output created by these types of backups usually require specific software to restore.  So just use the sql output from phpmyadmin for creating your backup instead of any host specific or proprietary backup systems.
-<tip c n> Be sure to use the Drop Table option as it makes recreating the database a bit easier. </tip>
-Once you have this done, you can use this backup sql document just created to create the "geodesic" installation database tables in the MySQL database created for your installation on your new server. Moving the database over from the old installation to the new installation "moves" all the changes, configurations and settings you made through the old installations admin tool into the new installation. Consult your host's support documentation as they should provide help documents regarding using phpmyadmin.
-) The admin: Once the files have been transferred and the database has been created, there are a few settings that need to be addressed in the config.php file and admin to correspond with the new server. Below is the list of them:
-) The config.php file:
-Will need to be edited to match your new database connection settings. This includes the new database server location (usually localhost), database name, database username and password to connect to that new database. Once this is done you can then log into the admin. Check all of the "location" settings within the two admin tool pages below in case the actual url has changed.
-  SITE SETUP > GENERAL
-  REGISTRATION SETUP > GENERAL
-Check the setting below to make sure the server path to the "user images" directory matches the directory structure of your new server.
-  ADMIN > LISTING SETUP > PHOTO UPLOAD SETTINGS > "server path to root of photos directory" (pre version 4.1)
-  ADMIN > LISTING SETUP > FILE UPLOAD & DISPLAY SETTINGS > Server Path to Root of Photos Directory (post version 4.1)
-Also double check that the above mentioned directory has the correct rights on it so the script can "write" uploaded files to that directory like your previous installation had.
-) The html:
-Within your templates and/or html logged in/out modules, you may have to adjust links and image references. This typically will need to be done if you changed the domain name or if you changed the subdirectory that the software is installed relative to the domain.
-) Email Configuration:
-Go through the following admin tool to make sure you do not need to change the email configuration:
-  EMAIL SETUP > GENERAL EMAIL SETTINGS
-Send some test emails from this admin tool to yourself and possibly other email addresses to make sure the software is sending emails correctly.  Changing servers can mean a change here as the SMTP server location, login (if used) and configuration could be different for the new server even though you may have stayed with the same host.
-) SEO:
-If you use the SEO addon to rewrite your urls to more Search Engine friendly ones you may need to recreate the "rewrite rules" within your .htaccess file to reflect the new location...possibly the new domain if that changed.  Go to the SEO addon wizard to recreate that file.
-) The license for you installation has almost undoubtedly changed somewhat. You will need to contact [email protected] with the new installation locations ip address, url and server path to the installation so that the license can be updated to the new location.  You can usually determine all of the new license necessary details in the license error you see when you login to the admin tool at the new location.  A simple copy of those details to sales or support should be enough to update the license in our license validation server.
-If you know the domain AND installation path before you make the move you can send that information into [email protected] before you start the migration.  The license could be updated with this information before the move is made.  This would assure the least downtime as the new installation would work immediately after completing the move.  The old location would need to be removed from the license in this process also.
-All in all it is a pretty simple and straight forward process but if you feel that you do not want to do this, we do offer this as a service. Please contact [email protected] if you would like us to perform this for you.

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools