After this device would automagically do (incremental?) encrypted backups tothe SD card on given interval.

Incremental backups could be done with unencrypted index that has filename ->hash so we would know if some file has changed and need to be on next backup.If we wish to be more secure even filename would not be needed in index. hashof it or inode information would be enough to match.

I know there is online Ovi backups, but I think something like this would bebeneficial for the users. Especially if they are not able to sync for few days.

Lot improvements there- like where and how to store the private key. 3 security levels there.1) leave it on device2) leave it on device if it has passphrase3) store it elsewhere and delete it from device altogether.- How to make sure that we do not take too much space from SD card(allow only backups over 1 week?, allow only backups to take x% or xMB fromcard?)- notify user as backups have been completed.

Solution #3: Based on wireless network

Based on wireless network. It should be possible to set up automatic backups to a fileserver. When in reach of the wirelss networks with access to the fileserver backups should be made at regular intervals.

0

0

0

0 0

Solution #4: Duplicity port for Maemo

"Duplicity backs directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server.

The duplicity package also includes the rdiffdir utility. Rdiffdir is an extension of librsync's rdiff to directories---it can be used to produce signatures and deltas of directories as well as regular files. These signatures and deltas are in GNU tar format."