On Wed, Mar 20, 2013 at 4:00 PM, Jeff Boyce <jboyce AT meridianenv DOT com>
wrote:
>
> I am trying to figure out if my objective is possible. I want to be able to
> backup a remote Window box that connects to the local network via OpenVPN.
> I have scanned through the archives and have seen some discussion of similar
> things, but nothing that really gives me good overall direction on whether
> it will work, or how to get it to work, with my network configuration.
There's no real difference as long as it is up at a reachable IP address.
> I am
> using BackupPC to backup the local Windows boxes, and would like to add a
> remote one. I am not that concerned about the time it would take to
> complete a backup over the WAN, as I can configure it to work at night.
>
> Local Network
> Sequoia = Samba (and WINS server) and OpenVPN server (192.168.112.50)
> Taxa = DNSmasq (dns and dhcp server) (192.168.112.51)
> Bacteria = BackupPC server (192.168.112.52)
> Network IP = 192.168.112.0/24
>
> Remote Windows Box
> Computer Name = jks-e6500
> Remote LAN IP = unknown
> Remote WAN IP = dynamic
> OpenVPN Common Name = jkssequoiaclient
> OpenVPN IP = static, 10.9.8.10
> OpenVPN routed network
>
> I have BackupPC configured to connect to the local Window boxes via SMB, as
> I didn't care for the cygwin and rsync implementation on windows when I used
> it in the past. Besides, I already have Samba configured and running just
> fine, so why not just use it.
The big difference would be bandwidth usage after the initial copy.
Every smb full is going to send all the data. Another difference is
that smb incrementals are based on the file timestamps and won't track
files added in ways that keep an old timestamp, old files in their new
position under a renamed directory, or deletions. You might like the
cwrsync or deltacopy variations of rsync - still cygwin based but
packaged in a windows installer.
> I seem to have both DNS and netbios name
> resolution working properly for the local LAN, but don't know how the remote
> box fits into that when it connects to Samba via a VPN network.
If you manage local dns you can add the target name with the VPN IP
and everything should work the same as locally. Alternatively, you
could set ClientNameAlias to the VPN IP in the backuppc config.
> My thinking is that since the remote Windows box can connect and browse the
> Samba shares on Sequoia via the VPN, then obviously Samba knows how to
> communicate with this remote client.
No, that's not entirely obvious unless the backuppc server is also the
VPN server. Sometimes VPN servers are configured to NAT to their
ethernet interfaces to provide LAN connectivity for the remote
clients. In your case you need routing from the backuppc server to
the client IP which may or may not be present. Can you connect with
smbclient to the 10.9.8.10 IP?
--
Les Mikesell
lesmikesell AT gmail DOT com
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
