So, from what I can tell, configuration of the backuppc server is pretty straight forward:
1. append a hosts entry to $BackupPCHome/conf/hosts 2. create the $BackupPCHome/conf/pc/bpcaccount.pl file for client specific configs. 3. create a $BackupPCHome/pc/bpcaccount directory Then execute the ssh -oStrictHostKeyChecking=no command for initial known_hosts addition. done. On Sep 20, 2007, at 10:57 AM, Rob Owens wrote: > ssh -o StrictHostKeyChecking=no yourhostname > > This bypasses a security check and will automatically add the host key > to the known_hosts file. > > -Rob > > >> On Sep 20, 2007, at 8:37 AM, Jon Saints wrote: >> >>> I have a number of Linux and Mac clients that acquire network >>> addresses via DHCP. The backuppc server is able to identify >>> clients without trouble using nmblookup, and I back them up using >>> SHH/rsync. >>> >>> The problem occurs when the DHCP server changes the IP address of >>> one of the clients. Once this happens, the security key exchange >>> that i did originally with the client is no longer valid. As a >>> result, subsequent backups fail. >>> >>> What is the best way around this? I prefer to keep my clients using >>> DHCP. Would using a local Certificate Authority solve this problem? >>> or is my best option to have the DHCP server assign fixed IPs to >>> the clients that need to be backed up (i would prefer to avoid this >>> if possible)? >>> >>> Thanks for your thoughts! >>> Jon >>> >>> >>> >>> >>> >>> ____________________________________________________________________ >>> __ >>> ______________ >>> Moody friends. Drama queens. Your life? Nope! - their life, your >>> story. Play Sims Stories at Yahoo! Games. >>> http://sims.yahoo.com/ >>> >>> -------------------------------------------------------------------- >>> -- >>> --- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> BackupPC-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/backuppc-users >>> http://backuppc.sourceforge.net/ >> >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> BackupPC-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/backuppc-users >> http://backuppc.sourceforge.net/ > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > BackupPC-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/backuppc-users > http://backuppc.sourceforge.net/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
