HPE 3PAR Features: HPI RFQ - 28 July 2016

HPE 3PAR Features
HPI RFQ| 28 July 2016

1
Copyright © Capgemini 2016. All Rights Reserved
Table of Contents
3PAR concepts: Networking concepts
Common Provisioning Groups (CPGs)
Virtual Volumes (VV)
Physical Copies/ Virtual Copy
Thin Reclamation / Persistence
Thin Conversion
File persona
System tuner
3PAR Features: Data optimization Dynamic/Priority Optimization

Adaptive Optimization
Adaptive flash cache
Peer Motion Peer Motion
Storage Federation
Remote copy Configurations

Quorum Witness/ Peer Persistence
File Persona Remote Copy

2
3PAR Concepts
Product and Engineering Services 3

Networking Concepts
Bond : Network bonding refers to the combination of network interfaces VLAN: A VLAN is a group of devices on one or more LANs that
on one host for redundancy and/or increased throughput. are configured to communicate as if they were attached to the
same wire, when in fact they are located on a number of different
Three modes of network bonding: LAN segments. Because VLANs are based on logical instead of
 Active-Passive: there is one NIC active while another NIC is asleep. If physical connections, they are extremely flexible.
the active NIC goes down, another NIC becomes active.
 Link Aggregation: aggregated NICs act as one NIC which results in a VLAN types:
higher throughput.  Default VLAN
 Load Balanced: the network traffic is equally balanced over the NICs  Data VLAN
of the machine  Native VLAN
 Management VLAN
 Voice VLAN

4
Common Provisioning Groups (CPGs)
Physical Disks
HPE 3PAR StoreServ
FC, NL and SSD.
Chunklets
Physical Disk Chunklets Spare Chunklets
Chunklets • All chunklets are 1 GB. • Chunklets designated as spares to
Physical disk space • 256 MB of space is reserved for the table hold relocated data during a disk
allocated in 1GB units of contents (TOC), which contains the failure or during maintenance
internal description of the System. procedures
• 4 MB of space is reserved for diagnostic
Logical Disks use—2 MB beginning after the TOC and 2
Chunklets arranged as MB from the end of the disk logical block
rows of RAID sets address.
• RAID 0
• RAID 10 (RAID 1)
• RAID 50 (RAID 5) Logical Disks
• RAID MP (Multi-Parity)
or RAID 6 Storage space to virtual volumes Created by the system
• User LDs - user storage space to virtual • Logging LDs - RAID 10 LDs that are
volumes used to temporarily hold data during
Common Provisioning • Snapshot data LDs - storage space for disk failures and disk replacement
Groups Common Provisioning Groups snapshots or virtual copies procedures
Virtual pools of logical disk • Snapshot administration LDs - storage • Preserved data LDs - RAID 10 LDs
space space for snapshot administration used to hold preserved data
Virtual Volumes
• Administration volume LDs - provide
Storage space Fully-Provisioned Volumes Thinly-Provisioned Volumes storage space for the admin volume, a
allocated to hosts single volume created on each system
during installation
Hosts

5
Virtual Volumes (VV)
Thin Deduplication is ideal for data that has a high level of

redundancy. Data sets that are good candidates for
deduplication include:
• Virtual Machine (VM) images -The operating system
binaries from multiple VMs can be reduced to a single copy
by deduplication
• Virtual Desktop Infrastructure (VDI) - Client virtualization
environments with hosted persistent desktops can achieve
excellent deduplication ratios.
• Home directory and file shares - Users often store copies
of the same file in their private workspaces and therefore
storage deduplication can offer significant space savings.
Data with a low level of redundancy should be stored on thin

provisioned volumes. Data sets that are not good candidates
for deduplication include:
• Databases - Most databases do not contain redundant
data blocks.
• Deduplicated data - Data that has already been
deduplicated on the host will not be compacted further by
storage deduplication.
• Compressed data - Compression creates a stream a
unique data that will not benefit from storage deduplication.
• Encrypted data -The use of host or SAN encryption will
also result in a stream unique of data that will not benefit
from storage deduplication.

6
Physical Copies/ Virtual Copy
Clones/Physical Copies
A clone duplicates all the data from a base volume to a destination volume. The base volume is the original volume that is copied to the
destination volume. The clone on the destination volume remains available if the original base volume becomes unavailable.
A clone requires the destination volume have usable capacity equal to or greater than the usable capacity of the base volume being cloned.
Snapshots /Virtual Copy

Unlike a clone, which is a block for block duplicate of an entire volume, snapshots preserve a bitmap of a VV at a particular point in time.
Updates to VVs are written to SD (Snap Data) space and the bitmap (Snap Admin space) of the VV.
Snapshots for FPVVs, TPVVs, clones and other snapshots are created using copy-on-write techniques available only with the HPE 3PAR
snapshot software license (aka Virtual Copy) snapshots for TDVVs are created using ROW (Redirect On Write).
Copy-on-write (copies any blocks before they are overwritten with new information):
If a block in a protected entity is to be modified, the system will copy that block to a separate snapshot area before it is overwritten with
the new information. This approach requires three I/O operations for each write: one read and two writes. Prior to overwriting a block, its
previous value must be read and then written to a different location, followed by the write of the new information.
Redirect-on-write (uses pointers to represent all protected entities):

If a block needs modification, the storage system merely redirects the pointer for that block to another block and writes the data there (i.e.
it redirects on writes). The snapshot system knows where all of the blocks are that comprise a given snapshot; in other words, it has a list
of pointers and knows the location of the blocks those pointers are referring to.

7
Thin Reclamation/Persistence
Thin Reclamation/ Persistence :

HP 3PAR Thin Persistence Software augments the benefits of HP 3PAR Thin Provisioning Software and HP 3PAR Thin Conversion
Software by ensuring that thin volumes on the HP 3PAR Storage System stay as lean and efficient as possible. HP 3PAR Thin
Persistence Software leverages the unique Thin Built In hardware capabilities of the HP 3PAR Gen3 ASIC to drive the ongoing, inline
“thinning” of volumes at wire speeds while preserving service levels and preventing disruption to production workloads.
Thin Persistence achieves this by using the zero-detection capability embedded in the HP 3PAR Gen3 ASIC to reclaim unused space
associated with data deleted from a storage volume.
A Thin Reclamation API developed in conjunction with Symantec allows host file systems to intelligently communicate with HP 3PAR
Storage Systems to reclaim space associated with file deletions.

8
Thin Conversion
Thin conversion:
HP 3PAR Thin Conversion Software leverages the zero-detection capabilities within the HP 3PAR Gen3 ASIC to drive the conversion
of inefficient, "fat" volumes on legacy arrays to more efficient, higher utilization "thin" volumes on HP 3PAR Storage Systems.
The conversion process has four steps:

• Assessment: The potential benefits of zeroing free space prior to copying or migrating the data to a TPVV
• Data preparation:
Perform clean-up tasks on the source volume by:
• Emptying trash cans or permanently deleting files.
• Archiving unused files.
• Shrinking databases.
• Deleting temporary files.
• Zeroing unused space:
Use a host application to write zeros to the allocated but unused volume space.
• Creating a physical copy:
After writing zeros to the allocated but unused space, the source volume is ready for the final phase of conversion.
 Use standard file system tools/scripts to write zero

blocks
 Zeros detected inline and mapped, not written

9
File Persona
HPE 3PAR File Persona
File Lock

10
System Tuner
Virtual Lock:
3PAR Virtual Lock is an optional feature that enforces the retention period of any volume or copy of a volume. You must
purchase the 3PAR Virtual Lock license to use this feature. Locking a volume prevents the volume from being deleted
intentionally or unintentionally before the retention period elapses.
System Tuner:
3PAR System Tuner is an optional feature that improves performance by
identifying over-used physical disks, and performing load balancing on
those disks without interrupting access.
3PAR System Tuner allows you to:

■ Perform physical disk performance tuning on an entire InServ
Storage Server or on a specified subset of disks.
■ Set performance thresholds for physical disk tuning.
■ Identify and relocate under-performing chunklets.

11
3PAR Features
Product and Engineering Services 12

Data optimization
Dynamic optimization:
HP 3PAR Dynamic Optimization Software is an autonomic storage
tiering tool that provides the ability to react quickly and non-
disruptively to changing application and infrastructure requirements.
Adaptive optimization:
Adaptive Optimization Software is a granular, policy-driven,
autonomic storage tiering software solution that delivers service level
optimization for enterprises and cloud data centers to reduce cost
while increasing agility and minimizing risk.

13
Peer Motion
The primary HPE 3PAR data migration Data migration types: Five different objects can be managed
and data mobility products are:  Online migration in peer motion from the SSMC:
 “Storage federation functionality  Minimally disruptive migration  Virtual volumes
within SSMC” (MDM)  Virtual volume sets
 “Peer Motion Utility”  Offline migration  Hosts
 “Online Import Utility”  Host sets
 Remote copy groups

14
Peer Motion - Flow
Host connected to the source array Interlinking source & destination storage systems Admit stage
Import stage Migration complete

15
Peer Motion – Storage Federation
Map of the components of the storage federation named Brussels
Peer links zoning layout for a two-member federation

16
Remote Copy - Configurations
Unidirectional 1-to-1 configuration Bidirectional 1-to-1 configuration
Synchronous long-distance configuration
N-to-1 configuration 1-to-N configuration

17
Remote Copy for Disaster Recovery
Failover Remote Copy Groups
When the source system in a Remote Copy setup becomes unavailable, perform a failover operation on the Remote Copy groups in
order to continue your normal operations on the backup systems while the primary system is down.
• Primary-Rev displays under the Backup Role column, and indicates that the groups on the backup system are now actively
performing the primary role. Any data is written to the groups on the backup system.
Switchover Remote Copy Groups

The remote copy switchover operation migrates the remote copy group from the primary to secondary without impacting the host IO.
• Primary-Rev displays under the Backup Role column, and indicates that the groups on the backup system are now actively
performing the primary role. Any data is written to the groups on the backup system.
Revert Remote Copy Groups

Undo a failover operation by reverting the Remote Copy groups to their normal state.
• Primary is displayed under the Source Role column and Secondary is displayed under the Backup Role column indicating that
the Remote Copy groups have been restored to their original roles.
Recover Remote Copy Groups

Recover the groups to the source system once the source system is brought back up.
• Secondary-Rev is displayed under the Source Role column indicating that the groups on the source system are currently acting
as backup to the groups on the backup system. Data is written to the groups on the backup system and replicated on the source
system.
Restore Remote Copy Groups

Restore the groups in order to restore the original Remote Copy relationship between your source and backup system(s).
• Primary is displayed under the Source Role column and Secondary is displayed under the Backup Role column indicating that the
Remote Copy groups have been restored to their original roles.

18
Remote Copy – Peer Persistence
Quorum witness update and status messaging
HPE 3PAR Quorum Witness

19
www.capgemini.com/P&ES

HPE 3PAR Features: HPI RFQ - 28 July 2016

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HPE 3PAR Features: HPI RFQ - 28 July 2016

Uploaded by

Copyright:

Available Formats

HPE 3PAR Features

HPI RFQ| 28 July 2016

Common Provisioning Groups (CPGs)

Virtual Volumes (VV)

Physical Copies/ Virtual Copy

Thin Reclamation / Persistence

3PAR Features: Data optimization Dynamic/Priority Optimization

Peer Motion Peer Motion

Remote copy Configurations

HPI RFQ| 28 July 2016

Product and Engineering Services 3

HPI RFQ| 28 July 2016

HPI RFQ| 28 July 2016

Thin Deduplication is ideal for data that has a high level of

Data with a low level of redundancy should be stored on thin

HPI RFQ| 28 July 2016

Snapshots /Virtual Copy

Redirect-on-write (uses pointers to represent all protected entities):

HPI RFQ| 28 July 2016

Thin Reclamation/ Persistence :

HPI RFQ| 28 July 2016

The conversion process has four steps:

 Use standard file system tools/scripts to write zero

HPI RFQ| 28 July 2016

HPI RFQ| 28 July 2016

3PAR System Tuner allows you to:

HPI RFQ| 28 July 2016

Product and Engineering Services 12

HPI RFQ| 28 July 2016

HPI RFQ| 28 July 2016

Import stage Migration complete

HPI RFQ| 28 July 2016

Peer links zoning layout for a two-member federation

HPI RFQ| 28 July 2016

Synchronous long-distance configuration

N-to-1 configuration 1-to-N configuration

HPI RFQ| 28 July 2016

Switchover Remote Copy Groups

Revert Remote Copy Groups

Recover Remote Copy Groups

Restore Remote Copy Groups

HPI RFQ| 28 July 2016

Quorum witness update and status messaging

HPE 3PAR Quorum Witness

HPI RFQ| 28 July 2016

You might also like