Adaptec 5325301656 Administration Guide - Page 139

Unicode and Protocol Interaction, Step 4: Make a new DRImage

Get Adaptec 5325301656 - Snap Server 14000 NAS PDF manuals and user guides
UPC - 753253016563
View all Adaptec 5325301656 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 139 highlights

Unicode and Protocol Interaction Step 4: Make a new DRImage Once your system has been converted to unicode, make a new DRImage. The procedures are the same as before (see "Disaster Recovery Procedural Overview" on page 107 for more details). Step 5: Back up the system with Unicode enabled backup applications Back up your system with a Unicode compliant backup application. Please see the following section "Backing Up Unicode Servers" on page 127 for more information. Unicode and Protocol Interaction Extended characters in filenames are encoded on the Snap Server file system using UTF8, a method of representing all Unicode characters. However, network protocols and clients vary in their support of Unicode and UTF8, which has ramifications in the way they interact with one another when sharing files with extended characters in filenames. The following sections describe how different protocols interact with extended characters. SMB Most Windows and MacOS X clients, as well as the SMB protocol, support the majority of Unicode characters. Therefore, in general, all characters written by Windows and MacOS X clients will be properly retained and visible to other Windows and MacOS X clients and Unicode-compliant protocols. However, if there are characters on the file system that are invalid UTF8 or are otherwise not mappable to the Unicode encoding method (UCS2) used by the SMB protocol, an escape sequence will display in the file name of the file being read. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the filename; for example, you might see {!^AB in a file name. Windows and MacOS X clients can edit such files, and the names will be retained in their original form when written back to the file system. AFP MacOSX and higher use the same method to represent Unicode characters as the Snap Server: UTF8. Information written to the server from MacOSX or higher will be encoded wth UTF8 and should be viewed correctly from the MacOS UI. However, similarly to SMB clients, characters in filenames that are incompatible with UTF8 will be returned with an escape sequence. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the Chapter 10 Unicode 125

  • 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
Unicode and Protocol Interaction
Chapter 10
Unicode
125
Step 4: Make a new DRImage
Once your system has been converted to unicode, make a new DRImage. The
procedures are the same as before (see “Disaster Recovery Procedural Overview”
on page 107 for more details).
Step 5: Back up the system with Unicode enabled backup applications
Back up your system with a Unicode compliant backup application. Please see the
following section “Backing Up Unicode Servers” on page 127 for more information.
Unicode and Protocol Interaction
Extended characters in filenames are encoded on the Snap Server file system using
UTF8, a method of representing all Unicode characters. However, network
protocols and clients vary in their support of Unicode and UTF8, which has
ramifications in the way they interact with one another when sharing files with
extended characters in filenames.
The following sections describe how different protocols interact with extended
characters.
SMB
Most Windows and MacOS X clients, as well as the SMB protocol, support the
majority of Unicode characters. Therefore, in general, all characters written by
Windows and MacOS X clients will be properly retained and visible to other
Windows and MacOS X clients and Unicode-compliant protocols.
However, if there are characters on the file system that are invalid UTF8 or are
otherwise not mappable to the Unicode encoding method (UCS2) used by the SMB
protocol, an escape sequence will display in the file name of the file being read.
Escape sequences begin with
{!^.
The following two characters are the hexidecimal
value of the characters in the filename; for example, you might see
{!^AB
in a file
name. Windows and MacOS X clients can edit such files, and the names will be
retained in their original form when written back to the file system.
AFP
MacOSX and higher use the same method to represent Unicode characters as the
Snap Server: UTF8. Information written to the server from MacOSX or higher will
be encoded wth UTF8 and should be viewed correctly from the MacOS UI.
However, similarly to SMB clients, characters in filenames that are incompatible
with UTF8 will be returned with an escape sequence. Escape sequences begin with
{!^.
The following two characters are the hexidecimal value of the characters in the