Term
|
Definition
| push whole LUN to 3rd device |
|
|
Term
|
Definition
| Grab full copy of data from 3rd device |
|
|
Term
|
Definition
|
|
Term
| CLARiiON models that SAN Copy is available on |
|
Definition
|
|
Term
|
Definition
| Data migration for arrays. Installed on CLARiiON networked storage system. Eliminates need for LAN bw and critical server CPU cycles. |
|
|
Term
|
Definition
| Can be larger than source. |
|
|
Term
| SAN Copy Data Transfer Rate |
|
Definition
|
|
Term
| SAN Copy Granularity size used for incremental copies |
|
Definition
|
|
Term
| SAN Copy communicates via |
|
Definition
| Uses World Wide Names to communicate over SAN, LAN, or WAN (via FC/IP conversion) |
|
|
Term
|
Definition
1) SnapView Snapshot (full copies only) or Clone
2) TimeFinder BCV
3) Idle production LUN |
|
|
Term
|
Definition
1) Enable better business decision (Content Distribution)
2) Stop costly data errors (Disaster Recovery)
3) Reduce operational costs (Data migration) |
|
|
Term
| SAN Copy - Number of active, bi-directional sessions |
|
Definition
| 16 simultaneous, bi-directional active sessions allowed |
|
|
Term
| SAN Copy - Number of destinations one source can have |
|
Definition
| 100 destinations (systems) |
|
|
Term
| SAN Copy - Scalable and Flexible |
|
Definition
1) Dynamically pause / resume copy sessions
2) Raise or lower priority settings for copy process
3) up to 16 simultaneous, bi-directional SAN Copy sessions. Queues 300 jobs. One source can have 100 destinations. |
|
|
Term
|
Definition
1) advanced RAID algorithms
2) disk scrubbing
3) LUN expansion |
|
|
Term
| SAN Copy manager from within |
|
Definition
| CLARiiON's Navisphere Manager and Navisphere CLI |
|
|
Term
| CLARiiON Navisphere Management Suite |
|
Definition
1) Navisphere Manager, CLI/Agent, Analyzer
2) Access Logix, SnapView, MirrorView, SAN Copy
3) FLARE intelligent operating environment
4) hardware: FC4500, FC4700, CX200, 400,600 |
|
|
Term
|
Definition
| Incremental SAN Copy. Transfers only changed chunks, from source to destination. uses SnapView Snapshot to keep track of where those changes are.
1) Primary host writes to Source LUN
2) COFW invoked if needed
3) Ack from local storage system
4) Trigger event
5) Chunks copied from local to remote storage system
6) Ack from remote storage system |
|
|
Term
|
Definition
| Source LUN is always available to host. Target LUN is only of use to attached host once transfer is complete. Then it will be consistent, restartable, but previous point-in-time copy of Source LUN |
|
|
Term
|
Definition
| Synchronous, Bi-directional. Storage-based software that resides on CLARiiON. Online, host independent, mirrorated data storage and protection that duplicates data to one or two secondary sites in campus environment. Doesn't use host CPU cycles. |
|
|
Term
|
Definition
Every time host writes to the primary array, the secondary array mirrors the write before an ack is returned to the host.
1) I/O write received from host into write cache of primary array
2) I/O is transmitted to the write cache of secondary array
3) Acknowledgement is sent by secondary array back to primary
4) Write Acknowledgement is presented to host
Single connection is supported. SPs use CMI protocol over link when communicating. Connected SPs must be the same designation: SP-A to SP-A and SP-B to SP-B. |
|
|
Term
|
Definition
| Incremental Remote Mirroring bwtn 2 CLARiiON systems. Management via EMC Navisphere. Concurrent information access when used with SnapView. Does not require same RAID. Secondary LUN is inaccessible. Distance independent. Replication over IP. Asynchronous. Integrated with SnapView, SAN Copy, and MirrorView. Managed via Navisphere Management. |
|
|
Term
|
Definition
| Must be same size as Primary LUN. Does not need to be same RAID type as Primary. Not accesible to host(s). [Mirror must be removed or secondary promoted to primary for host to have access.] Bi-directional. |
|
|
Term
|
Definition
| Must be installed on both arrays, even if you don't want bi-directional |
|
|
Term
| Protection of Mirrored Data |
|
Definition
1) I/O write received from host into write cache of primary array
2) If secondary array is not reachable, mirror marked as fractured
3) Acknowledgement is sent by primary array back to production host |
|
|
Term
| MirrorView Switch attached Connectivity |
|
Definition
FC/IP router > 60 km
DWDM = 200 km
Optical extender = 40 km
Longwave GBIC = 10 km
Shortwave GBIC = 500 m |
|
|
Term
| MirrorView Direct Attached Connectivity |
|
Definition
CLAR to CLAR = 300/500 m
Optical extender = 10 km |
|
|
Term
|
Definition
| Dense Wave Division Multiplexor. Optical technology used to increase bandwidth over existing fiber optic backbones. |
|
|
Term
|
Definition
| R1. CLARiiON that serves mirrored primary data to production host |
|
|
Term
|
Definition
| CLARiiON that contains mirrored secondary copy of primary data |
|
|
Term
| MirrorView Mirror Synchronization |
|
Definition
| Copy data from primary LUN to secondary LUN. May use fracture log / write intent log to avoid full data copy. |
|
|
Term
| MirrorView Mirror Fracture |
|
Definition
| Condition when secondary is unreachable by primary. Can be invoked by admin command. |
|
|
Term
| MirrorView/A relies on SnapView for |
|
Definition
| Tracking changes made to primary image |
|
|
Term
MirrorView Remote Mirror Data States:
out of sync
In sync
Consistent
Synchronizing
Rolling back |
|
Definition
Out of sync = full sync needed
In sync = primary LUN and secondary LUN contain identical data
Consistent = write intent log or fracture log may be needed
Synchronizing = mirror sync operation in progress
Rolling back = secondary MirrorView/A image is rolling back |
|
|
Term
| MirrorView Remote Mirror Heartbeat |
|
Definition
| Messages are used to determine when secondary is reachable. Heartbeat is only used after secondary is determined unreachable. |
|
|
Term
MirrorView Remote Mirror States:
Inactive
Active
Attention |
|
Definition
Inactive = admin control to stop mirror processing
Active = I/O allowed (normal state)
Attention = admin action required |
|
|
Term
| Synchronous MirrorView Fracture Log |
|
Definition
| Lives in memory. Captures pending writes to remote system when communications link is down. Minimizes time to get back to fully synchronous state with secondary system. |
|
|
Term
| Synchronous MirrorView Optional Write Intent Log |
|
Definition
| Minimizes recovery time in event of failure of primary system. Only pending writes are sent to remote site. Written to each time a write request happens on particular mirror. |
|
|
Term
| MirrorView Remote Mirroring Consolidation |
|
Definition
| 1 CLARiiON can be target for 4 other systems. Used to consolidate or "fan-in" info on 1 remote CLARiiON. |
|
|
Term
| MirrorView switched relationships |
|
Definition
| 1 CLARiiON can be both source and target. Up to 4 relationships per CLAR. Enables bi-directional remote mirroring. |
|
|
Term
| MirrorView Concurrent Mirroring |
|
Definition
| 1 source mirrored to 2 target systems. 1 remote mirror for disaster recovery / bzness continuity. 1 remote mirror for parallel processing via SnapView. |
|
|
Term
|
Definition
| Does not use Fracture Log or Write Intent Log |
|
|
Term
| CLARiiON Remote Mirror High Availability |
|
Definition
| Host I/O allowed to mirror while mirror sync active. |
|
|
Term
|
Definition
| ControlCenter Navisphere (optional CLi available) |
|
|
