Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Backup Restore fails if we use same name as source db pod

Open
#767 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
azure, postgresql
Domain
cloud, databases

Research direction

Start by reproducing the restore with CNPG 1.26 and Barman Plugin 0.11.0 on Azure Blob Storage, using the same cluster name after deleting the original. Collect the restore failure output and compare it with the successful restore under a different name; done means identifying the cause and confirming whether same-name restoration works or documenting the limitation.

Written by the indexing model from the issue text.

Description

bug

@dosu
I am using CNPG 1.26 with Barman Plugin 0.11.0 on ak8s.

I taken the backup of one of DB cluster on azure blob stoarage.

I restore db with different name from that backup and it worked.

Now i deleted that original db . tried to restore db from backup with same db cluster name and it is failing. why we cannot use same db name.

Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 7h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/plugin-barman-cloud

All issues in cloudnative-pg/plugin-barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.