# Fdbbackup expire timing out

**URL:** <https://forums.foundationdb.org/t/fdbbackup-expire-timing-out/4175>\
**Category:** Using FoundationDB\
**Created:** [October 3, 2023, 9:54am UTC](https://forums.foundationdb.org/t/fdbbackup-expire-timing-out/4175 "2023-10-03T09:54:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hbs](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/hbs/32/1419_2.png) [@hbs](https://forums.foundationdb.org/u/hbs)\
**Post date:** [October 3, 2023, 9:54am UTC](https://forums.foundationdb.org/t/fdbbackup-expire-timing-out/4175/1 "2023-10-03T09:54:55Z")

</div>

Hi,

often when attempting to perform a `fdbbackup expire` call to purge all backups, the call fails with an error indicating a time out when in the `Describing backup` or `Listing files` phase. There is no alternative than to retry the call over and over again until it goes through.

Is there a knob that can be tuned to increase the time out or force `fdbbackup` to perform multiple attempts?

---

<div class="post-metadata">

**Author:** ![hbs](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/hbs/32/1419_2.png) [@hbs](https://forums.foundationdb.org/u/hbs)\
**Post date:** [October 4, 2023, 2:27pm UTC](https://forums.foundationdb.org/t/fdbbackup-expire-timing-out/4175/2 "2023-10-04T14:27:17Z")

</div>

Found out the timeouts could be modified in the blobstore URL, using the `connect_tries`, `connect_timeout` and `request_timeout_min` parameters. That did the trick.
