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 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. Search the archives for "rsync incremental-only backups for eternity" in July of 2007. -Rob Toni Van Remortel wrote: > Hi, > > Two issues we have before using BackupPC are this: > 1) Can we pre-populate backups with offsite backup data? > 2) Can we set BackupPC to only make incremental backups? > > The reason for 1) is that we have big remote data servers that need to > be backed up over slow lines. So we can take local backups to eg USB > disks and use them as 'start point' for incremental backups. Thus > reducing data transfers for the remote servers. > 2) is an obvious result of explanation 1) :-) > > Thanks. ------------------------------------------------------------------------- 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/
