# Backup to DigitalOcean Spaces fails if uploads and backup are both set to S3

**URL:** <https://meta.discourse.org/t/backup-to-digitalocean-spaces-fails-if-uploads-and-backup-are-both-set-to-s3/106916>\
**Category:** Product Support\
**Created:** [18.Январь.2019 15:21:11 UTC](https://meta.discourse.org/t/backup-to-digitalocean-spaces-fails-if-uploads-and-backup-are-both-set-to-s3/106916 "2019-01-18T15:21:11Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [28.Январь.2019 19:21:45 UTC](https://meta.discourse.org/t/backup-to-digitalocean-spaces-fails-if-uploads-and-backup-are-both-set-to-s3/106916/8 "2019-01-28T19:21:45Z")

</div>

> [@gerhard](#):
>
> Essentially you need to either use two different buckets or a prefix for the backup bucket.

So my solution of a prefix for the _images_ bucket was the only one that didn’t work. 🙂

That explains it. Thanks!

FWIW, it would seem that if the multisite default of sticking backups in a backups directory would solve the two-bucket problem, but you’ve probably mucked with this code enough for now.

---

_[View the full topic](https://meta.discourse.org/t/backup-to-digitalocean-spaces-fails-if-uploads-and-backup-are-both-set-to-s3/106916)._
