Issue

The application utilizes the Mendix cross-region backup service; however, only a single record is generated containing the snapshot ID. This implementation does not include any metadata or identifiers to indicate the originating region of the backup. As a result, it is currently impossible to determine which region the backup belongs to, creating challenges for tracking, auditing, and troubleshooting.

Environment

• Free app
• Applications hosted in Mendix Cloud

Cause

The Mendix backup service creates a single record for each backup operation, which is why it appears as only one entry in the system. Internally, the service replicates the AWS S3 snapshot data from the primary region to a secondary (replication) region while retaining the same Snapshot ID. The replication region exists solely for resilience and disaster recovery.

As a result, when performing a GET request through the Mendix Backup API or viewing backups in the Mendix Cloud Portal UI, only one snapshot record is returned. Although the data is replicated across regions, the snapshots share the same identifier, making them indistinguishable at the record level between the primary and replication regions.

Solution / Workaround

Not Applicable

Additional information

Mendix Documentation: Backups - Data location