Error When Using BR Backup for TiDB Deployed on K8s

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: k8s部署的tidb使用br备份时报错

| username: daylight

[Test Environment for TiDB] Testing
[TiDB Version] v5.4.0
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Phenomenon and Impact] Error occurred when using br backup for TiDB deployed on k8s
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

It seems to be an issue on the official website, kv is not mounted, but this has already been deployed, how to remount it is a problem.

| username: DBAER | Original post link

Is the PD IP written correctly?

| username: daylight | Original post link

That’s correct.

| username: yiduoyunQ | Original post link

To summarize the issue, if the question is “TiKV has already been deployed, but the NFS disk is not mounted, how to remount it?” you can directly use additionalVolumes & additionalVolumeMounts to mount it.

| username: yytest | Original post link

The problem is indeed quite difficult to handle, I haven’t seen similar logs before.

| username: hacker_77powerful | Original post link

I encountered this issue once before. The system user using BR was root, but the actual user writing to the disk was omm. The backup failed because omm did not have write permissions for the shared directory.