Autofsrename

The autofsrename option renames an existing file space that is not Unicode-enabled on the Tivoli® Storage Manager server so that a Unicode-enabled file space with the original name can be created for the current operation.

When you specify autofsrename yes in your client options file, and the server value of autofsrename is set to client, the Tivoli Storage Manager server generates a unique name by appending _OLD to the file space name you specify in the current operation. For example, the server renames the file space Jaguar to Jaguar_OLD. If the new file space name is too long, the suffix replaces the last characters of the file space name. For example, the mylongfilesystemname file space name is renamed to:

   mylongfilesystem_OLD

Mac OS X operating systems If the new file space name already exists on the server, the server renames the new file space Jaguar_OLDx, where x is a unique number.

Mac OS X operating systems The server creates new Unicode-enabled file spaces that contain only the data specified in the current operation. For example, assume that Jaguar is the name of your startup disk and you archive all of the .log files in the /Users/user5/Documents directory. Before the archive takes place, the server renames the file space to Jaguar_OLD. The archive places the data specified in the current operation into the Unicode-enabled file space named Jaguar. The new Unicode-enabled file space now contains only the /Users/user5/logs directory and the *.log files specified in the operation. The server stores all subsequent full and partial incremental, selective backup, and archive data in the new Unicode-enabled file spaces.

Mac OS X operating systems For example, assume that Jaguar is the name of your startup disk and you archive all of the .log files in the /Users/user5/Documents directory. Before the archive takes place, the server renames the file space to Jaguar_OLD. The archive places the data specified in the current operation into the Unicode-enabled file space named Jaguar. The new Unicode-enabled file space now contains only the /Users/user5/logs directory and the *.log files specified in the operation. All subsequent full and partial incremental, selective backup, and archive data are stored in the new Unicode-enabled file spaces.

When you specify autofsrename yes in your client options file, and the server value of autofsrename is set to client, the Tivoli Storage Manager server generates a unique name by appending _OLD to the file space name you specify in the current operation. For example, the server renames the file space \\your-node-name\h$ to \\your-node-name\h$_OLD. If the new file space name is too long, the suffix replaces the last characters of the file space name, as follows:

   \\your-node-name_OLD

Windows operating systems If the new file space name already exists on the server, the server renames the new file space \\your-node-name_OLDx, where x is a unique number.

The server creates new Unicode-enabled file spaces that contain only the data specified in the current operation. For example, to archive files from your H: disk named \\your-node\h$, issue the following archive command:

   arc h:\logs\*.log

Windows operating systems Before the archive takes place, the server renames the file space to \\your-node\h$_OLD. The archive places the data specified in the current operation into the Unicode-enabled file space named \\your-node\h$. The new Unicode-enabled file space now contains only the \logs directory and the *.log files specified in the operation. All subsequent full and partial incremental, selective backup, and archive data are stored in the new Unicode-enabled file spaces.

Renamed file spaces remain on the server as stabilized file spaces. These file spaces contain all the original data, which you can restore as long as they remain on the server.

Note: When an existing file space is renamed during Unicode conversion, any access rules defined for the file space remain applicable to the original file space. New access rules must be defined to apply to the new Unicode file space.

After installation, perform a full incremental backup and 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. This operation requires increased processing time and storage on the server.

File spaces that are not Unicode-enabled can be viewed in the character set of the locale from which the files were backed up. A workstation running in a different locale might be unable to view or restore from these file spaces. Unicode-enabled file spaces that are backed up in one locale are visible in all other locales, provided that the workstation has the proper fonts installed.

Windows operating systems To restore or retrieve from a file space that is not Unicode-enabled, specify the source on the server and the destination on the client. See

Mac OS X operating systems The server can define the autofsrename option and override the autofsrename setting on the client.

Supported Clients

Mac OS X operating systems This option is valid for Mac OS X only. The server can define the autofsrename option and override the autofsrename setting on the client. The Tivoli Storage Manager API does not support this option.

Windows operating systems This option is valid for all Windows clients. The server can define the autofsrename option and override the autofsrename setting on the client. The Tivoli Storage Manager API does not support this option.

Options File

Mac OS X operating systems Place this option in the client system-options file (dsm.sys) within a server stanza. You can set this option on the General tab, Rename non-Unicode filespaces during backup/archive drop-down list box of the Preferences editor.

Windows operating systems Place this option in the client options file (dsm.opt) file. You can set this option on the General tab, Rename non-Unicode filespaces during backup/archive drop-down list box of the Preferences editor.

Syntax


                 .-Prompt-.   
>>-AUTOFsrename--+--------+------------------------------------><
                 +-Yes----+   
                 '-No-----'

Parameters

Yes: Specifies that the Tivoli Storage Managerserver automatically renames all file spaces that are not Unicode-enabled in the current backup or archive operation.
No: Specifies that the server does not rename file spaces that are not Unicode-enabled in the current backup or archive operation.
Prompt: Specifies that you are prompted whether to rename the file spaces that are not Unicode-enabled in the current operation. This is the default.

Considerations:

This option applies only when the server sets the autofsrename option to client.
When the client scheduler is running, the default behavior is to not prompt you. The next interactive session prompts you to rename the file space.
The client prompts you only one time per file space. If you specify no at the prompt, the client cannot rename the file spaces later. However, the Tivoli Storage Manager administrator can rename the file spaces on the server.
When backing up files to a file space that is not Unicode-enabled, the Unicode-enabled client skips the files and directories with names containing characters from a code page that is different from the current locale.
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, they might be expired. The Unicode-enabled client expires these files if you do not migrate the file space to a Unicode-enabled file space. You can back up and archive these files to a Unicode-enabled file space.

Examples

Options file:: autofsrename yes