Archive by Author

Back In Time version 0.9.99beta6

This is the second beta release on the way to 1.0. It is available on testing repository. Please keep in mind that this version is for testing only.

Changes (for 1.0):

  • fix kde4plugin
  • ask to upgrade snapshots structure only if there are old snapshots

Back In Time version 0.9.99beta5

This is the first beta release on the way to 1.0. It is available on testing repository. Please keep in mind that this version is for testing only.

Changes (for 1.0):

  • add support for ionice
  • multiple profiles support
  • remove “schedule per included directory” (profiles do that)
  • new snapshot folder is restructure: /backintime/machine/user/profile_id/
  • added option to disable snapshots when on battery
  • many bugs fixed

Back In Time version 0.9.26

Change log:

  • update translations
  • Fix a bug in smart-remove algorithm (https://bugs.launchpad.net/backintime/+bug/376104)
  • Fix bug: https://bugs.launchpad.net/backintime/+bug/374477
  • Fix bug: https://bugs.launchpad.net/backintime/+bug/375113
  • add ‘–no-check’ option to configure scripts
  • use only ‘folder’ term (more consistent with GNOME/KDE)
  • add ‘expert option’: enable/disable nice for cron jobs
  • GNOME & KDE4: refresh snapshots button force files view to update too
  • you can include a backup parent directory (backup directory will auto-exclude itself)
  • fix some small bugs

Files not copied when backup directory is on smbfs

Mount a samba share using smbmount and then configure Back In Time to save snapshots into this share. Taking a snapshot don’t work, only some directories are created.

After some investigation: using a windows share it works, using a samba is doesn’t work.

Samba provide some extensions to the protocol to support uid/gid and permissions.
I mounted the share using smbmount (‘sudo smbmount’) and I create a directory: the user/group of the new directory are root/root and the permissions are user:rwx and group/other:rx only. Then creating a sub-directory will fail since I don(t have the rights.

To void problems the only solution I found is to mount the share using “-o nosuids,noperms” arguments (not uid/gid and no permissions). This way the application seems to works. The only problem is that snapshots are no longer read-only. Starting from version 0.9.24, user/group and permissions are stored in a special file so restoring them should be OK.

Back In Time version 0.9.24

Change log:

  • update translations
  • KDE4: fix python string <=> QString problems
  • KDE4 FilesView/SnapshotsDialog: ctrl-click just select (don’t execute)
  • KDE4: fix crush after “take snapshot” process
  • store basic permission in a special file so it can restore them correctly (event from NTFS)
  • implement Gnome/KDE4 systray icons and user.callback as plugins
  • reorganize code: common/GNOME/KDE4
  • GNOME: break the big glade file in multiple file
  • backintime is no longer aware of ‘backintime-gnome’ and ‘backintime-kde4′ (you need run ‘backintime-gnome’ for GNOME version and ‘backintime-kde4′ for KDE4 version)

KDE4: Could not connect to host for smb://smb-network/

The application allow you to select local folders only.

In KDE4 I use KFileDialog static method:

QString getExistingDirectory(
                KUrl     startDir=KUrl(),
                QWidget  parent=0,
                QString  caption=QString() )

According to the documentation:

Creates a modal directory-selection dialog and returns the selected directory (local only) or an empty string if none was chosen.

For more information:

So it is not normal to be able to select network. This looks more like a KDE4 bug.

Snapshots on NTFS drive are not read-only

The problem with read-write snapshot is that you can modify it accidentally. Even worst, if the file you modified is shared between different snapshots (hard-link) all snapshots will be affected.

This is because by default in ntfs-3g driver (this driver provide read/write support for NTFS)  files and directories are owned by the effective user and group of the mounting process (usually root) and everybody has full read, write, execution and directory browsing permissions.

To get more information:

Solution

I don’t have one. Check out ntfs-3g site (http://www.ntfs-3g.org) for more information.If you find a solution please share it.

System freeze on Ubuntu Jaunty (9.04) with ext4

If you set snapshots directory on a ext4 partition the system may freeze.

It seems to be a problem in ext4 on Ubuntu:

Solution (thanks to mahikeulbody)

You need to  set ‘nodelalloc’ option for each ext4 partition it accesses into fstab file .

Back In Time version 0.9.22.1

Change log:

  • fix French translation

Back In Time version 0.9.22

Change log:

  • update translations
  • KDE4: fix some translation problems
  • remove –safe-links for save/restore (this means copy symlinks as symlinks)
  • create directory now use python os.makedirs (replace use of mkdir command)
  • KDE4: fix a crush related to QString – python string conversion
  • GNOME & KDE4 SettingsDialog: if schedule automatic backups per directory is set, global schedule is hidden
  • GNOME FilesView: thread “*~” files (backup files) as hidden files
  • GNOME: use gtk-preferences icon for SettingsDialog (replace gtk-execute icon)
  • expert option: $XDG_CONFIG_HOME/backintime/user.callback (if exists) is called a different steps  of “take snapshot” process (before, after, on error, is a new snapshot was taken).
  • add more command line options: –snapshots-list, –snapshots-list-path, –last-snapshot, –last-snapshot-path
  • follow FreeDesktop directories specs:
    • $XDG_DATA_HOME (default: $HOME/.local/share) to store app.lock files
    • $XDG_CONFIG_HOME (default: $HOME/.config) to save settings
  • new install system: use more common steps (./configure; make; sudo make install)