Re: [rdiff-backup-users] feature suggestions

[aurbain]

Philippe Froidevaux wrote:
> > > 2. backwards compatibility
> > > I know this is hard to implement. But in a large network, you can't
> > > live without. (think http 1.0 and http 1.1, ssh 1 and 2)
> > > That's my suggestion for future versions. Provide some level of
> > > compatibility between stable releases of rdiff-backup. So you only
> > > have to upgrade the rdiff-backup install on you backup server(s).
> > >   
> > >       
> > We eliminate the client completely by installing rdiff only on backup
> > server and mount remote boxes via fuse and sshfs.  Simple.  Works great.
> >     
>
> not sure it works well if you have a lot of Terabytes to backup :)
>
>
>   
Please be aware that rdiff-backup connecting to rdiff-backup uses the 
same mechanism as rdiff to sshfs, ie: ssh. 

That said, I'm pretty sure the sshfs method works.

In my DR site,  I'm using  pair of hp dl360-g5 8-cores, each has two 
MSA-20s filled with 250G sata = 4T local raid 5.     I'm backing up 
100's of mac and linux desktops and smaller linux servers with sshfs 
several times a day.  For the linux nfs clusters (fibre connected to 4 
eva8000s = 30T) I nfs mount them nightly from the backup servers over 
link-aggregated (using 802.3ad)  1G drops from a 48-port gig switch with 
10G uplinks to the nfs servers.  Poor man's fractional 10G for cheap.  
Cisco 48 switch=$9k.  If I need more b/w, I add another quad nic to the 
backup server and drop another 1G line.     While the initial full 
backup takes all weekend, the nightly deltas fit into my 15 hour backup 
window very nicely.    Works for me.

I tip the hat on top of my orange fright-wig to rdiff-backup.  Well 
done, folks.

Is anyone else using rdiff-backup in a large environment?  Please describe?