Hi, keep in mind that with a no-query restore, you can also run a multi-session restore. You would need to increase your "resourceutilization" client option from the default value of 2. You would then need to adjust the "Maximum Mount Points Allowed" value of the node with the "update node <nodename> maxnummp=x" to account for the increase usage of tape drives for this client.
For example, with the client using : resourceutilization 10 You would then update the client node with : update node <nodename> maxnummp=8 Now, provided you have 8 tape drives available, and the data to be restored is spread over 8 different tapes or more, the restore would be done using up to 8 simultaneous concurrent sessions. Rejean Larivee IBM Tivoli Storage Manager Software Support "ADSM: Dist Stor Manager" <[email protected]> wrote on 01/22/2014 12:17:49 PM: > From: Dwight Cook <[email protected]> > To: [email protected], > Date: 01/22/2014 12:18 PM > Subject: Re: Massive Restore > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > With the "no query restore" you are pushing the workload onto the TSM > server. > The client will still have to transmit the details on all the 7.5M files > up to the TSM server. > And I believe a simple "restore -replace=no -subdir=yes X:\*" will trigger > a ~no query restore~ by default. > OK, interesting, I double checked in the manual and I would want to test > this to ensure this is how it would behave but it looks like that would > trigger a no query restore which would simply trigger the tsm server to > send the data down to the client where at that point it would be > determined if a replace would be performed and it wouldn't due to the > replace=no... but what I'm reading leads me to believe all the data would > actually be transmitted down to the client at which point you would get > the typical "file exists... skipping." notification. > > From the manual: > 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, or volinformation, 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 > coming from the server and restores it to the destination named on the > restore > command. > > I don't have time to test but would be interested in hearing how the > restore behaves. > > Dwight E. Cook > Technical Services Prof. Sr. > Strategic Outsourcing Delivery > (918) 493-4678 > > > > From: Zoltan Forray <[email protected]> > To: [email protected], > Date: 01/21/2014 12:31 PM > Subject: Re: Massive Restore > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > > > Definitely want to do a "No Query Restore". Depends on the memory, > client > (64-bit). > > > On Tue, Jan 21, 2014 at 11:53 AM, Bill Boyer <[email protected]> wrote: > > > Windows 2012 server with TSM V6.4.1 client installed. TSM Server is > V6.3.3 > > > > > > > > The server is for archived "stuff". It is rather large. >10TB of data > and > > probably close to millions of objects. They have it backed up from a > while > > ago and recently some files/directories were deleted. So now they want > to > > do a restore with REPLACE=NO to get those files back. A backup hasn't > been > > done so the deleted files weren't expired. The one top level directory > they > > want to run this against has more than 7.5 million objects. > > > > > > > > Is this going to be too much for the client to handle on a single > restore > > request? The next level down in that directory has dozens of sub > > directories > > and to do the restores at that level would be a real pain. > > > > > > > > Any opinions? Any special options you think I should consider using? I > know > > the initial file determination will take a long time. The admin doesn't > > really care how long it runs.. they just want to recovery as much as > they > > can. > > > > > > > > Bill Boyer > > DSS, Inc. > > (610) 927-4407 > > "Enjoy life. It has an expiration date." - ?? > > > > > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [email protected] - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html >
