Installation and User's Guide

Considerations for migrating between processor architecturesx32 and x64When migrating between the Tivoli Storage Manager processor architectures (x32and x64), there are some items that you need to consider for a successful migrationfrom one architecture to another.Consider the following items when migrating from one processor architecture toanother:vvvvvvvvThe restore of DFS links backed up from 32-bit Windows environments to 64-bitWindows environments, is not supported.The restore of DFS links backed up from 64-bit Windows environments to 32-bitWindows environments, is not supported.System state or system object data is incompatible between different processorarchitectures. Therefore, when migrating client data between different processorarchitectures, avoid backing up the system object or system state data from onearchitecture into the same file spaces containing the system object or systemstate data from another architecture. To avoid commingling the data, you can doeither of the following before the migration:– Ask your Tivoli Storage Manager administrator to rename the existing systemobject or system state file spaces. Once the migration is complete and youhave new backups of the system object or system state data, your TivoliStorage Manager administrator can delete the renamed file spaces. The filespaces to rename include one or more of the following:- SYSTEM OBJECT- SYSTEM STATE- SYSTEM SERVICES- ASRAsk your Tivoli Storage Manager administrator to delete the existing filespaces (listed above) for your node.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 filespaces are deleted. You can find additional information in the IBM Tivoli StorageManager for Windows Administrator's Guide.When an existing file space is renamed during Unicode conversion, any accessrules defined for the file space remain applicable to the original file space. Newaccess rules must be defined to apply to the new Unicode file space, if necessary.When backing up files to a file space that is not Unicode-enabled, theUnicode-enabled client skips the files and directories with names containingcharacters from a code page other than the current locale.If files and directories with names containing characters from a code page otherthan the current locale were previously backed up with a client that was notUnicode-enabled, Tivoli Storage Manager expires them in the file space that is notUnicode-enabled. However, the Unicode-enabled client can back up or archivethese files to a Unicode-enabled file space.When migrating from a client that is not Unicode-enabled to a Unicode client,file names with double-byte characters mixed with single-byte characters mightbe restored in mixed single-byte character set (SBCS) format. This is only adisplay issue.2 IBM Tivoli Storage Manager for Windows Backup-Archive Clients: Installation and User's Guide