# Creating a backup plan
## Backup plan setup
{% stepper %}
{% step %}
Login to [**XMS**](#user-content-fn-1)[^1], open the **Plans** > **Backup** tab and click the **Add plan** button in the top bar.
{% endstep %}
{% step %}
Select **GitHub** from the list.
{% endstep %}
{% step %}
Select (or add) the **GitHub Enterprise** environment you want to include in the backup process, and choose the repositories to back up.
{% hint style="warning" %}
In **Xopero ONE**, you can select repositories based on custom properties, but these properties **must be configured at the organization level in GitHub**. During synchronization, **Xopero ONE** retrieves the property definitions from the organization and the assigned values from the repositories. After synchronization, the panel displays a list of all properties fetched from every organization on the **GitHub** side that was added to **XMS**. For the feature to work correctly, **the token used for authorization must also include the read:org permission**.
{% endhint %}
{% hint style="success" %}
Optionally, **Xopero ONE** allows you to protect the entire **GitHub Enterprise** environment.
{% endhint %}
{% endstep %}
{% step %}
Specify a name for the backup plan.
{% endstep %}
{% step %}
Select the appropriate metadata that you want to back up. Here, you can also change the **default worker**, which is the device directly responsible for the backup process of your repositories.
{% hint style="success" %}
You can have multiple workers and assign different workers to each backup plan.
{% endhint %}
{% hint style="info" %}
It is worth noting that the **cloud worker** (a cloud-installed **Xopero ONE** worker) allows you to perform cloud-to-cloud backups if you want to store your backups in the cloud.
{% endhint %}
{% endstep %}
{% step %}
Select one of the locations assigned to your **Xopero ONE** instance as storage.
{% endstep %}
{% step %}
Customize the scheduler and specify how long your data should be retained. If needed, adjust the advanced settings to suit your needs.
{% endstep %}
{% step %}
If necessary, adjust the advanced settings such as encryption, error handling, or bandwidth limits to fit your requirements.
{% endstep %}
{% step %}
Double-check your data and click **Save** to create the backup plan.
{% endstep %}
{% endstepper %}
***
## Useful links and items
{% content-ref url="../../../../storage/cloud-storage" %}
[cloud-storage](https://helpcenter.xopero.com/xopero-one-en/storage/cloud-storage)
{% endcontent-ref %}
{% content-ref url="../../../../deployment-and-configuration/xopero-one-worker" %}
[xopero-one-worker](https://helpcenter.xopero.com/xopero-one-en/deployment-and-configuration/xopero-one-worker)
{% endcontent-ref %}
{% content-ref url="../../../../management/scheduler-and-retention" %}
[scheduler-and-retention](https://helpcenter.xopero.com/xopero-one-en/management/scheduler-and-retention)
{% endcontent-ref %}
[^1]: Xopero ONE Management Service
---
# 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.xopero.com/xopero-one-en/backup-and-recovery/devops/github-enterprise/backup/creating-a-backup-plan.md?ask=
```
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.
**Add plan** button in the top bar.
{% endstep %}
{% step %}
Select **GitHub** from the list.
{% endstep %}
{% step %}
Select (or add) the **GitHub Enterprise** environment you want to include in the backup process, and choose the repositories to back up.
{% hint style="warning" %}
In **Xopero ONE**, you can select repositories based on custom properties, but these properties **must be configured at the organization level in GitHub**. During synchronization, **Xopero ONE** retrieves the property definitions from the organization and the assigned values from the repositories. After synchronization, the panel displays a list of all properties fetched from every organization on the **GitHub** side that was added to **XMS**. For the feature to work correctly, **the token used for authorization must also include the read:org permission**.
{% endhint %}
