Restore from file spaces that are not Unicode-enabled

If you want to restore from file spaces that are not Unicode-enabled, you must specify the source on the server and a destination on the client, prior to installing the Unicode-enabled client.

Note: This Unicode section applies only to Mac OS X.

If you want to restore from file spaces that are not Unicode-enabled, you must specify the source on the server and a destination on the client. For example, you backed up your H disk named \\your-node\h$ prior to installing the Unicode-enabled client. After the installation, you issue the following command for a selective backup:

   sel h:\logs\*.log

For example, assume that Jaguar is the name of your startup disk and you back up all of the .log files in the /Users/user5/Documents directory. Before the backup takes place, the server renames the file space to Jaguar_OLD. The backup places the data specified in the current operation into the Unicode-enabled file space named /. The new Unicode-enabled file space now contains only the /Users/user5/Documents directory and the *.log files specified in the operation.

If you want to restore a file from the renamed (old) file space to its original location, you must enter both the source and destination as follows:

   restore Jaguar_OLD/Users/user5/Documents
     /mylog.log /Users/user5/Documents/

Before the backup takes place, the server renames the file space to \\your-node\h$_OLD. The backup continues placing the data specified in the current operation into the Unicode-enabled file space named \\your-node\h$. That file space now contains only the \logs directory and the *.log files. If you want to restore a file from the (old) renamed file space to its original location, you must enter both the source and destination as follows:

   restore \\your-node\h$_OLD\docs\myresume.doc h:\docs\