Just brew a pot of coffee... I tell folks, just because you "can" do something doesn't mean its a good idea "to" do something and that much data, that many files in a single mount point is a "poor choice" (but I deal with it almost daily so you're not alone).
I haven't been dealing with the Win2012 boxes or the V6.4 client code that much (yet) but TSM will do the standard restore type action of downloading to the client the list of active files in TSM where the client will do the comparison and determine if it should or shouldn't restore the file. That many TSM DB lookups, transfer of info, comparisons is going to take a long time but it should run OK. Dwight E. Cook Technical Services Prof. Sr. Strategic Outsourcing Delivery (918) 493-4678 From: Bill Boyer <bjdbo...@comcast.net> To: ADSM-L@vm.marist.edu, Date: 01/21/2014 11:07 AM Subject: Massive Restore Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> 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." - ??
