Ralf Bertling wrote:
I am not an expert, but the MTTDL is in tousands of years when using  
raidz2 with a hot-spare and regular scrubbing.
If you add zpool send/receive and geographically dislocated severs,  
this may be better than optical media, because you detect the errors  
early.
  
Two things to be aware of with this type of statistical info ( also true for MTBF ),
It is statistical info and it is an average, it does not give any guarantee that a catastrophic event will not happen in the next hr.
Secondly this figure is defined on subsystem level, if the box goes up in smoke the thousands of years MTTDL is of no use!

So the moral of the story is to always plan for a second copy of your data if you want to design resilience from a data set point of view.
-- 
Regards Peter Brouwer,
Sun Microsystems Linlithgow
Principal Storage Architect, ABCP DRII Consultant
Office:    +44 (0) 1506 672767
Mobile:    +44 (0) 7720 598226
Skype :    flyingdutchman_,flyingdutchman_l


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
          • ... Mark A. Carlson
            • ... Bob Friesenhahn
              • ... Gregory Matthews
  • ... Scott
  • ... Ralf Bertling
    • ... Bob Friesenhahn
      • ... Jonathan Loran
        • ... Bob Friesenhahn
          • ... Jonathan Loran
            • ... Bob Friesenhahn
    • ... Peter Brouwer, Principal Storage Architect, Office of the Chief Technologist, Sun MicroSystems

Reply via email to