Installation, updates & backup
Disaster recovery: building a new appliance from a full backup
On a fresh appliance without an EasyUC installation, rebuild the instance from an .eucbak archive.
In EasyUC: Manager → Sicherung → Wiederherstellung aus einer Vollsicherung → Disaster Recovery
What it is for
If an appliance fails completely, you rebuild the installation on a new appliance from a full backup. The disaster recovery wizard creates the EasyUC instance with the selected release and then restores files, CDR history, database and configuration.
The new appliance keeps its own identity keys and needs its own licence. Licence and identity keys do not come from the archive. All users log in again.
Prerequisites
- A freshly initialised appliance with the Manager but without an EasyUC installation. The Manager is at the same or a newer level than on the source system.
- The images of the target release are on the appliance. The target release has the same major version as the source and at least its version.
- The release file of the target release (YAML or JSON), the same file as for the installation.
- The archive and the private key of a key it is encrypted for.
- If possible, the same IP address and host name as the source. Otherwise DNS, the targets in CUCM and the ACD media IP have to be adjusted afterwards.
- For an import from the server: the remote target on the Sicherung page of the new appliance, with a confirmed host key for SFTP.
Step by step
Fields and options
| Field / action | Meaning and use |
|---|---|
| Quelle ausser Betrieb oder getrennt | Mandatory confirmation. It is logged. |
| ACD-Media-IP aus dem Archiv uebernehmen | Without the tick the value stays empty and is set later in the configuration of the installation. |
| ACD-JAR-Host-Pfad aus dem Archiv uebernehmen | Only tick this if the path exists on this host. |
| Legacy-Quelle mit ACD-Media bzw. Teams | Only for sources without a module selection and with manually created additional services. Select the modules of the new instance or continue without these additional components. |
| Licence notice | This system needs its own licence. It receives at most one restore licence, valid for 7 days. |
| Assistent neu beginnen | Discards the entries and starts from the beginning. |
| As before | Database, files, CDR history, modules, storage sizes, the host name of the web interface and, if selected, certificates and Manager passwords. |
| Different from before | Licence, logins of all users, backup keys, two-factor setup of the Manager, EasyUC version (that of the target release), and cluster, nodes and IP addresses of the new appliance. |
Check the result and troubleshoot
- The report names source and target version, the number of files and CDR documents, the licence case and the next steps. The instance is released afterwards.
- "Auf diesem System existiert bereits eine EasyUC-Instanz … bitte den Restore-Assistenten verwenden.": the wizard is only intended for systems without an installation.
- "Entscheidung zu den Zusatz-Deployments der Legacy-Quelle noetig": the run stopped before any change. Select Mit Modulauswahl neu starten and select the private key again.
- If images of the target release are missing, the run stops before the instance is created.
- If the run fails after the instance has been created, it stays suspended. The wizard shows it under Nicht abgeschlossene Disaster-Recovery-Laeufe.
- With a new IP address or host name: change the DNS record, adjust the billing server for CDR delivery, the External Call Control profile and SIP trunks in CUCM, and enter the ACD media IP.
- The two-factor login of the Manager has to be set up again on the new appliance.
- 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.