EasyUC
4.8.7

Installation, updates & backup

Migrating from EasyUC 3.x

Transfer the data of a 3.74/3.75 installation into a fresh 4.x installation.

EasyUC · Version 4.8.7

In EasyUC: Manager → Migration 3.x

What it is for

The migration transfers the data of an EasyUC system of version 3.74 or 3.75 into a freshly installed 4.x installation. You enter the SSH access to the old system in the Manager. The Manager creates an encrypted migration archive (.eucmig) there, fetches it, checks it in a dry run and only then imports it.

The old system is only read. Database, containers and installation directory stay unchanged there. The IDs of the records are kept; there is no merging with existing data.

The menu item only appears with the CUCM module.

Prerequisites

  • A freshly installed 4.x installation without CUCM connections. Otherwise the check reports the blocker TARGET_NOT_EMPTY. A factory reset produces the empty state.
  • CUCM module active.
  • SSH access to the old system with an account that is root or may become root with sudo.
  • Network clearance from the appliance to the SSH port of the old system.
  • Enough free space under /tmp on the old system for the archive.
  • Without a network connection to the old system: the manually created archive and its passphrase.

Step by step

  1. Open the Migration 3.x page in the Manager.
  2. Step 1 Altsystem verbinden: enter Host oder IP der alten Anlage, SSH-Port, Benutzer, Passwort and, if needed, the sudo-Passwort.
  3. Select Zeitfenster Verlaufsdaten and CDR-Historie.
  4. Select Verbindung pruefen. The pre-check shows the detected version, SSH, rights, Docker and free space.
  5. Select Migration starten. The Manager creates the archive on the old system, fetches it and cleans up there. The page can stay open.
  6. Select Weiter zur Pruefung.
  7. Step 2 Pruefen: select Pruefung starten. The dry run writes nothing to the target database.
  8. Read the report: blockers, warnings and the Uebersicht je Inhaltsbereich. Download it as HTML or JSON if needed.
  9. Select Weiter zur Migration. This is locked while blockers exist.
  10. Step 3 Migrieren: decide on Verlaufsdaten uebernehmen and CDR-Historie uebernehmen and the time windows.
  11. Select Migration starten and follow the Live-Log.
  12. Select Weiter zum Abschluss. Step 4 Abschluss: read Ergebnis der Migration and Manuelle Nacharbeiten.
  13. Select Archiv aus dem Speicher loeschen. The archive contains credentials in clear text.

Fields and options

Fields and options
Field / actionMeaning and use
SSH-Port1 to 65535.
sudo-PasswortLeave empty if it is identical to the password or the user is already root.
Zeitfenster VerlaufsdatenLogs, tickets, orders and similar history tables. Older data is not exported. Default for the import: 12 months.
CDR-HistorieCall detail records. They are the largest share of the data volume. Default for the import: 3 months; "keine CDR uebernehmen" is possible.
Archiv stattdessen manuell hochladenFor cases without a network connection to the old system: drop the .eucmig file and enter the Passphrase des Archivs.
Archiv im SpeicherShows file, size, time of provision and whether a passphrase is stored.
Blocker uebergehenOnly useful for TARGET_NOT_EMPTY when the target database is to be overwritten deliberately. To unlock, type FORCE and repeat the check. All other blockers remain.
Master data and filesAre always transferred. History data and CDR history can be deselected.

Check the result and troubleshoot

  • The final step shows Ergebnis der Migration with inserted and skipped rows per content area and "Der Bericht nennt keine offenen Nacharbeiten." or the list of follow-up tasks.
  • "Abruf noch nicht moeglich" with "Das steht dem Abruf im Weg": the pre-check names the obstacles, for example missing root rights or Docker not running.
  • Blocker TARGET_NOT_EMPTY: CUCM connections already exist in the target. Perform a factory reset first.
  • "Export durchgelaufen — mit Warnungen": individual parts were left out. What is missing is in the output and shows up in the dry run.
  • "Auf der alten Anlage sind Reste liegen geblieben": the clean-up did not complete. Delete the named directory on the old system manually, otherwise a decryptable copy of the data remains there.
  • Warnings in the report: the migration runs, but the result has to be checked afterwards.
  • The labels on this page are German and write umlauts as ae, oe and ue. This chapter quotes the labels as the interface shows them.

Related chapters