Data backup and disaster recovery

Data is only as safe as its last working backup. EGroupware has every­thing you need for this – in the cloud and on your own server. Here we show what a good backup strategy looks like and where the focus lies depending on the operating model.

Principles

Three rules for reliable backups

Whether cloud or own server: these three rules protect against data loss, outages and unwanted dependency.

Several copies

Keep at least three versions of your data: the live system and two independent backups.

Separate locations

At least one copy is kept outside the system and the site – for example in S3 storage with another provider.

Test the restore

A backup is only worth something once a restore has worked. Test it regularly.

Building blocks

What EGroupware provides

Four building blocks that can be combined – from automatic basic backups to a copy under your own control.

Automatic backups in the cloud

In the EGroupware Cloud we back up all data automatically: 7 daily and 12 weekly backups in two data centres in Frankfurt am Main. In an emergency, we help you restore your data.

EGroupware backup

Under Admin → Backup you schedule the backup yourself: choose weekdays and time, and it then runs automatically. The target is defined in setup. In the cloud, every backup is stored in both S3 storage systems of our data centres.

Third S3 directory

In addition, every backup can go to a third S3 storage – with a hosting provider of your choice or in your own data centre. You can set this up yourself at any time or with our support.

Mail archive

A mail archive does not replace a backup; it meets the legal retention requirements for emails. We recommend Benno MailArchiv – on premise or in the cloud – or an archive that can be connected easily via OAuth.

Depending on the operating model

Different priorities

The building blocks are the same – what to focus on depends on who runs the server.

In the cloud

We take care of the basic backups. Your focus: an independent copy under your control.

  • Schedule the EGroupware backup under Admin → Backup.
  • Set up a third S3 directory with a hosting provider of your choice – a complete copy outside our data centres.
  • Add a mail archive for the retention requirements.
  • This keeps you able to switch at any time – which is exactly what digital sovereignty means.

On your own server

Backups are entirely your responsibility. Your focus: a reliable routine and a plan for outages.

  • Schedule the EGroupware backup to run automatically.
  • Also set up snapshots of the virtual machine or of the file and backup directories.
  • If the mail server runs locally, back it up as well – in addition to the mail archive.
  • Keep at least one copy off-⁠site, for example in S3 storage.
  • Test the restore regularly.
  • Add a mail archive for the retention requirements.

Cloud or own server? The comparison

Disaster recovery

Restart in the EGroupware Cloud

The simplest way is the third S3 directory: your EGroupware backup also goes to external S3 storage. If your own server fails, an EGroupware instance in our cloud is connected to this S3 storage – the backups are available there immediately and can be restored. Your team keeps working while you rebuild your own server.

Whether you move back afterwards or stay in the cloud is up to you: cloud and own server use the same software.

How the disaster recovery plan worksOWN SERVER
Preparation
EGroupware backup also goes to an external S3 directory
In an outage
Connect an instance in the EGroupware Cloud to this S3 storage and restore the backup
Afterwards
Back to your own server or stay in the cloud
Costs
Please contact us

Ask about a recovery plan

Open standards

Your data stays readable – even without EGroupware

EGroupware works with open standards: emails via IMAP, appointments via CalDAV, contacts via CardDAV and files via WebDAV. In addition, there is JMAP and the EGroupware REST API, which lets you read and write contacts, appointments, tasks and emails automatically. This means your data can not only be opened with common programs and transferred to other systems, but also exchanged automatically on an ongoing basis – with your ERP system, for example. That way, separate systems still work together.

More about the REST API

Digital sovereignty fact-checked

  • Emails: IMAP
  • Appointments: CalDAV
  • Contacts: CardDAV
  • Files: WebDAV
  • Emails, appointments, contacts: JMAP
  • Automated access: REST API

Frequently asked questions about data backup

How often should I back up?

At least daily. The EGroupware backup can be scheduled for any weekday at a fixed time. In the cloud, the automatic daily and weekly backups come on top.

Where does the EGroupware backup go?

The target directory is defined in setup. In the cloud, every backup is stored in both S3 storage systems of our data centres and, on request, additionally in a third S3 storage with a hosting provider of your choice.

Does the backup replace a mail archive?

No. A backup protects against data loss; a mail archive meets the legal retention requirements for emails. We recommend Benno MailArchiv – on premise or in the cloud – or an archive that can be connected via OAuth.

Do you help with the setup?

Yes. You can set up the backup, the third S3 directory and the disaster recovery plan yourself, or we take care of it on request via support contingents.

Review your backup strategy

Together we look at your backups and show what is still missing – in the cloud and on your own server.