Process overview

Overview of the Confluence recovery process, including available restoration destinations and recovery options.

GitProtect provides a structured Confluence recovery process for protected resources, enabling restoration of content such as pages, spaces, attachments, and associated metadata to a selected recovery point. The recovery workflow supports granular restore scenarios, ensuring data consistency and minimizing downtime during incident recovery operations.

---

General information

With granular recovery, GitProtect enables restoring selected Confluence content without a full environment rollback. You can target specific spaces or groups that were deleted or modified, and selectively restore only the content you need. This speeds up recovery, reduces operational disruption, and prevents overwriting healthy data.

Granular recovery is ideal when only a small portion of information needs to be restored. It’s especially useful when:

• Only a small set of data was lost, corrupted, or changed incorrectly.

• You don’t want to overwrite current data.

• You want a faster, targeted restoration with minimal disruption.

---

Restore options

GitProtect provides two Confluence restore types:

1. Restore spaces — allows you to restore one or more spaces from a selected backup copy.

2. Restore groups — allows you to restore selected or all groups from a backup copy.

---

Restore destination

GitProtect allows you to restore Confluence backups in two ways:

1. To the original Confluence organization — restoring backups directly to the original organization.

2. To a new Confluence organization — restoring backups to a different Confluence organization*.

_{*The organization must already be integrated with GitProtect; adding a new organization during the recovery process is not supported.}