Geodesic Solutions Community Wiki

User Tools

Site Tools

You are here: Auction and Classified Software Support Home » Tutorials » Server and Backup Related » Installation Migration
tutorials:server:migration:start

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
tutorials:server:migration:start [2012/10/12 23:50]
jonyo [Step 1 - Move Files] 		tutorials:server:migration:start [2014/09/25 16:55] (current)
Line 7: Line 7:
   * Server Migration (meaning copying from one server to another) : Follow **all steps** <   * Server Migration (meaning copying from one server to another) : Follow **all steps** <
   * Move installation to a different folder on the same server : **Skip step 2** <   * Move installation to a different folder on the same server : **Skip step 2** <
-  * Create test installation : skip part of final step((Do NOT delete the old installation, since that is your live installation!)). <+  * Create test installation : Follow **all steps**, see note below. <
   * Domain change only((Files do not move to a new location, and database is not moving.)) : Use the reduced steps in the tutorial for [[tutorials:server:changing_domains:start]]((Note that the linked tutorial is actually this tutorial, with only step 3, step 4, step 5, and step 7.)) <   * Domain change only((Files do not move to a new location, and database is not moving.)) : Use the reduced steps in the tutorial for [[tutorials:server:changing_domains:start]]((Note that the linked tutorial is actually this tutorial, with only step 3, step 4, step 5, and step 7.)) <
  
 If you aren't sure which instructions to follow for your situation, when in doubt ask support!  Support can tell you exactly which instructions you should be using for your situation. If you aren't sure which instructions to follow for your situation, when in doubt ask support!  Support can tell you exactly which instructions you should be using for your situation.
  
-<tip c n>**Note for Test Installations:**  This tutorial will also work when creating a duplicate installation for **development**, **staging**, or **testing** purposes. Note though that you are creating **two separate and autonomous installations** when you do so. 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/testing/staging purposes.+**NOTE:**  We provide these steps to allow you to perform the migration (moving the software to be installed in a different location) yourself.  However if you would prefer us to make the move for you, we do offer [[http://geodesicsolutions.com/support/installation-migration-services/81-server-migration.html|professional server migration service]] which you can purchase from the client area.
  
-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: +<tip c n>**Note for Test Installations:**  This tutorial will also work when creating a duplicate installation for **development**, **staging**, or **testing** purposes. Note though that you are creating **two separate and autonomous installations** when you do so. 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/testing/staging purposes.</tip>
- +
-EMAIL SETUP > NOTIFICATION EMAIL SETTINGS</tip>+
 ===== Step 0 - Preparation ===== ===== Step 0 - Preparation =====
  
Line 35: Line 33:
 Option 2 is standard option for moving files from one place to another, using FTP. Option 2 is standard option for moving files from one place to another, using FTP.
  
-Option 3 (located on it's own page) uses SSH to zip then SCP the files from one server to the other.  This option is **only for advanced users** that are **comfortable with using SSH**.  This option is much faster than option 2 but does require running things in SSH command line.  In other words it is faster and more reliable, but also much more complex, and only works if the servers involved support SSH.  If you fall into that group, see the magical SSH option at [[tutorials:server:migration:ssh_method]].+Option 3 (located on it's own page) uses SSH to zip then SCP the files from one server to the other.  This option is **only for advanced users** that are **comfortable with using SSH**.  This option is much faster and more reliable, but also more complicated, and only works if the servers involved support SSH.  If you fall into that group, see the magical SSH option at [[tutorials:server:migration:ssh_method]].
  
 ==== Option 1: Folder Rename, on Same Server ==== ==== Option 1: Folder Rename, on Same Server ====
Line 54: Line 52:
  
 And finally, you will need to delete all the files in the **templates_c/** folder, as there are times when moving the folder can cause those files to need to be re-generated.  Keep the folder, but delete the contents of the folder. And finally, you will need to delete all the files in the **templates_c/** folder, as there are times when moving the folder can cause those files to need to be re-generated.  Keep the folder, but delete the contents of the folder.
 +
 +<tip c n>**Tip:** If, after your site has moved from one location to another, you see a "SmartyException" error, it typically means this last step above was skipped. In that case, deleting all files in the templates_c folder will usually clear the error.</tip>
  
 Once that is complete, continue to the next step [[#Step 2 - Create Database]] Once that is complete, continue to the next step [[#Step 2 - Create Database]]
Line 95: Line 95:
 Then in [[admin_menu:e_mail_setup:general_e_mail_settings:start|Email Setup > General Settings]] you may need to adjust the e-mail settings to make e-mails work on the new location.  This is mainly a concern if changing servers, but it is still a good idea regardless, to send a test e-mail to yourself to make sure e-mail is working. Then in [[admin_menu:e_mail_setup:general_e_mail_settings:start|Email Setup > General Settings]] you may need to adjust the e-mail settings to make e-mails work on the new location.  This is mainly a concern if changing servers, but it is still a good idea regardless, to send a test e-mail to yourself to make sure e-mail is working.
  
-**Test installations Only:**  In the admin at [[admin_menu:e_mail_setup:notification_e_mail_settings:start|Email Setup > Notification E-mail Settings]], turn off all notifications!  Otherwise your test installation may send out e-mail notices to your "real" users since the test installation is based on copy of the live installation database.+**Test installations Only:**  In the admin at [[admin_menu:e_mail_setup:notification_e_mail_settings:start|Email Setup > Notification E-mail Settings]], turn off all notifications!  Otherwise your test installation may send out e-mail notices to your "real" users since the test installation is based on copy of the live installation database.  If you run auctions, you may also want to disable the addon **Main E-mail Sender** and that will disable the ability for the test installation from sending any e-mails (since auctions will send notifications beyond what you can disable normally).
 ===== Step 5 - Update Links in Templates & Text ===== ===== Step 5 - Update Links in Templates & Text =====
  
Line 125: Line 125:
  
 If it says 0 rows affected, check to make sure you have set both values correctly. If it says 0 rows affected, check to make sure you have set both values correctly.
 +
 +<tip c n>**Test Installation Tip:**  If you created a copy of your site for "testing" purposes, and did **not** follow this step when you originally created your test installation, the test installation may be deleting images from your live website before they should be deleted, even if the "live" version of the listing has not expired yet!
 +
 +If this happened for your site:  First, follow this step for your test installation to keep it from happening in the future.  Second, copy all of the images from your test installation **user_images/** folder, to your live installation **user_images/** folder, and you can **skip images that already exist**.  This will restore any images that were deleted by not following this step to begin with!  Then in the live installation, you can use the tool to remove orphaned images to get rid of images that do actually need to be moved.  If that tool is not able to remove the images, you may need to CHMOD 777 all files in the user_images folder on your live site so that the software can delete them.</tip>
 ===== Step 7 - SEO Addon ===== ===== Step 7 - SEO Addon =====
  
Line 138: Line 142:
  
 If you elected to turn your site off during the move, don't forget to **turn your site back "on"**!  You can do so at **[[admin_menu/site_setup/general_settings/start#Site On/Off Switch|Site Setup > General Settings#Site On/Off Switch]]**. If you elected to turn your site off during the move, don't forget to **turn your site back "on"**!  You can do so at **[[admin_menu/site_setup/general_settings/start#Site On/Off Switch|Site Setup > General Settings#Site On/Off Switch]]**.
 +
 +**Test Installations:**  If you are creating a test installation, we also recommend to turn all e-mail notifications off in the admin at **E-mail Setup > Notification E-Mail Settings**, that way it does not generate e-mails to users resulting in duplicate e-mails sent since the main installation would also be sending it's own notices.  Make sure you do not turn the notices on in the future, as that will generate "past notices" to be sent in certain cases.
tutorials/server/migration/start.1350085805.txt.gz · Last modified: 2014/09/25 16:55 (external edit)

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki