Planning and Designing HP LeftHand SAN Solutions Rev 9.41 HP LeftHand - Technical Overview 1 © 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice HP LeftHand Product Technical Overview
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 1
© 2008 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice
HP LeftHand ProductTechnical Overview
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 2
2 For HP Internal and Partner Use Only
Objectives
• HP LeftHand (SAN/iQ)
−product features & solutions
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 3
3 For HP Internal and Partner Use Only
HP LeftHand solution portfolio
Multi-Site SAN solutions
Virtualization & StarterSAN solutions
Expansion Nodes
Virtual SAN Appliancefor VMware ESX
Physical SAN appliancesFor central main sites
Virtual SAN appliancesFor small & remote sites
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 4
4 For HP Internal and Partner Use Only
SAN/iQ Storage ClusteringTrue clustering brings reliability, performance, and ease ofmanagement
• Storage clustering
− Aggregates critical components
− Data is load balanced
− Predictable scalability
• Grow on your terms
− Scale-out storage
− Non-disruptive
− Throttle bandwidth
• Storage tiering
− Optimized for type of data
− Online volume migration
• Simple centralized management
− One step server-volume mapping
− Integrated performancemanagement
SAS
SATA
Centralized Management Console
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 5
5 For HP Internal and Partner Use Only
Multi-Subnet iSCSI Clusters
• iSCSI Clusters can span up to 3 subnets (aka: network,VLAN)
• Each Cluster/Subnet group will have its own VIP
− A cluster can have multiple VIPs for High Availability
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 6
6 For HP Internal and Partner Use Only
SAN/iQ Network RAIDAlways on storage, data remains accessible during sitefailures
• Beyond componentredundancy
− Protects data from array failure
− Synchronous replication
− Configure on a per-volumebasis
− Configure on-the-fly, no downtime
• High availability
− Multiple disks, controllers, orarrays
− Zero disruption of data access
− Ensures “high availability” fordata
SAN/iQ Cluster
A
B
C
D
A
B
C D
B
A
C
D
BA
C
D
• The goal for SAN availability is "no nines,"or 100% availability. (Gartner,2007)
• Human error and firmware bugs are theweakest links, even in properly deployedSANs. (Gartner, 2007)
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 7
7 For HP Internal and Partner Use Only
SAN/iQ Multi-site SANReal-time protection from site failure
• Protect Storage By:
− Racks
− Room
− Floor
− Building
− Site
• Keep Data OnlineDuring:
− Facility disruption
− Natural disaster
− Site maintenance
SAN/iQ ClusterSAN/iQ Multi-site SAN
A D A D
BA BA
C B BC
C D C D
Volumes Remain Online
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 8
8 For HP Internal and Partner Use Only
SAN/iQ Multi-site SAN withFail-over Clustering• Protect storage by isolating:
− Racks
− Room
− Floor
− Building
− Site
• Keep data online during:
− Facility disruption
− Natural disaster
− Site maintenance
• No manual steps forApplication / VM re-connect
− MSCS fail-over / VMwareVMotion works as expected
− Storage volumes do NOT goaway
− No re-configuration orfailover/takeover of storagerequired
SAN/iQ ClusterSAN/iQ Multi-site SAN
A D A D
BA BA
C B BC
C D C D
Standard Clustering solutions
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 9
9 For HP Internal and Partner Use Only
Automatic Data Center Mirroring
• Leverages Network RAIDLevel-2, 3 and 4 (VolumeReplication)
• SAN/iQ automaticallyorders the nodes in thecluster to span multiple sitesfor optimal High Availabilityand Fault-tolerance
• SAN/iQ prevents thecustomer from configuringtheir system into a non-Fault-tolerant system
• Setup and Configuration ofMulti-Site SAN is done viathe Cluster Wizard
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 10
10 For HP Internal and Partner Use Only
Network RAID-ADP
• Network RAID Advanced Data Protection
• Network RAID Level-2, 3 and 4 are integrated with Multi-Site SAN features toprovide optimal availability and redundancy
• Network RAID Level-4 is a Multi-Site SAN feature only
− Common use-case: 2 data centers, each data center has 2 copies of the volume for faulttolerance in the data center
A DB C
A DB C
A DB C
A DB C
Gigabit Connection
Network RAID Level-2 = Site ProtectionNetwork RAID Level-4 = Site Protection +
Fault-tolerance in remaining siteSite A Site B
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 11
11 For HP Internal and Partner Use Only
How Replication works
• Creates redundant copies ofblocks that resides ondifferent storage nodes
• Can specify up to three (3)copies will be maintained –3-way replication
• Replication level can notexceed the number of nodesin the cluster
• Recommended/default – 2-way replication
The order in which nodes are added to the cluster determines theorder in which copies of data are written to the volume.
One Cluster… Three different volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 12
12 For HP Internal and Partner Use Only
Preferred Configurations – 3-sites
• 3 Physical Sites, Failover Manager in the 3rd-site
• Automatic Failover and Failback
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 13
13 For HP Internal and Partner Use Only
Preferred Configurations – 2 Sites, 1Logical Site
• 2 Physical Sites, 1 Logical Site
• Logical Site built with separate network and power
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 14
14 For HP Internal and Partner Use Only
Other SAN/iQ / Multi-Site Features
• We will support 2-site Configurations where one of the sites is Primary =runs majority of managers
− If the Primary site fails, the customer can Recover Quorum in the secondarysite (Technical support command line function only)
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 15
15 For HP Internal and Partner Use Only
Security: Multi-Network Domain Clusters
• Customers can use the Site and Subnet capabilities to segment / isolateiSCSI data path traffic to the same cluster
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 16
16 For HP Internal and Partner Use Only
Common Multi-Site SAN Configurationswith Recommended Managers
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 17
17 For HP Internal and Partner Use Only
SAN/iQ Thin ProvisioningRaise storage utilization, increase return on investment, andreduce costs
• Cost Savings− Purchase only what you need
today
− Allocate only as data is written
− No reserve necessary
− Integrated with SmartClones,Snapshots and Remote Copy
• Delay Future StoragePurchases− Grow capacity as warranted
• Simple to Manage− Enable/disable with radio
button on per-volume basis
Full Provisioned
Thin Provisioned
50 GB written
50 GB written
50 GB written
50 GB written
200 GB Volume
200 GB Volume
Allocated 200 GB
Available 0 GB
Used 0 GB
Wasted 200 GB
Allocated 0GB
Available 200GB
Used 0GB
Wasted 0GB
Allocated 200 GB
Available 0 GB
Used 50 GB
Wasted 150 GB
Allocated 200 GB
Available 0 GB
Used 100 GB
Wasted 100 GB
Allocated 50GB
Available 150GB
Used 50GB
Wasted 0GB
Allocated 100GB
Available 100GB
Used 100GB
Wasted 0GB
Waste
Available
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 18
18 For HP Internal and Partner Use Only
SAN/iQ SnapshotsPoint-in-time, space-efficient snapshots for backup andrecovery
• Simplified Backup and Recovery
− Point-in-time volume copies
− Scheduled, ad hoc or scripted
• Functional
− Volume rollback
− Recover granular data
− Backup integration
• Microsoft VSS
• VMware VCB
• Space Efficient
− Thin provisioned always
− Delta changes only
− No snap reservation
SAN/iQ Cluster
1:00
2:00
3:00
1:00
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 19
19 For HP Internal and Partner Use Only
Snapshot Layered Architecture
• Volume/snapshot relationship canbe conceptually thought of as“layers”
• Space is allocated from thestorage pool to accommodatesnapshots
• User_Data_ss1 is the base linesnapshot, the volume is read only
• User_Data_ss2 contains the deltassince User_Data_ss1 was created
• User_Data contains the deltassince User_Data_ss2 was created.
• The User_Data volume iscomprised of User_Data +User_Data_ss2 + User_Data_ss1
User_Data
User_Data_ss1
User_Data_ss2
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 20
20 For HP Internal and Partner Use Only
Monday
Snapshot Layered Architecture – BlockLevel
• Think of a stack ofsnapshots as a stack oftransparencies
• Initially there is a singlevolume where all the readsand writes are taking place
DCA B
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 21
21 For HP Internal and Partner Use Only
User_Data
User_DataMounted as Drive U
User_Data_ss1
New volume is created tohold any changed blocks
Previous volume becomesSnapshot volume and is read only
User_Data Volumecomposed of Disk Blocks:A, B, C
User_Data Volumecomposed of MODIFIEDDisk Blocks
All Operations Transparent to the Operating System and the User Community
How a Snapshot Works
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 22
22 For HP Internal and Partner Use Only
Snapshot Layered Architecture – BlockLevel
• When a snapshot is taken,the first volume is moveddown the stack
• Another piece oftransparency paper (thenew volume) is placed onthe stack.
• The new volume is where allthe modified blocks will beheld
• The Tuesday snapshot willhold all the changed blocksfor Tuesday, in essentially itis an incremental backup
DCA B
E
D’A’
F
Monday
Tuesday
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 23
23 For HP Internal and Partner Use Only
User_Data
User_DataMounted as Drive U
New volume is created tohold any changed blocks
User_Data_ss1
Snapshot volume is readonly
User_Data Volumecomposed of Disk Blocks:A, B, C
User_Data Volumecomposed of MODIFIEDDisk Blocks: A’, D, E
Snapshot volume becomessread only
User_Data_ss2
NEW User_Data Volumecomposed of MODIFIEDDisk Blocks:
How a Snapshot Works… cont
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 24
24 For HP Internal and Partner Use Only
How SAN/iQ reads a Snapshot Volume
• When a file is read,SAN/iQ will assemble thefile
• For example if a file consistsof blocks ABCD, it will beassembled from part ofeach snapshot
• Think of this as reading astack of transparencieslooking from the top-down
• This file would consist ofblocks A” B’ C D’
D
E
D’A’
CA B
HGF’
B’A”
F
.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 25
25 For HP Internal and Partner Use Only
How SAN/iQ reads a Snapshot Volume -Cont
• If you entered the snapshotstack at a different location,the data would be different
• For example if you enteredthe stack on Tuesday andread the same file it nowwould be comprised ofblocks
• A’ B C D’
D
E
D’A’
CA B
HGF’
F
BA”
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 26
26 For HP Internal and Partner Use Only
User_DataMounted as Drive U
User_Data
User_Data_ss1
User_Data Volumecomposed of DiskBlocks: A, B, C
User_Data Volumecomposed ofMODIFIED DiskBlocks: A’, D, E User_Data_ss2
NEW User_DataVolume composedof MODIFIED DiskBlocks:
An Executive come to the ITdepartment and says they accidentallydeleted a file. The file from yesterdayis the one they need.
User_Data-ss2Mounted as Drive Z
With a snapshot you can mount thesnapshot on to a server and allow theexec to access a previous version ofthe file.
Using a Snapshot
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 27
27 For HP Internal and Partner Use Only
Writing to a snapshot
Volume Branching– Non-persistent changes– Created upon client connect– Deleted upon deleting snapshot or deleting
writable space
Volume
Snapshot
Snapshot
Snapshot
Writablesnapshot
Always thin Provisioned WritableSpace
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 28
28 For HP Internal and Partner Use Only
Rolling Back a Volume
• Replaces the original volume with a read/writecopy of the selected snapshot
• Offers DR support where snapshot is last “knowngood” state of data
• Rolling back a volume to a snapshot must beverified before the operation proceeds
• Rolling back a volume also requires a name changeto the volume. If the original name is required,simply roll back twice and give the original nameon the second roll back.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 29
29 For HP Internal and Partner Use Only
User_DataMounted as Drive U
User_Data_ss1
Snapshot volume isread only
User_Data Volumecomposed of MODIFIEDDisk Blocks: A’, D, E
Snapshot volume isread only
User_Data_ss2
User_Data
Volume created to holdany changed blocks
User_Data Volumecomposed of MODIFIEDDisk Blocks: A’’, B’, E’, F
User_Data_ss1
Snapshot volume isread only
User_Data Volumecomposed of DiskBlocks: A, B, C
User_Data
Volume becomesRead/Write
User_Data Volumecomposed of DiskBlocks: A, B, C
Remember: The volume isstill using snapshots, so therolled back volume actuallygoes to the second positionin the stack because the top
volume is where all thechanged blocks will be held
How a Rollback Works
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 30
30 For HP Internal and Partner Use Only
Rolling back a Snapshot
• When a snapshot is rolledback the top most snapshotis removed
• A new volume is placed ontop to hold all of the new orchanged blocks
D
E
D’A’
CA B
HGF’
B’A”
F
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 31
31 For HP Internal and Partner Use Only
SAN/iQ SmartCloneCost efficient volume copies that allow for quick provisioning
• Realize cost savings throughcloning
− No duplicate data, onlychanges are stored
− Ideal for storing system images
− Instant provisioning of volumecopies for test anddevelopment
− Testing can be done with realdata
− No impact to production
SmartClone Volumes
SAN/iQ Cluster
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 3232
32 For HP Internal and Partner Use Only
SmartClone Volumes
• SmartClone volumes are multiple volumes that sharea common subset of data as a base template tomake copies from.
• SmartClone volumes can be used to duplicateconfigurations or environments for widespread use.
• Also SmartClone volumes are createdinstantaneously and are fully featured, writeablepersistent volumes.
• Additionally, they help minimize space used on theSAN.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 3333
33 For HP Internal and Partner Use Only
SmartClone Volumes
• For example,
− you create a volume with a specific OS configuration.
− Then, using the Smart-Clone process, you create multiple volumes withaccess to that same OS configuration, and yet you only need a singleinstance of that configuration.
− Only as additional data is written to the different SmartClone volumesdo those volumes consume additional space within the SAN cluster.
• Some examples of SmartClone Volume use.
− Virtual Machine Clones
− Boot From SAN volume mass creation.
− Virtual Desktops
− Data Mining
− True testing of data bases without risking production data
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 34
34 For HP Internal and Partner Use Only
Planning SmartClone volumes must take into account multiple factors, such as space requirements, serveraccess, and how to manage multiple SmartClone volumes, source volume and snapshot. SmartClonevolumes inherit the size and replication level of the source volume and snapshot. By default SmartClonevolumes are thin provisioned but can be made fully provisioned after created if desired. Characteristics forSmartClone volumes are the same as for regular volumes, however, certain characteristics are sharedamong all the SmartClone volumes and snapshots. If you want to change one of these shared characteristicsfor one SmartClone volume, that change will apply to all related volumes and snapshots, including theoriginal volume and snapshot from which you created the SmartClone volumes.
SmartClone volumes are created from a Source volume with the original data in itand a Snapshot of that data from which a “Clone Point” is established. A Clonepoint is indicated with this Icon.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 35
35 For HP Internal and Partner Use Only
In the example below there are 5 SmartClone volumes created from a singlesource volume and it’s clone point. Whatever data was in the clone point at thetime of it’s creation will also be in the SmartClone volumes. However after theircreation any additional data written to one SmartClone created volume will beunique to that volume.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 36
36 For HP Internal and Partner Use Only
Some characteristics for SmartClone volumes are the same as for regular volumes. However,certain characteristics are shared among all the SmartClone volumes and snapshots. If youwant to change one of these shared characteristics for one SmartClone volume, that changewill apply to all related volumes and snapshots, including the original volume and snapshotfrom which you created the SmartClone volumes. Simply use Edit Volume on the selectedvolume, and make the change to the volume. A message opens, stating that the change willapply to all of the associated volumes, which are noted in the message.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 37
37 For HP Internal and Partner Use Only
Because the SmartClone volumes depend on the clone point from which they were created, theclone point appears underneath each SmartClone volume in the navigation window. While theclone point may appear many times, it exists as a single object within the SAN. The display inthe navigation window depicts this by the multiple highlights of the clone point underneath eachSmartClone volume that was created from it, as shown below.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 38
38 For HP Internal and Partner Use Only
Shared SnapshotsShared Snapshots occur when a newer snapshot is created that has an older snapshot in the treebelow it. They are designated with this Icon.
The reason the first two snapshots become “sharedsnapshots” is because the SmartClone volume depends on theshared data in both those snapshots.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 39
39 For HP Internal and Partner Use Only
Map View allows you to look at the tree structure from different perspectives.
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 40
40 For HP Internal and Partner Use Only
SmartClone Volumes
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 41
41 For HP Internal and Partner Use Only
SmartClone Volumes
• Everything that you can do with “regular” SAN/iQvolumes can be done with SmartClone volumesincluding the following.
−Remote IP copy
−Managed Snapshots (Scheduled)
−Full or Thin Provisioning
−Volume migration from one cluster to another. Thisrequires all associated clone points and snapshots movewith the SmartClone Volume
−Edit the size, description, server assignments,provisioning, replication level, priority and volume type(Primary vs Remote)
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 42
42 For HP Internal and Partner Use Only
SmartClone Volumes
Deleting SmartClone volumesAny volumes or snapshots that are part of a SmartClone network can be deleted just like anyother volumes or snapshots. The only exception is the clone point, which cannot be deletedas easily. However you can delete a clone point if you delete all but one volume that dependon that clone point. Once you delete all but one volume that depend on a clone point, theclone point returns to being a standard snapshot, and can be managed just like any othersnapshot.
You must delete any two of the three volumes in thisexample before you can delete the clone point.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 43
43 For HP Internal and Partner Use Only
SmartClone Volumes
• Smart Clone Volumes summary.
−SmartClone volumes are Persistent Volumes created from aSource volume with the original data in it and a Snapshotof that data from which a “Clone Point” is established.
−Space is used on the SAN only as additional informationis written to the Smart Clones if they are thin provisionedas they share the common subset of data from thetemplate, or “Original” Volume
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 44
44 For HP Internal and Partner Use Only
SAN/iQ Remote CopyTime and space-efficient asynchronous replication for disasterrecovery and backups
• AsynchronousReplication
− Per volume basis
− Scheduled or manual
− Thin provisioned
− No reserve spacerequired
− Incremental failback
• Simple to Manage
− Bandwidthmanagement
− Failover / FailbackWizard
SAN 1
SAN 2
2:00
1:00
3:003:00
2:00
1:00Baseline Copy
Incremental Copy
Incremental Copy
RecoveryServer
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 45
45 For HP Internal and Partner Use Only
SAN/iQ Remote Copy Overview
• Builds on existing volume andsnapshot features
• Remote copy is an asynchronousreplication process acrossgeographic distance to createremote snapshots
• Copies only changed blocks,extremely efficient operation
• Requires a VPN connectionbetween the primary and remotesite, or that both Managementgroups be on the same network
• Remote copy is a pull operationso the remote site will be pullingthe information from the primarysite
• Use remote copy for:
− Business continuance/DisasterRecovery
− Off-site backup and recovery
− Split mirror, data migration,content distribution
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 46
46 For HP Internal and Partner Use Only
First Remote Copy
Storage Node Storage Node Storage Node Storage Node Storage Node Storage Node
Storage Node Storage Node Storage Node
100 GB
100 GB
1 GB
Remote OperationMounted as Drive QPrimary Site Remote Site
Current changes arebeing kept here
Auto grow featureallows the volume toexpand as needed
A A A A A
Snapshot of the primaryvolume is taken and
copied to the remote site
Remote snap is anexact copy of theprimary snapshot
Remote volume
The first remote copy will need to copy all the data.Subsequent remote copies of the same volume will
only copy changed blocks.
User_DataMounted as Drive U
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 47
47 For HP Internal and Partner Use Only
Remote Copy – PrimeSync Step 1
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 48
48 For HP Internal and Partner Use Only
Remote Copy – PrimeSync Step 2
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 49
49 For HP Internal and Partner Use Only
Remote Copy – PrimeSync Step 3
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 50
50 For HP Internal and Partner Use Only
Remote Copy – PrimeSync Step 4
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 51
51 For HP Internal and Partner Use Only
Storage Node Storage Node Storage Node
User_DataMounted as Drive U
Storage Node Storage Node Storage Node
Storage Node Storage Node Storage Node
100 GB100 GB
Remote OperationMounted as Drive Q
Once at the remote site, a script canmount the remote snapshot for otheroperations like data mining or backup
Auto grow has allowedthe current volume togrow from 10GB to
15.3GB to accommodateall the changes
Primary Site Remote Site
15.3 GB
10 GB15.3 GB
New volume is placed onthe stack and the size isback at the original size
System only has to copied 15.3GB of changed blocks
As the next snapshot is taken,the volumes move down the
stack and the changed blocksare copied to the remote site
Subsequent remote copieswill continue in the same
manner.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 52
52 For HP Internal and Partner Use Only
Storage Node Storage Node Storage Node
User_DataMounted as Drive U
Storage Node Storage Node Storage Node
Storage Node Storage Node Storage Node
100 GB100 GB
1 GB
11.5 GB
15.3 GB
11.5 GB
15.3 GB
Current changes arebeing kept here
Remote OperationMounted as Drive Q
A script mounts each remotesnapshot to the backup server to
perform incremental backups
Auto grow featureallows the volume toexpand as needed
Primary Site Remote Site
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 53
53 For HP Internal and Partner Use Only
iSCSI Storage from SAN/IQ
SAN/iQ Cluster
HP P4000 Virtual SAN Appliance for VMware ESXHigh Availability for Server & Storage For Remote/Branch Offices
• Full Featured Virtual SAN
− SAN/iQ within an ESX virtualmachine
− Virtualizes ESX server’sinternal disk resources
− Up to 10 TB per VSA
− Only SAN appliance onVMware SAN/Storage HCL
• SAN/iQ cluster within ESX
− Highly Available storageacross multiple ESX systems
− Shared storage for VMs
ESXServer
ESXServer
VSAVSA
LinuxWin WinLinuxVMware HA
Vmotion
Server internal storage Server internal storage
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 54
54 For HP Internal and Partner Use Only
SAN 1 SAN 2
2:00
1:00
3:003:00
2:00
1:00Baseline Copy
Incremental Copy
Incremental Copy
VMwareESXServer
SAN/iQ
Remote Office Solution PackCost effective disaster recovery, no hardware required
• Replication for up to10 Remote Sites− No SAN hardware at
remote site
− No other vendor canoffer this
− All other offerings arehost based or requirehardware at remotesites
• Included for noadditional cost with:− Virtualization SAN
− Multi-Site SAN
• Support included withphysical SAN
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 55
55 For HP Internal and Partner Use Only
What is SAN/iQ Multi-Site HA/DRSolution Pack?
• targeted at multi-datacentercustomers
• included in SAN/iQ 8 and higher
• includes:
− Automatic Data Center Mirroring(Multi-Site SAN)
− Multi-Subnet iSCSI Clusters
− I/O Preferencing based onSite/Subnet
− Geographic / Site Awareness
− Network RAID-ADP (AdvancedData Protection)
− Automatic 2-Site Failover ANDFailback
− SAN/iQ Failover Manager
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 56
56 For HP Internal and Partner Use Only
iSCSI Communication in SAN/iQ
• SAN/iQ 6.5 and above with VIP Load Balance
− Initial communication goes through one storage node, thenit is transferred to the least busy storage node
• SAN/iQ 6.5 and above with SAN/iQ DSM MPIO(available in the Windows Solution Pack)
− Initial communication goes through one storage node, thencommunication is created to each storage node
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 57
57 For HP Internal and Partner Use Only
Cluster_0
Group_0
•Connections toeach NSM areestablished
•Connection getsredirected to leastbusy NSM
•Session staysconnected to VIP
•Session Logs intoVIP
Virtual IP Load Balancing
VIP 10.0.0.100
IP 10.0.0.20 IP 10.0.0.30
VIP with LoadBalancing
MPIO Servers
MPIO
Initiators that don’t support MPIO or VIPLB
VIP
VIPLB willredirect the
iSCSIcommand to
the least busystorage node
MPIO connectsthe host to eachstorage node.
When a read/writeoperation is
executed, it will godirectly to thecorrect node
All other initiators willcontinue to operate inthe same way. They
will be directedthrough the nodehosting the VIP
IP 10.0.0.10
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 58
58 For HP Internal and Partner Use Only
LeftHand iSCSI Virtual IP Load Balancing(VIPLB)
• Module independent, serverindependent
• Requires no special software onthe host
• Supported initiators with VIPLBenabled are listed in the interfacevia a web link so it can beupdated at any time without asoftware release
• VIPLB support for an initiator isdependant on it handling “iSCSIredirect” correctly. It is adeficiency in an initiator if it is notsupported currently.
• As more initiators are proven towork with VIPLB they will be listed
• It is generally supported on mostcurrent iSCSI initiators
• VIPLB is enabled by default in 8.0of SAN/iQ
In a multi module environment, VIPLBwill direct the iSCSI communication to
the least busy storage module.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 59
59 For HP Internal and Partner Use Only
SAN/iQ MPIO
• Part of the Windows solution pack
• Available on all platforms with 6.5 SAN/iQ andabove
• White Paper on the web site
−Shows MPIO performance improvement over non MPIO
−MPIO should be used whenever performance is anconcern
• Software driver, installed on the host
Essentially SAN/iQ MPIO provides the host with the datamapping, so the host goes directly to the storage module
to both read and write block operations.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 60
60 For HP Internal and Partner Use Only
LHN & Microsoft MPIO Support
• Overview
− LHN SAN’s support MicrosoftMPIO with LHN DeviceSpecific Module (DSM)
− Microsoft DSM is included iniSCSI Initiator package
− LHN DSM included with theLHN Solution Pack forMicrosoft Windows
− LHN DSM is supported onWindows 2003, SP1 or R2only at this time (SAN/iQ 6.6)
− During Microsoft iSCSI Initiatorinstallation, select MicrosoftMPIO Multipathing Support foriSCSI
If using SAN/iQ DSM for MPIO8.0 or higher, you do not need toinstall Microsoft MultipathingSupport for iSCSI
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 61
61 For HP Internal and Partner Use Only
LHN & Microsoft MPIO Support
• Specific modules:
− I/O Path redundancy
− I/O Path Failover
− I/O Load Balancing
• LHN DSM for enhanced functionality MPIO:
− I/O path to each storage module with volume:
• SAN/iQ DSM handles path creation automatically for Administrator
− Superior performance architecture:
• Read I/O’s serviced by module that has copy of requested data
• Write I/O’s serviced by module based on volume replication algorithm(0-, 2-or 3-way replication)
− Superior fault tolerance:
• Each storage or DSM connected volume has its own iSCSI MPIOconnection to SAN
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 62
62 For HP Internal and Partner Use Only
LHN & Microsoft MPIO Support
• LeftHand Networks DSM for MPIO:
− LHN DSM for MPIO fully understands data layout acrossmultiple storage modules & can send IO requestsconcurrently to each independent device.LHN for MPIO provides for superior performance andfault-tolerance capabilities
− LHN DSM for MPIO works with 2.03 initiator & higher
− LHN DSM for MPIO is supported on versions:Windows 2003 Server SP1; Windows 2003 Server R2
− In 8.0, it’s is unnecessary to install the Microsoft MPIOMultipathing Support for iSCSI as our Solutions Pack forWindows LHN DSM for MPIO will do this for you.
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 63
63 For HP Internal and Partner Use Only
LHN & Microsoft MPIO Support
• DSM works with Microsoft iSCSI driver in order to buildMPIO connections to SAN
• SAN/iQ DSM for MPIO is a server-side plug-in software
• Data map of volumes in storage cluster according to LHNpatented replication algorithm (read & write to correctstorage node)
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 64
64 For HP Internal and Partner Use Only
Typical MPIOLeftHand MPIO
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 65
65 For HP Internal and Partner Use Only
Standard Best Practices ArchitectureOverview
Corporate LAN10/100/1000
Storage Node Cluster
Highlights
1. Provides multiple network paths
2. Clustered Applications ensuresuser availability
3. Clustered storage ensures dataavailability
4. Eliminates any single point offailure
iSCSI SAN (Gb Ethernet)
iSCSI Target
CentralManagementConsole
iSCSI SoftwareInitiators
ExchangeSQL Fileshares
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 66
© 2008 Hewlett-Packard Development Company, L.P.The information contained herein is subject to change without notice
Customer benefits
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 67
67 For HP Internal and Partner Use Only
Storage Clustering
• Customer problems
− Large up front investment
− Inherent performance bottlenecks
− Storage controller upgrades
− Silos of storage
− Troubleshooting performance issues
• HP LeftHand storage clustering
− Pay as you grow, scale outarchitecture
− An all inclusive feature set
− Scale performance non-disruptively
− Manage all systems via single paneof glass
− Integrated performance monitor
SAS
SATA
Centralised Management Console
DiskCache
Storage Node
Hardware RAID
SAN/iQ StorageSoftware
Redundant coolingRedundant power
CPU
NICs
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 68
68 For HP Internal and Partner Use Only
Network RAID
• Customer problems
− System or box failures
− Human errors
− Power failures
− Air conditioning failures
− Availability/utilization trade off
• HP LeftHand Network RAID
− Data availability in addition tohardware RAID
− Data availability implemented at thenetwork layer
− Adjust data availability per volume
P4000 Cluster
A
B
C
D
A
B
C D
B
A
C
D
BA
C
D
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 69
69 For HP Internal and Partner Use Only
Multi-site
• Customer problems
− Traditional arrays only protectagainst component failures
• HW RAID
• Redundant components
− No protection against
• System failure
• Room maintenance
• Data center outage
• HP LeftHand Multi-Site SAN
− Keep data online during:
• Facility disruption
• Natural disaster
• Site maintenance
SAN/iQ ClusterSAN/iQ Multi-site SAN
A D A D
BA BA
C B BC
C D C D
Volumes remainonline
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 70
70 For HP Internal and Partner Use Only
Thin Provisioning
• Cost Savings− Purchase only what you need
today
− Allocate only as data is written
− No reserve necessary
− Integrated with SmartClones,Snapshots and Remote Copy
• Delay Future StoragePurchases− Grow capacity as warranted
• Simple to Manage− Enable/disable with radio
button on per-volume basis
Full Provisioned
Thin Provisioned
50 GB written
50 GB written
50 GB written
50 GB written
200 GB Volume
200 GB Volume
Allocated 200 GB
Available 0 GB
Used 0 GB
Wasted 200 GB
Allocated 0GB
Available 200GB
Used 0GB
Wasted 0GB
Allocated 200 GB
Available 0 GB
Used 50 GB
Wasted 150 GB
Allocated 200 GB
Available 0 GB
Used 100 GB
Wasted 100 GB
Allocated 50GB
Available 150GB
Used 50GB
Wasted 0GB
Allocated 100GB
Available 100GB
Used 100GB
Wasted 0GB
Waste
Available
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 71
71 For HP Internal and Partner Use Only
Snapshots
• Simplified Backup and Recovery
− Point-in-time volume copies
− Scheduled, ad hoc or scripted
• Functional
− Volume rollback
− Recover granular data
− Backup integration
• Microsoft VSS
• VMware VCB
• Space Efficient
− Thin provisioned always
− Delta changes only
− No snap reservation
SAN/iQ Cluster
1:00
2:00
3:00
1:00
Planning and Designing HP LeftHandSAN Solutions Rev 9.41
HP LeftHand - Technical Overview 72
Summary