====== Cloning eBiss systems ======

===== Preparations in the existing system =====

  - disable all eBiss automations and stop the eBiss service.
  - Make sure you have a backup((data backup of VM for example)) and dump the database((The executable **eBiss.DBCopy.exe** allows to DUmp and IMport the eBiss database including transactional data(but exclusive of message content))) and move it to the new location.
  - Upgrade to the latest version.
  - Dump all eBiss nodes.
  - Move the message store (keeps the physical messages in files on the drive).
  - Move the plugins that represent your integration(s).

===== Activities in the new location (e.g. staging environment) =====

  - Install the same version as an "empty" system.
  - Add the individual integration plugins((The plugins that represent your specific eBiss integration.)).
  - Configure eBiss with a new DB.
  - Import the eBiss dump objects into the appropriate nodes.
  - Adapt the endpoints to the new environment.


{{:images:sign_warning.png?nolink|}} Note: check also [[en:ueberblick:installation:serverumzug|]]

===== Alternative =====

The executable **eBiss.DBCopy.exe** allows dumping and importing of the eBiss database including all nodes and transactional data (but excluding the message contents) and can therefore be taken for identical mappings including specific passwords on communication channels and users, but care should be taken, because the communication channels are finally "sharp".