On 2016-11-20 17:58, Les Mikesell wrote:
> On Sun, Nov 20, 2016 at 4:32 PM, Bob of Donelson Trophy
> <[email protected]> wrote:
>
>> I am currently testing backing up one client machine from the other end of
>> the vpn. I used the client machines ipaddress instead of it's hostname. The
>> ssh key was copied and the backup began as expected. So, the different ip
>> subnet did not matter to the backuppc machine. (First time I had ever tried
>> backing up thru the vpn.) I also expected the backup to be slower thru the
>> vpn than the local backuppc machine there and it appears to be that, slower.
>>
>> I figured, for now, keep it simple and just try this and see what happens.
>>
>> When the backup completes I will compare the two backuppc machine client
>> data. I'm looking for redundancy with two backups per client machine in two
>> different geographical locations, one local lan and the other at my house
>> (other end of vpn.) Backup has been running about three hours now.
>>
>> Like you said, the two subnets are well translated by the vpn link.
>>
>> As far as his "string", I'm still studying what the "options" mean and might
>> his way be a faster backup method or not. These are only thoughts at this
>> point.
>
> The -C enables compression for the ssh and is likely to help
> considerably - unless your VPN is also doing compression. The
> initial copy of each client is likely to take a long time, depending
> on the speed of your network connections, but subsequent runs with
> rsync will be much faster, only copying the differences. If the
> initial full runs are impractical, it might work to initial set the
> 2nd server up locally, then move it to the offsite location with the
> initial data in place - or ship a drive for a similar machine.
(First my apologizes, my webmail client has a glitch. Not a story for
this mailing list but my reply will look like an extension of the
previous message and can cause confusion during reading . . . you'll see
what I mean if the "glitch" happens.)
Thanks for the info, Les.
I backed up a small Active Directory Domain Controller (Samba4). It is
about 5Gb in size and (full) backed up in about an hour. Slower than the
local Backuppc but, not a lot slower.
Then I started the backup of one of the ADDC member file servers . . .
about 250Gb (I think) . . . Backuppc (thru vpn) has been running now for
about 21 hours for this first, full backup. This backup took about five
or six hours locally.
I'm guessing it will finish soon . . . I hope.
This idea of doing the initial backup (of the second machine) on the
local lan and then moving it to the second location, I do not see this
as very practical. Every week (6.97 days) Backuppc does a full backup,
does this mean I need to move the machine every 6.97 days to the local
lan?
Surely there is some compression options that could be put in place to
better stream the data thru the vpn and improve the backup speed?
So I add "-C" to the "RsyncClientCmd sshpath" or "RsyncArgs"?
Aren't the "-q -x -l" default options in the "RsyncClientCmd sshpath"
ssh options? (Therefore the "-C" addition goes with them?)
--
_______________________________
Bob Wooden of Donelson Trophy
------------------------------------------------------------------------------
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
