Cisco UCS S3260 M5 Посібник з проектування - Сторінка 27
Переглянути онлайн або завантажити pdf Посібник з проектування для Сервер Cisco UCS S3260 M5. Cisco UCS S3260 M5 35 сторінок. Server with cloudian hyperstore object storage
Друкувати сторінкуDesign Criteria
Physical Infrastructure Considerations
Single Node versus Dual Node Cisco UCS S3260
Cisco UCS S3260 is offered with single node and dual node configurations for a full chassis in a 4RU rack space.
Cluster may be categorized as capacity-based or performance-based depending on the requirements. A dual
server offers double the CPU and memory for the same set of disks. So, when performance is more important, a
dual node configuration is recommended.
When performance is not that important and fewer cores per disk suffice as in backup or archives, a single node
configuration is recommended. This also reduces the TCO of the solution.
Replication versus Erasure Coding
Central to Cloudian's data protection are its storage policies. These policies are ways of protecting data so that
it's durable and highly available to users. The Cloudian HyperStore system lets you preconfigure one or more
storage policies. Users, when creating a new storage bucket, can choose which preconfigured storage policy to
use to protect data in that bucket. Users cannot create buckets until you have created at least one storage policy.
For each storage policy that you create, you can choose from the following two data protection methods:
Replication
With replication, a configurable number of copies of each data object are maintained in the system, and each
copy is stored on a different node. For example, with 3X replication 3 copies of each object are stored, with each
copy on a different node.
Erasure Coding
With erasure coding, each object is encoded into a configurable number (known as the "k" value) of data
fragments plus a configurable number (the "m" value) of redundant parity fragments. Each fragment is stored on a
different node, and the object can be decoded from any "k" number of fragments. For example, in a 4:2 erasure
coding configuration (4 data fragments plus 2 parity fragments), each object is encoded into a total of 6
27