Many of you have heard about the changes we've made in Exchange 2010 that combine to give you the ability to use less expensive storage and deploy large mailboxes. There have been many discussion...
Updated Jul 01, 2019
Version 2.0
Blog Post
CY -
In terms of MSIT's architecture (JBOD configuration that leverages 7.2K 1TB nearline SAS), we typically reseed from a passive copy, and thus, since the passive is doing very little work (compared with the active copy), we can achieve much higher throughput (around 70GB/hour). So with a 500GB database file, with 35GB/hr you are looking at 14 hours, or 7 hours if you are hitting around 70GB/hour.
Since the architecture has a total of 4 copies, the loss of a single copy and the reseed time (7-14 hours) is not a concern as we have 3 other copies to rely on if another failure event occurs. In fact, a reseed rate of 24 hours is not a concern due to the design.
Ross
In terms of MSIT's architecture (JBOD configuration that leverages 7.2K 1TB nearline SAS), we typically reseed from a passive copy, and thus, since the passive is doing very little work (compared with the active copy), we can achieve much higher throughput (around 70GB/hour). So with a 500GB database file, with 35GB/hr you are looking at 14 hours, or 7 hours if you are hitting around 70GB/hour.
Since the architecture has a total of 4 copies, the loss of a single copy and the reseed time (7-14 hours) is not a concern as we have 3 other copies to rely on if another failure event occurs. In fact, a reseed rate of 24 hours is not a concern due to the design.
Ross