0% found this document useful (0 votes)

2 views

ASM_10g_ASM

Automatic Storage Management (ASM) simplifies database storage management by integrating the file system and volume manager, allowing for optimal performance and resource utilization. It organizes storage into disk groups, enabling automatic rebalancing and reducing complexity for database administrators. ASM enhances productivity by eliminating manual I/O tuning and providing a streamlined management interface for storage resources.

Uploaded by

kulmit gill

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2 views

ASM_10g_ASM

Uploaded by

kulmit gill

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

You are on page 1/ 49

Automatic Storage Management

Storage Management Gap

Avg. Managed Capacity per

Administrator
In Database
60 Sites with >100 GB Capacity
50
Disk
40 Capacity
Capacity in
Terabytes
30
Capacity
20 /DB Adm

10
0
Mgmt Gap

Strategic Research Corporation

DBA Storage Challenges
 Databases are rapidly growing in size
– DBAs have to manage thousands of data files
 Decreasing windows of scheduled downtime
 Storage resources involve many organizations
– Database Admin
– Systems Admin
– Storage Admin
– Network Admin
 Management of database storage is increasing
in complexity and cost
Automatic Storage Management
 Provides a vertical integration of the
file system and volume manager for
Oracle database files

 Spreads database files across all

available storage for optimal
performance and resource utilization

 Enables simple and non-intrusive

resource allocation and provides
automatic rebalancing
The Operational Stack

TODAY ASM

Tables Tables
Tablespace Tablespace
0010 0010 0010 0010 0010
Files 0010 0010 0010 0010 0010
Files
File System File System ASM
Logical Vols Logical Vols
Disks Disk Group

“The best way to lower mgmt costs is to remove complexity”

ASM Disk Groups

 A pool of disks managed as a

logical unit

Disk Group
ASM Disk Groups

 A pool of disks managed as a

logical unit
 Partitions total disk space into
uniform sized megabyte units

Disk Group
ASM Disk Groups

 A pool of disks managed as a

logical unit
 Partitions total disk space into
uniform sized megabyte units
 ASM spreads each file evenly
across all disks in a disk
group

Disk Group
ASM Disk Groups

 A pool of disks managed as a

logical unit
 Partitions total disk space into
uniform sized megabyte units
 ASM spreads each file evenly
across all disks in a disk
group
 Coarse or fine grain striping
based on file type

Disk Group
ASM Disk Groups

 A pool of disks managed as a

logical unit
 Partitions total disk space into
uniform sized megabyte units
 ASM spreads each file evenly
across all disks in a disk
group
 Coarse or fine grain striping
based on file type
 Disk groups integrated with
Oracle Managed Files
Disk Group
ASM Disk Groups

• Administer disk groups not files

• Number of disk groups remains
constant while number of files
and disks continually increases

Fast Disk Group Slow Disk Group

Mirroring with ASM
Failure Groups
 Storage resources organized into
Disk Groups and Failure Groups
 A Disk Group is a collection of disks
managed as a logical unit in which ASM
files are stored
Controller 1 Controller 2
 Disk Groups assigned by DBAs
 A Failure Group is a set of disks
sharing a common resource whose
failure needs to be tolerated
– Redundant copies of an extent are
stored in separate Failure Groups
 Failure Groups assigned by DBAs or
Failure Group 1 Failure Group 2
automatically by ASM
Disk Group 1
Mirroring with ASM

 3 choices for disk group redundancy

– External: defers to hardware mirroring
– Normal: 2-way mirroring
– High: 3-way mirroring
ASM Mirroring

 Mirror at extent level

 Mix primary & mirror extents on each disk
ASM Mirroring

 Mirror at extent level

 Mix primary & mirror extents on each disk
ASM Mirroring

 No hot spare disk required

– Just spare capacity
– Failed disk load spread among survivors
– Maintains balanced I/O load
Where DBAs Spend Their Time

Installation
6%
Creation &
Others
Configuration 12 %
15%

Software Data
Maintenance 6% Loading 6%
Ongoing System
Management 55%

Source: IOUG 2001 DBA Survey

ASM Functions
Drill Down

 Getting started
 Defining a DB
 Adding/deleting/migrating storage
 Hot spots
 Storage fragmentation
Traditional vs ASM
Setup

1. Determine required 1. Determine required

storage capacity storage capacity
2. Install Volume Manager, 2. Install ASM
File System 3. Create Disk Groups
3. Architect data layout to 4. Install database
avoid hot spot 5. Create database
4. Create logical volumes
5. Create file systems
6. Install database
7. Create database
Create or Delete Disk Groups
CREATE DISKGROUP dgroup1 DISK ‘/dev/raw/raw*’

CREATE DISKGROUP dgroupA NORMAL REDUNDANCY

FAILGROUP controller1 DISK
'/devices/diskA1' NAME diskA1 SIZE 120G,
'/devices/diskA2',
'/devices/diskA3'
FAILGROUP controller2 DISK
'/devices/diskB1',
'/devices/diskB2',
'/devices/diskB3';

DROP DISKGROUP dgroupA INCLUDING CONTENTS;

Traditional vs ASM
Add Disk

1. Add Disk to OS 1. Add Disk to OS

2. Create volume(s) with 2. Issue the Add Disk
Volume Manager command
3. Create File System over
volume
4. Figure out data to move to
new disk
5. Move data to new files
6. Rename files in database
7. Re-tune I/O
Adding Disks to Disk Groups

ALTER DISKGROUP dgroupA ADD DISK '/dev/rdsk/c0t4d0s2';

Disk Added to Disk Group

Disk Group Rebalancing

Traditional vs ASM
Remove Disk

1. List all data that is on disk 1. Issue drop disk command

2. Choose existing 2. Remove the disk from OS
filesystem to hold data when Oracle says it is
from dropped disk done
3. Move data to new files
4. Rename files in database
5. Remove disk from OS
6. Re-tune I/O
Removing Disks to Disk Groups

ALTER DISKGROUP dgroupA DROP DISK Group2_0003;

Disk Group Rebalancing

ALTER DISKGROUP dgroupA REBALANCE POWER 5;

DEMO
Traditional vs ASM
Migrate Data

1. Add new disks to OS 1. Add new disks to OS

2. Figure out new location 2. Issue Add disk command
on other disks for new disks
3. Create volume(s) with 3. Issue Drop Disk command
Volume Manager for old disks
4. Create new FS 4. Remove old disks from
5. Move data to new files OS when Oracle says it is
6. Rename files in database done
7. Remove old disks from
OS
8. Re-tune I/O
Traditional vs ASM
Tune I/O

1. Daily monitor I/O This space intentionally left

performance blank
2. Discover hot spots
3. Figure out how to remove
hot spots
4. Move data to new files
5. Rename files in database
6. Verify that hot spot is
gone
Traditional vs ASM
Manage Space

1. Daily monitor storage This space intentionally left

utilization blank
2. Discover fragmentation
3. Figure out how to remove
fragmentation
4. Move data to new files
5. Rename files in database
6. Verify that fragmentation
is gone
ASM Lowers Management Costs

8
7 7
8
6 6 6
7

6
5
5
4
Nbr Steps

4
3
2 2
2
Traditional
1
0 0 ASM
0
Install Add Storage Remove Migrate Tune I/O Manage
Storage Storage Space

“Best way to save costs is to remove complexity”

Integration with Oracle tools
AKA “How do we get data out?”
 Backup
– Rman
 Transportable Tablespaces
– ftp to FTP server
 Data Pump
– Can specify disk group and data pump will dump
to ASM
Why We Stripe

Unstriped Disks Striped Disks

Automatic Storage Management Extends SAME

– Allows dynamic and online reconfiguration of storage resources
– Efficient relocation of data during rebalance
– Eliminate manual I/O tuning in all storage configurations
Dynamic Rebalancing