# Percona xtrabackup binlog Permission denied

**URL:** <https://forums.percona.com/t/percona-xtrabackup-binlog-permission-denied/24108>\
**Category:** Percona XtraBackup\
**Tags:** percona\
**Created:** [August 1, 2023, 3:55pm UTC](https://forums.percona.com/t/percona-xtrabackup-binlog-permission-denied/24108 "2023-08-01T15:55:02Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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:** [August 3, 2023, 3:52pm UTC](https://forums.percona.com/t/percona-xtrabackup-binlog-permission-denied/24108/9 "2023-08-03T15:52:49Z")

</div>

> [@Isreal\_Urephu](#):
>
> whenever i run the percona backup with the above command, it automatically generates a new binlog file

Yes, I understand exactly what you are saying. However, you need to understand that PXB **is not** creating the new binlog. PXB itself does **not** create binary logs. _MySQL_ is creating the new binlog. Whatever permissions `mysqld` is running as is the permissions (owner) that the new binlog file will inherit.

`chmod 777` is incorrect and a bad practice.

I see someone else had a similar issue with PXB and docker. Please [look over this conversation](https://forums.percona.com/t/xtrabackup-in-docker-from-percona-percona-xtrabackup-8-0-for-mysql-8-33-on-docker-fails-with-error-my-012592-innodb-operating-system-error-number-13-in-a-file-operation/23017/4) and see if you have a similar setup.

---

_[View the full topic](https://forums.percona.com/t/percona-xtrabackup-binlog-permission-denied/24108)._