Installation, updates & backup
Performing a factory reset
Reset an EasyUC installation to the delivery state; the licence is kept.
In EasyUC: Manager → Werksreset
What it is for
The factory reset discards the databases of the installation and rebuilds them empty. Afterwards the installation is as empty as after the first installation. You need this, for example, before migrating a 3.x system, because the migration requires an empty target, or when a test installation is to start over.
The licence is kept. The run saves it before discarding and writes it back afterwards. The Manager itself is not affected: it runs separately from the installation and stays reachable even if the run fails.
Prerequisites
- A login to the Manager and the password of the Manager account.
- An installed licence. Without a licence row it cannot be proven after the reset that the correct licence came back.
- A backup that you can restore. For the full backup before the reset, at least one backup key must be registered.
- A maintenance window. The installation is suspended during the run.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| Werksreset komplett | Delivery state: both databases are discarded and rebuilt. The user accounts are created anew as well; the owner account has no password afterwards. |
| Benutzerkonten behalten | The database with the user accounts stays in place. All other user data is deleted anyway, and the assignments of the accounts to connections and locations are cleared. |
| Migrationsarchiv mitloeschen | Off by default. An archive of a 3.x system that has already been uploaded then stays available for the following migration. |
| Vorher eine Vollsicherung erstellen | On by default as soon as a backup key is registered. Only this way do files and Elasticsearch data survive the reset. The instance stays suspended longer for it. |
| Ohne Vollsicherung fortfahren, falls sie scheitert | Off by default: if the full backup fails, the reset aborts without deleting anything. |
| Pflicht-Backup | The run always creates a database backup before it deletes anything. |
| CUCM-Verbindungen aktuell | Number of CUCM connections that exist. For a migration this must be 0. |
| Instanz wieder starten | Lifts the suspension after a failed run. It resets nothing and restores no backup. |
Check the result and troubleshoot
- The report shows "Die Lizenz ist erhalten" and, under CUCM-Verbindungen aktuell, the value 0 with the note "Leer — die Instanz taugt als Migrationsziel."
- "Stimmt nicht mit dem Namespace der Instanz ueberein. Gross- und Kleinschreibung zaehlt.": correct the entry.
- "Die Vollsicherung ist gescheitert — der Reset wurde abgebrochen": nothing was deleted and the instance starts again. Fix the cause and start again.
- "Der Lauf ist gescheitert": the instance may be in a half-finished state and stays suspended. Repeat the run or restore the mandatory backup.
- "Exit-Code 1 — durchgelaufen, mit Warnungen" is the normal case for this run. Only a blocker (exit code 2) stops it.
- "Die Lizenz ist NICHT nachweisbar erhalten": install the licence again before you continue working.
- "Eine Vollsicherung ist derzeit nicht moeglich": register a backup key under Sicherung and refresh the page.
- 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.