Extend borgweb to monitor several repositories #108

Activity

1. ThomasWaldmann commented on Oct 30, 2017

   

   ThomasWaldmann

   on Oct 30, 2017

   Last edited by ThomasWaldmann

   Member

   More actions

   What it does is:

   • have 1 command to start a backup
   • have 1 directory to look at for backup logs

   While one could just multiply that (1 -> N), the question is whether that make sense for the scenario it was made for (borgweb running on same linux server that is to be backed up, so it runs together with the borg client, not on the borg repo server).

   You can also just start some 1 script that does multiple backups and have them all write their log into the 1 log directory (sorting/selection would have to be checked here).
2. henfri commented on Oct 30, 2017

   

   henfri

   on Oct 30, 2017

   ContributorAuthor

   More actions

   Hello,

   I understand what borg does.
   A while ago we had this discussion via IRC and you suggested I capture this as an Issue.
   I do understand that this was not what borgweb was intended to.
   But frankly: borgweb as it is today does not do very much, but is a good start.
   I think that borg is great. What needs to be improved though is the user interface. From my experience the most risky thing about backups is that they tend to stop working. They need to be monitored. And this is something where crashplan (see above) is good in. Why not learn from it.

   So, whether it is borgweb or something else:
   Is my intent clear?

   Greetings,
   Hendrik

   👍React with 👍2Reacted by SBPro and TristanAgnelli
3. turtle0x1 commented on Jan 25, 2019

   

   turtle0x1

   on Jan 25, 2019

   More actions

   @ThomasWaldmann I have started this in my fork are you still happy for it to go ahead ?
   
4. ThomasWaldmann commented on Jan 25, 2019

   

   ThomasWaldmann

   on Jan 25, 2019

   Member

   More actions

   if the UI could be in a way so it does not waste must screen width for simple use cases (1 repo), that would be fine.
5. turtle0x1 commented on Jan 25, 2019

   

   turtle0x1

   on Jan 25, 2019

   More actions

   It requires a new variable BACKUP_REPOS in the config.py which looks something like;

       BACKUP_REPOS = {
           "test": {
               "repo_path": "/root/repo",
               "backup_commands": [
                   "a",
                   "b",
                   "c"
               ]
           }
       }
   

   My plan was to restructure the ui so you can "start backups" for individual backups for each repo instead of one backup button for one command, will this be an issue?
6. ThomasWaldmann commented on Jan 25, 2019

   

   ThomasWaldmann

   on Jan 25, 2019

   Member

   More actions

   Maybe have a look at borgmatic, wether the same config format could be used.
7. turtle0x1 commented on Jan 25, 2019

   

   turtle0x1

   on Jan 25, 2019

   More actions

   The format is completly incompatible with the current backend might aswell re-write it to work with borgmatic cli instead of borg itself?
8. ThomasWaldmann commented on Jan 26, 2019

   

   ThomasWaldmann

   on Jan 26, 2019

   Member

   More actions

   i don't personally use borgmatic, so not sure if it makes sense.
   my idea was rather about "do not invent yet another config file format".