Restore error for multiple configurations #1160

New issue

Closed

opened 2025-10-08 21:22:39 +00:00 by markruys · 3 comments

markruys commented 2025-10-08 21:22:39 +00:00

Copy link

What I'm trying to do and why

I have a Borgmatic setup with a single repository and two configurations files 'year.yaml' and 'week.yaml'. Only the 'year.yaml' contains a database configuration definition.

Database restore does work, but gives errors related to the configuration without database configuration ('week.yaml').

Steps to reproduce

21d37bdf8f4e:/# borgmatic restore --archive year-2025-10-08-220606  --database xxxx --verbosity 1

Actual behavior

backupserver: Restoring data sources from archive year-2025-10-08-220606
backupserver: Error running actions for repository
backupserver: No data source dumps were found to restore
/etc/borgmatic.d/week.yaml: Error running configuration
/etc/borgmatic.d/week.yaml: An error occurred
backupserver: Restoring data sources from archive year-2025-10-08-220606
backupserver: Restoring data source xxxx@mariadb (mariadb_databases)

summary:
An error occurred
Error running actions for repository
No data source dumps were found to restore
Error running configuration
/etc/borgmatic.d/year.yaml: Successfully ran configuration file

Need some help? https://torsion.org/borgmatic/#issues

Expected behavior

backupserver: Restoring data sources from archive year-2025-10-08-220606
backupserver: Restoring data source xxxx@mariadb (mariadb_databases)

summary:
/etc/borgmatic.d/year.yaml: Successfully ran configuration file

Other notes / implementation ideas

No response

borgmatic version

2.0.7

borgmatic installation method

Container

Borg version

1.4.1

Python version

3.13.3

Database version (if applicable)

MariaDB 10.6.23

Operating system and version

Alpine 3.21.4

### What I'm trying to do and why I have a Borgmatic setup with a single repository and two configurations files 'year.yaml' and 'week.yaml'. Only the 'year.yaml' contains a database configuration definition. Database restore does work, but gives errors related to the configuration without database configuration ('week.yaml'). ### Steps to reproduce ``` 21d37bdf8f4e:/# borgmatic restore --archive year-2025-10-08-220606 --database xxxx --verbosity 1 ``` ### Actual behavior ``` backupserver: Restoring data sources from archive year-2025-10-08-220606 backupserver: Error running actions for repository backupserver: No data source dumps were found to restore /etc/borgmatic.d/week.yaml: Error running configuration /etc/borgmatic.d/week.yaml: An error occurred backupserver: Restoring data sources from archive year-2025-10-08-220606 backupserver: Restoring data source xxxx@mariadb (mariadb_databases) summary: An error occurred Error running actions for repository No data source dumps were found to restore Error running configuration /etc/borgmatic.d/year.yaml: Successfully ran configuration file Need some help? https://torsion.org/borgmatic/#issues ``` ### Expected behavior ``` backupserver: Restoring data sources from archive year-2025-10-08-220606 backupserver: Restoring data source xxxx@mariadb (mariadb_databases) summary: /etc/borgmatic.d/year.yaml: Successfully ran configuration file ``` ### Other notes / implementation ideas _No response_ ### borgmatic version 2.0.7 ### borgmatic installation method Container ### Borg version 1.4.1 ### Python version 3.13.3 ### Database version (if applicable) MariaDB 10.6.23 ### Operating system and version Alpine 3.21.4

witten commented 2025-10-08 22:02:30 +00:00

Owner

Copy link

Thanks for filing this. The behavior you're seeing is somewhat by design... When you run an action, you're telling borgmatic: Execute this action (independently) for each borgmatic configuration file. So in the case of restore, it tries to restore the selected --database once for each config. That's why you're getting one success and one failure (resulting in an overall failure).

So one thing you can do is specify --config year.yaml along with the rest of your command to select a particular config file. That way you're only running the restore action for that one config file.

Thanks for filing this. The behavior you're seeing is somewhat by design... When you run an action, you're telling borgmatic: Execute this action (independently) for *each* borgmatic configuration file. So in the case of restore, it tries to restore the selected `--database` once for each config. That's why you're getting one success and one failure (resulting in an overall failure). So one thing you can do is specify `--config year.yaml` along with the rest of your command to select a particular config file. That way you're only running the `restore` action for that one config file.

markruys commented 2025-10-09 19:26:03 +00:00

Author

Copy link

Awesome, that did the trick!

I must say I'm really impressed by the high quality of borg and borgmatic, glad I found it. Also documentation is very clear and helpful. Talking of documentation, you might want to add a note how to handle a multi config setup in https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#database-restoration and the --config option.

Awesome, that did the trick! I must say I'm really impressed by the high quality of borg and borgmatic, glad I found it. Also documentation is very clear and helpful. Talking of documentation, you might want to add a note how to handle a multi config setup in https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#database-restoration and the `--config` option.

markruys closed this issue 2025-10-09 19:26:04 +00:00

witten added the

question / support

label 2025-10-09 21:09:55 +00:00

witten commented 2025-10-09 21:11:04 +00:00

Owner

Copy link

Glad to hear that did it! I'm currently revamping the documentation as part of #942, so I'll update the database restoration as you suggest as part of that work.

Glad to hear that did it! I'm currently revamping the documentation as part of #942, so I'll update the database restoration as you suggest as part of that work.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

borgmatic-collective/borgmatic#1160

No description provided.