Adaptec 5325301507 Administration Guide - Page 161

Unicode and Expansion Arrays, Backing Up Using Unicode-Enabled UNIX Clients

Page 161 highlights

Unicode and Expansion Arrays Backing Up Using Unicode-Enabled UNIX Clients Most Unicode-enabled UNIX clients run one of three language codes: 8859-1 (US), 8859-15 (Europe), or EUC-JP (Japan). In each of these situations, it is important to backup via the UNIX client with a language compliant backup application. Mixing languages (example: having a Japanese UNIX server and a Chinese backup application) will lead to data corruption. If you do not have language compliant backup applications, do not back up using UNIX. Backing Up Using Unicode-Enabled MacOS Clients Macintosh text encoding UTF8 is supported by MacOS 10.1.4 AFP 3 and later. For Unicode to function properly, your version of MacOS must fully support AFP 3. It is important to back up via the MacOS client with a language compliant backup application. Mixing languages (example: having Russian files on a server, then using a German backup application) will lead to data corruption. Unicode and Expansion Arrays This section outlines how SnapServer expansion arrays interact with Unicode. Unicode Converted Expansion Arrays When an expansion array is converted to Unicode, it stays converted to Unicode. This means that a Unicode enabled expansion array is only compatable with head units that have also been converted to Unicode. The following is a usage scenario concerning expansion arrays and how they operate with Unicode enabled servers. You have a SnapServer and an expansion array. You enable Unicode on both. You cannot then attach the expansion array to a non-Unicode-enabled SnapServer. The Unicode-enabled expansion unit will not be seen by a non-Unicode enabled server. Once an expansion array has been converted to Unicode, it cannot be used with non-Unicode enabled SnapServers. Chapter 10 Unicode 145

  • 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
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Unicode and Expansion Arrays
Chapter 10
Unicode
145
Backing Up Using Unicode-Enabled UNIX Clients
Most Unicode-enabled UNIX clients run one of three language codes: 8859-1 (US),
8859-15 (Europe), or EUC-JP (Japan). In each of these situations, it is important to
backup via the UNIX client with a language compliant backup application. Mixing
languages (example: having a Japanese UNIX server and a Chinese backup
application) will lead to data corruption. If you do not have language compliant
backup applications, do not back up using UNIX.
Backing Up Using Unicode-Enabled MacOS Clients
Macintosh text encoding UTF8 is supported by MacOS 10.1.4 AFP 3 and later. For
Unicode to function properly, your version of MacOS must fully support AFP 3.
It is important to back up via the MacOS client with a language compliant backup
application. Mixing languages (example: having Russian files on a server, then
using a German backup application) will lead to data corruption.
Unicode and Expansion Arrays
This section outlines how SnapServer expansion arrays interact with Unicode.
Unicode Converted Expansion Arrays
When an expansion array is converted to Unicode, it stays converted to Unicode.
This means that a Unicode enabled expansion array is only compatable with head
units that have also been converted to Unicode.
The following is a usage scenario concerning expansion arrays and how they
operate with Unicode enabled servers.
You have a SnapServer and an expansion array. You
enable Unicode on both. You
cannot then attach the expansion array to a non-Unicode-enabled SnapServer.
The
Unicode-enabled expansion unit will not be seen by a non-Unicode enabled server.
Once an expansion array has been converted to Unicode, it cannot be used with
non-Unicode enabled SnapServers.