--database does not find database dump when port is specified for database in config #1322
Labels
No labels
blocked
breaking
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
borgmatic-collective/borgmatic#1322
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
I'm trying to restore selected databases from my archives for the purpose of not having to restore all of them at once. This however results in an error saying the dumps don't exist:
$PATH_TO_REPO: Cannot restore data source dump immich missing from archive. This error goes away when I don't specify the port in my borgmatic config (it's postgres default port 5432 but I like to be explicit).Steps to reproduce
borgmatic create --config path/to/this/config.yamlborgmatic restore --archive latest --database nextcloudActual behavior
When the port is specified, the
restorefails with the following output:Expected behavior
It works.
Other notes / implementation ideas
No response
borgmatic version
2.1.5
borgmatic installation method
Either pip or package, don't remember and can check later if needed
Borg version
1.4.2
Python version
3.13.7
Database version (if applicable)
18.4
Operating system and version
Fedora 42
Thanks for filing this! It's fixed in main and will be part of the next release. I also fixed the case of the reverse—starting with an explicit default port in config, dumping, and then removing the port from the config and doing a restore.
Note that I only bothered to fix this when using Borg 1.4+. Should be fine for your case, but I'm calling this out in case anyone else stumbles across the issue. If using Borg 1.2... upgrade!
Ah, looks like I only fixed this when not using the
--databaseflag. I'm gonna have to fix it a little harder...Oh I lied; that case actually works as well! I just had a typo on my command-line. Calling this done again.
Thank you!
Released in borgmatic 2.1.7!