# Geplante Multisite-Backups laufen nur für eine Website

**URL:** <https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486>\
**Category:** Support\
**Created:** [11. August 2016 um 03:50 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486 "2016-08-11T03:50:17Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![brahn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brahn/32/109267_2.png) [@brahn](https://meta.discourse.org/u/brahn)\
**Post date:** [11. August 2016 um 03:50 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/1 "2016-08-11T03:50:17Z")

</div>

I have 3 sites in a standalone multisite setup and recently noticed that only one of them is actually performing the scheduled backup.  
There does not appear to be anything in the logs about the other sites failing to backup. The `unicorn.stdout.log` shows only the one site being backed up. A manual backup of all sites works fine.  
It seems to have stopped working around the time I updated from 1.4 to 1.5 (on 1.6 now but no change).

Any ideas on how to diagnose this?

---

<div class="post-metadata">

**Author:** ![brahn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brahn/32/109267_2.png) [@brahn](https://meta.discourse.org/u/brahn)\
**Post date:** [12. August 2016 um 00:39 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/2 "2016-08-12T00:39:05Z")

</div>

Could the issue be connected to this fix?

[https://github.com/discourse/discourse/commit/737c6067104e06a9b96c11956062e10eccebf9e9](https://github.com/discourse/discourse/commit/737c6067104e06a9b96c11956062e10eccebf9e9)

The cancel\_scheduled\_job call in ScheduleBackup is different to the others I found in that it doesn’t supply any args.

My WAG is that perhaps each RailsMultisite iteration in the base scheduler is cancelling the previous scheduled backup leaving only the last one to run?!

---

<div class="post-metadata">

**Author:** ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)\
**Post date:** [12. August 2016 um 11:18 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/3 "2016-08-12T11:18:41Z")

</div>

While the issue was not related to that commit (_the bug was present before_), it got me to the right point: we were _indeed_ canceling jobs for all the sites on a multisite install… 😑

[https://github.com/discourse/discourse/commit/7db2083d4553001acbb12771a261e8dc61151eaf](https://github.com/discourse/discourse/commit/7db2083d4553001acbb12771a261e8dc61151eaf)

---

<div class="post-metadata">

**Author:** ![brahn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brahn/32/109267_2.png) [@brahn](https://meta.discourse.org/u/brahn)\
**Post date:** [13. August 2016 um 12:47 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/4 "2016-08-13T12:47:09Z")

</div>

That’s awesome news, thanks!  
I’m tracking the stable branch so I assume I will need to wait until v1.7 before I see this fix?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [14. August 2016 um 23:47 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/5 "2016-08-14T23:47:35Z")

</div>

Yes, in general we only backport egregious bugs and security fixes into stable.

If you are going to be stuck on stable you can always look at adding a cron job to backup your sites.

---

<div class="post-metadata">

**Author:** ![brahn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brahn/32/109267_2.png) [@brahn](https://meta.discourse.org/u/brahn)\
**Post date:** [15. August 2016 um 05:50 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/6 "2016-08-15T05:50:27Z")

</div>

Thanks @sam, understood.

BTW, when I marked the earlier post a the solution it seems to have removed the preview of the link. Is that supposed to happen?

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [15. August 2016 um 05:54 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/7 "2016-08-15T05:54:14Z")

</div>

That is some weird bug…

---

<div class="post-metadata">

**Author:** ![brahn](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/brahn/32/109267_2.png) [@brahn](https://meta.discourse.org/u/brahn)\
**Post date:** [15. August 2016 um 05:55 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/8 "2016-08-15T05:55:24Z")

</div>

Oh, its back now anyway.

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [15. August 2016 um 05:55 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/9 "2016-08-15T05:55:57Z")

</div>

Yeah I rebuilt the html

---

<div class="post-metadata">

**Author:** ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)\
**Post date:** [8. Juni 2024 um 12:45 UTC](https://meta.discourse.org/t/multisite-scheduled-backup-is-only-running-for-one-site/48486/10 "2024-06-08T12:45:26Z")

</div>

Dieses Thema wurde nach 2858 Tagen automatisch geschlossen. Neue Antworten sind nicht mehr möglich.
