Well, it turns out that the client has no downtime for this system so I don't think the image thing is an option. Not to mention one of the admins installed the LVSA code through the GUI setup wizard the night before and chose to reboot later and the system crashed with a bugcheck for TSMLVSA.sys yesterday. IBM had multiple tickets where this had occurred at other customers in their database. We are waiting on a reasonable explanation from IBM but the client is not too comfortable with the image idea at this point and is looking to use their old Backup Exec system where they have been successful doing this in the past (SHAME! SHAME!). I suggested the robocopy method to them but it is their decision/data.
Thanks for all of your help!! Your are a great bunch of folks!! Nicholas If you assume a file create rate of about 100,000/hour then you are looking at a 20 hour restore if all else goes well. You might squeeze more file creates out of your new server, but who really knows? If you assume a 200 GB/hour transfer rate and use image instead, you can cut the restore time in half. You can't improve the file create rate by using multiple streams. In fact, that actually reduces the rate. I'm still advocating the image route. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nicholas Rodolfich Sent: Thursday, December 11, 2008 3:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Best way to use TSM to move 2Tb of data It is ~2,000,000 individual files after hours.
