On Tue, Oct 30, 2007 at 10:08:47AM -0600, Larry Bernstone wrote:
> Well, I'd really prefer to manage this from a backuppc perspective than
> a DHCP/DNS perspective. This is a Microsoft network, so the clients are
> obviously going to do what is best for BillG. Can anyone give me a
> rough of what I need to change as far as the nmblookup/pingcmd scripts?
> I just need some architecture help, I can handle the scripting details.
> >From: Micha Kersloot <[EMAIL PROTECTED]>
>
> >Larry Bernstone schreef:
> >> Has anyone set up a system where they have a preferred network for
> >> backups? I have laptops that connect to wireless and wired subnets
> on
> >> my network. I?d like for the wired network to be used if available,
> but
> >> since DNS gives out seemingly random results to a hostname lookup, it
> >> behaves really screwy, is difficult to script, and will often choose
> the
> >> wireless connection over the wired. Anyone come up with a good
> config
> >> for this?
>
> >Not really a backup question, but I can think of two solutions,
> >depending on the OS on the laptops and the server.
> >1. If the OS on the laptop is Linux, you can script DCHP-client so it
> >sends a hostname depending on several variables, for example the
> network
> >card.
> >2. You can setup the DHCP server to fix ip numbers to mac addresses. In
> >that case you are always certain about the connection type in use.
Note I am just starting with bckuppc and haven't used any of the DHCP
stuff.
Do you have a single DHCP network range for both wired and wireless,
or do you serve up say 192.168.1.x to wired hosts and 192.168.2.x to
wireless?
If you do have different ranges, then I think you can have backuppc
scan only the wired network for clients. Then change the config file
and have it scan the wireless network. If the host was backed up on
the wired network, it won't need a backup on the wireless. Also you
may be able to do both without having to reload a config file by
adding multiple dhcp scan ranges in the config file if they are used
in a given order.
Alternatively could you modify the path to the ping command and
replace that with a shell script that can detect when a host is on the
wireless (say via traceroute, or ethernet address). Then it can return
a failure (or long delay time) to backuppc stopping the backup over
the wireless.
However the ping solution only blocks backups over the wireless, it
doesn't help you change backuppc to scan for the wired interface at a
different IP range. So you may end up having hosts that aren't backed
up at all.
If you had a fully hardwired multihomed host with backuppc you would
have the same issue, but you could hard code the IP you wanted to use
in that case.
So maybe a perl routine called from the .../pc/host.pl files that
returns/sets the $Conf{ClientNameAlias} to the proper IP (hardwired ip
if available or wireless if no hardwire), may work. However this is
documented to not work if DHCP field is set to 1 in hosts file.
Maybe using a custom NmbLookup command may work, but that may only be
used for smb backups.
Do these rambilings provide a spark for anybody?
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-643-9300 x 111
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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/
