Re: Large Restore

2000-07-26 Thread Richard Sims
>The issue is the Database reads required to restore millions of >small files. That's certainly a factor. If your tape drive technology is a poor performer in start-stop operations, then the positioning involved in getting to each file is going to be a much larger factor, which as some customers

Re: Large Restore

2000-07-26 Thread Kyle Payne
S. Sent: Tuesday, July 25, 2000 10:12 AM To: [EMAIL PROTECTED] Subject: Large Restore We are running ADSM 3.1 and we are looking a restoring 400GB of data for a test. Anyone out there have any experience with restores this large? What kind of time frame am I looking at for this restore? Any

Re: Large Restore

2000-07-26 Thread Slaughter, Bill
July 25, 2000 11:12 AM To: [EMAIL PROTECTED] Subject: Large Restore We are running ADSM 3.1 and we are looking a restoring 400GB of data for a test. Anyone out there have any experience with restores this large? What kind of time frame am I looking at for this restore? Any lessons learned that

Re: Large Restore

2000-07-26 Thread Cook, Dwight E
mpressed data should be about 30-45GB/hr client file space...) hope this helps later, Dwight > -- > From: Ewen, Bill S.[SMTP:[EMAIL PROTECTED]] > Reply To: ADSM: Dist Stor Manager > Sent: Tuesday, July 25, 2000 10:11 AM > To: [EMAIL PROTECTED] > Subj

Large Restore

2000-07-26 Thread Ewen, Bill S.
We are running ADSM 3.1 and we are looking a restoring 400GB of data for a test. Anyone out there have any experience with restores this large? What kind of time frame am I looking at for this restore? Any lessons learned that I could incorporate before I start this project? Thanks Bill Ewen