Backups

Last update: Download PDF Edit

1 Introduction

Backups are created every night or on-demand, as described in the Backups section, below.

Backups in the Mendix Cloud have two parts: the database and file documents. A full backup of the database is made each time, while file documents are backed up incrementally.

You can also buy a replication/failover add-on to enable incremental backups with a 15 minute interval for both the database and file documents.

2 Creation and Retention Schedules

The pruning schedule applies to nightly backups and backups initiated by users. If you want to keep a backup for longer than scheduled, you will have to download it.

The following backups are retained:

  • Nightly backups: two weeks
  • Weekly backups (Sunday night): three months
  • Monthly backups (First Sunday night of the month): one year
  • Manual (user-initiated) backups: three months

The start time of nightly backups is between 21:00 and 05:00 UTC.

3 Backups

The Backups page under the Operate category presents options for managing your backups. These are described below.

3.1 Create Backup

This will automatically generate a backup from your application data. See Create a Backup.

3.2 Upload Backup

The sections below present details on uploading data in recent Mendix Cloud versions.

3.2.1 Uploading Data in Mendix Cloud V4

In Mendix Cloud V4, the upload will create a new backup item in your backup list, which you can then restore via the regular restore process. This will ensure less downtime for your application.

Anything you can download you can also upload again, which means you can upload the following:

  • Full Snapshot
  • Database Only
  • Files Only

3.2.2 Uploading Data in Mendix Cloud V3

You must stop the application before executing this process. This functionality is used to transfer data from your local or on-premises application to the cloud environment.

You can upload two types of data:

  • Database
  • Uploaded files (zip or tar.gz)

3.3 Download Backup

You can download one of the following:

  • Full Snapshot
  • Database Only
  • Files Only

See Download a Backup for more information.

3.4 Restore Backup

You can choose the destination environment to which you want to restore the backup. This allows you to, for example, restore a production environment backup to an acceptance environment.

If you restore a backup that was originally deployed with an older Mendix version, you will get a warning. You can still restore the backup, but you will have to deploy the older model later on.

See Restore a Backup for more information.

3.5 Details

When you click Details, you can view the following details:

Backup Details Cloud Version Description
Origin of Environment V3 From which environment this backup was made
Status V3 & V4 The status of the backup. Backups can have the status of Queued, Running, Failed, and Completed
Created by/
Type
V3
V4
The name of the person who created the backup. Automated system backups are named Nightly
ID/
Snapshot id
V3
V4
Unique identifier for the backup snapshot
Date/
Created on
V3
V4
The creation date of the backup
Expires on V3 & V4 The date on which the backup will be removed from the system
Mendix version V3 & V4 The version of the deployment package used during backup creation
Comment V3 & V4 A specific comment added to the backup

At the bottom of the screen, you can click Delete to delete this particular backup.

4 Known issues

Mendix Cloud V4 backups that contain a very large number of files (that is, greater than about 50,000) will experience slow performance for all backup operations (create, download, restore, and upload). This is because of the inherent overhead associated with each file; as the number of files increases, this overhead becomes quite significant, and can be in the order of hours.

5 Read More