Based on the log file generated by the (equivalent) "naked" rsync backup
log: recv cS+++++++++ rwxrwx--- 1006, 1006 0 cam_socket0 log: recv cS+++++++++ rwxrwx--- 1006, 1006 0 cam_socket1 log: recv >f+++++++++ rwx------ 1000, 1000 8 hidden_volume.txt it seems like it gets stuck somewhere between backing up 'cam_socket1' and 'hidden_volume.txt' since the last BackupPC log line I see is: recv cS+++++++++ rwxrwx--- 1006, 1006 0 cam_socket1 If the problem is backing up a 'socket', the problem is not in native rsync as it proceeds fine but rather presumably in rsync_bpc. "" wrote at about 13:41:35 -0500 on Friday, January 21, 2022: > I have long been able to back up my (rooted) Android phones using > ssh/rsync. > I also have no problem backing up my Windows and Linux machines. > > However, BackupPC timesout when I try to back up an old Samsung S3 (which > used to back up perfectly before). The timeout occurs no matter what > value I use even though the total backup size is only about 5.2 GB. > > The corresponding rsync_bpc client command is: > /usr/bin/rsync_bpc --bpc-top-dir /var/lib/backuppc --bpc-host-name > droidtestmachine --bpc-share-name /data --bpc-bkup-num 0 --bpc-bkup-comp 3 > --bpc-bkup-prevnum -1 --bpc-bkup-prevcomp -1 --bpc-bkup-inode0 6621 > --bpc-log-level 1 --bpc-attrib-new -e /usr/bin/ssh -p 22 -l u0_a500 > --rsync-path=PATH=su\ -lpc\ /data/mybin/rsync --super --recursive > --protect-args --numeric-ids --perms --owner --group -D --times --links > --hard-links --delete --delete-excluded --one-file-system --partial > --log-format=log: %o %i %B %8U,%8G %9l %f%L --stats --checksum > --timeout=72000 --exclude=media/0/Download/Temp/* droidy:/data/ / > > And the corresponding rsync (remote) server command on the android host is: > 20298 10500 0:00 su -lpc /data/mybin/rsync --server --sender > -slHogDtprcxe.iLsfxC > 20373 0 0:52 /data/mybin/rsync --server --sender > -slHogDtprcxe.iLsfxC > > Interestingly, I can successfully manually run the same rsync > command directly by invoking rsync with the above parameters and the > rsync completes successfully in just a couple of hours (far less than the > timeout). > > The corresponding rsync client command is: > sudo rsync -e /usr/bin/ssh\ -p\ 22\ -l\ u0_a500 --rsync-path=su\ -lpc\ > /data/mybin/rsync --super --recursive --protect-args --numeric-ids --perms > --owner --group -D --times --links --hard-links --delete --delete-excluded > --one-file-system --partial --log-format=log:\ %o\ %i\ %B\ %8U,%8G\ %9l\ > %f%L --stats --checksum --timeout=72000 --exclude=media/0/Download/Temp/\* > droidy:/data/ /tmp/droid-backup > > And the corresponding rsync server command on the (remote) android > host is exactly as above. > > Since 'manual' rsync works, the problem is presumably *NOT* > - The android phone > - The setup of ssh and rsync on the phone > - The files on the phone > - The connection between the phone and the Linux machine invoking > rsync or rsync_bpc > > Also, since my BackupPC server otherwise works fine, there is > presumably nothing fundamentally wrong with my BackupPC installation. > > Finally, since at least some files are transferred (according to the > BackupPC logs) before the timeout, there is no problem with the ssh > keys for the android connection. > > > So, why would rsync_bpc timeout but not when I run straight rsync? > i.e., what is rsync_bpc doing differently that would cause a hang? > > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: https://github.com/backuppc/backuppc/wiki > Project: https://backuppc.github.io/backuppc/ _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
