Full backup and backup keys

What it is for

The full backup contains everything needed for a restore on a fresh appliance: the database, the files (recordings, announcements, music on hold, CDR files, reports, photos), the CDR history from Elasticsearch and the configuration of the installation. The result is an encrypted archive with the extension .eucbak.

It is encrypted for each registered backup key. Only the public part is stored on the appliance. Only someone who holds the matching private key can decrypt. If every private key of an archive is lost, the archive can no longer be read; the vendor cannot recover it either.

The licence and the identity keys of the appliance are not in the archive. On a restore the target keeps its own licence, and all users log in again.

Prerequisites

A login to the Manager. Critical actions ask for the Manager password again; the confirmation is valid for 5 minutes and only for that action.
The full backup is enabled. Otherwise the page shows "Die Vollsicherung ist in dieser Installation nicht freigeschaltet."
At least one backup key is registered (RSA from 3072 bits, at most 4 keys).
The Manager is opened over HTTPS so that the browser can generate and test keys.
Enough storage in the cluster. The pre-check estimates the requirement and aborts without suspension if it is not sufficient.
A maintenance window. The suspension is limited to at most 120 minutes.

Step by step: generate and register a backup key

Open the Sicherung page in the Manager and go to the Backup-Schluessel card.
In the Schluesselpaar erzeugen area, optionally enter a label, for example "Notfall-Schluessel Tresor".
Select Schluesselpaar erzeugen. The browser generates an RSA key pair with 4096 bits.
Select Private Key herunterladen. The private key is offered exactly once and is never sent to the server.
Store the file safely outside the appliance and tick Ich habe den Private Key sicher abgelegt (ausserhalb dieser Appliance).
Select Public Key hinterlegen and confirm with the Manager password.
Register a second key in the same way and keep it separate from the first.
Test the key later in the Schluessel testen area with Private Key waehlen und testen. The result is "Passt" or "Passt nicht".

Step by step: create and download a full backup

On the Sicherung page, go to the Vollsicherung card.
Select Vollsicherung erstellen.
In the dialog "Vollsicherung jetzt erstellen?", read the list of affected services and the note on retention.
Under Enthalten (einzeln abwaehlbar), deselect individual areas if they are not to be backed up.
Select Stilllegen und sichern.
Follow the steps from "Vorabpruefung (noch ohne Stilllegung)" through "Instanz stilllegen (Beginn der Ausfallzeit)" and "Instanz freigeben (Ende der Ausfallzeit)" to "Abschluss und Aufraeumen".
In the list Archive auf dem Backup-Volume, select Download for the new archive and confirm with the Manager password.
After the download, compare the SHA-256 checksum shown with the checksum of the downloaded file.

Fields and options

Fields and options
Field / action	Meaning and use
Public Key hochladen	Registers a public key you generated yourself (PEM, `BEGIN PUBLIC KEY`) with an optional Bezeichnung.
Fingerprint	SHA-256 identifier of the key. The archive list shows per archive for which keys it is encrypted.
Entfernen (key)	Future full backups are no longer encrypted for this key. Existing archives remain readable with the matching private key.
CUCM-Logs	Area of the backup that can be deselected. Default: included.
Archivierte CDR-CSVs	Can be deselected. Contains the only copy of the CDRs that the retention rule deleted from Elasticsearch. Default: included.
App-Backups	Can be deselected. Default: included.
Never included	Licence, migration archive, CDR test data and working files of a running restore.
Retention on the appliance	Default: only the newest full backup is kept. Older own archives are deleted after the new archive has been verified. Archives found on the volume and uploaded archives are kept.
Herkunft	"eigener Lauf" or "vorgefunden".
Loeschen	Deletes an archive after password confirmation. Blocked while a restore, a transfer or a download uses the archive.
Vollsicherung hochladen	Uploads an `.eucbak` archive in parts, resumable after a connection loss. The restore is started separately afterwards.
Admin-Override: Stilllegung aufheben …	Releases the instance when a run hangs, with a reason and the password. A running backup is aborted.

Check the result and troubleshoot

The card reports "Archiv … erstellt." with the size, and the archive is in the list with date, trigger and key.
"Kein Backup-Schluessel hinterlegt: Vollsicherungen sind deaktiviert.": generate or upload a public key first.
"Erzeugen und Testen im Browser sind nur ueber HTTPS moeglich": open the Manager over HTTPS, or generate the key pair with openssl on a trusted computer and upload only the public key.
An error in the pre-check aborts without suspension. The error code is shown on the run, for example when storage is insufficient.
If the suspension exceeds the maximum duration, the run aborts, cleans up and releases the instance.
Under Hinweise the run names areas that were not captured, for example directories outside the data volume.
While a backup or restore is running, the Manager rejects further backups. This also applies to database backups and the factory reset.
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.