# Gravity Sync, an easy way to keep multiple Pi-hole In-sync

**URL:** <https://discourse.pi-hole.net/t/gravity-sync-an-easy-way-to-keep-multiple-pi-hole-in-sync/33545>\
**Category:** Customizing Pi-hole\
**Created:** [May 28, 2020, 7:18pm UTC](https://discourse.pi-hole.net/t/gravity-sync-an-easy-way-to-keep-multiple-pi-hole-in-sync/33545 "2020-05-28T19:18:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![\_popeofmope](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/_/df788c/32.png) [@\_popeofmope](https://discourse.pi-hole.net/u/_popeofmope)\
**Post date:** [May 29, 2020, 10:49pm UTC](https://discourse.pi-hole.net/t/gravity-sync-an-easy-way-to-keep-multiple-pi-hole-in-sync/33545/7 "2020-05-29T22:49:20Z")

</div>

Cool solution! I also wanted to run redundant Pi-holes. I wound up deploying to Docker Swarm with GlusterFS to keep the instances in sync. Haven't had any issues with the 5.0 db. My latest blog post is about swarm MACVLAN routing and links to my Ansible playbook, [http://jpft.win/docker-swarm-macvlan/](http://jpft.win/docker-swarm-macvlan/)

---

_[View the full topic](https://discourse.pi-hole.net/t/gravity-sync-an-easy-way-to-keep-multiple-pi-hole-in-sync/33545)._