Quick Question Concerning Cache, Backups & Upgrades/Patches

[jjwdesign]

Before upgrading or patching SugarCRM it is, of course, very important to backup your instance of SugarCRM. Or even better yet, to test the upgrade/patch on a clones version first. I'm currently doing the first in most cases; especially the simple patches. Unfortunately, creating a backup copy of the sugarcrm directory takes several hours. Our cache directory has grown to be over 40GB in size. This got me wondering if we could just copy everything other than the cache dir; as a temporary backup for upgarde failure? Do we need to backup the cache directory every time?

Thanks,

[eNick]

It depends. There are some things which are stored in the cache. In particular, if you use the documents module, that's where the documents are stored.

Sounds like you might benefit from a more incremental backup solution which can just backup what's new or changed since the last backup.

[jjwdesign]

Our Windows network does have a Incremental Backup solution available, but the SugarCRM is install on a Linux box. I believe I had Samba working at one time, but it's been a while. I guess we could move everything to a Windows 2000 server or some kind of managed Virtual Server. Fun, fun.

[ptemplin7]

If you look into your Linux tool kit you can use the tar/gzip to only backup things that are changed. there are various options to have this done. There are other ways as well such as using the find with a date flag to create a list of files that have changed since a certain date and thej only back those up. This is if you can't get your windows tool to backup for you.

Leave sugar on the Linux its much safer over there on an Apache server. Move as a last resort. Good Luck, Paris

[jjwdesign]

Paris, thanks for the reply! I never thought about just using a find command. I'll also take a look at the latest functionality in Tar and Gzip.