HP 3PAR StoreServ Concepts Guide: HP 3PAR OS 3.1.3

takes about 30 seconds, and booting takes an additional 5 seconds. Rekeying under a light load
takes about 15 seconds.
CAUTION:
Keep the encryption key file and password safe. If you lose the encryption key and the HP 3PAR
StoreServ system is still functioning, you can always perform another backup of the encryption key
file. However, should you lose the encryption key file or the password, and should the HP 3PAR
StoreServ system then fail, the HP 3PAR StoreServ system will be unable to restore access to data.
Ensure that backup copies of the latest encryption key file are kept and that the password is known.
The importance of keeping the encryption key file and password safe cannot be overstated. HP
does not have access to the encryption key or password.
Different arrays need separate backups, although the same password can be applied.
The SED DataStore provides an open interface for authentication key management. DataStore
tracks the serial number of the array that owns each SED, which disallows SEDs from being used
in other systems.
NOTE: The HP 3PAR data encryption solution will help mitigate breach notifications under the
Health Information Technology for Economic and Clinical Health (HITECH) Act, but is not compliant
with the Federal Information Processing Standard (FIPS) 140-2.
Priority Optimization
During recent years, consolidation of storage systems has reduced complexity of data storage,
delivering efficiency in management, occupied floor space, and energy consumption. However,
the consolidation of many disjoint workloads into a single storage system also results in contention
for shared system resources on the system.
Examples of such shared resources include front-end host Fiber Channel (FC), iSCSI and FCoE
adapters, back-end FC or SAS disk connections, physical disks, data and control cache, ASICs,
CPUs, and backplane interconnections. Data packets arriving at the front-end FC HBA adapters
are handled on a first-come, first-serve basis. On the surface, this may sound fair, but it can lead
to unequal and inconsistent throughput for multiple concurrent workloads.
HP 3PAR’s Priority Optimization software manages and distributes the I/O capacity of an HP 3PAR
StoreServ Storage system across multiple workloads. The tool enables the co-location of the data
of workloads of different types, such as sequential, random, online transaction processing (OLTP),
with different I/O packet sizes on a single storage system while achieving adequate and stable
performance in a multi-tenant environment.
The System Busy feature automatically manages IO latency goals. System Busy will be set to 0%
if no latency goals are set and all items under QoS rules will be delayed or rejected I/O requests
when nearing the IOPS or Max Limit of the QoS rule. If a QoS rule is defined then System Busy
level will be calculated in real-time. When Priority Optimization detects a QoS rule is not meeting
their latency goal then the System Busy level will increase and delay and/or reject lower priority
VVset IOs. The delays and rejections can reduce VVset and Domain IOPS to their Minimum Goal
IOPs, allowing higher priority QoS rules to consume the more system resources to meet their latency
goals. If the System Busy level continues to increase and high priority QoS rules on VVsets and
Domains will be delayed to the point of exceeding their latency goal. System Busy levels are
calculated every 200 ms. If the IOs miss their latency goal then the System Busy level will increase
from zero to a larger value. If the IOs meet their latency goal then the System Busy level will be
decreased.
HP 3PAR Priority Optimization software introduces quality-of-service rules to manage and control
the I/O capacity of an HP 3PAR StoreServ Storage system across multiple workloads. Application
of the rules enables co-location of the data from workloads of different types (such as sequential,
60 Enhanced Storage Applications