Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Given an existing EMG 7.1 installation, the following steps provide an upgrade to EMG 7.2. This can be done in multiple phases. It requires an active support agreement with an updated license file. All commands should be run as the user "emg", or the non-root user used for the EMG installation.


  1. Add BACKEND=TC in the top part of the server.cfg file. This ensures EMG 7.2 will use the existing storage backend, in case you want to downgrade back to EMG 7.1.
  2. Do not add DLR_TO_SAME_IP yet.
  3. Make sure the current emgd binary is called emgd-7.1.x-nnnnn or something similar, where x and nnnnn matches the output from "emgd -v".
  4. Download the new EMG binaries, and unpack them in a new directory.
  5. Copy the new binaries into the bin directory, renaming them from emgXXX into emgXXX-7.2.0-50785, again using the exact version information from "emgd -v" from the new binary.
  6. Copy emgclient, emgd, emgload, emgpdu, emgsend, emgsink and emgstat into the same format emgXXX-7.1.n-nnnnn, using the old version information.
  7. You can run "emgd -upgradesql" to see the optional database schema updates.
  8. Check the output from "ulimit -a". The number of open files must be at least twice the total number of connector instances. If this is not the case, run "ulimit -n" to change it. Please also add that command to the /etc/rc.local file, before it starts the EMG Watchdog.


  1. To upgrade the database schema, first make a copy of the existing EMG database. This makes it possible to see the time required to run the commands given by "emgd -upgradesql".
  2. If the time spent is not acceptable, the upgrade may need to be done in multiple steps. Please consult with your local database administrator.
  3. Comment out the BACKEND line in the server.cfg.
  4. Now you may set DLR_TO_SAME_IP on the relevant connectors, if needed.
  5. Change the database sections to use the new format: ADDRESS=username:password@host:port/dbname. This makes it possible to multiple ip's for the same database profile.
  6. Run "emgd -stop".
  7. Update the database schema, either by running the commands shown earlier, or by running "emgd -upgradedb".
  8. Run "emgd".