Adaptec 5325301507 - Snap Server 4400 NAS, Руководство администратора

Страница: 157 / 250

Unicode and Protocol Interaction
Chapter 10 Unicode 141
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 123 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 143 for more information.
Unicode and Protocol Interaction
Extended characters in filenames are encoded on the SnapServer 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
SnapServer: 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 filename;