Novell Server Consolidation and Migration Toolkit 1.1, Руководство администратора, Страница: 84 / 126

84 Novell Server Consolidation and Migration Toolkit Administration Guide
no
vd
ocx
(E
NU)
9 Decem
ber
200
5
The Server Consolidation Utility copies data at a faster rate than a Windows
file copy.
Server Consolidation Utility Copies Incomplete Data Files
Problem: Files copied to the destination server have any of the following characteristics:
• Destination is a 0-byte file.
• Creation time and date are incorrect when compared to the source server.
• Modification time and date are incorrect when compared to the source
server.
• File was not completely copied. (This would be indicated by the
destination file being smaller in size than the source file.)
Action: Use the latest SMDR and TSAFS modules on the source NetWare server.
Path Size Limitations for Data Copy
Problem: Because the Server Consolidation Utility is a Windows-based program, it is
subject to the path size limitation of Windows, which is 255 characters. If you
have data where the path name is longer than 255 characters, the Server
Consolidation Utility cannot copy data that exceeds this maximum.
Action: One workaround is to reorganize the data on your source server so that the path
size does not exceed 255 characters.
Action: Another possibility is to use the server-based processing feature to copy the
data. Since the workstation does not monitor the file copy process, it is not
subject to the path size limitations of the workstation. However, the server-
based processing copy is limited by the supported path size of the server
operating system. For example, if the server allows path sizes up to 1024
characters, then data is copied up to the 1024-character path limit.
“Trustee Not Restored” Errors When Copying Double-Byte Character Data Tree-to-
Tree
Explanation: In a tree-to-tree consolidation, the Server Consolidation Utility stores the full
distinguished names of trustees in a file that is stored on the destination server.
This file is stored using the local code page of the destination server. Object
names containing double-byte characters (Japanese and other oriental
languages) may not match if the local code page versions on the source and
destination servers do not match exactly.
Problem: When the object names do not match between the source and destination
server, you might see messages such as “Trustee name was not restored for
path , because the trustee IDs are different.”
Action: Because of known limitations with code pages, this issue cannot be resolved in
the current version of the Server Consolidation Utility. Novell plans to address
this in a future release of the Server Consolidation and Migration Toolkit.
Copying Double-Byte Character Data from NetWare 5.1 to OES Linux
Problem: In NetWare 5.1, SMS uses the double-byte or multi-byte character set (MBCS)
format to back up Japanese data. NSS and Linux use Unicode. In order for