[Borgbackup] What don't you like about Borg?

[Walker Traylor]

-Documentation, getting started guide could use improvement.  I wanted to learn how to set it up as fast as possible and had to learn a lot more about internals and command switches than should be necessary on a first try for a 1.0 release with normal use case.  

-Repair files notice.   I would like to see in "borg list" the archives which have been “repaired” by borg repair (zero’d out.)

-Improved ability to cancel and resume.  I have to repair files a lot for some reason, probably on archives which were interrupted, which is troubling.   


Walker Traylor
walker at walkertraylor.com <mailto:walker at walkertraylor.com>
m: +1.703.389.4507
skype: wtraylor
linkedin.com/in/walkertraylor <http://www.linkedin.com/in/walkertraylor>
> On Oct 20, 2016, at 5:15 PM, Marian Beermann <public at enkore.de> wrote:
> 
> It's easy to lose track of what's important and what annoys people, or
> doesn't work for them.
> 
> We all know about the good stuff Borg does, where it shines. I want to
> know about the bad stuff. Where it's annoying, doesn't work like one
> wanted to...
> 
> 
> Cheers, Marian
> 
> -
> 
> Things that annoy me:
> 
> - No good desktop GUI (I'm not a good designer, my own attempt kinda
> failed).
> - Sometimes it's slow and it's hard to tell why without knowing a lot
> about internals
> - Error messages are often kinda obscure
> - When used on the command line progress output is often missing (in
> current beta) even with --progress
> 
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20161020/bcb4094d/attachment.html>