You will be lucky to get 30gb/hr. Typically about 7 to 8 MB/sec is all you will ever see, maybe 10 if your files are larger over a 100mb interface. Also, not all interface cards and Ethernet card drivers are created equal. Many are 100mb connectivity, but really cannot perform at continuous throughput of more than 60mb. There are many ways to help which various responders have suggested.
Windows allocation is slow at best and single thread to a file share or drive letter which ever applies based on some documents that I have reviewed. One suggestion was to make sure you create multiple file spaces, but also you need to use collocate by filespace to make sure the data is spread across the tapes so that parallel restore commands could be issued from the client. The other pieces to this equation are what kind of disk subsystem is the windows server going to be attached to. If it is something like an IBM ESS, HDS 9900, or EMC 8730 with FC connections, then it will perform pretty well. The other piece is how many tape drives did you put on the SCSI channels each. I prescribe to 1 adapter to 1 drive on these high end drives if you really have the network bandwidth. But there is no way you are doing that. I bet you are 1 adapter to 3 to 5 drives. This causes the drives to collide on the SCSI bus and potentially dramatically slow down if the are active. However, all said and done, you have many issues to resolve for restoring a server of this magnitude, from experience. Be prepared to roll out your wallet. Gigabit connectivity, parallel pathways, CISCO switch upgrades, converting to SAN tape, etc are in the offing. This has nothing to do with TSM it is just physics. -----Original Message----- From: John Naylor [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 15, 2002 5:26 AM To: [EMAIL PROTECTED] Subject: Re: Large server restore time? Karel, Your network might be a problem. If it was dedicated to this client alone you could expect at 90% efficiency about 39 gb per hour, So the quickest you could expect to restore your max size client over the network would be around 19 hours. Would this be fast enough? Karel Bos <[EMAIL PROTECTED]> on 01/15/2002 07:44:35 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: John Naylor/HAV/SSE) Subject: Large server restore time? Today I received a request to back-up a win2000 fileserver. They will start with 200 gig. Based on servers we currently host I predict this server to store 8755028 files and 756095 mb on the TSM server. The TSM server is version 4.1.3 and runs on a 1gig 2 cpu AIX machine. The library is a 3584L32 from IBM with 10 scsi lto drives. The TSM client will be version 4.2.x. The network is 100mbps ethernet (which will not be THE problem). Smaller fileservers have a poor restore time (>26 hours), so this will become a disaster. Is there anyone out there who has something like this AND can keep the restore time less than 24 hours (tested!). If so, tell me how, please. Thanx, Karel Bos NUON ICT Holland ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy plc. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Scottish Hydro-Electric, Southern Electric, SWALEC and S+S are trading names of the Scottish and Southern Energy Group. **********************************************************************
