HP AutoRAID 12H Kurzanleitung

hp vir

tual array:

double your operating efficiency

executive summary

In today’s market environment, you are

constantly challenged

to find ways to both grow your

business and save costs. And with the current market growth uncertainties,

saving costs is getting a lot of attention by everyone from Main Street to Wall Street

to inside the Beltway. HP has invented a solution that will get you on the road to

saving money and set you up to grow revenue streams once the economy turns

around. That solution is HP’s Virtual Arrays.

It may sound complicated at first, but HP’s Virtual Arrays are simply just another

automated advancement. They free your organization from the many manual

functions required by the current vintage of arrays on the market today. Just as

automated printing machines revolutionized the publishing industry in the last

century, HP revolutionized the personal and corporate printing industry with its

industry-leading LaserJet printers. Now, HP’s Virtual Arrays are revolutionizing the

storage industry, creating industry-leading storage solutions that save your

organization 2x in operating costs over the current set of arrays on today’s market.

HP’s Virtual Arrays are automated to maximize

your operating efficiencies

and maximize your return

on investment. They are automated to save you money.

The following customer quotes and two articles explain

how HP’s Virtual Arrays deliver on this money-saving

promise. Read them for the details or have your trusted

IT professionals do this for you. Just remember that HP’s

Virtual Arrays are the only automated arrays on the

market today that offer you these cost-saving features at

a mid-range price.

Can you think of even one profitable publishing house that

has not fully adopted automated publishing equipment?

Can you think of any successful organization that has not

adopted laser printing? The same will be said for HP’s

Virtual Arrays. Capture these savings today.

table of contents

• Amazon.com i

• Room & Board i

”

• State of New Mexico

• ViaSat

• Santa Clara ii

section 1: hp storage white paper

November 2001

• virtualization, simplification and storage 1.0

• array virtualization defined 1.0

• the reasons you need more virtualization in the array 1.1

• key features of hp’s patented virtual technology 1.1

• why now is the time for array virtualization 1.2

• managing traditional storage 1.2

• configuring an array for a database 1.3

• the system administrator’s dilemma 1.4

• managing the hp virtual array 1.4

• adding capacity with hp virtual arrays 1.4

• time to implementation: formatting the array 1.5

• automating the cache parameters 1.5

• performance 1.5

• faqs 1.6

• summary 1.8

• for more information 1.8

section 2: “hp extends virtualization to

the array”

—by D.H. Brown Associates, Inc. November 15, 2001

• virtual value in hp’s va7000 series 2.0

• super redundancy enhances RAID 2.1

• reliability characteristics of hp’s va7000 series 2.2

• software extends virtual functions 2.3

customer quotes

virtualization new. Many companies have optimized their performance with HP, including: ”

Amazon.com

“We look at three things when selecting data

warehouse disks. Price per terabyte, throughput

capabilities, and availability features. With the

HP Virtual Array 7100, the price per terabyte

was extremely competitive and the throughput

was phenomenal. Our current Superdome VA7100

configuration is capable of driving three to four

gigabytes of I/O per second, and the autoraid

features of the VA7100 exceed our availability

requirements.”

Mark Dunlap

Director of Data Warehousing

Amazon.com

Room & Board

“After reviewing various competitive scenarios

for our SAP environment, we selected HP as our

single vendor with rp5450 servers and a VA7100

for our SAN. We found the set-up to be fast and

easy, and the performance excellent. It was an

easy decision to add a second virtual array, a

VA7400, to accommodate our growth and

position us for the future.”

John Focht

Systems Administrator

Room & Board

State of New Mexico

“In consolidating from eight controllers to the HP

Surestore VA7100 we expected to see some

performance degradation in running our Children,

Youth, and Family Department databases. We

haven't seen any degradation and are pleased

with the performance. We've found it very easy

to allocate space with the VA7100 and have

saved time with reduced administrative overhead.

With the AutoRAID feature, we've eliminated

worrying about mirroring. Welet AutoRAID go

to work and don't even have to think about it.”

Tom Elder

DBA 3 Children, Youth and Family

Department

State of New Mexico

customer quotes

After seven years and 20,000 sales,

we hardly consider

”

Santa Clara

“We needed to move to the next generation of

technology as we merged data centers. Wehad

outgrown the large server farm scenario and

wanted to focus on consolidation. In discussing our

current and future needs for our NT environment,

the VA7400 was the best solution. Wehave

transformed to an enterprise environment with

great expandability for the future. And as a hospital

environment with needs for an always-on, 24x7

operation, we've found a reliable solution with HP.”

Gary Davis

Hospital Information Systems Manager II

Santa Clara

ViaSat

“We selected the HP Surestore Virtual Array

7400 storage based on the number of Oracle

ERP instances that would be needed. Wefound

the Virtual Array has many more features and

capabilities than the Sun solution that was being

proposed. Wefelt it would scale the way we needed,

provided strong price/performance, and offered

excellent operating efficiencies. It has saved many

hours and long nights for our DBA’s and system

administrators. Plus, we're using the HP Surestore

tape library for efficient tape backup data protection.”

Mike Johnson

IT Manager

ViaSat

customer quotes cont’d

in storage capacity they will only become more so.

HP’s Array Virtualization is evolutionary, not

revolutionary. It is a logical progression in array

technology. It is proven. It is necessary. It is the

perfect storage area network (SAN) technology.

And it is offered only by Hewlett-Packard!

section 1

virtualization, simplification

and storage

In 2001, HP announced two new disk arrays—

the HP Surestore Virtual Array 7400 and the HP

Surestore Virtual Array 7100. This paper will focus

entirely on the virtualization technology that makes

these the easiest arrays to manage and the most

intelligently simple arrays on the market. This paper

answers the question, “What is the value

of HP’s Array Virtualization?”

For those familiar with data center environments,

virtualization is not a new concept. Virtualization

already exists to some extent at every point in the

solution stack. For example, servers, operating

systems, databases, file systems, volume managers,

drivers, switches, and storage devices all require

virtualization to achieve their purposes.

At the array level, HP’s Virtual Architecture simply

expands on already familiar ground, and it

cleanly fulfills the promise of virtualization—

it hides complexity from the administrator and

can have a dramatic and positive effect on real-

world performance.

This reduction in complexity greatly simplifies and

streamlines the data center environment.

hp’s array virtualization:

• reduces the time spent managing individual

arrays

•allows storage administrators to manage

more storage with less effort

•reduces the opportunities for human error

•frees up precious IT resources to work on

revenue-generating projects

•self-manages the RAID configuration for

optimum performance

array virtualization defined

The purpose of virtualization in any technology

is to hide complexity from the user, or in the case

of disk arrays, to hide complexity from the storage

administrator and provide a standard environment

for application development and increased

price/performance.

Disk arrays are complex devices designed for

complex tasks. A disk array with 50 disk drives

is more complex to manage than a disk array

with one drive. Armed with virtualization, an

array could potentially allow the 50 drives to be

perceived and managed as one big drive or as

one big pool of storage. The power of virtualization

is the power of simplification.

Now for the definition: Virtualization in arrays is

about creating and managing virtual storage

devices. It is about taking blocks of storage on

the disk drives and presenting them as LUNs

(logical units of storage). What system administrators

see, then, are not the actual physical disk drives

but rather a created, simplified “virtual” view of

the actual physical storage, i.e., the LUNs.

HP’s Virtual Array works with LUNs just as traditional

arrays do. However, the virtual array doesn’t

stop there. The virtual array actually manages

the disks down to the level of the smallest available

“cluster” or “chunk.” Further, while traditional

arrays utilize static address-translation algorithms

for managing the chunks, the virtual array uses

a dynamic mapping system.

1.0

hp storage white paper

These are not trivial benefits. Data centers are

already complex, and with the continued explosion

hp storage white paper

This allows the array to dynamically allocate and

de-allocate clusters of any RAID type without

affecting the logical view as seen from the server.

In other words, clusters can be moved and new

RAID 5 and RAID 1+0 stripes can be created or

extended dynamically without the host view being

changed and without system administrator

intervention.

Just as a file system on the host presents a virtualized

view of the storage to the application or user,

the virtual array presents a virtualized view of

the storage to the file system. For example, just

as you can create and delete files in a file system,

you can create and delete LUNs within the virtual

array.This degree of virtualization is what gives

the virtual array its unique ability to relieve the

system administrator of many of his/her mundane

storage management responsibilities.

the reasons you need more

virtualization in the array

• capacity requirements will always grow

• IT departments will always have a limited

budget and limited human resources for

managing storage

• virtualization improves the efficiency of

storage administrators

• virtualization reduces the training required

for people to manage storage

• data always grows, but human head count

doesn’t—virtualization reduces the number

of people required to manage storage

key features of hp’spatented

virtual technology

• automatically stripes every LUN across all

disks in a very large redundancy group

Benefit: simplifies overall management;

reduces the number of LUNs required to

“hot spots” 1

• automatically adds new disk drives into

existing RAID groups

Benefit: capacity upgrades require no

IT training, are faster, and hot spots are

virtually eliminated

• dynamically, and without any human

intervention, optimizes the RAID level to

the application workload

Benefit: performance tunes the array 24

hours per day and eliminates downtime for

reconfigurations

• allows LUNs to be created in seconds

Benefit: reduces setup times

• allows immediate use of the array after

LUN configuration

Benefit: speeds implementation time

• allows hundreds of LUNs to be created of

virtually any size—from a single megabyte

to over 2TB

Benefit: simplifies configurations, improves

application performance, and greatly

decreases management complexity and

potential for security errors

• allows any combination of disk drive

capacities and speeds within the array

Benefit: simplifies disk drive inventory

control and capacity management

• allows disk drives and controllers to be

moved to any slot in the array

Benefit: reduces the chance for human error

1.1

array virtualization defined

achieve a balanced workload and eliminates

hp storage white paper 1

why now is the time for array

virtualization

Data centers have become enormously complex.

Interestingly,new technologies that initially held

the promise of simplifying the data center have,

in fact, added to the complexity—at least for

now. Fibre Channel, SANs, and the low cost

and ease of adding storage have enabled data

centers to expand both in size and complexity.

The world is moving from SCSI to Fibre Channel.

Fibre Channel and SANs allow for more devices

to be connected together, with greater performance,

and at far greater distances. All of these are

wonderful benefits, but along with those benefits

comes an ability to now create configurations

that are larger, more complex, further apart, and

harder to manage than anything envisioned even

a few years ago. Couple this new reality with the

exponential increase in storage, fueled by its low

cost, and you have a recipe for losing control of

the data center.

Consider this: while human resources remain static,

environments grow larger and more complex.

Simplification is the only realistic answer.

Adding newer and slicker management software

oftentimes can help, but in the long term, adding

software tends to have the opposite effect of

reducing complexity. Software may give you

a central place from which to manage your

hardware and it may simplify processes, but

it doesn’t necessarily eliminate those processes.

Armed with better management software,

environments are encouraged to add more

hardware and eventually the environment

becomes as complex as it was before, but for

different reasons. And when the human resources

are already stretched to the breaking point, this is a

recipe for complexity, stress, long hours, and human

error. Virtualization is the answer. It solves the basic

underlying problem. It permanently simplifies the

environment for the system administrator.

—Chessmaster Savielly Grigorievitch

Tartakower on the game’s opening

position

Configuring and managing traditional storage

is time-consuming and challenging even for

experienced system administrators. When

configuring storage, a wide variety of factors

must be accounted for, judgments must be

made, and steps repeated over and over again.

The potential for error is high. The cost of configuring

an array improperly is also high. The administrator

must consider the following factors:

• capacity, cost, performance and availability

requirements

• requirements for future additional capacity

and performance

• number of disk drives and their capacity

• performance characteristics of the disks

• which RAID level will meet desired capacity,

cost, and availability needs

• number and type of RAID groups

• number of LUNs based on application,

performance, and array configuration needs

• size of LUNs

• configuration of the server volume manager

• cache configuration options

• stripe depth configuration

• implementation plan: who, what, and when

• time to bind LUNs

1.2

reasons for more virtualization in the array

managing traditional storage

“The mistakes are all there waiting to be made.”

section 1

In addition, the same processes must be followed

whenever disk drives are added or the environment

changes. Plus, these additional factors must be

considered:

• current configuration

• desired additional capacity, performance,

and availability

• whether the new disks will be stripe extensions

of existing disks or be independent groups

here is a typical process for setting up

a traditional array:

1. Determine number of disks, number of RAID

groups, disks and disk type per RAID

group, RAID level of each group, total

LUNs, LUNs per RAID group, stripe depth.

2. Determine volume manager configuration,

stripe size and depth, LUNs per logical

volume.

3. Using the command station, set up the

LUNs and their RAID levels and assign

them to particular disks.

4. Set up the cache page size depending

on the size of the I/Os coming in from

the host.

5. Finally, before the new LUNs can be

used, disks must be formatted, which can

take many hours per array.

configuring an array for

a database

Properly configuring an array for a database

typically involves a large problem set with many

variables. Many database administrators have

been taught to isolate different pieces of the

database in an attempt to optimize performance,

availability, and recovery. This process, although

based on sound objectives, is far too error-prone.

This typically involves a large problem set with

many, many variables. Unfortunately, database

performance requirements for each of the pieces,

and they don’t know the performance behavior

of the array in its multitude of configurations.

In these real-world environments, it is typically far

too time-consuming to try a number of different

storage configurations, so database administrators

typically apply rules from previous installations.

The changing characteristics of newer versions

of the database typically result in an unbalanced

configuration that has “hot spots” that limit the

performance of the system.

This entire process can take from a few hours

to several days, depending on the skill of the

administrator and the number and size of the

LUNs. During much of this time the array is

either unusable or must operate in a degraded

performance mode. In other words, LUNs

cannot be utilized until they have been formatted.

This formatting takes up a lot of the array’s

internal resources and bandwidth. After a LUN

has been formatted, it can be used; but as long

as other LUNs in the array are also going

through their format process, the entire array

will suffer from degraded performance.

Now, a short word about human error.Every step

of this process has the potential for human error.

Except in the grossest cases, errors would probably

not result in data loss, but every miscalculation

in this process would easily result in a decline in

performance. Some of these declines could be

huge. For example, miscalculating the RAID levels

or the cache page size could severely degrade

the array’s performance.

1.3

hp storage white paper

administrators oftentimes don’t have all the critical

information. They don’t know the precise database

section 1

the system

administrator’s dilemma

Change is the issue. Many environments change

over time and this makes their initial configurations

progressively less and less optimal. The dilemma

is that an optimum configuration today eventually

becomes out-of-date, and typically over time,

performance degrades in traditional arrays, but

the administrator usually has neither the time nor

the window of opportunity to bring the system

down and perform the necessaryreconfiguration.

Access patterns change. Different areas of the

database become more highly used. Sometimes

at the end of the month certain data that normally

lies unused now becomes highly used and requires

higher performance. All of this poses problems

for the conscientious system administrator.

At first, the administrator notices a change in

performance, but it is not enough to justify bringing

the system down. However, over time, the

performance continues to degrade until eventually

the problem is so severe that the administrator is

forced to bring the system down over the protests

of the users. He must then go through all 13

configuration steps, including binding all the

LUNs and waiting for the reformat to complete.

After that the cycle begins again: Performance

initially is great, but over time it degrades

until finally the pain increases to the point that

a reconfiguration again becomes justifiable.

managing the hp virtual array

Configuring an HP Virtual Array is much simpler

than the process for configuring a traditional

array. Remember the complex steps involved in

configuring a traditional array? The steps involved

in configuring the HP Virtual Array consist of:

• determining the total capacity and

performance requirements

• for each application, determining the

number and size of LUNs

for the necessary performance

Step away from the array; the configuration is

now complete. Every other step is automatic.

RAID levels are automatic. The different capacity,

number, and speeds of disk drives are automatically

accounted for. The cache page size is automatically

set. Even the disk formatting is performed

automatically. Moreover, after the LUNs are set,

the array is immediately available to accept data.

The array does the work, not the administrator.

Not only is this the initial configuration process,

but the process is just as simple for any subsequent

reconfigurations. In other words, if LUNs have to

be deleted and new ones created, the process is

just as simple. Note: As with any array,if you

wanted to delete the LUNs but save the data,

you would have to do a backup and restore.

adding capacity with

hp virtual arrays

HP’s Virtual Array Architecture also simplifies the

process of adding capacity to an array. Today,

many traditional arrays allow the administrator

to add disks on-the-fly—in other words, to add a

disk drive when the array is up and running and

accepting I/Os.

However, when the disk drive is added to a

traditional array, it is not part of any LUN. It is

not formatted, and it is not able to accept data.

An administrator must go in and manually perform

those functions. If the disk drive is to be added

to an already existing RAID group, then the data

in that group must first be backed-up and later

restored to the newly created LUN that now

contains the new disk drive. And except for the

backup, the steps are the same as when an

array is first configured.

1.4

hp storage white paper

• determining the number of disks required

• creating the LUNs—note: creating LUNs

takes only a few seconds per LUN

Dieses Handbuch passt für folgende Modelle

Inhaltsverzeichnis

Andere HP Lagerung Handbücher

HP StorageWorks 8B - FC Entry Switch Bedienungsanleitung

HP StorageWorks 600 - Modular Disk System Bedienungsanleitung

HP StorageWorks 8000 - NAS Bedienungsanleitung

HP N1528A Bedienungsanleitung

HP Surestore Tape Library Model 2/28 Bedienungsanleitung

HP StorageWorks 4000/6000/8000 - Enterprise Virtual... Bedienungsanleitung

HP 4X Bedienungsanleitung

HP StorageWorks P4000 Series Bedienungsanleitung

HP Surestore 64 - Director Switch Bedienungsanleitung

HP StorageWorks 2/128 - SAN Director Switch Bedienungsanleitung

HP StorageWorks 2000s Bedienungsanleitung

HP Xw8200 - Workstation - 1 GB RAM Referenzhandbuch

HP StorageWorks EVA4000 Leitfaden

HP 9153A Bedienungsanleitung

HP StorageWorks 3800ux Bedienungsanleitung

HP C7745NB - SureStore DLT Tape Autoloader 1/9 Bedienungsanleitung

HP D2D Bedienungsanleitung

HP StorageWorks NAS b2000 - v2 Bedienungsanleitung

HP StorageWorks DLT80 Bedienungsanleitung

HP StorageWorks 2012i Bedienungsanleitung

HP STOREEVER LTO 4 Bedienungsanleitung

HP Xw6600 - Workstation - 2 GB RAM Bedienungsanleitung

HP StorageWorks 7100 - Virtual Array Technisches Dokument

HP SSD Bedienungsanleitung

Beliebte Lagerung Handbücher anderer Marken

QNAP

QNAP TS 32PXU Series Bedienungsanleitung

LaCie

LaCie RUGGED RAID Bedienungsanleitung

Freecom

Freecom CLS DOCK Bedienungsanleitung

PNY

PNY Attache P-FD64MBATT3 Bedienungsanleitung

OLT

OLT 6x6 Maximizer Bedienungsanleitung

Transcend

Transcend JetFlash 160 Bedienungsanleitung

LaCie

LaCie RUGGED MINI Bedienungsanleitung

Thunderbolt

Thunderbolt 600 Bedienungsanleitung

Panasonic

Panasonic LB-DH8 series Handbuch

Intel

Intel RAID High Availability Bedienungsanleitung

LaCie

LaCie 12big Thunderbolt 3 Bedienungsanleitung

Spectra Logic

Spectra Logic T-Series Spectra T50e Bedienungsanleitung

Panasonic

Panasonic LKM-F931-1 Bedienungsanleitung

Tabernus

Tabernus Enterprise Erase E2400 Bedienungsanleitung

Rocstor

Rocstor COMMANDER 3F series Bedienungsanleitung

Western Digital

Western Digital Ultrastar Data60 Bedienungsanleitung

Dell

Dell PowerVault MD3600f Series Bedienungsanleitung

CFI

CFI TERA STOR SATA RAID IV Bedienungsanleitung