...
Data in ROSS starts as triple replicated, but then transforms to erasure coding for resilience without major costs. ROSS currently uses 12/16 error coding, meaning that for every 12 blocks of data stored it writes 16 blocks. Up to four blocks could be damaged before ROSS is no longer able to recover data if a fifth block were damaged. In contrast, most RAID systems only have a 1 or 2 drive redundancy. ROSS scatters the 16 storage blocks across the storage nodes on a campus, improving the performance of data retrievals and further improving the resilience of the system. Data can be access from any of the storage nodes. Currently the two systems (UAMS and UARK) are isolated from each other, not allowing replication. But the plans to join the two are in progress. Eventually all of the content in ROSS, regardless of which campus it physically lives on, would be accessible from either campus. Of course, if data living on one campus is accessed from the other campus, the access will be somewhat slower due to networking delays and bandwidth limitations going cross campus.
As mentioned, soon Grace will have an option for replicating data in Fayetteville. However, even in this case I would not consider the copy in Fayetteville as a true backup copy. The replication is good for maintaining data that needs high availability and equivalent performance regardless of which campus it is accessed from. Replication also doubles the storage cost since it reduces available storage capacity at twice the rate that non-replicated storage does. We still recommended that researchers keep backup or archive copies of data somewhere else, even if replication is turned on.
...