Installation, updates & backup
Transferring backups to an external server on a schedule
Set up a remote target over SFTP, FTPS or FTP, define the schedule and check the history.
In EasyUC: Manager → Sicherung → Remote-Ziel / Zeitplan / Verlauf
What it is for
A backup that only exists on the appliance does not help when the appliance fails. The Manager therefore transfers backups to a server of your choice, over SFTP, FTPS or FTP. The connection is initiated by the appliance.
The schedule creates database backups or full backups automatically and transfers them. On the server, retention is by count, separately for database backups and full backups.
Prerequisites
- A login to the Manager.
- A server with SFTP, FTPS or FTP access and an account with write permission in the target directory. SFTP is recommended.
- Network clearance from the appliance to the server (SFTP: TCP 22, FTP/FTPS: TCP 21, each as the default).
- For scheduled full backups: at least one registered backup key and, with SFTP, a confirmed host key.
Step by step: set up the remote target
Step by step: define the schedule
Fields and options
| Field / action | Meaning and use |
|---|---|
| Zielverzeichnis | Without a leading slash relative to the login directory, with a slash absolute. It is created if it does not exist. |
| Aufbewahrung DB-Backups | Number of database backups on the server. Default 7. 0 = keep everything. |
| Aufbewahrung Vollsicherungen | Number of full backups on the server. Default 2. 0 = keep everything. |
| Bestaetigter Host-Key | The confirmed fingerprint of the SFTP server. Afterwards the Manager rejects any other host key. Entfernen deletes the confirmation. |
| Zertifikatsfehler ignorieren | FTPS only, for self-signed certificates. Not recommended. |
| Alle… Stunden | Interval for the hourly rhythm, 1 to 23. |
| Tag im Monat | 1 to 28, so that the run takes place in every month. |
| Cron-Ausdruck | Five fields: minute, hour, day, month, weekday. Example 0 3 * * 1-5 = on working days at 03:00. Default 30 2 * * *. |
| Wartungsfenster | Mandatory for scheduled full backups. Suggestion 02:00 to 05:00. Runs outside it are logged as skipped. |
| Zeitzone | Default Europe/Berlin. |
| DB sichern & uebertragen | Creates a database backup immediately and transfers it. |
| Vollsicherung & uebertragen | Creates a full backup immediately and transfers it after the instance has been released. |
| Verlauf | The most recent transfers with start, type, trigger, status, file, size, duration and message. |
Check the result and troubleshoot
- The history shows the run with file and size, and the file is on the server.
- "Geplante Vollsicherung fehlgeschlagen: kein Backup-Schluessel" as a banner: register a public key under Backup-Schluessel.
- "Ohne Backup-Schluessel ist der Zeitplan fuer Vollsicherungen deaktiviert.": the schedule cannot be saved this way.
- Warning "weicht vom bestaetigten Host-Key ab": the server has changed its key or the connection leads to another system. Confirm only after checking with the operator.
- Full backups are only transferred or imported over SFTP with a confirmed host key. Database backups continue without confirmation, with a warning.
- If a transfer fails, the local archive remains valid. The history names the error.
- A scheduled run is logged as skipped when it falls outside the maintenance window or another backup or restore is running.
- FTP transmits credentials in clear text. The full backup itself stays encrypted, the database backup does not.
- 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.