On 10/25/2012 12:30 PM, Les Mikesell wrote:
> On Thu, Oct 25, 2012 at 10:38 AM, Timothy J Massey <tmassey AT obscorp DOT 
> com> wrote:
>> 1) Constantly mirroring the pool and occasionally breaking the mirror to 
>> take it off-site.  (Option 1 above).  A variation of this would be to take 
>> the pool down and make a copy of it, then bring it back up (or use LVM 
>> snapshots to reduce the downtime).  This variation is left as an exercise 
>> for the reader:  there are a *lot* of unexpected details in that answer:  
>> problems with file-level copy will most likely require block-level copies, 
>> LVM snapshots present performance and reliability issues, etc.
> This works, but has the down side of taking most of a day to re-sync
> the replaced mirror with the drives being too busy to be useful for
> much else during that time.

It's not all that bad depending on the size of the drives.  I have 1TB 
drives in a 3-way md mirror.  It takes about 3 hours to re-sync when I 
replace a drive.  You can let it re-sync during the day when backups 
aren't running.

-- 
Bowie

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
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/