# Self Hosted Backup

**URL:** <https://forum.ghost.org/t/self-hosted-backup/45220>\
**Category:** Self-hosting\
**Created:** [February 22, 2024, 7:29pm UTC](https://forum.ghost.org/t/self-hosted-backup/45220 "2024-02-22T19:29:27Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![markstos](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/markstos/32/18182_2.png) [@markstos](https://forum.ghost.org/u/markstos)\
**Post date:** [April 2, 2024, 7:25pm UTC](https://forum.ghost.org/t/self-hosted-backup/45220/15 "2024-04-02T19:25:38Z")

</div>

I’ve started building an Ansible role to manage my Ghost installs (discussed here: [Interested in Ansible Role to install Ghost to run with podman containers / systemd / private networking?](https://forum.ghost.org/t/interested-in-ansible-role-to-install-ghost-to-run-with-podman-containers-systemd-private-networking/46226) ).

I’m considering extending it to add this Ansible Role for the Restic backup tool along with BackBlaze B2 backups.

> **[GitHub - roles-ansible/ansible\_role\_restic: Ansible role to deploy and...](https://github.com/roles-ansible/ansible_role_restic)**
>
> Ansible role to deploy and configure restic. Contribute to roles-ansible/ansible\_role\_restic development by creating an account on GitHub.

The idea is simply by defining a new Ghost blog in my Ansible config, per-site backups with Restic would automatically be set up for it. So, rather than restoring a snapshot of the whole filesystem, I would be able to restore just the files or MySQL database for a single Ghost instance.

But since I’m using Ansible, I would only have to define the backup scheme once for it be available to all my Ghost installs.

---

_[View the full topic](https://forum.ghost.org/t/self-hosted-backup/45220)._