[Enhancement] Progress Bar #106

New Issue

Closed

opened 2018-11-06 10:28:33 +00:00 by pwnyprod · 5 comments

pwnyprod commented 2018-11-06 10:28:33 +00:00

Copy Link

How about a progressbar or something to see that is any progress there with the update.

Also okay is an estimation time or something or a rolling Bar or something with Filename next to it with echo -n

How about a progressbar or something to see that is any progress there with the update. Also okay is an estimation time or something or a rolling Bar or something with Filename next to it with echo -n

witten commented 2018-11-13 06:47:04 +00:00

Owner

Copy Link

That would be pretty cool. Are you in particular thinking about a progress bar when creating a backup?

It looks like Borg backup already has an existing --progress flag to borg create, so it might just be a question of passing that through from borgmatic. The way I could imagine that working is to add an optional --progress to the borgmatic command-line that basically triggers the built-in Borg progress bar.

That would be pretty cool. Are you in particular thinking about a progress bar when creating a backup? It looks like Borg backup already has an existing `--progress` flag to `borg create`, so it might just be a question of passing that through from borgmatic. The way I could imagine that working is to add an optional `--progress` to the borgmatic command-line that basically triggers the built-in Borg progress bar.

witten commented 2018-11-18 18:53:21 +00:00

Owner

Copy Link

Based on some discussion on #108, it sounds like borg create --progress doesn't actually include a progress bar as I originally assumed! So a pass-through flag wouldn't be sufficient here.

In any case, it would be helpful if you could describe what you'd like a progress bar for (creating backups, etc). Thanks.

Based on some discussion on #108, it sounds like `borg create --progress` doesn't actually include a progress bar as I originally assumed! So a pass-through flag wouldn't be sufficient here. In any case, it would be helpful if you could describe what you'd like a progress bar for (creating backups, etc). Thanks.

witten commented 2018-11-18 19:00:55 +00:00

Owner

Copy Link

Okay, having played with borg create --progress a bit.. It's not a progress bar, but it does provide updating per-file rolling progress.. Here's an example:

351.11 MB O 197.07 MB C 66.16 MB D 2171 N home/.../file.sqlite                         

And those numbers update until the file backup is complete. This is just a built-in Borg feature. Here are the docs on it:

The --progress option shows (from left to right) Original, Compressed and Deduplicated (O, C and D, respectively), then the Number of files (N) processed so far, followed by the currently processed path.

Let me know if that works for your needs or not.

Okay, having played with `borg create --progress` a bit.. It's not a progress *bar*, but it does provide updating per-file rolling progress.. Here's an example: ``` 351.11 MB O 197.07 MB C 66.16 MB D 2171 N home/.../file.sqlite ``` And those numbers update until the file backup is complete. This is just a built-in Borg feature. Here are the [docs](https://borgbackup.readthedocs.io/en/stable/usage/create.html#description) on it: > The --progress option shows (from left to right) Original, Compressed and Deduplicated (O, C and D, respectively), then the Number of files (N) processed so far, followed by the currently processed path. Let me know if that works for your needs or not.

pwnyprod commented 2018-11-19 08:58:32 +00:00

Author

Copy Link

Hey, thanks for your reply.

i overthinked it and that will be fine. To build a real Progress bar in the natural way a bar works you need to count all backed files before backup. That might be unefficient for the Tool itself.

So parse the param through will be the beste way.

Hey, thanks for your reply. i overthinked it and that will be fine. To build a real Progress bar in the natural way a bar works you need to count all backed files before backup. That might be unefficient for the Tool itself. So parse the param through will be the beste way.

jwest75674 referenced this issue 2021-03-20 12:45:08 +00:00

Enhancement Request - Visual Progress Bars (Revisited) + Time to Completion Estimate #401

witten commented 2036-02-07 12:08:03 +00:00

Owner

Copy Link

Cool. In that case, I'll close this ticket as a duplicate in favor of #108. (Even though this ticket was technically filed first!) Thanks for filing the enhancement, and please continue to follow progress (heh) on #108.

Cool. In that case, I'll close this ticket as a duplicate in favor of #108. (Even though this ticket was technically filed first!) Thanks for filing the enhancement, and please continue to follow progress (heh) on #108.

witten closed this issue 2036-02-07 12:08:03 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

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

No description provided.