Image 01
profile-image

snowweb

Peter Snow
Kup Backup System

System Software 203 comments

Score 81%
81 Likes
19 Dislikes
Jan 06 2018
Sorry, still no reply option on your posts (for me at least).. weird!

Anyway, I always thought GIT did a pretty good job of doing the right thing with compression without any help. It's pretty efficient anyway, so I for one won't miss the compression option (particularly if it's a bit of a 'red-herring' and doesn't really make a lot of difference.

I think you're doing a great job over-all. It will be great to be able to do my backups with GIT. Thanks for your efforts. - Feb 27 2013
Strange... no reply to option on your last post!

Anyway, I tried "bup version" as you requested but the response was "unknown-".

I then did the following:
$ dpkg -s bup
Package: bup
Status: install ok installed
Priority: extra
Section: admin
Installed-Size: 680
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Architecture: i386
Version: 0.22a-1
Depends: libc6 (>= 2.4), python (<< 2.8), python (>= 2.7), python-support (>= 0.90.0), git (>= 1:1.7.0.4-2) | git-core, python-fuse, python-tornado (>= 1.0.1-1)
Recommends: par2
Description: highly efficient file backup system based on git
bup is a backup tool which stores the backups in a system based around
the packfile format from git.
Original-Maintainer: Jon Dowland <jmtd@debian.org>
Homepage: http://github.com/apenwarr/bup

Regarding whether I'm now using the newly self-compiled version of Kup or not, I completely removed the previous version, which was installed from a .deb, then verified it had gone, then compiled the new obtained via GIT.

I noticed some differences in it, it still had the compression option, but it also has some extra text around the options and in the display area for externally detected devices, there was some new text in there, explaining about it.

I've also restarted the machine since too but still get that error. I'm wondering if maybe you are using the "bup version" method to get the version number programmatically (which fails on my machine) and whether it might succeed if you were using "dpkg -s bup"?

- Feb 27 2013
OK, thanks. Solved that and am now running the new version.

Nice work on the configuration options. That's a lot clearer now for me.

But I'm getting this error when I try to run a backup:

Backup did not complete successfully:</nl><i>error: option -0 not recognized<br>usage: bup save [-tc] [-n name] <filenames...><br><br> -r, --remote ... hostname:/path/to/repo of remote repository<br> -t, --tree output a tree id<br> -c, --commit output a commit id<br> -n, --name ... name of backup set to update (if any)<br> -d, --date ... date for the commit (seconds since the<br> epoch)<br> -v, --verbose increase log output (can be used more than<br> once)<br> -q, --quiet don't show progress meter<br> --smaller ... only back up files smaller than n bytes<br> --bwlimit ... maximum bytes/sec to transmit to server<br> -f, --indexfile ... the name of the index file (normally<br> BUP_DIR/bupindex)<br> --strip strips the path to every filename given<br> --strip-path ... path-prefix to be stripped when saving<br> --graft ... a graft point *old_path*=*new_path* (can be<br> used morethan once)<br></i> - Feb 25 2013
I can't find any differences with this new version. I'm wondering if maybe the upgrade wasn't installed properly here? I have restarted the computer but it still looks like I have the previous version.

This is the output from the terminal for the "make install" step:

$ sudo make install
Generating moc_kupsettings.cpp
[ 0%] Built target kupsettings_automoc
Scanning dependencies of target kupsettings
[ 4%] Building CXX object settings/CMakeFiles/kupsettings.dir/kupsettings_automoc.o
Linking CXX static library ../lib/libkupsettings.a
[ 14%] Built target kupsettings
Generating moc_backupplanwidget.cpp
Generating moc_kupkcm.cpp
Generating moc_planstatuswidget.cpp
Generating moc_driveselection.cpp
Generating moc_folderselectionmodel.cpp
[ 14%] Built target kcm_kup_automoc
Scanning dependencies of target kcm_kup
[ 19%] Building CXX object kcm/CMakeFiles/kcm_kup.dir/kcm_kup_automoc.o
Linking CXX shared module ../lib/kcm_kup.so
[ 47%] Built target kcm_kup
[ 52%] Built target actions for org.kde.kup.runner
Generating moc_edexecutor.cpp
Generating moc_kupdaemon.cpp
Generating moc_fsexecutor.cpp
Generating moc_bupjob.cpp
Generating moc_planexecutor.cpp
[ 52%] Built target kupdaemon_automoc
Scanning dependencies of target kupdaemon
[ 57%] Building CXX object daemon/CMakeFiles/kupdaemon.dir/kupdaemon_automoc.o
Linking CXX executable kupdaemon
[ 85%] Built target kupdaemon
Generating moc_buphelper.cpp
Generating moc_bupjob.cpp
[ 85%] Built target kuphelper_automoc
Scanning dependencies of target kuphelper
[ 90%] Building CXX object daemon/CMakeFiles/kuphelper.dir/kuphelper_automoc.o
Linking CXX executable kuphelper
[100%] Built target kuphelper
Linking CXX shared module CMakeFiles/CMakeRelink.dir/kcm_kup.so
Building CXX object daemon/CMakeFiles/kupdaemon.dir/kupdaemon_automoc.o
Linking CXX executable CMakeFiles/CMakeRelink.dir/kupdaemon
Linking CXX executable CMakeFiles/CMakeRelink.dir/kuphelper
Install the project...
-- Install configuration: "RelWithDebInfo"
-- Installing: /usr/local/lib/kde4/kcm_kup.so
-- Installing: /usr/local/share/kde4/services/kcm_kup.desktop
-- Installing: /usr/local/bin/kupdaemon
-- Installing: /usr/local/share/autostart/kupdaemon.desktop
-- Installing: /usr/local/share/apps/kupdaemon/kupdaemon.notifyrc
-- Installing: /usr/local/lib/kde4/libexec/kuphelper
-- Installing: /usr/share/polkit-1/actions/org.kde.kup.runner.policy
-- Installing: /usr/local/etc/dbus-1/system.d/org.kde.kup.runner.conf
-- Installing: /usr/local/share/dbus-1/system-services/org.kde.kup.runner.service
-- Installing: /usr/local/share/icons/hicolor/32x32/actions/./kuprunning.mng
-- Installing: /usr/local/share/icons/hicolor/scalable/apps/./kup.svgz

How can I tell if I'm now running the new package?

Should I have removed the old package first?
- Feb 25 2013
Great, will give it a try.

GIT's no problem, compiling might be, but will see what I can do (I originally installed from a .deb).

Will get back to you.

Thanks. - Feb 24 2013
Sorry about the Re...Re..!

The version I'm using is:

Version: 0.22a-1 (for i386)

I'm not sure how to find which repo supplied it, but I have a clean new install of Kubuntu 12.04.2 and only added one additional repo so far, which I think was 'extras' maintained by Canonical. I'd love to use the latest version of things like bup, but unless there's a repo I can add with it in, it's hard to do that.

Regarding the dialogs in the application, I do have a couple of suggestions:

1) How about "Locally Attached External Storage" as a label, instead of "External Storage"?

2) The box where I assume detected external storage shows up, should be labelled "Detected external devices:" because if nothing is detected you're left wondering what should be in there!

3) When using the Local Storage option I think the folder field should be labelled, "Path to Backup Directory". I think if it is not too difficult to add tooltips, they would be useful here to be able to add, "May include mounted network drives, etc."

4) Also I would recommend an information screen to be displayed each time the configuration screen is opened, until a check is removed labelled, "Show this screen every time". In there, it would be useful to see a couple of paragraphs about what to expect to happen when you perform the setup, ie, "When you first enable backups on a directory, a '.git' folder will be created in the top level directory, which you should not delete, and the included contents will immediately be indexed. If you disable backups at any point, it will be automatically removed. A cron job is also added under the user, blah, blah.."

That kind of information would make it a bit easier for people to begin troubleshooting permissions issues, etc. I think.

I also noticed and am not sure if this is related to my bup issues or not, that when I start the laptop, if my directory becomes available after Kup has started, Kup continues to report the backup location as not available, even after it is. It would be great if things like this were less of a mystery by including information regarding how this monitored and the frequency of monitoring.

One last thing, I'm interested to know the effect of the storage becoming unavailable, part way through a backup or if the user shuts down their machine?

Thanks, for what promises to be among the 'must have' utilities of Linux in the future. Great job!

Regards,

Peter
- Feb 22 2013
I've got that working now - my fault, it was permissions issue, but now I seem to have another issue...

Backup did not complete successfully:</nl><i>error: option -1 not recognized<br>usage: bup save [-tc] [-n name] <filenames...><br><br> -r, --remote ... hostname:/path/to/repo of remote repository<br> -t, --tree output a tree id<br> -c, --commit output a commit id<br> -n, --name ... name of backup set to update (if any)<br> -d, --date ... date for the commit (seconds since the<br> epoch)<br> -v, --verbose increase log output (can be used more than<br> once)<br> -q, --quiet don't show progress meter<br> --smaller ... only back up files smaller than n bytes<br> --bwlimit ... maximum bytes/sec to transmit to server<br> -f, --indexfile ... the name of the index file (normally<br> BUP_DIR/bupindex)<br> --strip strips the path to every filename given<br> --strip-path ... path-prefix to be stripped when saving<br> --graft ... a graft point *old_path*=*new_path* (can be<br> used morethan once)<br></i> - Feb 22 2013
I've just moved the path in to the local storage field thinking that the external storage field might be for detected USB storage, rather than network storage.

Still doesn't work though. I did notice that if I enter "cupdaemon status" at the command line, it says, "Kup is not enabled. Enable it from the system settings module."

According to the system settings module, I have checked "Backups Enabled". - Feb 22 2013
I've just moved the path in to the local storage field thinking that the external storage field might be for detected USB storage, rather than network storage.

Still doesn't work though. I did notice that if I enter "cupdaemon status" at the command line, it says, "Kup is not enabled. Enable it from the system settings module."

According to the system settings module, I have checked "Backups Enabled". - Feb 22 2013
I've configured the options and input a path to a NFS folder in the external storage folder field (/mnt/NAS/backups/) but the icon in the system tray still has that backup greyed out in the menu and when scheduled it doesn't run either.

I've confirmed that the drive is mounted and accessible. What could be wrong please?

(I also have installed 'bup')

Thanks. If I can get it working, I rekon I might switch from Rsnapshot which I've been using for the last few years. - Feb 22 2013
Kup Backup System

System Software

Score 81%
81 Likes
19 Dislikes
Feb 25 2013
Kup Backup System

System Software

Score 81%
81 Likes
19 Dislikes
Feb 25 2013