Database backups to multiple files #438

New Issue

Closed

opened 2021-07-30 18:33:14 +00:00 by jorgemfm · 7 comments

jorgemfm commented 2021-07-30 18:33:14 +00:00

Copy Link

Allow doing database backup to multiple files, one for each database, instead of a single file when using all option.

This is particular usefull when having to do backups of multiple large databases, to better organize and simplify restoring single databases.

Something like:

hooks:
    mysql_databases:
        - name: all-multiple
          username: user
          password: pass

Allow doing database backup to multiple files, one for each database, instead of a single file when using **all** option. This is particular usefull when having to do backups of multiple large databases, to better organize and simplify restoring single databases. Something like: ``` hooks: mysql_databases: - name: all-multiple username: user password: pass ```

👍 4

witten commented 2021-10-11 16:51:33 +00:00

Owner

Copy Link

This makes sense to me. But is the idea that, after this backup occurs, you'd like to be able to restore a single database manually outside of borgmatic? Or would you expect borgmatic to be able to restore a single database created in this manner? Or perhaps both?

This makes sense to me. But is the idea that, after this backup occurs, you'd like to be able to restore a single database manually outside of borgmatic? Or would you expect borgmatic to be able to restore a single database created in this manner? Or perhaps both?

jorgemfm commented 2021-10-11 21:29:02 +00:00

Author

Copy Link

Manually is already a given, since the file is on text mode, you can easilly extract the files and restore it yourself.

Using borgmatic to restore a single database would be a good feature, but, at least for me, its not as critical as having the files separated, because of the size and to simplify restoration of single databases manually.

Manually is already a given, since the file is on text mode, you can easilly extract the files and restore it yourself. Using borgmatic to restore a single database would be a good feature, but, at least for me, its not as critical as having the files separated, because of the size and to simplify restoration of single databases manually.

witten commented 2021-10-11 22:48:15 +00:00

Owner

Copy Link

Gotcha, thanks!

Gotcha, thanks!

adrian commented 2021-11-07 15:33:18 +00:00

Copy Link

Same here, it would be wonderful if there would be a difference between "all" and "all-by-database". Right now I have a bash script that iterates over /usr/bin/mysql -e 'show databases' -s --skip-column-names to dump per-db files to circumvent this, would be cool if this was a borgmatic option.

I do not see borgmatic responsible for a clean restore, just file backup and file restore, not db restore.

Same here, it would be wonderful if there would be a difference between "all" and "all-by-database". Right now I have a bash script that iterates over `/usr/bin/mysql -e 'show databases' -s --skip-column-names` to dump per-db files to circumvent this, would be cool if this was a borgmatic option. I do not see borgmatic responsible for a clean restore, just file backup and file restore, not db restore.

acsfer commented 2022-04-28 22:25:24 +00:00

Copy Link

Giving more fuel to this request. As for now, a similar solution like @adrian's is in place, having this as an option included to Borgmatic would be great.

I do not see borgmatic responsible for a clean restore, just file backup and file restore, not db restore.

Agree on this too.

Giving more fuel to this request. As for now, a similar solution like @adrian's is in place, having this as an option included to Borgmatic would be great. > I do not see borgmatic responsible for a clean restore, just file backup and file restore, not db restore. Agree on this too.

👍 2

witten referenced this issue 2022-07-05 18:12:41 +00:00

Restoring a specific database conflicts with creating a backup that includes all databases #560

witten referenced this issue from a commit 2022-12-16 07:00:10 +00:00

Optionally dump "all" PostgreSQL databases to separate files instead of one combined dump file (#438, #560).

witten commented 2022-12-16 07:03:25 +00:00

Owner

Copy Link

Proposed configuration for this:

hooks:
    mysql_databases:
        - name: all
          format: sql
          username: user
          password: pass

The idea being that if a specified format is present in your configuration, then you're requesting individual files be dumped in that format instead of in a combined dump file. Similar approach would work for PostgreSQL.

I'm open to feedback on this, of course!

Proposed configuration for this: ```yaml hooks: mysql_databases: - name: all format: sql username: user password: pass ``` The idea being that if a specified `format` is present in your configuration, then you're requesting individual files be dumped _in that format_ instead of in a combined dump file. Similar approach would work for PostgreSQL. I'm open to feedback on this, of course!

👍 1

witten referenced this issue from a commit 2023-01-26 07:31:53 +00:00

Optionally dump "all" PostgreSQL databases to separate files instead of one combined dump file (#438, #560).

witten referenced this issue 2023-01-26 17:06:33 +00:00

Error with database backup #633

witten referenced this issue from a commit 2023-01-26 18:54:37 +00:00

Update documentation about changes to "all" database restores (#438, #560).

witten commented 2023-01-26 23:22:13 +00:00

Owner

Copy Link

This has been implemented in borgmatic 1.7.6! To enable it, add a format option to your "all" database configuration. Then borgmatic will create individual dump files per database. See the documentation for more information: https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#all-databases

This has been implemented in borgmatic 1.7.6! To enable it, add a `format` option to your "all" database configuration. Then borgmatic will create individual dump files per database. See the documentation for more information: https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#all-databases

witten closed this issue 2023-01-26 23:22:13 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

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

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

No Label

Milestone

No items

No Milestone

Assignees

Clear assignees

diivi import_bot witten

No Assignees

4 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#438

No description provided.