Restore specific schemas #375

New Issue

Closed

opened 2020-12-04 09:26:33 +00:00 by pbakiewicz · 6 comments

pbakiewicz commented 2020-12-04 09:26:33 +00:00

Copy Link

What I'm trying to do and why

At this point using database hooks we can restore whole databases. Problematic is when someone uses multitenancy architucture, so that, one database can hold many separate schemas.

Other notes / implementation ideas

Add to restore optional flag --schema taking schema_name to restore. Therefore comamnd:

borgmatic restore --schema tenant1 --database db1

Will destroy and restore only tenant schema in database db1 and by doing so support multitenancy archituctures.

#### What I'm trying to do and why At this point using database hooks we can restore whole databases. Problematic is when someone uses multitenancy architucture, so that, one database can hold many separate schemas. #### Other notes / implementation ideas Add to restore optional flag `--schema` taking schema_name to restore. Therefore comamnd: ``` borgmatic restore --schema tenant1 --database db1 ``` Will destroy and restore only `tenant` schema in database `db1` and by doing so support multitenancy archituctures.

witten added the

good first issue

label 2023-02-04 21:25:10 +00:00

diivi commented 2023-03-22 13:07:35 +00:00

Collaborator

Copy Link

something like this - https://stackoverflow.com/a/1013956/11304203? (for dump files)

something like this - https://stackoverflow.com/a/1013956/11304203? (for dump files)

witten commented 2023-03-22 16:41:47 +00:00

Owner

Copy Link

I think it's actually easier than that if I'm understanding the ask. pg_restore takes a --schema parameter that restores only objects in the given schema. I don't know of something comparable in MySQL/MongoDB though (which might be just fine).

I think it's actually easier than that if I'm understanding the ask. `pg_restore` takes a `--schema` parameter that restores only objects in the given schema. I don't know of something comparable in MySQL/MongoDB though (which might be just fine).

diivi commented 2023-03-22 17:26:51 +00:00

Collaborator

Copy Link

For MongoDB (scehma == collection?), I think it's straightforward too:
https://www.mongodb.com/docs/cloud-manager/tutorial/restore-single-database/#use-mongorestore-to-restore-the-single-database-or-collection

mongorestore takes a similar --collection parameter.

For MySQL, I didn't find any parameter to restore specific tables yet.
Except some workarounds, like the SO answer I shared above, and dumping just a table to restore it later (can't do for already created dumps, of course).

By the way, if this gets implemented, should there also be a feature to dump a specific schema?

For MongoDB (scehma == collection?), I think it's straightforward too: https://www.mongodb.com/docs/cloud-manager/tutorial/restore-single-database/#use-mongorestore-to-restore-the-single-database-or-collection `mongorestore` takes a similar `--collection` parameter. For MySQL, I didn't find any parameter to restore specific tables yet. Except some workarounds, like the SO answer I shared above, and dumping just a table to restore it later (can't do for already created dumps, of course). By the way, if this gets implemented, should there also be a feature to dump a specific schema?

witten commented 2023-03-23 21:07:25 +00:00

Owner

Copy Link

(Ugh, for some reason I'm not getting all projects.torsion.org comment email notifications. Just saw this now.)

For MySQL, I didn't find any parameter to restore specific tables yet.
Except some workarounds, like the SO answer I shared above, and dumping just a table to restore it later (can't do for already created dumps, of course).

Personally, I think it's okay not to support this feature for MySQL/MariaDB (at least not at first) and only support it for databases that do it natively.

By the way, if this gets implemented, should there also be a feature to dump a specific schema?

That seems reasonable but not required. For dumping, it would probably make sense for it to be a config option in each database's configuration.

(Ugh, for some reason I'm not getting all projects.torsion.org comment email notifications. Just saw this now.) > For MySQL, I didn't find any parameter to restore specific tables yet. Except some workarounds, like the SO answer I shared above, and dumping just a table to restore it later (can't do for already created dumps, of course). Personally, I think it's okay *not* to support this feature for MySQL/MariaDB (at least not at first) and only support it for databases that do it natively. > By the way, if this gets implemented, should there also be a feature to dump a specific schema? That seems reasonable but not required. For dumping, it would probably make sense for it to be a config option in each database's configuration.

witten commented 2023-04-14 23:30:08 +00:00

Owner

Copy Link

@diivi has implemented this via a new --schema argument to borgmatic restore: https://github.com/borgmatic-collective/borgmatic/pull/67

It will be part of the next release!

@diivi has implemented this via a new `--schema` argument to `borgmatic restore`: https://github.com/borgmatic-collective/borgmatic/pull/67 It will be part of the next release!

🎉 1

witten closed this issue 2023-04-14 23:30:09 +00:00

witten referenced this issue from a commit 2023-04-14 23:33:31 +00:00

feat: restore specific schemas (#375).

witten referenced this issue from a commit 2023-04-14 23:33:31 +00:00

Add "borgmatic restore --schema" flag to NEWS (#375).

witten referenced this issue from a commit 2023-04-14 23:41:26 +00:00

Add documentation for "borgmatic restore --schema" (#375).

witten commented 2023-05-16 17:05:11 +00:00

Owner

Copy Link

This was just released in borgmatic 1.7.13!

This was just released in borgmatic 1.7.13!

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

No results found.

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

good first issue

Milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

3 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#375

No description provided.