Simone Marzona wrote:

> what about these approaches:
> 
> - use lvm for backuppc pool, and schedule some kind of incremental dd of
> the device by taking a snapshot of the lvm volume

That should work - or the similar concept of software raid1 where you 
periodically fail/remove/add a mirror to rotate offsite.  You need a 
disk type that can be hot-swapped (usb, firewire, some SATA, some SCSI).

> - use coda or other replicating filesystem on the backuppc pool? could
> be?

I'm not sure if these work well without high-bandwidth connections.

> - use some dedicated storage that to hardware replication (like
> datadomain)
> 
> any opinion is very appreciated..

I think the zfs filesystem with snapshot and incremental send/receive 
capability sounds promising.  I just haven't had time to test it.

-- 
   Les Mikesell
     lesmikesell AT gmail DOT com


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/