2010 Oracle Corporation - DOAG Deutsche ORACLE ... · 4 © 2010 Oracle Corporation Agenda Unified...

<Insert Picture Here>

© 2010 Oracle Corporation 2

Karlheinz Vogel Storage ConsultantOracle Hardware Sales

SUN STORAGE 7000 SYSTEMS FROM ORACLEGeneral Guidelines, Use Cases, Best Practice


The following is intended to outline our general product direction. It is intended for information

purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any

material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any

features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


<Insert Picture Here>

Agenda

➢ Unified Storage Introduction➢ Unified Storage General Guidelines➢ Unified Storage Use Cases and Best Practice➢ Q&A


Introduction


Breakthrough Storage Economics

Gain significant cost savings• Reduce your footprint and power bill• Speed – Better price/performance• Reduce operational costs with simple data management• No additional software license fees• Enjoy a Single Point of Contact (SPOC) with Oracle

Services

Sun Storage 7000 Systems

• Fastest ramping storage product in Sun/Oracle history• In first year and half:

• Shipped over 3700+ systems • Shipped over 80PB+ of storage


Architecture – Unified StorageIntegration of Standard Hardware, Operating System and IO Protocols, extended by High Performance Flash

Software Storage

ServersServices

Microelectronics

Network.comSPARC 64

SAN / NAS / IB...

Unified Storage System Optimized for Unified Access


Oracle Solaris™OS – The Heart of Unified Storage Systems

•Storage Pools•Raid •Checksum•Compression•Snapshot•De-duplication•Replication•Block protocols iSCSI, FC•File protocols NFS, Cifs..•Network•Security•Etc. etc.


BEST DENSITY ACTIVE-ACTIVE CONTROLLERS

BEST SCALABILITY ACTIVE-ACTIVE CONTROLLERS

BEST VALUE FULL SUITE OF

DATA SERVICES

NEW BENEFITSBest Density and Scale: Industry-leading density, scale up to 1PB for ConsolidationFlash Everywhere and More Of It: Industry-leading flash capacity for Application PerformanceDoubled the Processing Power: Performance to drive enterprise Data Protection

STANDARD FEATURES (ALL MODELS)All Data Protocols: FC, iSCSI, IB, NFS, CIFS, WebDAV, etc.

Advanced Data Services: Snap, dedup., compression, replication, etc.

CLIENTS AND APPLICATIONS (ALL MODELS)Oracle Solaris • Oracle LinuxOracle Database, Middleware, and ApplicationsOracle VM • VMware • WindowsMore than 50 business applications supported

ZFS Storage AppliancesSecond Generation Systems

BEST FLEXIBILITY SINGLE OR DUAL

CONTROLLERS


Storage Software Included at No Additional Cost

Hybrid Storage PoolSingle, Double&Triple Parity RAID (RAIDZ, Z2, Z3)Mirroring & Triple MirroringEnd-to-End Data IntegrityRemote ReplicationSnapshots and ClonesQuota(s)In-line DedupCompressionThin ProvisioningAntivirus via ICAP ProtocolOnline Data MigrationClustering

Data Protocols Data Services Management Fibre Channel• iSCSI• Infiniband over IP/RDMA• iSER• SRP • NFS v3 and v4• CIFS• HTTP• WebDAV• FTP• NDMP v4• - ZFS NDMP

Browser and CLI Interface Management Dashboard Hardware/component view Role-based AccessControl Phone Home Event and Threshold based Alerting Dtrace Analytics Scripting Workflow Automation Advanced Networking DFS Standalone Namespace Source Aware Routing

Sun Unified Storage Systems

New!

New!

New!


Sun Unified StorageBest Speed and EfficiencyOnly Storage Appliance with Hybrid Storage Pools (HSPs)• Data is intelligently and automatically migrated

between DRAM, Flash and Disk

• Continuously optimizes storage system performance and efficiency

• Simplifies management, transparently managed as a single storage pool

• Combines high density 7200 RPM SAS drives with Read and Write SSD for best price/performance

• Delivers great performance while reducing rack space and power consumption per TB dramatically

Write SSD

7200 RPM SAS HDD

ReadSSD


7000 Unified StorageBest in Management Simplicity

Only Storage Appliance with Dtrace Analytics• Automatic real-time visualization ofapplication and storage related workloads

• Simple yet sophisticated instrumentationprovides real-time comprehensive analysis

• Supports multiple simultaneous applicationand workload analysis in real-time

• Analysis can be saved, exported andreplayed for further analysis

“S7000 series presents a very simple, straightforward management model. It represents refreshing and original insights into reducing storage complexity and cuts through layers of fossilized storage technology thinking...”David Allen, Senior Vice President & CTO


7000 Unified Storage SystemKey storage subsystems instrumented with DTrace

• NFS v3 and V4• CIFS• ISCSI• FC• ZFS• CPU• Memory Utilization• Networking• and more....


AnalyticsReal-time graphical business analytics

• “What files are hot right now?”• “What is the distribution of reads

and writes?”• “Which clients are hot right now,

displayed by protocol?”

• Group analytics into worksheets, can be made persistent

• Data can be exported for further number crunching, or can be saved on the appliance


General Guidelines


7120 for: general purpose file sharing, web storage, entry level storage application requirements robust data services at entry level price low to medium capacity requirement (12 to 120TB)

7320 for: general purpose file sharing, virtualization, streaming workloads such as video/media high availability, good performance, scalability limited to 192TB

7420 for: consolidated of virtualization environments requiring multiple data services,

heterogeneous file sharing and bulk storage high availability, high performance, high scalability (over 1 PB)

7720 for: consolidated environments requiring multiple data services, heterogeneous file sharing,

large capacity storage environments (bulk storage consolidation, backup/archival) Highest-availability, high performance, highest density (720 TB per 19” rack)

Use the Storage 7000


7000 Key Target Environments

• Any current customers• Customers who require NAS with high level of data services (snapshot,

replication, thin provisoning, de-dup, compression,etc.)• Customers looking to add Bulk (Tier 2) storage

– $/GB is a primary business driver– To support consolidation, application upgrade, data protection

initiatives– 100% availability not an absolute requirement

• Customers need to lower TCO– Low acquisition costs, managing licenses a nightmare– Lower floor space requirements, better density– Reduced power & cooling requirements


7000 NOT Key Targets (Today)

• Environments currently not optimal • Customers who have tight application integration ( eg. VMWare w/

Snap Manager Integration )• Customers looking to replace Tier 1 storage

• High volume OLTP• Synchronous replication• 100% availability

• Customers who want the absolutely lowest capacity/cost solution• Customers who require compliance archiving

• Strict, storage WORM centric• Customers who require Gateways


How many CPUs do you need ?

• only for 7420 • Always ask: Which data services will be used?• When max # of CPU's help/required when:

– max RAM needed (CPU's are required)– high 10GigE or multiple quad-GigE used w/LACP (for

TCP/IP interrupts)– high Compression and/or Dedupe and/or Replication usage


How much Memory ?

• Maximizing recommended– Easiest performance win– Memory is used as a cache for data blocks (ARC)

• Try to size so that “working set” fits into appliance memory– working set size = amount of actively processed data

• RAM needed for readzillas ( ~ 2.5% size of RZ) and de-dup (DDT)


How Many Storage Pools ?

• 2010.Q1 firmware introduced support for:• >1 storage pool per head

• For good performance we need as many drives and SSDs as possible per pool so discourage lots of small pools!

• A Log or Read SSD can only be part of ONE pool so if you have many pools you need to include dedicated SSDs for each pool as required

• GOOD Reason for Multiple Pools: applications/general usage dictate different RAID levels required within an appliance e.g. Mirrors for Exchange, DP RAID for Home Folders

• BAD Reason for Multiple Pools: Customer wants create separate pools for different projects/departments → Use projects, roles, access rights


Log SSDs for Synchronous Writes

• Applications control Synchronous Writes– Databases– Email Systems– Writes over NFS (e.g. at file close)– Writes over CIFS are NOT synchronous writes on the

appliance unless the application writing requests them

– Writes to Fibre Channel & iSCSI LUNs are always synchronous on the appliance

• Also known as logzillas and write optimized SSDs• Log SSDs accelerate Synchronous Writes

> Synchronous writes do not complete until stored somewhere non-volatile


Log SSD BIG RULES

Need one log SSD / log SSD mirror per 100 MB/sec of synchronous (*) writes/3300 4K IOPS/sec

Log SSDs are required when apps or protocols doing sync writes are going to be used

No need to mirror log SSDs - Stripe for best performance Not protected against DOUBLE failure though(SSD “lights out” failure (rare) + box crash + within 5 seconds)

Always configure a minimum of two log SDDs in (Log SSD can only be part of ONE pool, you might have multiple pools)

(*) additional asynchronous writes do not use log SSDs


Read SSD BIG RULES

• Also known as readzillas and Read Optimized SSDs• Now 512 GB usable capacity• Very fast read response times < 1millisecond• ZFS L2ARC sits on these• L2ARC stores frequently accessed randomly read data

blocks as second level cache to ARC Read SSDs can be added to a 73/74/7720 non-distruptively Each Read SSD can service 5000 x 8 Kbyte IOPS/sec While a Read SSD is being written to it is not available for

reading, configure a minimum of two Read SDDs in (or more for multiple pools)

be aware: Readzillas need warm-up time!(e.g. 2000 random read IOPS x 8 kB = 16 MB/s ==> 1TB = 1000000 / 16 = 17,5 hours warmup)


Deep(er) Dive on Storage Pools

• Storage Pool Comprises multiple RAID stripes of disks called vdevs

• Each record is striped across the disks in a single vdev

• IOPS are spread across the vdevs

• Performance is a function of> vdev RAID Level> Number of disks in the vdev> Number of vdevs in the pool> Available IOPS Per Drive Pool

Disk

vdev

Record


Sizing for Random Workloads

• Most Workloads we have to size for are random• Database, Email, Fileservers, VMware

• Random Reads> Random Reads are challenging as 7200 RPM drives do

roughly of 100 IOPS/sec> ZFS caching and prefetching aim to compensate for this

but caching depends upon a dataset being accessed over “long” periods (hours/days)

• Random Writes> Writes are serviced by DRAM (and SSD for sync writes)> ZFS aggregates writes and flushes them to disk

asychronously


Choosing a RAID LevelDouble Parity

RAID is default. Not a Good Choice for Random

Workloads

© 2010 Oracle Corporation 28

How Many IOPS Per vdev ?

RAID Level Write IOPS Available per vdev

Read IOPS Available per vdev

Mirror X X*2RAIDZ1 X XRAIDZ2 X X

• Where:> X=number of IOPS available per diskIn Other Words: As a First Estimate a RAID Stripe (vdev)

Only Runs At The Speed of one drive

Supporting data at:http://blogs.sun.com/roch/entry/when_to_and_not_to

http://blogs.sun.com/relling/entry/zfs_raid_recommendations_space_performance


How Many IOPS on Physical Disks (pool)

• assuming 100 IOPS per drive / vdev

Pool Type vdevs Raw Usable Capacity

Available in the Pool

Disk Write IOPS Available in the

Pool

Disk Read IOPS Available in the

Pool

Mirror 21 * 2 disk 21TB 2100 IOPS 4200 IOPS*

RAIDZ1 10 * 4 disk 30TB 1000 IOPS 1000 IOPS

RAIDZ2 3 * 14 Disk 36TB 300 IOPS 300 IOPS

*assumes that both sides of mirror independently service reads


RAID & IOPS BIG RULES

• The more disks in a pool the more IOPS available so keep the number of storage pools to a minimum

• Assume 100 Random IOPS/vdev• For random and/or latency sensitive workloads

• Use a mirrored pool and have enough Log & Read SSD

• RAIDZ2/Z3 provide great usable capacity for archives and filestores but don't use it where random workloads are expected


Let's not forget Sequential...

• Rule of Thumb for Front-End Bandwidth per Tray: 160MB/sec per SATA trays of FRONT-END Bandwidth– Can be anywhere between 160MB/sec – 300MB/sec

• have seen higher per tray (i.e. > 300MB/sec)(160MB/sec/tray a good conservative sequential average)

• back-end bandwidth could be 2x (think mirrored)• RAIDZ1 can be best compromise between Mirrors and

RAIDZ2/Z3 for sequential.• Expect ~ 15% performance hit for RAIDZ2/Z3 over

RAIDZ1 for sequential workloads• multi-pool support now can separate more random

workloads from sequential (but do not define to many pools !!)


Block Support – iSCSI & FC

• Set reasonable expectations about LUN Failover times in Clusters> Applications must be tolerant of failover times, can be over 1 minute

• In very high availability scenarios consider mirroring FC and iSCSI LUNs at the host level between the nodes of one cluster or between the nodes of two separate clusters to remove dependency on cluster failover and LUN availability


De-Duplication

• 2010.Q1 introduces support for ZFS block level de-duplication> Blocks must be identical to de-duplicate.> De-duplication ratios will be affected by data type, block size

and data retention > Enabled per filesystem/LUN

> Not effective with backup data due to block alignment differing between backup> Consider using compression or use native dedup features of

backup product


Use Cases& Best Practice


Business Drivers• Reduce management costs• Increase IT utilization• Increase IT agility

Core Product Requirements• Performance at Scale• Cost (Mgmt, $/GB, W/GB, $/IOPS)• Visibility/Control

Oracle Unified Storage (7000) excels at all three!

• Great for bulk storage requirements • Broad set of data protocols and data

services • No added software fees or licenses

Storage Consolidation

Unified Storage was considered a tier-2 storage solution and is now moving up to the data center as an alternative to SAN storage.”

FutureGov, June 2010

LAN SAN

Outlook usersFile clients

ExchangeServers

SQLServers

FCiSCSINAS

Unified Storage7410C

Pooled Management

Consistent Processes

Thin Provisioning

Deduplication

Compression

Writable Snapshots

Replication

NFS, CIFS, iSCSI Fibre Channel


Unified File Server for Windows and Unix

NFS CIFS

• Integrate into existing directory services• Provision shares according to exisiting rules• Allow Unix users to access Windows shares and vice versa• Use Identity Mapping to smoothly integrate• Use storage based Snapshots and Remote Replication• Extend by Thin Provisioning and Deduplication

TCP/IP

NFS CIFS1. create new data

2. store new data

3. need access to data from different client


Oracle Data Base Storage Consolidation

Fibre Channel

DB Replication

Data Base Cloning at a Single Click Faster Application Development and Deployment Always up-to-date Training Ressources

Clone is a virtual device (pointers)Additional space only required when new data written to cloneOracle Data Guard


Business Drivers• Reduce risk (lose/litigation)• Increase productivity• Long-term retention (data mining)• Shorten back-up windows

Core Product Requirements• Highly available architecture• Scalable, multi-tiered solution• Data movement software (app. Int.)• Services (migration, scripting, etc.)

Sun Storage 7000• Use compression for >50% space

savings• Certified with a number of data

protection & backup apps

Data Protection

Media Management with B/U app

To DR Site

Primary Disk

Tape Library

Secondary Disk

Sun Storage 7000

Client #1 Client #2 Client #3 Client #4

Primary Disk @ DR Site

Cost Effective Backup


Oracle Database

Tape Backup

Sun Storage 7000 Unified Storage SystemOracle RMAN Target

Primary Disk Array

RMAN Disk Backup

Media Management Server with NetBackup,

Networker, etc.

Sun StorageTek SL3000 Modular Library System

Backup to Disk to Tape (B2D2T):Sun Storage 7000 Unified Storage Systems are theideal platform for Database backup and recovery


Oracle Database

Tape Backup

Sun Storage 7000 Oracle RMAN Target

Primary Disk Array

RMAN Disk Backup

Media Management Server with NetBackup,

Networker, etc.

Sun StorageTek SL3000 Modular Library System

Backup to Disk to Tape - Extended:Sun Storage 7000 Unified Storage Systems built in replication enable cost effective DR

ReplicatedOracle RMAN Target


Centralized Data Store for Cross Location Access:Built in replication enable cost effective Consolidation


Oracle VM•Application type: Virtualization•Relevant versions: OVM 2.x• Workload profile

– O/S Images: Large block sequential read/writes, synchronous writes

– User Data: Mixed workload•Suggested Platforms: 7320(c), 7420(c), 7720

– Pool: Mirrored Protection, 2 W-SSD per pool, 2 R-SSD per pool (or) 4 per head for user data

– Protocol: NFS, FC, iSCSI>NFS Shares Record size:

• 8kB for application data, 64kB-128kB for storage repositories

>Block (FC/iSCSI) record size: 64kB


Vmware ESX•Application type: Virtualization•Relevant versions: ESX 3.5u2+ & vSphere 4.0+• Workload profile: Random, synchronous writes•Suggested Platforms: 7310(c), 7410(c), 7720

– Pool: Mirrored Protection, 2 W-SSD per pool, optionally

2 R-SSD per pool (or) 4 per head for user data>Shares: 128kB for O/S images (low usage), smaller depending on application needs on NFS. 64KB for block.>Protocol: FC, iSCSI, NFS• Additional Information:

– http://www.vmware.com/resources/compatibility/search.php– http://www.sun.com/bigadmin/features/articles/storage_vmware.jsp

http://www.vmware.com/resources/compatibility/search.php

http://www.sun.com/bigadmin/features/articles/storage_vmware.jsp


Oracle Database - OLTP

•Application type: Database•Relevant versions: 9i, 10g, 11g, RAC•Workload profile : 8kB random read/write, 70:30•Suggested Platforms: 7310(c), 7410(c), 7720

– Pool Configuration • Mirrored protection• 2 W-SSD per pool, 2 R-SSD per pool (or) 4 per head

– Protocol: NFS, FC, iSCSI>Block (FC/iSCSI) record size : 64kB• Reference :

https://www.sun.com/offers/docs/820-7213.pdf

https://www.sun.com/offers/docs/820-7213.pdf


Microsoft Exchange•Application type: E-mail server•Relevant versions: 2007, 2010• Workload profile: 8kB random read, 8kB random

synchronous writes– Latency sensitive, IOPS heavy

•Suggested Platforms: 7310(c), 7410(c), 7720– Pool: Mirrored Protection, 2 W-SSD per pool

(required)• R-SSD is not required, but may show some benefit

>Shares: LUN, 64kB record size, write cache disabled>Protocol: FC, iSCSI• Additional Information: ESRP -

http://technet.microsoft.com/en-us/exchange/bb412164.aspx

http://technet.microsoft.com/en-us/exchange/bb412164.aspx

2010 Oracle Corporation - DOAG Deutsche ORACLE ... · 4 © 2010 Oracle Corporation Agenda Unified...

Documents

Transcript of 2010 Oracle Corporation - DOAG Deutsche ORACLE ... · 4 © 2010 Oracle Corporation Agenda Unified...