Rob Owens wrote: > 1) I've successfully "pre-populated" backups in the following way. > > a) Configure backuppc to backup my host machine (myhost.com) over the > internet. > b) Take my host machine (myhost.com) and physically place it on the same > local network as my BackupPC server. > c) Determine the local IP address of the host machine (lets say it's > 192.168.1.100) > d) Edit /etc/hosts on the BackupPC machine to include the following line: > 192.168.1.100 myhost.com > > This "tricks" the BackupPC machine into looking on the local network for > myhost.com
Well ... I do not have the option to take the physical machines to my network (and it are about 100 servers), but I might use this trick with setting up a simulation host, filling in /etc/hosts for all hosts temporary (pointing all to the same IP), and then run all backups. That will however result in ... very much lost time :-( No other options? > 2) For remote backups, you should probably use rsync or rsyncd as your > transport. That way only the changes are transferred, even with "full" > backups. "Full" to rsync only means that it does extra checking of the > files. Specifically, it uses the --ignore-times option. So to be > clear, using rsync or rsyncd you will need to transfer the entire backup > only once. rsync is the only protocol used (Linux <-> Linux backups), so that problem is solved then. Thanx 4 the expl. Regards, -- Toni Van Remortel [EMAIL PROTECTED] ------------------------------------------------------------------------- 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/
