Support for tar backup extraction #300

New Issue

Closed

opened 2020-04-17 14:15:04 +00:00 by floriplum · 3 comments

floriplum commented 2020-04-17 14:15:04 +00:00

Copy Link

What I'm trying to do and why

Export my Backup to a program behind a pipe or restore it to a tar file

Other notes / implementation ideas

I basically would like to do what export-tar does(https://borgbackup.readthedocs.io/en/stable/usage/tar.html).

Environment

borgmatic version: [1.5.1]

borgmatic installation method: [pip]

Borg version: [1.1.9]

Python version: [3.7.3]

operating system and version: [Debian 10]

#### What I'm trying to do and why Export my Backup to a program behind a pipe or restore it to a tar file #### Other notes / implementation ideas I basically would like to do what export-tar does(https://borgbackup.readthedocs.io/en/stable/usage/tar.html). #### Environment **borgmatic version:** [1.5.1] **borgmatic installation method:** [pip] **Borg version:** [1.1.9] **Python version:** [3.7.3] **operating system and version:** [Debian 10]

witten commented 2020-04-23 05:12:45 +00:00

Owner

Copy Link

Nice idea. Would you use a borgmatic export tar feature to write to stdout, or would you want to write directly to file? I'm just trying to think through how a stdout tar export would interact with logging.

Also, out of curiosity, what's your use case for exporting an archive in tar format? As opposed to, say, extracting or mounting? Thanks!

Nice idea. Would you use a borgmatic export tar feature to write to stdout, or would you want to write directly to file? I'm just trying to think through how a stdout tar export would interact with logging. Also, out of curiosity, what's your use case for exporting an archive in tar format? As opposed to, say, extracting or mounting? Thanks!

floriplum commented 2020-04-27 15:09:57 +00:00

Author

Copy Link

If i could export the tar stream i could just put the stream in a file so i would prefere the stream option.

I came to the idea after the need to transfer a few files from my backup to a windows computer via nc. Since it was a computer i had no real access to.
So i copied the files from the mounted backup, used tar to send the stream over netcat and received and untared it on the other side.

So maybe kind of an edge case, but i still think it would be cool if this could be implemented.

If i could export the tar stream i could just put the stream in a file so i would prefere the stream option. I came to the idea after the need to transfer a few files from my backup to a windows computer via nc. Since it was a computer i had no real access to. So i copied the files from the mounted backup, used tar to send the stream over netcat and received and untared it on the other side. So maybe kind of an edge case, but i still think it would be cool if this could be implemented.

witten referenced this issue from a commit 2020-07-23 04:56:32 +00:00

Add "borgmatic export-tar" action to export an archive to a tar-formatted file or stream (#300).

witten commented 2020-07-23 05:00:41 +00:00

Owner

Copy Link

Just implemented this with a new borgmatic extract-tar command. Run with --help after upgrading to borgmatic 1.5.9 for info on usage. Please let me know whether it works for your use case!

The new export-tar action supports exporting to file or to stdout.

Thanks for the feature idea!

Just implemented this with a new `borgmatic extract-tar` command. Run with `--help` after upgrading to borgmatic 1.5.9 for info on usage. Please let me know whether it works for your use case! The new `export-tar` action supports exporting to file or to stdout. Thanks for the feature idea!

witten closed this issue 2020-07-23 05:00:41 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

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   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

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#300

No description provided.