Adaptec 5325301656 Administration Guide - Page 138

Step 2: Back up your system, Step 3: Convert to Unicode

Page 138 highlights

Converting to Unicode Step 2: Back up your system Back up your system as you normally would. For more information about backing up your server, please see "Backing Up Server and Volume Settings" on page 101. Step 3: Convert to Unicode Navigate to Server > Unicode and enable Unicode. Once it has been enabled on your Snap Server you cannot disable Unicode. Be sure your settings and data have been saved to an off-server location before enabling Unicode. If NFS is enabled on your system, you must also select a client code page that will be used by NFS clients. Options include ISO-8859-1, ISO-8859-15, EUC-JP, and UTF8. Caution Do not convert to Unicode if your volume is full. Unicode requires space on the volume for a reference file. If the volume is full, Unicode will not convert the system properly and might cause data corruption. Once you have converted to Unicode, it is important to note the following: • The server reboots after Unicode has been enabled. • After rebooting, the server will convert all file systems to Unicode file names, which can take some time. • File systems are accessible during conversion. During this time, file names with extended characters in them before Unicode was enabled will appear with garbled characters before being converted to Unicode. • File system conversion is made assuming code page 1252. If files with extended characters were written to the server via NFS or FTP prior to Unicode conversion, and the NFS or FTP client was operating in a code page other than 1252 or ISO 8859-1, these characters may not convert properly. • A small number of extended characters (about 10 total characters) written by Macintosh clients over AFP will be converted with different characters than originally written. • Prior to Unicode conversion, if Macintosh clients are connected to the server selecting a code page other than MacRoman (US), extended characters written by those clients may not convert properly. • Local users are converted to Unicode assuming the original source is code page 1252. 124 Snap Server Administrator 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
  • 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

Converting to Unicode
124
Snap Server Administrator Guide
Step 2: Back up your system
Back up your system as you normally would. For more information about backing
up your server, please see “Backing Up Server and Volume Settings” on page 101.
Step 3: Convert to Unicode
Navigate to
Server > Unicode
and enable Unicode. Once it has been enabled on your
Snap Server you cannot disable Unicode. Be sure your settings and data have been
saved to an off-server location before enabling Unicode.
If NFS is enabled on your system, you must also select a client code page that will
be used by NFS clients. Options include ISO-8859-1, ISO-8859-15, EUC-JP, and
UTF8.
Caution
Do not convert to Unicode if your volume is full. Unicode requires space
on the volume for a reference file. If the volume is full, Unicode will not convert the
system properly and might cause data corruption.
Once you have converted to Unicode, it is important to note the following:
The server reboots after Unicode has been enabled.
After rebooting, the server will convert all file systems to Unicode file names,
which can take some time.
File systems
are
accessible during conversion. During this time, file names with
extended characters in them before Unicode was enabled will appear with
garbled characters before being converted to Unicode.
File system conversion is made assuming code page 1252. If files with extended
characters were written to the server via NFS or FTP prior to Unicode conversion,
and the NFS or FTP client was operating in a code page other than 1252 or ISO
8859-1, these characters may not convert properly.
A small number of extended characters (about 10 total characters) written by
Macintosh clients over AFP will be converted with different characters than
originally written.
Prior to Unicode conversion, if Macintosh clients are connected to the server
selecting a code page other than MacRoman (US), extended characters written by
those clients may not convert properly.
Local users are converted to Unicode assuming the original source is code page
1252.