Monday, January 16, 2017

HP 3PAR Storeserv Tutorial



HP 3PAR Storeserv Tutorial:

HP 3PAR storage systems include the hardware components that physically store your data and the software applications that manage your data.

The HP 3PAR storage system is composed of the following logical data layers:

• Physical Disks
• Chunklets
• Logical Disks
• Common Provisioning Groups
• Virtual Volumes

Chunklets are drawn from physical disks,
logical disks are created from groups of chunklets, common provisioning groups (CPGs) are groups of logical disks, and virtual volumes use storage space provided by CPGs. The virtual volumes are exported to hosts and are the only data layer visible to hosts.

Physical Disks

A physical disk is a hard drive mounted on a drive magazine located in an HP 3PAR storage system drive cage.

Chunklets

Physical disks are divided into chunklets. Each chunklet occupies contiguous space on a physical disk. On F-Class and T-Class systems all chunklets are 256 MB. On 10000 and 7000 systems all chunklets are 1 GB. Chunklets are automatically created by the HP 3PAR Operating System and they are used to create logical disks.

Logical Disks

A logical disk is a collection of physical disk chunklets arranged as rows of RAID sets. Each RAID set is made up of chunklets from different physical disks. Logical disks are pooled together in Common Provisioning Groups (CPGs) which allocate space to virtual volumes.

Common Provisioning Groups

A CPG is a virtual pool of logical disks that allocates space to virtual volumes on demand. A CPG allows virtual volumes to share the CPG resources. You can create fully provisioned virtual volumes (FPVVs) and thinly-provisioned virtual volumes (TPVVs) that draw space from a CPG logical disk pool.

Virtual Volumes

Virtual volumes draw their resources from CPGs, and volumes are exported as logical unit numbers (LUNs) to hosts. Virtual volumes are the only data layers visible to the hosts.

Fully-provisioned Virtual Volumes

An FPVV is a volume that uses logical disks that belong to a CPG. Unlike TPVVs, FPVVs have a set amount of user space that is allocated for user data.

Thinly-provisioned Virtual Volumes

A TPVV is a volume that uses logical disks that belong to a CPG. TPVVs associated with the same CPG draw space from the logical disk pool as needed, allocating space on demand in small increments for each controller node.

Physical Copies

A physical copy is a full copy of a volume. The data in a physical copy is static; it is not updated with subsequent changes to the parent volume. The parent volume is the original volume that is copied to the destination volume.

Virtual Copy Snapshots

A snapshot is a virtual copy of a base volume. The base volume is the original volume that is copied. Unlike a physical copy, which is a duplicate of an entire volume, a virtual copy only records changes to the base volume.

Exporting Virtual Volumes

For a host to see a virtual volume, the volume must be exported as a LUN. Volumes are exported by creating Virtual Volume-LUN pairings (VLUNs) on the system.

Install the HP 3PAR Management studio to access the HP 3PAR.








Login through HP 3PAR Management console.



Using this GUI, you can manage the ports, controllers, hosts and volumes.


In this you can see full summary of storage system and controller nodes and ports.


You can see the complete disk information.



You can list the software information.




Controller information.



Listing and managing ports.




Listing drive cage information.



List and Manage the disk information.




Configuring FC ports.



Listing and Host management.



Creating and managing hosts.




Add the initiator name like wwpn or iqn.



Add the iqn number.



Host successfully created.


Listing and managing paths.




Managing and provisioning volumes.




Listing and Managing CPG's.


Creating a new CPG wirh RAID level and disk type.




Listing and managing virtual volumes.


Managing VV and creating virtual copy.


Managing AO (Adaptive Optimization) and Remote Copy.


Managing user Administration.



Hardware Inventory.




Managing through SSH.

Some command examples.





Friday, January 13, 2017

ONTAP 9 HA - Storage Fail over



ONTAP 9 HA - Storage Fail over :


An HA pair is two storage systems (nodes) whose controllers are connected to each other directly. In this configuration, one node can take over its partner's storage to provide continued data service if the partner goes down.
You can configure the HA pair so that each node in the pair shares access to a common set of storage, subnets, and tape drives, or each node can own its own distinct set of storage.
The controllers are connected to each other through an HA interconnect. This allows one node to serve data that resides on the disks of its failed partner node. Each node continually monitors its partner, mirroring the data for each other’s nonvolatile memory (NVRAM or NVMEM). The interconnect is internal and requires no external cabling if both controllers are in the same chassis.
Takeover is the process in which a node takes over the storage of its partner. Giveback is the process in which that storage is returned to the partner. Both processes can be initiated manually or configured for automatic initiation.

HA would manage by either System Manager or CLI.

Managing HA using GUI and CLI.

1. To check the HA status.


2. Cluster and HA status using CLI.


3. List the storage  fail over status.




4. Due to maintenance activity like any tech refresh, any will take care of another partner node.



5. LIF's will then migrate to the active node.



6. Take over in progress.



7. Take over is successfully completed.

 

8. Run the cluster show command to list the node status.



9. Check the LIF status.



10. Now you run give back.





11. Now give back is done.




12. Now you list the node status.


Now check the interconnect also.

Both are up and working fine.