No-query restore process

In the no-query restore process, a single restore request is sent to the server instead of querying the server for each object to be restored.

1. The client tells the server that a no-query restore is going to be completed and provides the server with details about file spaces, directories, and files.
2. The server uses a separate table to track entries which guide the restore.
3. The data to be restored is sent to the client. File and directory objects that are stored on disk are sent immediately since sorting for such data is not required before the object is restored.
4. You can use multiple sessions to restore the data. If the data is on multiple tapes, there are multiple mount points available at the server. The combination of using the resourceutilization option and MAXNUMMP allows multiple sessions.

When you enter an unrestricted wildcard source file specification on the restore command and do not specify any of the options: inactive, latest, pick, fromdate, or todate, the client uses a no-query restore method for restoring files and directories from the server. This method is called no-query restore because instead of querying the server for each object to be restored, a single restore request is sent to the server. In this case, the server returns the files and directories to the client without further action by the client. The client merely accepts the data that comes from the server and restores it to the destination named on the restore command.

When you enter an unrestricted wildcard source file specification on the restore command and do not specify any of the options: inactive, latest, pick, fromdate, todate, the client uses a no-query restore method for restoring files and directories from the server. This method is called no-query restore because instead of querying the server for each object to be restored, a single restore request is sent to the server. In this case, the server returns the files and directories to the client without further action by the client. The client merely accepts the data that comes from the server and restores it to the destination named on the restore command.

Using the IBM® Storage Protect GUI client, an example of an unrestricted wildcard command would be to select a folder from the restore tree window. An example of a restricted wildcard command would be to select individual files from a folder.

Using the command-line client, an example of an unrestricted wildcard command would be:

"/Users/user1/Documents/2004/*"

/home/mydocs/2004/*

c:\mydocs\2004\*

An example of a restricted wildcard file specification would be:

/Users/user1/Documents/2004/sales.*

/home/mydocs/2004/sales.*

c:\mydocs\2004\sales.*