EMC CX500I Configuration Guide - Page 37

RAID 1 Mirrored Pair, the mirror losing all

Page 37 highlights

RAID Types and Trade-offs larger. By using both the read and write cache, a RAID 3 group can handle several concurrent streams of access. RAID 3 Groups do not require any special buffer area. No fixed memory is required to use write cache with RAID 3. Simply allocate write cache as you would for RAID 5, and ensure that caching is turned on for the LUNs in the RAID 3 Groups. Access to RAID 3 LUNs is compatible with concurrent access to LUNS of other RAID types on the storage system. RAID 1 Mirrored Pair A RAID 1 Group consists of two disks that are mirrored automatically by the storage-system hardware. With a RAID 1 Group, you can create multiple RAID 1 LUNs to apportion disk space to different users, servers, and applications. RAID 1 hardware mirroring within the storage system is not the same as software mirroring, remote mirroring, or hardware mirroring for other kinds of disks. Functionally, the difference is that you cannot manually stop mirroring on a RAID 1 mirrored pair, and then access one of the images independently. If you want to use one of the disks in such a mirror separately, you must unbind the mirror (losing all data on it), rebind the disk as the type you want, and software format the newly bound LUN. With a storage system, RAID 1 hardware mirroring has the following advantages: ◆ automatic operation (you do not have to issue commands to initiate it) ◆ physical duplication of images ◆ a rebuild period that you can select during which the SP recreates the second image after a failure RAID Types 2-7

  • 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

RAID Types
2-7
RAID Types and Trade-offs
larger. By using both the read and write cache, a RAID 3 group can
handle several concurrent streams of access.
RAID 3 Groups do not require any special buffer area. No fixed
memory is required to use write cache with RAID 3. Simply allocate
write cache as you would for RAID 5, and ensure that caching is
turned on for the LUNs in the RAID 3 Groups. Access to RAID 3
LUNs is compatible with concurrent access to LUNS of other RAID
types on the storage system.
RAID 1 Mirrored Pair
A RAID 1 Group consists of two disks that are mirrored
automatically by the storage-system hardware.
W
ith a RAID 1 Group,
you can create multiple RAID 1 LUNs to apportion disk space to
different users, servers, and applications.
RAID 1 hardware mirroring within the storage system is not the same
as software mirroring, remote mirroring, or hardware mirroring for
other kinds of disks. Functionally, the difference is that you cannot
manually stop mirroring on a RAID 1 mirrored pair, and then access
one of the images independently. If you want to use one of the disks
in such a mirror separately, you must
unbind
the mirror (losing all
data on it), rebind the disk as the type you want, and software format
the
newly bound LUN.
With a storage system, RAID 1 hardware mirroring has the following
advantages:
automatic operation (you do not have to issue commands to
initiate it)
physical duplication of images
a rebuild period that you can select during which the SP recreates
the second image after a failure