# Process overview

**The Jira backup process overview outlines the steps GitProtect takes to securely back up your Jira organization's data.**

***

## General information

**GitProtect** is designed to protect **DevOps** ecosystems, including **Jira**.

With **GitProtect**, you can create separate backup plans for critical and non-critical spaces within the same **Jira** instance. Each plan can use different rotation scheme, ensuring your entire **Jira** environment is reliably protected.

For example, you can use the recommended Grandfather-Father-Son (GFS) rotation scheme for backup plans protecting critical spaces and metadata that change daily — or even more frequently. For unused spaces that must be retained for future reference, you can create a separate backup plan with a custom rotation scheme. This type of backup primarily serves **Jira** archival purposes, and with unlimited retention, copies can be stored for as long as needed — even indefinitely.

{% hint style="success" %}
You can delete spaces from your **Jira** account while keeping a copy in storage, which helps bypassing **Jira** limits.
{% endhint %}

***

## Backup method

{% hint style="danger" %}
Due to **Atlassian** API changes that took effect on March 30, 2026, the disaster recovery backup and restore functionalities are no longer available. **To ensure continued protection of your Jira data, please switch to the granular backup plan.** Data previously protected with disaster recovery backups can still be restored using the disaster recovery or granular recovery option.
{% endhint %}

When creating a backup plan, you define how **GitProtect** protects your data. For **Jira**, the default data protection method is granular backup.

Granular backup focuses on individual **Jira** components, such as issues (work items), spaces (projects), or attachments. In granular backup, each space (project) is handled as an individual task — if an error occurs during execution, only the spaces that were successfully backed up will have a restorable backup available.

The granular data protection method allows you to:

* [x] Select spaces (projects) to protect (all, selected, based on rules).
* [x] Select individual data to back up**\***.
* [x] Exclude **Jira** issues (work items).
* [x] Skip corrupted issue (work item) attachments.
* [x] Restore specific work items, spaces, assets, and other **Jira** objects without the need to restore the entire **Jira** organization.

<sub>**\***</sub><sub>Select individual data to protect, along with a short description of the dependencies visible in the interface (includes information about object activity history, which is disabled by default because it may affect backup performance).</sub>

***

## Backup storage

**GitProtect** is a multi-storage system that allows you to store your data in the cloud, locally, or in a hybrid/multi-cloud environment. You can use different storage types to replicate backups, reduce the risk of outages or disasters, and comply with the 3-2-1 backup rule — which means having at least three copies of your data on two different storage types, with at least one copy stored in the cloud.

{% hint style="info" %}
Learn more about supported storage types in [this article](/storage/supported-storage-types.md).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpcenter.gitprotect.io/backup-and-recovery/jira/backup/process-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.