Terms and Conditions backing up from a server to another

tonymontana

Hi,

We already have several servers and tried Epesi successfully... Thanks a lot for managing such a fabulous project !

For security issues, we are planning to perform automatic daily tasks for backing up Epesi installation from a server A (registered along Epesi Licence Key XXX) and restoring Epesi to another server B (registered along Epesi Licence Key YYY):
1- copy entire epesi A installation directory to other server B (including data directory) = first daily security backup
2- dump database from server A = second daily security backup
3- restore database on server B = daily security restore
4- if needed, update configuration file - database name, user, password (but while keeping the same data on both servers, we wouldn't need to update anything)

Tasks 1 to 4 seem to be quite easy to perform.
But we really don't want to breach Epesi Terms and Condition.
Do you agree with such a daily automatic backup and restore process on our servers ?

We also think about using Epesi eCommerce and Inventory Management Modules for server A, along its Licence Key XXX.
Those eCommerce and Inventory Management Modules will never be used on server B... as far as server A works.

If server A fails (or is down for any reason) we are expecting to very quickly modify server B, activating it with registration of Licence Key XXX, recovering all activities and data... hoping this will allow our backup server B to work fine, as a brand new server...

On the other hand, we could later repair server A (or start a new server C) using Licence Key YYY for backup purposes again.
Anytime we will use Epesi eCommerce and Inventory Management Modules on one server only.

Again, we really don't want to breach Epesi Terms and Condition.
Do you agree with such use of Epesi Licence Keys ?

Maybe we need to buy twice Epesi eCommerce and Inventory Management Modules for both servers ?
Could you please confirm ?

Thanks a lot for your support,
Best regards, Antoine

ethnar

Hello and welcome to the forums,

We can perfectly understand the need to have a backup version of EPESI ready to be used in case the server on which the main installation resides fails. We even want to encourage all administrators to have daily backups running - it doesn't really matter if it's EPESI or any other system - it's best to have a backup available.

And having this backup available to be used right away at another location is also fair use. Having this kind of setup is really no different than having a tech guy available to restore the backup at another location when the main server fails, even with the same key - only that it's more convenient and automated. As long as it's still the same userbase, the same data and virtually it's the same system it's OK to have this kind of setup.

Another situation where copying the entire installation along with License Key is desirable and even recommended is when a new version of EPESI is released and you want to test the upgrade process. Again - it's the same installation, virtually, and we have nothing against that.

I hope this answers your concerns.

Kind regards,
Arek

jasiek

I would like to add to what Arek already said:
- the licence key applies to a single EPESI setup with the same userbase and data.
- another instance of EPESI setup for testing purposes or backup is considered really as the same installation (if using the same users and data) and we highly encourage it and recommend this kind of setup to prevent downtime so critical for any business and organization. We consider such a setup as a CLONE of EPESI instance.

What is illegal and will void the license agreement is another installation of EPESI with the same license key but with different users and different data, but sharing Premium (commercial) modules purchased with this license key. Our ESS (Epesi Store Server) will track this kind of abuse and as a result we will block access to ESS, which in turn will stop future updates of the EPESI core system and any free and Premium (paid for) modules. This restriction will apply to the user who shared the license key and anyone who illegally obtained such a key (or the same user who created two separate EPESI installation for two different organization, different set of users and different data).

If you have any other questions regarding licensing issues please let us know.

jasiek

Here is the script to create a cloned copy of EPESI installation on Linux systems. We created it to automate the process of creating another instance of EPESI which is used during the development process and/or during training of new users. Basically the only difference in both instances will be different database connection string and therefore different config.php file.
The reason we also backup the logo file: we take the original logo and write on it in big red letters DEMO or CLONE to let the user know that he/she is operating not on LIVE version of the application.

Please modify this script as you feel fits your setup. To make a switch to a cloned instance in case of the live installation failure or to provide the same data for users for training and development purpose you should copy ALL modules, including Premium module. As long as userbase and data is the same this does not violate the license agreement.

Script to clone LIVE EPESI instance to CLONE (demo) instance

#!/bin/sh

cd /var/www

mv epesi-demo/data/config.php /tmp/config.php.bak

cp epesi-demo/data/Base_MainModuleIndicator/logo.gif /tmp/logo.gif.bak

echo Remove demo

rm -R epesi-demo

echo Clone live to demo

cp -R epesi epesi-demo

mv -f /tmp/ilogo.gif.bak epesi-demo/data/Base_MainModuleIndicator/logo.gif

mv -f /tmp/config.php.bak epesi-demo/data/config.php

chmod -R a+rwX epesi-demo/data

echo mysql replicate

mysqldump -u username -ppassword --add-drop-table epesi | mysql -u username -ppassword epesi-demo

If you can use rsync here is a modified script:

#!/bin/sh

cd /var/www

echo Making a backup of config file and custom logo

mv epesi-demo/data/config.php /tmp/config.php.bak

cp epesi-demo/data/Base_MainModuleIndicator/logo.gif /tmp/logo.gif.bak

#echo Remove demo

#rm -R epesi-demo

echo Clone live to demo using rsync

rsync -a epesi/ epesi-demo

mv -f /tmp/logo.gif.bak epesi-demo/data/Base_MainModuleIndicator/logo.gif

mv -f /tmp/config.php.bak epesi-demo/data/config.php

#chmod -R a+rwX epesi-demo/data

echo mysql replicate

mysqldump -u username -ppassword --add-drop-table epesi | mysql -u username -ppassword epesi-demo

Of course you need to make the first clone/backup manually and adjust the config.php on the second instance to point to another database and if needed provide a different username and password.

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

Help Me! | Download from SourceForge