# Performing backups to S3 with wsrep\_desync

**URL:** <https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813>\
**Category:** Percona XtraBackup\
**Created:** [June 9, 2021, 5:53pm UTC](https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813 "2021-06-09T17:53:19Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethaniel](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@ethaniel](https://forums.percona.com/u/ethaniel)\
**Post date:** [June 9, 2021, 5:53pm UTC](https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813/1 "2021-06-09T17:53:19Z")

</div>

Dear Forum,

Is it true that xtrabackup does not set wsrep\_desync=ON by itself and requires a wrapper script?  
I have a 3-node cluster and have been using bgbackup (which is now archived) with great success. But now, that I want to try doing backups to S3 with xbcloud, I couldn’t figure out if xtrabackup desyncs the node before the process or not.

Can someone please advise?

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [June 9, 2021, 7:46pm UTC](https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813/2 "2021-06-09T19:46:37Z")

</div>

xtrabackup does not desync the node because it is not necessary. Xtrabackup doesn’t require special locks (ie: FTWRL) that would prevent writes. xtrabackup is a hot-backup tool.

---

<div class="post-metadata">

**Author:** ![ethaniel](https://avatars.discourse-cdn.com/v4/letter/e/ba8739/32.png) [@ethaniel](https://forums.percona.com/u/ethaniel)\
**Post date:** [June 9, 2021, 8:20pm UTC](https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813/3 "2021-06-09T20:20:03Z")

</div>

The problem is that xtrabackup might saturate my disks, while xbcloud might saturate my network, slowing down the whole cluster as a result.

It would be better to desync the node first, run the backups, wait until it catches up with the cluster and then sync it back with the cluster.

Looks like a wrapper is needed, oh well. Thank you for the info!

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [June 10, 2021, 12:37pm UTC](https://forums.percona.com/t/performing-backups-to-s3-with-wsrep-desync/10813/4 "2021-06-10T12:37:13Z")

</div>

You can also control the resource consumption of xtrabackup with the [–throttle](https://www.percona.com/doc/percona-xtrabackup/2.4/advanced/throttling_backups.html) option. For xbcloud the default is to run 1 concurrent thread only, so if you throttle xtrabackup which comes first in the pipe, the network consumption should be limited as well.