Adaptec 5325301656 Administration Guide - Page 111

Estimating Snapshot Pool Requirements, Snapshots and iSCSI Disks

Page 111 highlights

Estimating Snapshot Pool Requirements Snapshots and iSCSI Disks Running a snapshot on a volume containing an iSCSI Disk will abruptly disconnect any clients attempting to write to the iSCSI Disk and the resulting snapshot may contain inconsistent data. Do not use snapshots on a volume containing an iSCSI Disk. Estimating Snapshot Pool Requirements Snapshot data grow dynamically for as long as a snapshot is active and as long as there is enough space available in the snapshot pool to store them. When the snapshot pool approaches its capacity (at about 95 percent), the Snap Server deletes the oldest snapshot's data to create space for more recent snapshot data. The default configuration allocates 80 percent of RAID capacity to the volume and 20 percent to the snapshot pool. You can adjust the size of the pool up (assuming unallocated space exists) or down according to your needs. If you find that your snapshot strategy does not require all of the space allocated to the snapshot pool by default, consider decreasing snapshot pool capacity and reallocating the capacity to the file system. To adjust the size of the snapshot pool, navigate to the Storage > Snapshots screen, and click the Adjust Snapshot Space link in the introductory text. The number of snapshots that a RAID can support is a function of these factors: • The space reserved for the snapshot data • The duration of the snapshots you create • The amount and type of write activity to the volume(s) since the snapshot was created The following table describes minimum and maximum allocation cases. Allocate about 10% of RAID if Allocate about 25% of RAID if • Activity is write-light • Activity is write-heavy • Write access patterns are concentrated in • Write access patterns are randomized a few places across the volume • A small number of Snapshots must be available at any point in time • A large number of Snapshots must be available at any point in time Chapter 7 Snapshots 97

  • 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
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224

Estimating Snapshot Pool Requirements
Chapter 7
Snapshots
97
Snapshots and iSCSI Disks
Running a snapshot on a volume containing an iSCSI Disk will abruptly disconnect
any clients attempting to write to the iSCSI Disk and the resulting snapshot may
contain inconsistent data. Do not use snapshots on a volume containing an iSCSI
Disk.
Estimating Snapshot Pool Requirements
Snapshot data grow dynamically for as long as a snapshot is active and as long as
there is enough space available in the snapshot pool to store them. When the
snapshot pool approaches its capacity (at about 95 percent), the Snap Server deletes
the oldest snapshot’s data to create space for more recent snapshot data.
The default configuration allocates 80 percent of RAID capacity to the volume and
20 percent to the snapshot pool. You can adjust the size of the pool up (assuming
unallocated space exists) or down according to your needs. If you find that your
snapshot strategy does not require all of the space allocated to the snapshot pool by
default, consider decreasing snapshot pool capacity and reallocating the capacity to
the file system. To adjust the size of the snapshot pool, navigate to the
Storage >
Snapshots
screen, and click the
Adjust Snapshot Space
link in the introductory text.
The number of snapshots that a RAID can support is a function of these factors:
The space reserved for the snapshot data
The duration of the snapshots you create
The amount and type of write activity to the volume(s) since the snapshot was
created
The following table describes minimum and maximum allocation cases.
Allocate about 10% of RAID if
Allocate about 25% of RAID if
Activity is write-light
Write access patterns are concentrated in
a few places
A small number of Snapshots must be
available at any point in time
Activity is write-heavy
Write access patterns are randomized
across the volume
A large number of Snapshots must be
available at any point in time