We'd like to request space‑level selective backup and restore capabilities for Confluence Cloud in Atlassian Backup and Restore (Atlassian Backup and Restore / BRIE).

Problem

Today, Atlassian Backup and Restore operates at the site level for Confluence Cloud.
For large Enterprise Confluence sites, this creates several challenges:

• Backup/restore duration becomes very long when the site contains a large volume of app data and attachments.

• Running frequent backups (e.g. daily) can have a higher risk of performance impact on the application.

• In many real‑world DR scenarios, only a subset of spaces is business‑critical and needs to be protected or restored.

Customers would like to:

• Reduce backup and restore time by limiting the scope to important spaces.

• Minimize performance impact on end‑users during backup windows.

• Align backup/restore scope with their internal criticality (e.g. specific departments, projects or business units).

Without space‑level control, it is hard for large Confluence Cloud customers to:

• Confidently plan RPO/RTO targets around Atlassian Backup and Restore.

• Use it as a practical DR solution for environments with very large datasets.

• Avoid full‑site operations when only one or a few spaces are affected.

Requested capabilities

Customers are specifically asking for:

1 Space‑level include/exclude (whitelist/blacklist)

• Ability to select which spaces are included in a backup.

• Ability to exclude certain spaces from backup (e.g. archive or low‑priority spaces).

• Example use case: run more frequent backups for critical spaces, and less frequent backups for the rest.

2 Option to skip unchanged spaces

• For recurring backups (e.g. daily), skip spaces that have not changed since the last backup.

• This would reduce backup time and load on the system, while still protecting frequently updated content.

3 Space‑level restore

• Ability to restore only selected spaces instead of the entire site.

• Example use cases:

• • Recovering from accidental deletions or corruption in a single space.

• • Rolling back one business unit without affecting the entire organization.

Why this matters

For large Confluence Cloud deployments, full‑site backup and restore is often:

• More time‑consuming than their DR windows allow.

• Heavier in terms of resource usage and potential performance impact.

• Misaligned with the fact that many organizations have a clear distinction between mission‑critical and non‑critical spaces.

Space‑level selective backup and restore would:

• Make Atlassian Backup and Restore more usable for large Enterprise sites.

• Help customers meet stricter RPO/RTO and performance requirements.

• Reduce the need to turn to third‑party backup tools just to get space‑level control.