EMC CX500I Configuration Guide - Page 80

MirrorView/A Example, the database server Storage Group. Storage System 2

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 80 highlights

Data Replication and Data Mobility Software MirrorView/A Example Figure 4-4 shows a sample remote mirror configuration with two sites and a primary and secondary image that includes a database of three LUNs. Database Server 1, the production host, executes customer applications. These applications access data on Storage System 1, in the database server Storage Group. Storage System 2 mirrors the data on the Database Server Storage Group. Storage Groups are different than Consistency Groups. A Storage Group is a group of LUNs is assigned to a server. A server can access only the LUNs in the Storage Group to which it is assigned. Each server has a path to each SP in each storage system through each fabric. If a failure occurs in a path, then the storage-system software may switch to the path through the other SP (transparent to any applications). The server sends a write request to an SP in Storage System 1, which then writes data to the local LUN. The change to the primary LUN is recorded, and at an interval that you define, all changes are copied to the secondary storage system. If a failure occurs in Storage System 1, an administrator can use the management station to promote the image on Storage System 2 to the role of primary image. Then the appropriate application can start on any connected server (here, Database Server 2) with full access to the data. The mirror will be accessible in minutes, although the time needed for applications to recover will vary. Database Server 2, the standby host, has no direct access to the mirrored data. (No server is necessary at the standby site; if there is no server, the storage-system SPs are still connected as shown.) This server can also run applications that access other data stored on Storage System 2. 4-18 EMC CLARiiON CX300, CX500, CX500i, and CX700 Storage Systems Configuration Planning Guide

  • 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
4-18
EMC CLARiiON CX300, CX500, CX500i, and CX700 Storage Systems Configuration Planning Guide
Data Replication and Data Mobility Software
MirrorView/A Example
Figure 4-4 shows a sample remote mirror configuration with two sites
and a primary and secondary image that includes a database of three
LUNs.
Database Server 1, the production host, executes customer
applications. These applications access data on Storage System 1, in
the database server Storage Group. Storage System 2
mirrors the data
on the Database Server Storage Group.
Storage Groups are different than Consistency Groups. A Storage Group is a
group of LUNs is assigned to a server. A server can access only the LUNs in
the Storage Group to which it is assigned.
Each server has a path to each SP in each storage system through each
fabric. If a failure occurs in a path, then the storage-system software
may switch to the path through the other SP (transparent to any
applications).
The server sends a write request to an SP in Storage System 1, which
then writes data to the local LUN. The change to the primary LUN is
recorded, and at an interval that you define, all changes are copied to
the secondary storage system.
If a failure occurs in Storage System 1, an administrator can use the
management station to promote the image on Storage System 2 to the
role of primary image. Then the appropriate application can start on
any connected server (here, Database Server 2) with full access to the
data. The mirror will be accessible in minutes, although the time
needed for applications to recover will vary. Database Server 2, the
standby host, has no direct access to the mirrored data. (No server is
necessary at the standby site; if there is no server, the storage-system
SPs are still connected as shown.) This server can also run
applications that access other data stored on Storage System 2.