EMC CX500I Configuration Guide - Page 75

MirrorView Features and Benefits, CLARiiON Environment

Get EMC CX500I - Insignia CLARiiON NAS Server PDF manuals and user guides View all EMC CX500I manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

Data Replication and Data Mobility Software MirrorView Features and Benefits MirrorView mirroring adds value to customer systems by offering the following features: ◆ Provision for disaster recovery with minimal overhead ◆ CLARiiON environment ◆ Bidirectional (cross) mirroring ◆ Integration with EMC SnapView LUN snapshot and clone copy software CLARiiON Environment MirrorView operates in a highly available environment, leveraging the dual-SP design of CLARiiON storage systems. If one SP fails, MirrorView running on the other SP controls and maintains the mirrored LUNs. If the server is able to fail over I/O to the remaining SP, then periodic updates continue. The highly-available features of RAID protect against disk failure, and mirrors are resilient to an SP failure in the primary of secondary storage system. Provision for Disaster Recovery with Minimal Overhead Provision for disaster recovery is the major benefit of MirrorView mirroring. Destruction of the primary data site would cripple or ruin many organizations. After a disaster, MirrorView lets data processing operations resume very quickly, often within minutes or a few hours. MirrorView is transparent to servers and their applications. Server applications do not know that a LUN is mirrored, and the effect on performance depends on the distance and application workload. MirrorView supports up to four connections per storage system, which means you can use it in a central backup configuration, where one storage system maintains remote mirrors for as many as four other storage systems. MirrorView uses synchronous writes, which means that server writes are acknowledged only after all secondary storage systems commit the data. Most disaster recovery systems sold today use this type of mirroring. MirrorView runs in storage systems, not on servers, therefore it uses no host I/O or CPU resources. The additional processing for mirroring is performed on storage systems. What Is MirrorView? 4-13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
What Is MirrorView?
4-13
Data Replication and Data Mobility Software
MirrorView Features and Benefits
MirrorView mirroring adds value to customer systems by offering
the following features:
◆
Provision for disaster recovery with minimal overhead
◆
CLARiiON environment
◆
Bidirectional (cross) mirroring
◆
Integration with EMC SnapView LUN snapshot and clone copy
software
CLARiiON Environment
MirrorView operates in a highly available environment, leveraging
the dual-SP design of CLARiiON storage systems. If one SP fails,
MirrorView running on the other SP controls and maintains the
mirrored LUNs. If the server is able to fail over I/O to the remaining
SP, then periodic updates continue. The highly-available features of
RAID protect against disk failure, and mirrors are resilient to an SP
failure in the primary of secondary storage system.
Provision for Disaster Recovery with Minimal Overhead
Provision for disaster recovery is the major benefit of MirrorView
mirroring. Destruction of the primary data site would cripple or ruin
many organizations. After a disaster, MirrorView lets data processing
operations resume very quickly, often within minutes or a few hours.
MirrorView is transparent to servers and their applications. Server
applications do not know that a LUN is mirrored, and the effect on
performance depends on the distance and application workload.
MirrorView supports up to four connections per storage system,
which means you can use it in a central backup configuration, where
one storage system maintains remote mirrors for as many as four
other storage systems.
MirrorView uses synchronous writes, which means that server writes
are acknowledged only after all secondary storage systems commit
the data. Most disaster recovery systems sold today use this type of
mirroring.
MirrorView runs in storage systems, not on servers, therefore it uses
no host I/O or CPU resources. The additional processing for
mirroring is performed on storage systems.