backintime ends with error 6144

Bug #1256300 reported by Daniel Betschart

This bug report was converted into a question: question #240098: backintime ends with error 6144.

6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
backintime (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Backintime runs but returns error 6144. Afther that it does the smart remove. All seems to be good, but I ask what is error 6144?

Revision history for this message
Daniel Betschart (dbet1) wrote :

Distributor ID: Ubuntu
Description: Ubuntu 12.04.3 LTS
Release: 12.04
Codename: precise

ii backintime-common 1.0.28~precise Simple backup system (common)
ii backintime-gnome 1.0.28~precise Simple backup system for GNOME Desktop
ii backintime-notify 1.0.28~precise Notifications using libnotify for BackInTime

Revision history for this message
Germar (germar) wrote :

You've to divide it by 256 (don't ask me why, I've no clue) so you will get rsync return code 24:
> 24 Partial transfer due to vanished source files

One or more files changed before rsync could transfer them. Rsync will transfer them next time again. You can browse the snapshot log to see which files where effected. But normally you don't need to worry about it.

Only if those files is a db (MySQL, Postgres, ...) you should rather exclude the files, create a db dump with custom user-callback script and backup only the dump.

Changed in backintime (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.