Tivoli Header

Tivoli Storage Manager for Windows Backup-Archive Clients Installation and User's Guide

Migrating to the Unicode-Enabled Client

Unicode is a universal character encoding standard that supports the interchange, processing, and display of text that is written in any of the languages of the modern world. Unicode-enabled file spaces provide support for multi-lingual workstations without regard for the current locale. Beginning with Tivoli Storage Manager version 4.2, the Windows NT, 2000, XP, and .NET clients are Unicode enabled. The Windows NT, 2000, XP, and .NET clients support the Unicode code page for file, directory, and file space names. Unicode is not supported on the Windows Me client.

Benefits of Using the Unicode-Enabled Client

How to Migrate to the Unicode-Enabled Client

To migrate to the Windows NT, 2000 version 4.2 client, the server must be a version 4.2.0 or later level server. New clients storing data on the server for the first time require no special set up. In this case, the server automatically stores data in Unicode-enabled file spaces. However, if your client already stores data on the server, you need to plan for the migration of your file spaces to Unicode-enabled file spaces. This involves renaming your file spaces on the server and creating new Unicode-enabled file spaces on the server using the autofsrename option. For detailed information about this option, see Autofsrename.

The administrator can specify three possible values using the server autofsrename option: yes, no, or client. Note that the server setting for this option overrides the setting on the client.

Optionally, your administrator can rename the file spaces on the server that are not Unicode enabled.

For options and results when using the autofsrename option, see the table below.

Server Option Client Option Result
Yes Prompt, Yes, No Renamed
No Prompt, Yes, No Not Renamed
Client No Not Renamed
Client Yes Renamed
Client Prompt Based on User Response

For detailed information about the autofsrename option, see Autofsrename. For additional migration information, see Tivoli Storage Manager for Windows Administrator's Guide. For additional information about working with the Windows NT and 2000 clients, see:

Considerations for Migrating to the Unicode-Enabled Client

When migrating to the Tivoli Storage Manager Windows NT, 2000, XP, or .NET client, please consider the following:

  1. To support Unicode functionality, Windows NT, 2000 clients must connect to a version 4.2 server. See Tivoli Storage Manager Installing the Clients, SH26-4119, for further environment and installation information.
  2. Ensure that you install the fonts for the languages you want to display. If you do not have the necessary fonts installed, the file names and archive descriptions may not display properly. However, the Windows NT, 2000, XP, and .NET clients can still back up, restore, archive, and retrieve the files and directories.
  3. The Unicode-enabled version of a renamed file space name may be unreadable if the server cannot display the Unicode name. In this case, use the file space identifier (fsID) of the file space to identify these file spaces on the server. Use the query filespace command with the detail option to display the fsID of a file space. The file information dialog in the native and Web client GUIs also displays the fsID.
  4. After installing the V.4.2 Windows NT, 2000, XP, or .NET clients, we recommend that you perform a full incremental backup to rename all existing file spaces that are not Unicode enabled and back up the files and directories within them under the new Unicode-enabled file spaces.
  5. Renamed file spaces remain on the server and managed as stabilized file spaces. These file spaces contain all the original data, which can still be restored until the file spaces are deleted. You can find additional information in the Tivoli Storage Manager for Windows Administrator's Guide.
  6. The server stores information about each node, and once a node logs onto the server using a Windows NT, 2000, XP, .NET client, it cannot log on with a client that does not support Unicode. The server allows only a Windows NT, 2000, XP, .NET client to restore files from a Unicode-enabled file space.
  7. When backing up files to a file space that is not Unicode enabled, the Windows NT, 2000 client skips the files and directories with names containing characters from a code page other than the current locale.
  8. If files and directories with names containing characters from a code page other than the current locale were previously backed up with a client that was not Unicode enabled, Tivoli Storage Manager will expire them in the file space that is not Unicode enabled. However, the Windows NT, 2000 client can back up or archive these files to a Unicode-enabled file space.
  9. When migrating from a client that is not Unicode enabled to a Unicode Client, filenames with double-byte characters mixed with single-byte characters may be restored in mixed single-byte character set (SBCS) format. This is only a display issue.
  10. When a client performs a selective backup of an object and the original file space is renamed, the new Unicode-enabled file space contains only that object. Tivoli Storage Manager will back up all other directories and file spaces during the next full incremental backup.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]