# Backup location

**URL:** <https://meta.discourse.org/t/backup-location/100397>\
**Category:** Announcements\
**Tags:** backups, new-feature\
**Created:** [October 24, 2018, 9:25pm UTC](https://meta.discourse.org/t/backup-location/100397 "2018-10-24T21:25:27Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)\
**Post date:** [March 14, 2019, 10:59am UTC](https://meta.discourse.org/t/backup-location/100397/9 "2019-03-14T10:59:52Z")

</div>

> [@RBoy](#):
>
> When once switches from S3 to Local or vice versa, do the existing backups get transferred or are they removed or are they left alone?

Existing backups won’t be touched. You need to delete them manually if you want to free up space.

> [@RBoy](#):
>
> When one see’s the list of backups in the Backup page is there a way to tell the location or are they all from the selected location in the setting?

Only from the selected backup location.

> [@RBoy](#):
>
> What is the meaning of this setting given that backups are no longer “synced” and either on S3 or Local? `Disable the removal of backups from S3 when removed locally.`

The description of the `s3_disable_cleanup` setting needs an update. It disables the removal of backups from S3 and makes the system ignore the value of `maximum_backups` when `backup_location` is set to S3.  
I think we could actually remove the `s3_disable_cleanup` setting and allow disabling the cleanup by setting `maximum_backups` to 0. That would make it work for all backup locations the same way.

---

_[View the full topic](https://meta.discourse.org/t/backup-location/100397)._