# Enable hidden setting to include S3 uploads in the backups

**URL:** <https://meta.discourse.org/t/enable-hidden-setting-to-include-s3-uploads-in-the-backups/276535>\
**Category:** Self-Hosting\
**Tags:** backups, how-to\
**Created:** [August 25, 2023, 12:32am UTC](https://meta.discourse.org/t/enable-hidden-setting-to-include-s3-uploads-in-the-backups/276535 "2023-08-25T00:32:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [August 25, 2023, 1:12am UTC](https://meta.discourse.org/t/enable-hidden-setting-to-include-s3-uploads-in-the-backups/276535/4 "2023-08-25T01:12:48Z")

</div>

> [@vinothkannans](#):
>
> I think you don’t need to destroy and the restart is enough

I’m certain you need to destroy and start to change the env variables applied to the container.

Of course, if they have done upgrades with docker manager, those will be lost when the container is destroyed, which is why the rebuild is the safest recommendation. Maybe it’s best to recommend the rebuild since it’s the most foolproof.

---

_[View the full topic](https://meta.discourse.org/t/enable-hidden-setting-to-include-s3-uploads-in-the-backups/276535)._