On 9/9/21 9:51 PM, Kenneth Porter wrote:
--On Thursday, September 09, 2021 4:29 PM -0400 jbk <j...@kjkelra.com> wrote:

The portion in bold below was not executed.

Like most mailing lists, this one is plain text only and stripped out the HTML part with the bolding. So it's not clear what part of the command wasn't executed.



By the time the digest came out I had figured out the issue. But to followup on loose ends I can recap my findings. First, the client command variable quoted below found in V3 is deprecated in V4.

"$Conf{RsyncClientCmd} = '$sshPath -l backuppc *$host nice -n 19 /usr/bin/sudo* $rsyncPath $argList+';" so none of that line was executed, but because there are separate lines defining the ssh command, path and rsync command and path and host V4 was connecting to the client without the "nice -n 19 /usr/bin/sudo" portion, thus not able to access any of the file data. Once I realized this I knew it was just a matter of rearranging the arguments to fit the new format which I succeeded in doing except for "nice -n 19".

A similar issue was how to backup the localhost and I found the solution by searching this list which was to substitute the call for ssh with one for sudo.

$Conf{RsyncSshArgs} = [
  '-e',
  '/usr/bin/sudo -p'
];

V4 is now up and running and has done round of full backups on clients and host with no errors of note yet. I'll have to do a test restore soon to verify.

--
Jim Kelly-Rand
j...@kjkelra.com

_______________________________________________
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/

Reply via email to