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

New Issue

Closed

opened 2021-03-20 12:45:08 +00:00 by jwest75674 · 1 comment

jwest75674 commented 2021-03-20 12:45:08 +00:00

Copy Link

Preface: I am new to torsion/git, Thank you for your patience.

I had the same feature request as #106 (a visual progress bar when interactive), and read through #108 as well. I saw that each #106 and #108 were closed, so I am replying here, even though this is a duplicate of #106.
--> My apologies if this isn't the correct ettiquitte.

As well, in order to create a visual progress bar, the creation of a time to completion estimate would also be available

In #106 another user thought that the issue with a natural/visual progress bar is the need to know ahead of time about how much data will be processed in total.

While @witten did not actually confirm that this was indeed the issue, it would make sense that it would be the primary hurdle.

I wanted to propose that a potential solution to avoiding having to traverse the filesystem might be to simply take note of the total filesystem size at the end of each borgmatic --create, probably to the cache dir, for use in the subsequent run's --progress-bar or --time-remaining.

My logic here as well is that if a filesystem is large:

1. Then progress bar is more useful for manual backups
2. It's less likely to grow or shrink by large percentages of the total size between runs

This is of interest to me, as I am running 6TB backups, and need to periodically create manual backups before larger sets of changes. With 6TB backups the process is expected to be lengthy enough that a progress bar, and the related time estimate until completion, would make manual backups much more bearable.
(It's the simple things in life. Good food, good company, a modicum of feedback about how long a backup will run, the usual. :D )

Preface: I am new to torsion/git, Thank you for your patience. I had the same feature request as #106 (a visual progress bar when interactive), and read through #108 as well. I saw that each #106 and #108 were closed, so I am replying here, even though this is a duplicate of #106. --> My apologies if this isn't the correct ettiquitte. As well, in order to create a visual progress bar, the creation of a time to completion estimate would also be available In #106 another user thought that the issue with a natural/visual progress bar is the need to know ahead of time about how much data will be processed in total. While @witten did not actually confirm that this was indeed the issue, it would make sense that it would be the primary hurdle. I wanted to propose that a potential solution to avoiding having to traverse the filesystem might be to simply take note of the total filesystem size at the end of each borgmatic --create, probably to the cache dir, for use in the subsequent run's --progress-bar or --time-remaining. My logic here as well is that if a filesystem is large: 1) Then progress bar is more useful for manual backups 2) It's less likely to grow or shrink by large percentages of the total size between runs This is of interest to me, as I am running 6TB backups, and need to periodically create manual backups before larger sets of changes. With 6TB backups the process is expected to be lengthy enough that a progress bar, and the related time estimate until completion, would make manual backups much more bearable. (It's the simple things in life. Good food, good company, a modicum of feedback about how long a backup will run, the usual. :D )

jwest75674 commented 2021-03-20 12:56:12 +00:00

Author

Copy Link

Closed:
https://github.com/borgbackup/borg/issues/1618

Closed: https://github.com/borgbackup/borg/issues/1618

jwest75674 closed this issue 2021-03-20 12:56:12 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

command-hook-steps

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 Label

Milestone

No items

No Milestone

Assignees

Clear assignees

witten

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#401