Nepomuk Backup

Roughly 2 weeks ago, just before the feature freeze, the Nepomuk backupsync service was pushed into the trunk.

A long time ago I posted a lot of features about the ‘planned’ Nepomuk Backup service. I did land up implementing most of those features, but ultimately disabled some of them for a more stable backup experience. I thought it would be better to have a stable backup tool, without all the frills, compared to unstable tool which may potentially mess up your data.

So, without further ado I present Nepomuk Backup -

Nepomuk now provides automated backups.

The Nepomuk Backup GUI

The user interface can be invoked by the ‘nepomukbackup’ command, or can be called from the Nepomuk KCM.

**DBus interface**

The Backup GUI is completely independent of the backupsync service, as they communicate with each other through DBus. The main advantage of using DBus is that backups can easily be integrated into your existing backup solution. The command to perform a backup is -

qdbus /backupmanager backup <url>

If a blank URL is given, the backup is performed in the default location which would be `$KDEDIR/share/apps/nepomuk/backupsync/backup`.
The backup could similarly be restored using DBus, but I would recommend using the gui for restoration as it allows you to resolve conflicts.

Index everything

Honestly, do it! It’s a lot easier for you and for us. Plus you’ll have a much better Nepomuk experience if you index everything. With Nepomuk Backup, the more stuff you have indexed, the less conflicts you can expect when restoring a backup.

Nepomuk Sync

This entire post I’ve been calling it the backupsync service, and yet I’ve only been talking about backups. That’s cause there is currently no user interface for performing syncs. The infrastructure is there ( and it works! ) In the coming weeks once I’ll start working on the user-interface and stuff. Maybe I can release it in extragear? Either way, I will try my best to get Nepomuk Sync into 4.7

Now let the full scale testing commence :)