1.4.1 Sales Opportunity module missing? [solved]

apuschak

Hi,

I upgraded to 1.4.1 and I'm testing Disaster Recovery on a test server. Normally I would install 1.4.1 clean with CRM and Sales Opportunity module. It's not available in the Modules Administration & Store nor was it an option when installing with the easyinstall like with 1.3.

Thanks for your help,
Andrew

ajb

I installed fresh 1.4.1 yesterday, registered it and Sales Opportunity is in store. I've downloaded, installed and everything works for me.

apuschak

I haven't registered yet. We do plan to purchase the Campaign Manager so I suppose I can register now. However, I am still wondering did this get moved into the registered store since 1.3?
Andrew

jasiek

You can register EPESI at any time. Once registered you can download and install new modules that are not included in the default package downloadable from Sourceforge. All Premium modules are now available from EPESI Store - some of them are free and other are commercial, but each one of them require EPESI to be reigistered and each module comes with its own license key - even the free ones.

ajb

I don't remember how it was in 1.3, but now Sales Opportunity module is available for free, but you have to register your installation first. Or you can reuse your key if your 1.3 was registered. But remember to use one key only on one live installation.

Best regards
Adam

apuschak

Ah ok, thanks for your replies!

For the keys issue: I have a production instance 1.4.1 with Sales Opportunity, and in the future more modules including the commercial ones, with dump of the database and /data/ directory. I want to restore epesi on a separate server just to test recovery. Should I register on my production instance, back up the keys, then restore using these keys or another way?

Do I install extra modules like Sales Opportunity on the clean install first or after importing the backup data? I was installing the modules before importing data because I got the 500 error if I didn't install the module first in 1.3. I've looked at the other posts on backup/recovery and its not clear to me.

Thanks again!
Andrew

jasiek

This is the proper way to do it:
- Install EPESI on your production server and register it. This particular instance will be your main one and any modules that you purchase or download should be linked to this license.
- There is no need to register another installation.

We allow to have 2 installations of EPESI with the same license key under the condition that it is used only for backup/recovery and it uses the same data sets (cloned installation). You can read more about it here:
viewtopic.php?f=3&t=1120&hilit=license

This post explains also how to setup a cloned instance of your EPESI application where you will have:
- the same license key
- the same users
- the same datasets
- the same modules

Note: In case you need to do full disaster recovery - meaning that you install EPESI from scratch - you can specify your existing EPESI license key. This will let you access modules that you already purchased. However in order to preserve your data you still need to restore your database and /data directory.

apuschak

Perfect!

I was able to install epesi with my new key, Sales Opportunities, and our custom module on a test server. Then, I imported our database dump and /data directory. Everything seems to be working so I'm confident we can recover if the production server has an issue. I did read the post on keys but I didn't understand where I should first register the key. Thank you for clarifying!

Everyone have a great weekend and thank you for your help!
Andrew

ajb

To do a proper recovery you should ensure that all files that existed in your installation are present in your restore installation. If you don't have backup of your EPESI dir, just only database and /data dir, you should first try to obtain all additional modules that you had in backuped installation.

It may be a problem when you restore database and there is stored info about some modules that are not present in your directories.
So I suggest to backup whole EPESI dir.

If you have only /data dir, your database backup, and your license key you should follow this steps:
1. Download EPESI in the same version as you had. Go through install process.
2. Reuse your license key and download every module that was present in your previous installation.
3. Now you should have all modules files required to restore backup properly.
4. Now remove data dir from current clean installation.
5. Copy your backed up /data dir into clean installation.
6. Restore your database overwriting current fresh install db.
7. Run EPESI.

jasiek

I would add one more step to what Adam (ajb) wrote:
Once you complete "clean installation" of EPESI resuing your license key and installing all additional modules - make a backup of /data directory and dump of the database from this "clean" installation in case you need to troubleshoot something.

Then substitute /data and database from your EPESI you are trying to recover. To do this just substitute your "production" /data directory and for database - empty it first and then import your production data.
Make sure that you update your /data/config.php file with the name of the database and username and password.

apuschak

Thanks Adam and Janusz,

I am clearing out the database and /data directory after a clean install. In a Disaster Recovery scenario I will take additional backups at each stage including after recover now, thanks. Do I need to backup the entire directory as Adam suggested or can I rely on a clean install and installing all the modules then just having a backup of the database and /data?

I need to keep my backups minimal since they are rsync'd and backing up the whole directory is another 57MB and we'll only grow. I don't mind the extra steps of installing everything clean since its not an everyday occurrence but backups are.

Thank you,
Andrew

ajb

You are right, that backing up whole dir on daily backups through rsync is redundant. Rsync only data dir, but You can perform rsync backup of EPESI dir (without /data), when you download some new module from Store. As I remember rsync shouldn't download any files that wasn't modified, but it has to check every file, so it may take some time.

apuschak

Great! Thanks Adam, I keep track of the modules and any new ones that are added, keep disaster recovery documentation, and test recovery. rsync does take some bandwidth, time, and data to check everything even though its not transferring anything. Normally this would be insignificant, however the backup server I'm working with now is an old machine over the internet so every bit counts for now.

Thanks for your help!
Andrew

Epesi ENS | Epesi Academy | epesi.cloud PaaS | GitHub

Help Me! | Download from SourceForge