EVA Architecture Introduction

EVA Architecture Overview
Rodger Daniels EVA Replication Architect

2004 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Disclosure information
The following information is HP Confidential and is intended only for a limited audience within HP who fulfill a need to know requirement. The information contained is to be handled accordingly with HPs policy for handling this classification of information.
http://legalweb.corp.hp.com/legal/files/labels.asp
This information may NOT be shared outside HP.
3-Dec-12
EVA Features
EVA

Excellent Random R/W performance Excellent cache read hit number Fault tolerant, scaleable virtualization mapping scheme (Garbage collection free) Mirrored write cache Volatile read cache Metadata in volatile memory (Policy Memory) Backend disks provide non volatile metadata store Replication features Snapclones, Snapshots (fully allocated, space efficient) CA disaster tolerant remote replication RAID0, RAID1, RAID5 Active mirroring between controllers through FC Mirror Port(s) GL - On the fly XOR XL Inline parity calculation
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 3
Architectural Discussion Objects

NSC (Network Storage Controller)
Refers to a controller from a VCS perspective
VCS
Virtual Controller Software (firmware) Becomes XCS for XL family
Physical Store
Unused Drive (In the process of becoming a useable part of the system, but needs to become incorporated into an RSS)
Volume
A used disk drive, can accept customer data at this point
Storage Cell
EVA Controllers, Shelves and Disks that have been initialized by the firmware. Can be logically constructed into Disk Groups (LDADs), Logical Disks, Virtual Disks and then used for customer data
Disk Group (LDAD Logical Disk Address Domain)

A group of disks that function as a separate storage pool. A virtual disk is contained within a single disk group and can not span disk groups. A disk group is made up of one or more redundant store sets. User data for a virtual disk is striped across the entire disk group.
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 4
Architectural Discussion Objects

Quorum
A set of disks that contains copies of the SCS data base
Logical Disk
Logical representation of a virtual disk. At the CS component level the representation of a virtual disk
Virtual Disk
A virtual representation of a logical disk, for external use by a host
Presented Unit
The presentation of a virtual disk, ie. its mounted and useable by a host
RSS (Redundant Store Set)

A subset of disks within a disk group that represents a smaller fault domain then the disk group..
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 5
RSS Example
2C12D: One disk group containing all 64 drives

Eight RSSs: RSS 1 RSS 2 RSS 3 RSS 4 RSS 5 RSS 6 RSS 7 RSS 8
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 6
Fault Manager
CSLD READY SCSCB
EIP
ALL COMPONENTS
CSIO EIRP,TEIRP
6
HTB
HP Tachyons
SEST,ERQ,IMQ
CODE HIGHWAY
SCMI Services
CONFIG/STATE CONFIG/STATE
Host Port
HTB XD
EETB
DRM FC
TDCB TDCB
CONFIG STATE
1
XD
Cache Manager 4
HTB
DRM Core
DTD
SCS
STORAGE CELL STATE
3
CNODE XD XD
1 4 5 6
CONFIG STATE XD
CONFIG STATE CONFIG STATE
2 3 EXEC RTOS
CS
CONTAINER SERVICES
MFCD
DRM Log
ALLOC DEALLOC
ALLOC DEALLOC CSIO
5
XD
Raid Services
FED
DRM Copy EMU

ENVIRONMENTAL MONITOR UNIT SEST,ERQ,IMQ
XD
TDSD, ELSD, MFCD,FED
FC Services
SEST,IMQ ERQ
FED
COMMAND STATE
OCP
OPERATIONAL CONTROL PANEL
Device Tachyons
Mirror Tachyon
HP Confidential 12/3/2012 9:53 PM 7
On Line
NSS
Architecture Component Overview

Host Port
Front end FC services, decodes and sequences instructions, controller responses to host, assigns work to code highway, passes commands to SCMI, supports SCSI interface, handles AAA logic (V4)
(SCMI) Storage Cell Management Interface

Architected interface to allow external management agents (Command View/Bridge) to manage the EVA
(SCS) Storage Cell State

Inoperative/Operative unit handling, SCMI requests to add/remove objects from the system, return info about objects, unit presentation, pullover, failover, meltdowns, meltdown recovery, ILF disk management, system database, RSS management, add/remove devices, cell mastership, error reporting
Cache Manager
Read/Write cache management, full stripe writes, assigns work to RAID services, RAID5 write recovery/parity recovery
(DRM) Data Replication Manager Continuous Access

Remote disaster tolerant replication
(Container Services)
Virtualization (Map management), local replication (snapclone/snapshot), sparing, leveling
RAID Services
Services supporting RAID0, RAID1 and RAID5
FCS
Backend FCS, Mirroring and DRM FCS support, Disk Drive handling
FM (Fault Manager)
Manage event logs, termination codes, etc.
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 8
Architecture Component Overview

Host Port (SCMI) Storage Cell Management Interface (SCS) Storage Cell State Cache Manager
Container Services
Data Replication Manager (DRM) Continuous Access FM Fault Manager
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 9
Host Port
3-Dec-12
10
Host Port and EVA GL Operation

EVA is made up of a controller pair
2 host ports per controller module
One controller is the master and the other slave

Actions affecting storage cell structures and database are restricted to the master controller Example is VDisk (LUN) creation
EVA GL (VCS3.XXX and earlier) is an Asymmetrical Virtual RAID controller

Asymmetrical LUN access Unit is ready read/write on one controller while it is not ready on the other controller Simultaneous access to LUN only supported via ports on same controller One queue for LUN, ordering based on command arrival
Host Ports only support Fabric connnection

1Gb, 2Gb switches supported Highest available link speed is auto negotiated
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 11
EVA GL and Host Port IDs

EVA Controller Pair
Defined as a single node Assigned a SCSI-3 WWID Two control units each containing two host ports Each host port defined by unique port WWID Node and Port Identifiers are 64 bit IEEE registered numbers, with a portion assigned by a company ID and the rest by a HP specific method to ensure uniqueness of the identifiers.
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 12
Host Port Module

Handles front end FC services
Decodes and sequences instructions Controller responses to Host
Assigns work to Code Highway

Passes along SCMI commands to SCMI module Supports SCSI interface
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 13
Fault Manager
CSLD READY SCSCB
EIP
ALL COMPONENTS
CSIO EIRP,TEIRP
6
HTB
HP Tachyons
SEST,ERQ,IMQ
CODE HIGHWAY
SCMI Services
Host Port
HTB XD
EETB
DRM FC
TDCB TDCB
CONFIG STATE
1
XD
Cache Manager 4
HTB
DRM Core
DTD
SCS
STORAGE CELL STATE
3
CNODE XD XD
1 4 5 6
CONFIG STATE XD
2 3 EXEC RTOS
CS
CONTAINER SERVICES
MFCD
DRM Log
ALLOC DEALLOC
ALLOC DEALLOC CSIO
5
XD
Raid Services
FED
DRM Copy EMU

XD
FC Services
SEST,IMQ ERQ
FED
COMMAND STATE
OCP
Device Tachyons
Mirror Tachyon
On Line
NSS
SCMI
3-Dec-12
15
SCMI Storage Cell Management Interface

Architected interface used by external management agents (Command View/Bridge) to communicate with the EVA Communication via SCSI Send Receive Diagnostics
All SCMI commands made through LUN0 Commands come in via SCMI command packet Response via SCMI response packet Original design limited response to a single attribute In order to reduce message traffic super SCMI commands developed which return a lot on information via a single response
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 16

External management agent uses SCMIApi or RealSCMI to communicate with the EVA SCMI Server processes the command inside of VCS SEND DIAGNOSTIC command - use page code 90 (vendor specific). Contains SCMI command packet, and command buffers(2). 64KB max buffer size. RECEIVE DIGNOSTIC command - returns the result in SCMI response packet and response buffers(2). Host Port layer handles matching of the send/receive pair and rejecting illegal combination. Built in security mechanism by establishing password (encrypted password is transmitted). The agent (client) must log-in using the correct password to be able to send SCMI commands for execution
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 17

Limitations
The system processes one send/receive diagnostic at a time This means when the system is synchronously executing a command via send receive diagnostic, until that command completes the next management command is held up When a management command is held up the management agent loses manageability of the array for that time Asynchronous background delete example Designing commands that take along time to execute See SCMI Spec section 6.7, 5.2.5, 4.57.1
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 18
State (SCS)
3-Dec-12
19
Fault Manager
CSLD READY SCSCB
EIP
ALL COMPONENTS
CSIO EIRP,TEIRP
6
HTB
HP Tachyons
SEST,ERQ,IMQ
CODE HIGHWAY
SCMI Services
Host Port
HTB XD
EETB
DRM FC
TDCB TDCB
CONFIG STATE
1
XD
Cache Manager 4
HTB
DRM Core
DTD
SCS
STORAGE CELL STATE
3
CNODE XD XD
1 4 5 6
CONFIG STATE XD
2 3 EXEC RTOS
CS
CONTAINER SERVICES
MFCD
DRM Log
ALLOC DEALLOC
ALLOC DEALLOC CSIO
5
XD
Raid Services
FED
DRM Copy EMU

XD
FC Services
SEST,IMQ ERQ
FED
COMMAND STATE
OCP
Device Tachyons
Mirror Tachyon
On Line
NSS
SCS Functionality
Storage Cell State (SCS State)
Inoperative/Operative unit handling SCMI requests to add/remove objects from the system Return info about objects Unit presentation Pullover Failover Meltdowns Meltdown recovery ILF disk management State database (Object Store Management) RSS management add/remove devices Cell mastership Error reporting
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 21
SCS Components
Cell State Manager (CSM)
Makes all State decisions, controls state of EVA Active only on the master controller Manages Quorum Disks Owns SCS data base SCMI command processing Cell realization Unit failover
Cell Volume Manager (CVM)

Volume transitions RSS membership Meltdown level
Cell State Agent (CSA)

Manipulates volatile data structures on behalf of CSM
Device Discovery
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 22
SCS Components
Quorum Disks
RSS0 is a special RSS that tracks the quorum disks It is the only RSS that has disks from multiple disk groups It is the only RSS that has disks that are all members of other RSSs At least 5 disks mirrored, max 16, 1 per disk group, 1 per shelf Master owns, slave cannot access quorum drives Read one, write all nway write User notified when all quorum disks are lost Special quorum disks called golden quorum, used in single controller configuration Kept in synch using an incarnation number In event of crash check all incarnation numbers SCS data base resides on quorum disks SCS data base keeps information about the current storage cell configuration Storage Cell, Disk Groups, VDisks, DR Groups Journals for Metadata Updates (Can be a performance issue)
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 23
RSS Management
RSS Membership
A disk is not available for storage if it is not a member of an RSS When new drives are added to the system they must be added to existing RSSs or new RSSs must be created When drives are removed from the system it may require that RSSs are merged
RSS Size
RSSs are 6 to 12 drives When an RSS drops below 6 drives it will merge with another RSS to create a larger RSS When an RSS grows beyond 11 drives it will be split to create 2 RSSs A merge can force a split Optimal size targeted by the system is 8 drives
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 24
RSS Management
RSS Goals
Size is important Optimal size targeted by system is 8 Must be greater then 5 and less then 12 When an RSS goes to 5 or less it is merged with another RSS is another RSS is available When an RSS grows to 12 or greater it is split into two smaller RSSs of size 6 or greater Every member has a mirror partner Talk about VA R1 geometry vs EVA R1 geometry Mirror partners should be on different shelves RSS Members should be on different shelves Mirror partners same size RSS members same size
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 25
RSS Management
Adding a Single Drive to an LDAD
Add a single disk then add to RSS with smallest odd membership If more than 1 to choose from then select based on shelf numbers and disk sizes
Adding Multiple Drives to an LDAD

Try to mate all unpaired disks Try to make it so everyone has a partner on a different shelf If more than 5 disks try to create as many new RSSs of size 8 and a new smaller RSS with whats left
Things Not Guaranteed

Mirror partners will be on a different shelf All RSS members will be on a different shelf Dont tear apart good RSSs to make RSSs with drives on different shelves Dont make 4 6 member RSSs into 3 8 member RSSs
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 26
Cache and Battery
3-Dec-12
27
Cache and Battery State

Cache Policy:
The battery capacity (i.e., write cache holdup time) is a major input for determining what is called the Cache Policy Cache Policy determines whether or not a unit is presented to hosts, which controller it is presented through, and whether it operates in write-back or write-through mode
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 28
Battery Holdup and Cache Policy
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 29
The Storage Cell and Cache Policy

When one controllers battery system is no longer good, units move to the other controller, if its battery state is better
Storagecell Slave Battery System Bad Storagecell Master Battery System Bad Storagecell Master Battery System Low Storagecell Master Battery System Good No unit presentation except SACD All units writethrough on Storagecell Master All units writeback on Storagecell Master Storagecell Slave Battery System Low Storagecell Slave Battery System Good
All units All units writethrough on writeback on Storagecell Slave Storagecell Slave All units All units writethrough on writeback on both Storagecell Storagecell Slave Master and Slave All units writeback on Storagecell Master All units writeback on both Storagecell Master and Slave
Adapted from VCS Battery Manager Overview by Bryan Walder (Aug 29, 02).
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 30
Battery Holdup Times

GL
Two batteries Low holdup time96 hours
XL Lite (4000, 6000)

One battery Low Holdup Time in Write Through is about 96 hours Normal Holdup Time in Write Back mode is up to 242 hours
XL (8000)
Two batteries Low Holdup Time in Write Through is about 96 hours Normal Holdup Time in Write Back mode is up to 244 hours
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 31
Cache Management for Dummies

Terminology:
Dirty Data Write cache data that has not been flushed to disk Write-back caching Committing data when it reaches write cache and is mirrored on the other controller to reduce write latencies Write-through caching Disabling write cache and forcing a write to successfully write to disk before returning successful status Atomic Write Guarantee that for any write up to 128K that does not cross a 128K boundary that a read of the data will either return all old data or all new data
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 32
Cache Management for Dummies

Terminology:
Fail-over Process of failing over a controllers write cache to the other controller Crash-over The process of reconstructing local cache data structures following a controller power cycle Volatile Memory Non battery backed memory assumed to not survive a power cycle Non-volatile Memory Battery backed memory assumed to survive a power cycle SACD (Storage Array Control Device)
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 33
Cache Benefits
Benefits of Caching:
The cache acts as a holding point between front and back end operations for a given piece of data Reduced host port command latency (disk v. electronic speed): Read hits to already cached data Write-back for absorbing bursty write data at electronic speedcan achieve electronic speed for absorbing new host writes as long as the cache doesnt fill up, and over time, the average host write data rate is less than the rate at which the media can absorb the data.
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 34
Cache Buffers
Cache Buffers:
Block = 512 bytes GL Buffer = 2048 bytes (populated with 1 to 4 blocks of user data) XL Buffer = 8192 bytes (populated with 1 to 16 blocks of user data) Cache Page = 128 kilo bytes
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 35
Cache Layout GL and XL (4000, 6000)
A Write Primary 256MB Non-volatile B Write Mirror 256MB Non-volatile
B Write Primary 256MB Non-volatile A Write Mirror 256MB Non-volatile
A Read 512MB Volatile
B Read 512MB Volatile
Cache-A
Cache-B
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 36
XL (8000)
A Write Primary 512MB Non-volatile B Write Mirror 512MB Non-volatile
B Write Primary 512MB Non-volatile A Write Mirror 512MB Non-volatile
A Read 1024MB Volatile
B Read 1024MB Volatile
Cache-A
Cache-B
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 37
Fault Manager
CSLD READY SCSCB
EIP
ALL COMPONENTS
CSIO EIRP,TEIRP
6
HTB
HP Tachyons
SEST,ERQ,IMQ
CODE HIGHWAY
SCMI Services
Host Port
HTB XD
EETB
DRM FC
TDCB TDCB
CONFIG STATE
1
XD
Cache Manager 4
HTB
DRM Core
DTD
SCS
STORAGE CELL STATE
3
CNODE XD XD
1 4 5 6
CONFIG STATE XD
2 3 EXEC RTOS
CS
CONTAINER SERVICES
MFCD
DRM Log
ALLOC DEALLOC
ALLOC DEALLOC CSIO
5
XD
Raid Services
FED
DRM Copy EMU

XD
FC Services
SEST,IMQ ERQ
FED
COMMAND STATE
OCP
Device Tachyons
Mirror Tachyon
On Line
NSS
Cache Manager Operations

Host Port Reads/Writes (HP Interface)
Mirroring write data to other controller Cooperation with DRM for order preservation Full stripe write aggregation for RAID5 to avoid RMW penalty R5 parity recovery World Peace
On Line
NSS
HP Confidential
12/3/2012 9:53 PM 39
Active-Active Controller Support on EVA EVA 3000, 5000 VCS 4.XXX EVA 4000, 6000, 8000
3-Dec-12
41
Active-Active Controller Support

Active-active multi-pathing Vdisk failover Controller failover
3-Dec-12
42
Active-Active Multi-Pathing
What is active-active multi-pathing? On the EVA 3000/5000 a Vdisk is preferred to a controller and it can only be accessed by that preferred controller
To read or write the vdisk from the other controller it must be moved to that other controller
3-Dec-12
43
What is active-active multi-pathing? On the EVA 4000/6000/8000 a Vdisk is mastered by one controller in the controller pair but it can be read from and written to via the slave controller in the controller pair This ability to access the Vdisk through either controller allows for active-active load balancing, path failover, and the support of native failover software on the servers
3-Dec-12
44
Vdisk access via the master controller All read and write requests are sent to the master controller The only data that moves across the mirror port between controllers is write data being mirrored to the slave controllers mirror write cache
3-Dec-12
45
Vdisk access via Master controller
Mirror write cache Primary write cache
Read cache
Slave controller
Transfers across the mirror ports
Virtual Disk
Mirror write cache
Primary write cache
Read cache
Master controller
Host write
Host read
Server
3-Dec-12 46
Vdisk access via the slave controller All read and write requests are sent to the master controller via the controller mirror ports Both read data and write data moved between the controllers via the controller mirror ports
3-Dec-12
47
Vdisk reads via the slave controller Read and write requests are received by the slave controller All requests are sent to the master controller Reads are fulfilled from the read cache on the master controller via the mirror port between the controller A performance penalty is paid for read requests on the slave controller
3-Dec-12
48
Vdisk writes via the slave controller Writes are fulfilled by first putting the data in the mirror half of the write cache on the slave controller and then sending the data to the master controller via the mirror port where it goes into the primary write cache Vdisks being replicated by Continuous Access can be written via the slave controller Minimal performance penalty for write requests to the slave controller
3-Dec-12
49
Vdisk read via non-mastering controller
Virtual Disk
Read cache
Master controller
Mirror write cache
Primary write cache
Read cache
Slave controller
Host read request
Server
3-Dec-12 50
Vdisk write via non-mastering controller
Virtual Disk
Read cache
Master controller
Mirror write cache
Primary write cache
Read cache
Slave controller
Host write
Server
3-Dec-12 51
Vdisk Failover
Vdisk failover on XL
Vdisk failover results in the slave controller becoming the master controller for a vdisk(s) Can occur in one of two manners
Implicit failover EVA decides to change the Vdisk master Explicit failover Administrator or host based software decides to change the Vdisk master
Causes
HBA failure SAN failure Controller failure Administrative decision
3-Dec-12
52
Vdisk Failover
Implicit Vdisk failover
Implicit transition of a vdisk between controllers is initiated by the EVA and is based on which controller the majority of read IO requests are being received Measurements are taken on an hourly basis Implicit failover occurs if >= 2/3 of the reads occur on the slave controller
3-Dec-12
53
Vdisk Failover
Implicit Vdisk failover
Based on reads because reading through the slave controller incurs a fairly large performance penalty Almost no performance penalty when writing through slave controller so writes are ignored Considered giving the administrator control of the measurement window but decided in the end not to provide this access
3-Dec-12
54
Vdisk Failover
Explicit Vdisk failover
Explicit transition of a vdisk between controllers is performed either by the storage administrator or host path failover software
True64 OVMS
Not allowed if the controller is in write-through mode during a fully allocated snapshot or snapclone creation
3-Dec-12
55
Vdisk Failover
Vdisk failover Can failover about 1TB per second regardless of the number of Vdisks being failed over Failover is done by group (DR Group for CA or Vdisk and snaps for other Vdisk) one vdisk at a time
3-Dec-12
56
Vdisk Failover
Vdisk failover When a Vdisk failover occurs, the Vdisk is first put into write-through mode and dirty cache entries for the Vdisk are flushed Metadata from the mastering controllers policy memory is then written to the disk group reserve metadata area (a hidden Vraid 1 disk owned by the controllers)
Metadata changes are also written to a journal that reside on the quorum disk but it is faster to use the disk group metadata area than the journal
The metadata is then read from the reserved metadata area by the new mastering controller New controller takes over the Vdisk
3-Dec-12 57
Vdisk Failover
Virtual Disk
Mirror write cache
Primary write cache
Read cache
Policy memory
Master controller Slave controller

Metadata
Hidden Vraid 1
Virtual Disk
Mirror write cache
Primary write cache
Read cache
Policy memory
Slave controller Master controller
Cache write-through mode - dirty cache entries for Vdisk are flushed
3-Dec-12 58
Controller Failure
Controller failure When a controller failure occurs all Vdisks mastered on the controller are failed over Can failover about 1TB per second regardless of the number of Vdisks being failed over Failover is done by group (DR Group for CA or Vdisk and snaps for other Vdisk) one vdisk at a time
3-Dec-12
59
Controller Failure
Controller failure Metadata changes in the controllers policy memory do not get written to hidden metadata area or the quorum drive because the controller has failed The new master controller reads the metadata from the hidden metadata area and it reads metadata journal entries from the quorum drive The metadata journal entries from the quorum drive are applied to the metadata from the hidden metadata area to recover any metadata changes that were in-process at the time of the controller failure
3-Dec-12
60
Controller Failover
Metadata Journal
Quorum drive
Virtual Disk
Mirror write cache
Primary write cache
Read cache
Policy memory
Master controller Slave controller

Metadata
Hidden VRaid 1
Virtual Disk
Mirror write cache
Primary write cache
Read cache
Policy memory
Master controller
Controller Failure
3-Dec-12 61

EVA Architecture Introduction

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

EVA Architecture Introduction

Diunggah oleh

Hak Cipta:

Format Tersedia

EVA Architecture Overview

Rodger Daniels EVA Replication Architect

Architectural Discussion Objects

Disk Group (LDAD Logical Disk Address Domain)

Architectural Discussion Objects

RSS (Redundant Store Set)

2C12D: One disk group containing all 64 drives

CONFIG STATE CONFIG STATE

ALLOC DEALLOC CSIO

DRM Copy EMU

TDSD, ELSD, MFCD,FED

Architecture Component Overview

(SCMI) Storage Cell Management Interface

(SCS) Storage Cell State

(DRM) Data Replication Manager Continuous Access

Architecture Component Overview

Host Port and EVA GL Operation

One controller is the master and the other slave

EVA GL (VCS3.XXX and earlier) is an Asymmetrical Virtual RAID controller

Host Ports only support Fabric connnection

EVA GL and Host Port IDs

Host Port Module

Assigns work to Code Highway

CONFIG STATE CONFIG STATE

ALLOC DEALLOC CSIO

DRM Copy EMU

TDSD, ELSD, MFCD,FED

SCMI Storage Cell Management Interface

SCMI Storage Cell Management Interface

SCMI Storage Cell Management Interface

CONFIG STATE CONFIG STATE

ALLOC DEALLOC CSIO

DRM Copy EMU

TDSD, ELSD, MFCD,FED

Cell Volume Manager (CVM)

Cell State Agent (CSA)

Adding Multiple Drives to an LDAD

Things Not Guaranteed

Cache and Battery

Cache and Battery State

Battery Holdup and Cache Policy

The Storage Cell and Cache Policy

Battery Holdup Times

XL Lite (4000, 6000)

Cache Management for Dummies

Cache Management for Dummies

Cache Layout GL and XL (4000, 6000)

A Write Primary 256MB Non-volatile B Write Mirror 256MB Non-volatile

B Write Primary 256MB Non-volatile A Write Mirror 256MB Non-volatile

A Read 512MB Volatile

B Read 512MB Volatile

A Write Primary 512MB Non-volatile B Write Mirror 512MB Non-volatile

B Write Primary 512MB Non-volatile A Write Mirror 512MB Non-volatile

A Read 1024MB Volatile

B Read 1024MB Volatile

CONFIG STATE CONFIG STATE

ALLOC DEALLOC CSIO

DRM Copy EMU

TDSD, ELSD, MFCD,FED

Cache Manager Operations

Active-Active Controller Support

Mirror write cache

Primary write cache

Mirror write cache