© 2006 EMC Corporation. All rights reserved. Managing the Data Center Section 5.2

© 2006 EMC Corporation. All rights reserved.

Managing the Data CenterManaging the Data Center

Section 5.2

© 2006 EMC Corporation. All rights reserved. Managing in the Data Center - 2

Managing in the Data Center

After completing this module, you will be able to:

Describe individual component tasks that would have to be performed in order to achieve overall data center management objectives

Explain the concept of Information Lifecycle Management


Managing Key Data Center Components

HBAHBAPortPort

HBAHBA

Cluster

IPIP

Kee

p A

live

Client

PortPort

Availability

Capacity

Performance

Security

Storage Arrays

Hosts/Servers with Applications

SAN

Network

Re

po

rting


Data Center Management

Capacity Management– Allocation of adequate resources

Availability Management– Business Continuity

Eliminate single points of failure Backup & Restore Local & Remote Replication


Data Center Management, continued

Security Management– Prevent unauthorized activities or access

Performance Management– Configure/Design for optimal operational efficiency

– Performance analysis Identify bottlenecks Recommend changes to improve performance


Data Center Management, continued

Reporting– Encompasses all data center components is used to provide

information for Capacity, Availability, Security and Performance Management

– Examples Capacity Planning

Storage Utilization File System/Database Tablespace Utilzation Port usage

Configuration/Asset Management Device Allocation Local/Remote Replica Fabric configuration – Zone and Zonesets Equipment on lease/rotation/refresh

Chargeback Based on Allocation or Utilization

Performance reports


Host

Scenario 1 – Storage Allocation to a New Server

File / Database

Mgmt

Configured

MappedHost Used

File System / Database

Used

Config New

Volumes

Assign Volumes

Ports

Storage Allocation Tasks

Array

Unconfigured

SAN

Allocate Volumes

Hosts

Reserved

SAN Zoning

Volume Group

Allocated

Host Allocated

File System Mgmt

Volume Mgmt


Array Management – Allocation Tasks

Configure new volumes (LUNs)– Choose RAID type, size and number of volumes

– Physical disks must have the required space available

Assign volumes to array front end ports– This is automatic on some arrays while on others this step must be

explicitly performed

Host Connectivity

Front End Back End

Cache

Physical Disks

Intelligent Storage System

LUN 0

LUN 1

RAID 0

RAID 1

RAID 5

…


Server must have HBA hardware installed and configured– Install the HBA hardware and the software (device driver) and

configure

Optionally install multi-pathing software– Path failover and load balancing

Server Management – HBA Configuration

HBA

HB

A D

rive

rNew Server

HBAMu

lti-

pat

h


Perform Zoning– Zone the HBAs of the new server to the designated array front end

ports via redundant fabrics Are there enough free ports on the switch? Did you check the array port utilization?

Perform LUN Masking– Grant the HBAs on the new server access to the LUNs on the array

HBA

HBA

SAN Management – Allocation Tasks

Storage Array

SW2

SW1

Port

HBA

HBA

New Server

Port

Port

Port


HBA

HBA

Server Management – Allocation …

Reconfigure Server to see new devices

Perform Volume Management tasks

Perform Database/Application tasks

HBA

HBA

LV

VG

FS

DB AppDB App


Scenario 2 – Running out of File System Space

Solutions

Offload non-critical data– Delete non-essential data

– Move older/seldom used data to other media ILM/HSM strategy Easy retrieval if needed

Extend File System– Operating System and Logical

Volume Manager dependent

– Management tasks seen in Scenario 1 will apply here as well

File System

Warning: FS is 66% Full

Critical: FS is 80% Full


No

Yes

No

Scenario 2 – Running out of File System Space, continued

Correlate File System with Volume Group or Disk Group.

Is there free space available in the VG?Execute Command to extend File System.

Is the File System being replicated?

Yes

Does the Array have configured LUNs that can be allocated?

Allocate LUNs to server

Execute Command to extend VG.

Yes

Does the array have unconfigured capacity?

Configure new LUNs

Identify/Procure another arrayNo

Does the server have additional devices available?

No

Yes

No

Done

Yes

Perform tasks to ensure that the larger File System and Volume Group are replicated correctly


Scenario 3 – Chargeback ReportStorage Arrays

SW2Hosts/Servers

with Applications

SW1

LV

VG

FSProduction

(Green)

Local Replica(Blue)

Remote Replica(Red)

DB AppDB AppLV

VG

FS

DB AppDB App

LV

VG

FS

DB AppDB App

Port

Port

Port

Port


Scenario 3 – Chargeback Report - Tasks

– Correlate Application File Systems Logical Volumes Volume Groups Host Physical Devices Array Devices (Production)

– Determine Array Devices used for Local Replication

– Determine Array Devices used for Remote Replication

– Determine storage allocated to application based on the size of the array devices

Example:Array 1

Source Vol 1

LocalReplica

Vol 1

Source Vol 2

LocalReplica

Vol 2

LV

VG

FS

Remote Array

RemoteReplica

Vol 1

RemoteReplica

Vol 2

DB AppDB App


Scenario 3 – Chargeback Report – Tasks, continued

– Determine RAID type for Production/Local Replica/Remote Replica devices

– Determine the total raw space allocated to application for production/local replication/remote replication

– Compute the chargeback amount based of price/raw GB of storage

– Repeat steps for each application and create report

– Repeat the steps each time the report is to be created (weekly/monthly)

Example:2 Source Vols = 2*10GB RAID 1 = 2* 20GB raw = 40GB

2 Local Replica Vols = 2*10GB = 2*10GB raw = 20GB

2 Remote Replica Vols = 2*10 GB RAID 5 = 2*12.5 GB raw = 25GB

Total raw storage = 40+20+25 = 85GB

Chargeback cost = 85*0.25/GB = 21.25


Information Lifecycle Management

Information Management Challenges

Information Lifecycle

Information Lifecycle Management– Definition

– Process

– Benefits

– Implementation


Key Challenges of Information Management

Informationgrowth is relentless

Informationis more strategic

than ever

Informationchanges in value

over time

Access, availability, and protection of critical information assets at optimal cost

Ability to prioritize information management based on data value

Scaling resources to manage complexity

1CHALLENGEScaling infrastructure within budget constraints

2CHALLENGE

Reducing risk of non-compliance

3CHALLENGE

4CHALLENGE

5CHALLENGE


New Order Record

Order Processing

Orders Fulfilled

WarrantyClaim

WarrantyVoided

VALUETIME

DisposeArchive

MigrateAccess

ProtectCreate

The Information Lifecycle

Sales Order Application Example


Information Lifecycle Management Definition


Information Lifecycle Management Process

AUTOMATED

Policy-based Alignment of Storage Infrastructure with Data Value

Storage infrastructure that is Application and Lifecycle Aware

FLEXIBLE

Classifydata /

applications based on

business rules

Implement policies with information

management tools

Manage storage

environment

Tierstorage

resources toalign with data

classes


Informationgrowth is relentless

Informationis more strategic

than ever

Information Lifecycle Management Benefits

1. Improve utilization of assets through tiered storage platforms

2. Simplify and automate management of information and storage infrastructure

3. Provide more cost-effective options for access, business continuity and protection

4. Ensure easy compliance through policy-based management

Informationchanges in value

over time

5. Deliver maximum value at lowest TCO by aligning storage infrastructure and management with information value


Path to Enterprise-Wide ILM

Step 1Networked Tiered Storage

Enable networked storage Automate environment Classify applications / data

App

Data

App

Data

App

Data

Automated Networked Storage

Lower cost through increased automation

Step 3Enterprise-wide ILM

Implement ILM across applications

Policy-based automation Full visibility into all information

App App App

Cross-Application ILM

Step 2Application-specific ILM

Define business policies for various information types

Deploy ILM components into principal applications

App App

Data

App

Data

ILM for Specific Applications


Module Summary

Key points covered in this module:

Individual component tasks that would have to be performed in order to achieve overall data center management objectives were illustrated– Allocation of storage to a new application server

– Running out of file system space

– Creating a chargeback report

Concept of Information Lifecycle Management


Check Your Knowledge

List the Data Center components that need to be managed?

What Storage Array tasks need to be performed in order to allocate storage to a new server?

What SAN Management tasks need to be performed in order to allocate storage to a new server?

What is Information Life Cycle Management?

What are the benefits of ILM?


Apply Your Knowledge

Upon completion of this topic, you will be able to:

Describe how EMC ControlCenter can be used to manage the Data Center


Array Configuration – Symmetrix


Array Configuration - CLARiiON

Some configuration options are only available when you select a

specific RAID Group, Storage Group or LUN


SAN Management – Zoning Operations


Array Device Masking - Symmetrix


Array Device Masking - CLARiiON

1

2


Allocation ReportsHow much storage is allocated, and where is it?


Hosts Chargeback Report

Chargeback summarizes host accessible storage devices, filesystems, and databases, independently dragged to the group


Summary

This topic introduced a very small subset of data center management tasks that can be performed using EMC ControlCenter.

Documents

© 2006 EMC Corporation. All rights reserved. Managing the Data Center Section 5.2