Cloning Sugar

[Deland01]

Does anyone have the link which covers cloning sugar with MyPHP admin onto a seperate server?

I've looked high & low on Sugar Wiki but can't find it?

Or can anyone give me some pointers how to do this?

[Angel]

Is your ultimate goal to copy the data from server 1 to server 2 on an ongoing basis or ad-hoc copy?

In the case of the latter, you could just copy the folder containing your database on server 1 over to server 2. Assuming both servers are running the same version of MySQL, it should be fairly transparent.

If your intention is to merge server 1's database into server 2's database, you'd need to use a more elaborate process. like replication:

http://dev.mysql.com/doc/refman/5.0/en/replication.html

[Deland01]

All I need a clone for is to use as a testing server. I've been using the live server at the moment & when things so wrong it just adds un-necessary stress to my job.



Using your production server isn’t a very good idea I know but I haven’t had the time to set a clone up yet.







The main problem I’ve had setting the clone up is I didn’t set the original installation up & the person who did is no longer around. I installed Apache, then PHP & MySQL then launched the setup wizard from http://localhost on the clone server. It said that it couldn’t find any MySQL databases.



I have MySQL Administrator installed but how do I actually create a sugar database & link it into sugar?

[paikmoses]

Create one database in the and then start with a new install of Sugar. While installation give the name of the new database.

Try this out.

Regards,

[kpit]

There are more issues involved than just database replication. This is a very complex configuration SugarCRM does not store everything in the database. There are files and metadata that needs to be kept in sync as well. You will need to have a common file share that both have access. Not to mention the session cache if you want seamless use between both installations if you are looking at load balancing automatically.

The biggest being cache directory structure. The files and attachments for documents and emails are stored in cache/uploads. The entire cache directory needs to be shared and writable by both servers.

The other major problem you will have is upgrades.. when you upgrade you must upgrade both systems at the same time or use a shared file system for the entire SugarCRM files. There are ways to not use shared file systems but there is a distinct possibility of being out of sync for a time until the servers catch up. This is especially true if the servers are far apart due to bandwidth and network delays.

This configuration is very, very advance and you should use an experienced systems administrator that has advanced knowledge of all systems and applications involved.

[Deland01]

Kpit,

I take your point on board but I've seen quite a few articles now which suggest that its a pretty easy thing to do.

Like this one:

http://www.sugarcrm.com/wiki/index.p...sting_purposes

Is this something you would advise against?

[tbivans]

Deland01,

I think it depends on what exactly you need the cloned instance to do. If you need the data on it to always be up-to-date, then kpit is correct, it would be more difficult. But if you really just need an instance that has the functionality of your current prodduction instance and enough data to test with, then it isn't that difficult, and the link that you mentioned should work for you well.

Hope that helps.

tbivans