Qsan SAN OS

2017

QCache 2.0

On April 13, 2017 the QSAN company announced start of addition of QCache 2.0 for the SAN OS operating system of version 4.0.

All models of DWH of the XCubeSAN XS3200 series work under control of SANOS 4.0 at the expense of what provide the most complete functionality of storage, including data availability and information resources^[1].

According to the statement of developers, the QCache 2.0 application will reduce a gap between the available cost of hard drives and high performance of SSD. QCache accelerates execution of operations of reading/record of random access per second (IOPS) for each pool of storage with selection to 32 TB capacities of SSD for a cache. On average, by estimates of QSAN, it will help to increase the speed of accomplishment of any read operations and record to 23 and 12 times respectively.

QCache 2.0 can be applied in any XCubeSAN system or XCubeDAS expansion unit connected to DWH. As result, it is possible to receive a set of pools of disks with the cache of SSD selected especially for them. At the same time not less than two and no more than eight SSD drives should fall on each separate cache pool of reading/record.

The option QCache 2.0 is available to all models of network storages XCubeSAN.

SAN OS

For April 13, 2017 SAN OS (SAN Storage Management Operating System) there is an operating system for DWH of Qsan Technology company.

Qsan SAN OS uses the selected processor core for processing of packets of iSCSI and the Fibre Channel. It allows to distribute more evenly loading between cores and to increase efficiency of the controller in general. Performance improvement at traffic handling:

• iSCSI write throughput up to 1.5 times
• FC IOPS performance up to 1.6 times

Representation of the movement of data in DWH under control of SAN OS, (2016)

SAN OS offers the built-in mechanisms of protection:

• creation of snapshots,
• cloning of sections
• remote replication.

The choice of a method of protection depends on type of the stored data. If it is temporary data, there will be enough snapshots. If important data are sales databases, contracts, etc. which should be available constantly, then the plan of their protection should include creation of copies, both local, and remote.

Notes