Thanks, these changes fixed it. I should have RTFM.
$Conf{RsyncSshArgs} = ['-e', '$sshPath -p -l root'];# Fixed
alternative port for ssh
$Conf{RsyncShareName} = ['/mnt/c/Users/']; # Fixed issue with hopping across
/mnt/c filesystem mount point on Win 10 Linux Subsystem
Stan Larson | Systems Administrator
Freedom | www.freedomsales.com
11225 Challenger Avenue Odessa, FL 33556
PH: 813-855-2671 x206 |
Direct Line: 1-727-835-1157
From: backu...@kosowsky.org
Sent: Tuesday, July 21, 2020 4:48 PM
To: General list for user discussion, questions and support
Subject: Re: [BackupPC-users] Windows 10 Subsystem For Linux
Stan Larson wrote at about 12:57:40 -0400 on Tuesday, July 21, 2020:
> We've been successfully using BackupPC 3.3 and the Windows 10 WSL feature to
> access Windows 10 PCs using rsync (without the cgwin plugin). We've been
> using this method on our production BackupPC server to back up about 30
> Win10 Pro clients. We just back up the C:/Users folder, which picks up the
> User's Desktop, Documents, AppData folders, etc. This method has proven to
> be very reliable using BackupPC 3.3.
>
> We are testing with BackupPC 4.4 so that we can overcome the filesystem
> issues that BackupPC 3.3 hard links present.
>
> We are running into a couple of problems that seem to be related to
> rsync_bpc.
>
> 1. On our BackupPC 3.3 server, we are able to use an alternate ssh port for
> our Windows 10 clients. We actually run ssh on port on the clients
> with no problem. With BackupPC 4.4 (rsync_bpc), we get errors when trying
> to run on alternate ports. The errors seem to indicate that even though we
> are specifying a different port, rsync_bpc is ignoring the alternate port
> and trying to use port 22. Here's the config declaration, which works on
> 3.3 but not 4.4... $Conf{RsyncClientCmd} = '$sshPath -p -q -x -l root
> $host $rsyncPath $argList+';
RsyncClientCmd is not a configurable variable for 4.x so not
surprising that you are having a problem...
You probably want to use: RsyncSshArgs.
For example:
$Conf{RsyncSshArgs} = ['-e', '$sshPath -p -q -x -l root'];
Though not sure you need '-q -x'
>
> 2. When we use port 22 on the client instead of port (see above), we
> get a successful backup, but we have a different problem. On the Win 10 WSL
> client, the C:\ drive is a separate filesystem presented as /mnt/c. On our
> BackupPC 3.3 server, we are able to cross this mount point successfully with
> no special configurations, using the config declaration...
> "$Conf{BackupFilesOnly} = ['/mnt/c/'];". On our BackupPC 4.4 server, the
> backup will run successfully, but no files below /mnt/c are included. It's
> as if BackupPC is refusing to cross from the / filesystem to the /mnt/c
> filesystem.
>
Suggest you test manually by running from the command line:
sudo -u backuppc rsync -navxH -p -l root :/mnt/c
> For the new server, we are using CentOS 8 and the default BackupPC yum
> packages.
>
> Any thoughts on either problem would be much appreciated.
>
> --
> [Freedom]
> Stan Larson | IT Manager
> Freedom |
> www.freedomsales.com>
> 11225 Challenger Avenue Odessa, FL 33556
> PH: 813-855-2671 x206 |
> Direct Line: 1-727-835-1157
>
>
> All commodities purchased from Freedom Sales are to be handled in accordance
> with US law including but not limited to the Export Administration
> Regulations, International Traffic in Arms Regulations, US Department of
> State, US Department of Homeland Security, US Department of Commerce, and US
> Office of Foreign Assets Control. Diversion Contrary to US law is prohibited.
> ___
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki:http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
All commodities purchased from Freedom Sales are to be handled in accordance
with US law including but not limited to the Export Administration Regulations,
International Traffic in Arms Regulations, US Department of State, US
Department of Homeland Security, US Department of Commerce, and US Office of
Foreign Assets Control. Diversion Contrary to US law is prohibited.
All commodities purchased from Freedom Sales are to be handled in accordance
with US law including but not limited to the Export Administration Regulations,
