# Running pgBackRest with pg\_tde: A Practical Percona … | Percona Community

**URL:** <https://forums.percona.com/t/running-pgbackrest-with-pg-tde-a-practical-percona-percona-community/40382>\
**Category:** Community website\
**Created:** [March 20, 2026, 12:15pm UTC](https://forums.percona.com/t/running-pgbackrest-with-pg-tde-a-practical-percona-percona-community/40382 "2026-03-20T12:15:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![daniil.bazhenov](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniil.bazhenov/32/62_2.png) [@daniil.bazhenov](https://forums.percona.com/u/daniil.bazhenov)\
**Post date:** [March 20, 2026, 12:15pm UTC](https://forums.percona.com/t/running-pgbackrest-with-pg-tde-a-practical-percona-percona-community/40382/1 "2026-03-20T12:15:13Z")

</div>

Not every PostgreSQL installation requires encryption at rest. However, for organizations mandating strict data protection and privacy standards, it is often non-negotiable. When security policies are this rigorous, you need a strategy that protects your data without sacrificing recoverability.

* * *
This is a companion discussion topic for the original entry at [https://percona.community/blog/2026/03/10/running-pgbackrest-with-pg\_tde-a-practical-percona-walkthrough](https://percona.community/blog/2026/03/10/running-pgbackrest-with-pg_tde-a-practical-percona-walkthrough)