Migrating From On-Demand to On-Site

1. Overview 2. Steps to Complete 3. Related

Overview
Occasionally system administrators will have the need to deploy versions of their On-Demand instance to an On-Site system. Reasons for this type of deployment are: Testing locally developed modules Migrating from On-Demand to On-Site (Please note, On-Demand-only releases such as 6.6 or 6.7 are not supported to be migrated to On-Site.)

Steps to Complete
For these situations, users may request a backup of their On-Demand system by filing a support case. When a backup is requested, SugarCRM will provide the user with an FTP account where they can download two files. instance_name-YYYYMMDDHHmm.sql.gz (backup of database) instance_name-YYYYMMDDHHmm.files.tgz (backup of file system) These files can be deployed to a local system as described below. 1. Extract and import the SQL data as follows: Extract the SQL file via an archive utility (e.g. 7-Zip) or via command line such as: gunzip instance_name-YYYYMMDDHHmm.sql.gz Create a database on your MySQL server via command line: mysqladmin -u mysql_username -p create instance_name Or, if already logged into MySQL, with a command such as: CREATE DATABASE instance_name; Import the SQL data to your MySQL server via the command line: mysql -u mysql_username database_name -p < instance_name-YYYYMMDDHHmm.sql

2. Extract the tar file to your web server's web root directory (e.g. /var/www/html) with the following command: tar -C /var/www/html -xzf instance_name-YYYYMMDDHHmm.files.tgz This will create a directory named "instance_name-YYYYMMDDHHmm" in your web root directory. 3. Rename the newly created directory: mv /var/www/html/instance_name-YYYYMMDDHHmm /var/www/html/instance_name 4. For Linux-based servers, perform the following actions: Change the ownership of the directory to be accessible by the Apache user and group. Please note that the user and group (e.g. apache, www-data, etc.) may differ depending on the web server configuration. chown -R apache:apache /var/www/html/instance_name Change the permissions of the directory to ensure files can be accessed by the application. The actual permission values may differ depending on server security settings. chmod -R 770 /var/www/html/instance_name 5. Edit the config.php file to point to your database. Open the config.php file: vi /var/www/html/instance_name/config.php Locate and update the "dbconfig" array with the information appropriate for your MySQL server as follows: 'dbconfig' => array ( 'db_host_name' => 'localhost', 'db_host_instance' => 'SQLEXPRESS', 'db_user_name' => 'mysql_username', 'db_password' => 'mysql_password', 'db_name' => 'instance_name', 'db_type' => 'mysql', 'db_port' => '', 'db_manager' => 'MysqliManager', ), 6. Edit the config.php file and modify the following parameters: 'site_url' should be the URL of the instance on your server (e.g. http://www.mysugarinstance.com) 'host_name' should be the URL of the instance without the http protocol (e.g. www.mysugarinstance.com) 7. Modify the .htaccess file in the root directory of the instance and remove the following lines if they exist: #Added by operations to force SSL RewriteEngine On

RewriteCond %{QUERY_STRING} !^entryPoint=WebToLeadCapture RewriteCond %{HTTP:X-SSL-CLUSTER} !^od2$ RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L] 8. If you are migrating permanently to an On-Site deployment, there are additional modifications that should be made to ensure full functionality for your instance of Sugar. To restore the ability to perform ad hoc file backups, open the ./modules/Administration/ Backups.php file, and at line 1 change: <?php die("Disabled on Sugar On-Demand. Please contact support@sugarcrm.com or file a support ticket at http://support.sugarcrm.com to request a backup."); ?><?php To: <?php To restore the ability to perform upgrades, open the ./config.php file and remove the following line: 'disable_uw_upload' => true, To display the full text search configuration options under Admin > Search, open the ./config.php file and remove the following line: 'hide_full_text_engine_config' => true, To display the Sugar log settings under Admin > System Settings, open the ./config.php file and remove the following line: 'logger_visible' => true, To bypass security checks when installing packages via Admin > Module Loader, open the ./config.php file and change the following line from: 'packageScan' => true, To: 'packageScan' => false, You should now have a working version of your On-Demand instance accessible from your local server. Notes: The local system must use MySQL. Converting the database to another system, such as SQL Server or Oracle, requires special handling. For more information regarding this type of conversion please speak with your Customer Advocate. On-Site system administrators must be familiar with their stack and the referenced tools (gunzip, tar, mysqladmin, mysql, etc.). It is the system administrators responsibility to diagnose and troubleshoot issues specific to the stack (permissions, environment variables, etc.).

Related
Topics Configuring Your SMTP Server to Work With On-Demand (100%) Module Loader Restriction Workarounds (100%) Module Loader Restrictions for Sugar On-Demand Guidelines for On-Site Hardware Size Requirements Sizing Guidelines for On-Site Hardware Requirements Tutorials Obtaining a Copy of Your On-Demand Data (100%) Migrating From On-Site to On-Demand (100%) Moving Sugar to Another Server (100%) Migrating From On-Demand to On-Site Creating a Backup Batch File for Windows Servers (Simple Working Copy) Migrating From On-Site to On-Demand Creating a Backup Batch File for Windows Servers (Simple Working Copy) Moving Sugar to Another Server Creating a Backup Batch File for Windows Servers (Rolling Archive) Migrating Customizations From One Instance to Another Troubleshooting Troubleshooting Issues With Filesystem Permissions Troubleshooting Missing Upload Button on Step 3 of Upgrade Wizard References Migrating Data From a Previous CRM System Other Migration

http://support.sugarcrm.com/04_Find_Answers/02KB/02Administration/100Migration/Migrating_From_OnDemand_to_On-Site Updated: Thu, 07 Mar 2013 04:39:14 GMT Powered by 4