![]() |
![]() |
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 different method for retrieving 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. This request results in files and directories being returned directly from the server without further action by the client. The client merely accepts the data coming from the server and restores it to the destination named on the restore command.
An example of an unrestricted wildcard command would be:
/home/mydocs/1999/*
An example of a restricted wildcard command would be:
/home/mydocs/1999/sales.*
When the client uses this method, the restore session is treated differently. If the restore process is interrupted for any reason, such as a power outage or network failure, the server records the point at which the restore was interrupted. This record is known to the client as a restartable restore. It is possible to create more than one restartable restore session. Use the query restore command to find out if your client has any restartable restore sessions in the server database.
The existence of a restartable restore inhibits further backups of that file system until the restartable restore is completed. If you attempt to repeat the restore that was interrupted or try to back up the destination file space, the attempt will fail because the original restore was not completed. You can restart the restore at the point of interruption by entering the restart restore command, or you can delete the restartable restore using the cancel restore command. If you restart the interrupted restore, it will restart with the first transaction, which may consist of one or more files, not completely restored when the interruption occurred. Because of this, you may receive some replace prompts for files from the interrupted transaction which were already restored.
The differences between the standard restore process and the no query restore process are outlined below.