# Creating a backup plan
## Backup plan setup
{% stepper %}
{% step %}
Login to **GitProtect Management Service**, 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** environment you want to include in the backup process, and choose the repositories to back up.
{% hint style="warning" %}
In **GitProtect**, you can select repositories based on custom properties, but these properties **must be configured at the organization level in GitHub**. During synchronization, **GitProtect** 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 **Management Service**. For the feature to work correctly, **the token used for authorization must also include the read:org permission**.
{% endhint %}
{% hint style="success" %}
Optionally, **GitProtect** allows you to protect the entire **GitHub** 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 **GitProtect 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 **GitProtect** 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-backup-destination-overview-and-setup/cloud-storage" %}
[cloud-storage](https://helpcenter.gitprotect.io/storage-backup-destination-overview-and-setup/cloud-storage)
{% endcontent-ref %}
{% content-ref url="../../../../management/scheduler-and-retention" %}
[scheduler-and-retention](https://helpcenter.gitprotect.io/management/scheduler-and-retention)
{% endcontent-ref %}
**Add plan** button in the top bar.
{% endstep %}
{% step %}
Select **GitHub** from the list.
{% endstep %}
{% step %}
Select (or add) the **GitHub** environment you want to include in the backup process, and choose the repositories to back up.
{% hint style="warning" %}
In **GitProtect**, you can select repositories based on custom properties, but these properties **must be configured at the organization level in GitHub**. During synchronization, **GitProtect** 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 **Management Service**. For the feature to work correctly, **the token used for authorization must also include the read:org permission**.
{% endhint %}
