freebsd stable - Oct 2008 - Anyone used rsync scriptology for incremental backup?

I've seen some stuff online that made it look like using hard-link trees
and then doing some rsync worked, but some of this appears to be obsoleted
by new rsync features.  If anyone has a pointer, that would be much
appreciated.

Thanks,

-Clint

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

On Wed, Oct 29, 2008 at 04:19:26PM -0700, Clint Olsen
wrote:
> I've seen some stuff online that made it look like using hard-link
trees
> and then doing some rsync worked, but some of this appears to be obsoleted
> by new rsync features.  If anyone has a pointer, that would be much
> appreciated.
We use sysutils/rsnapshot to take care of all of this in a very clean
manner.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |

On Wednesday 29 October 2008, Clint Olsen <clint.olsen@gmail.com> sent a 
missive stating: 
> I've seen some stuff online that made it look like using hard-link
trees
> and then doing some rsync worked, but some of this appears to be obsoleted
> by new rsync features.  If anyone has a pointer, that would be much
> appreciated.
Check out rdiff-backup  it's a python script using the rsync libs.

Henrik
-- 
Henrik Hudson
rhavenn@rhavenn.net
------------------------------
"There are 10 kinds of people in the world: Those who
 understand binary and those who don't..."

Clint Olsen wrote:
> I've seen some stuff online that made it look like using hard-link
trees
> and then doing some rsync worked, but some of this appears to be obsoleted
> by new rsync features.  If anyone has a pointer, that would be much
> appreciated.
I think freebsd-stable@ is not the right place to ask...

This is part of my script I am using for "snapshotted" backups:

src_host="10.20.30.40"	# ip, ip:port, host, host.example.com:873
src_user="rsync_user"
src_module="module_name"
pass_file="/path/to/.rsync.passwd"  # file with password for
rsync_user
dest="/where/to/store/backups"
rsync_log="/var/log/rsync_backup.log"
today=`date "+%Y-%m-%d"`
yesterday=`date -v -1d "+%Y-%m-%d"`
dest_curr="${dest}/${today}"	# current backup dir by date [today]
dest_last="${dest}/${yesterday}" # last backup dir from previous day

rsync -a -H --log-file=${rsync_log} --numeric-ids 
--password-file=${pass_file} --link-dest=${dest_last} 
rsync://${src_user}@${src_host}/${src_module} ${dest_curr}


This script is runned daily from backup server (where backups are stored).
Rsync daemon is configured and running on backed up machine.

Miroslav Lachman

Clint Olsen wrote:
> I've seen some stuff online that made it look like using hard-link
trees
> and then doing some rsync worked, but some of this appears to be obsoleted
> by new rsync features.  If anyone has a pointer, that would be much
> appreciated.
Not exactly sure what you mean by "new rsync features", but I wrote
the
following script a while back with a similar purpose in mind and have 
recently updated it:

https://lauren.room52.net/svn/lstewart/misc/scripts/rolling_backups/trunk/

Username/password: guest/guest

It still needs a little bit of polishing, particularly the stats 
reporting feature, but works as is. The configure script is currently 
redundant and you can simply rename "backup.sh.in" to
"backup.sh" and
make it executable. The usage statement and comments at the top of the 
script describe how to use it.

I use it to do all my home and non realtime-critical backups, but YMMV.

Cheers,
Lawrence