Retrieve use cases

Retrieve archives from file spaces that are not Unicode-enabled

If you want to retrieve archives from file spaces that were renamed by the Unicode-enabled client, you must specify the source on the server and a destination on the client.

This section applies to Mac OS X only. 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 /. 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 retrieve a file from the renamed (old) file space to its original location, you must enter both the source and destination as follows:

If you want to retrieve archives from file spaces that were renamed by the Unicode-enabled client, you must specify the source on the server and a destination on the client. For example, you archived files from your H-disk, named \\your-node\h$ prior to installing the client. After the installation, you issue the following archive command:

   arc h:\logs\*.log

Before the archive takes place, the server renames the file space to \\your-node\h$_OLD. The archive 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 retrieve a file from the (old) renamed file space to its original location, you must enter both the source and destination as follows:

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

Retrieve named streams

The backup-archive client retrieves named streams on a file basis only.

Directories in Windows systems can contain named streams. Named streams attached to a directory will always be overwritten (regardless of the value of the prompt option) during the retrieve.

Retrieve sparse files

When retrieving sparse files to a non-NTFS or non-ReFS file system, set the server communication time-out value (IDLETIMEOUT) to the maximum value of 255 to avoid client session timeout.

The following issues apply if more data is restored than the Microsoft disk quota allows:

• If the user who is performing the retrieve has a disk quota (for example, the user belongs to the Backup Operator Group), the backup-archive client does not retrieve any data that exceeds the disk quota of the retrieve user and displays a "Disk Full" message.
• If the user who is performing the retrieve does not have a disk quota (for example, the user belongs to the Administrator Group), the backup-archive client retrieves all data and transfers ownership of the files that exceed the disk quota of the original owner to the user who is performing the retrieve (in this case, the Administrator).