"No query" restore has nothing to do with minimizing tape mounts for restore. For a given restore, TSM mounts each needed tape once and only once, and reads it from front to back.
The most visible benefit of no query restore is that data starts coming back from the server sooner than it does with "classic" restore. With classic restore, the client queries the server for all objects that match the restore file specification. The server sends this information to the client, then the client sorts it so that tape mounts will be optimized. However, the time involved in getting the information from the server, then sorting it (before any data is actually restored), can be quite lengthy. No query restore lets the TSM server do the work: the client sends the restore file specification to the server, the server figures out the optimal tape mount order, and then starts sending the restored data to the client. The server can do this faster, and thus the time it takes to start actually restoring data is reduced. In either case, for a given restore, TSM will restore the files and directories in a manner that optimizes tape mounts. If it so happens that a file is restored before it's parent directory is restored, then the client will create the parent directory, restore the file, then restore the parent directory when it encounters it in the restore sequence. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. Karel Bos <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 08/20/2003 00:02 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: restore question Hi, Depends (love that statement) on the type of restore. If you have a no-query restore, the tsm server will restore the data in a "as few mounts as possible way", if you have a query restore the client will ask the tsm server for a object (being file or directory), so the TSM server can not do its thing to minimize the number of tapemounts. >From the read.me: No query restore 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. 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 coming from the server and restores it to the destination named on the restore command Regard, Karel > -----Oorspronkelijk bericht----- > Van: i love tsm [mailto:[EMAIL PROTECTED] > Verzonden: dinsdag 19 augustus 2003 21:02 > Aan: [EMAIL PROTECTED] > Onderwerp: restore question > > > Hi all > > A basic question... > > tapes are non collocated > > if you kick off a restore of multiple directories on a win2k > client will TSM > mount a tape and get all the data off that tape for the directories > concerned then move on to the next volume, or does it restore > sequentially > one directory at a time, i.e it could mount the same tape > numerous times as > it goes through thr directories. > > Many Thanks > > _________________________________________________________________ > Sign-up for a FREE BT Broadband connection today! > http://www.msn.co.uk/specials/btbroadband