Hey Tom, THAT is an interesting bit of information. What media is that 38GB file on? Do you know the volser? If I were going to work on it, the first thing I would do is copy that tape to a different tape and then try the restore again.
W On 3/11/08, Kauffman, Tom <[EMAIL PROTECTED]> wrote: > > We managed to restore a 206 GB file to the same server with no issues or > errors; the admin of the box determined we didn't need the 38 GB file, so > the issue was dropped. I'd rather have resolved the issue, myself. > Tom Kauffman > NIBCO, Inc > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Henrik Vahlstedt > Sent: Tuesday, March 11, 2008 3:05 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen > something like this before? > > Hello, > > Only curious, is this one solved? > > > //Henrik > > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of > Stefan Holzwarth > Sent: 10. mars 2008 20:33 > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] AW: Interesting problem in MS-Win restoer -- anyone seen > something like this before? > > In the past we had 2 times a similar problem: > first time (tsm server on mvs) the ip sequence number did a wrap around > and was not properly handled by mvs. (So large restores always stopped at > different positions) sencond time (tsm server on nt) we realized that our > network backbone did corrupt our ip pakets without crc errors! we could view > the problem by adding crc tothe communication layer within tsm. The restore > to that time (a exchange db) was no more possible since the backup data were > not correct. The restore always stopped at the same position. > > Regards > Stefan Holzwarth > > > -----Ursprüngliche Nachricht----- > > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag > > von Kauffman, Tom > > Gesendet: Montag, 10. März 2008 15:05 > > An: ADSM-L@VM.MARIST.EDU > > Betreff: Interesting problem in MS-Win restoer -- anyone seen > > something like this before? > > > > We've been trying to restore a 38 GB file to a Win2003 SP1 server; the > > restore comes to a near halt at 31.8 GB. > > > > At the TSM server side (5.5.0.0) we see 'sendw', and if we leave > > everything alone the restore continues at an incredibly slow pace (20 > > MB in 8 hours). > > > > On the client side - CPU utilization drops to between 1 and 3 percent, > > but task manager shows 'system idle process' using 99% of the cpu. > > > > The results have been the same with both the TSM 5.1.6 client and the > > 5.5 client, using both the GUI and the command line. > > > > The only errors that show up on either system occur when we kill the > > restore. > > > > And (FWIW) there is no anti-virus scanner running while the restore is > > running. > > > > I'm lost - any ideas/suggestions? > > > > TIA > > > > Tom Kauffman > > NIBCO, Inc > > > > ________________________________ > > CONFIDENTIALITY NOTICE: This email and any attachments are for the > > exclusive and confidential use of the intended recipient. If you are > > not the intended recipient, please do not read, distribute or take > > action in reliance upon this message. If you have received this in > > error, please notify us immediately by return email and promptly > > delete this message and its attachments from your computer system. We > > do not waive attorney-client or work product privilege by the > > transmission of this message. > > > > > ------------------------------------------------------------------- > The information contained in this message may be CONFIDENTIAL and is > intended for the addressee only. Any unauthorised use, dissemination of > the > information or copying of this message is prohibited. If you are not the > addressee, please notify the sender immediately by return e-mail and > delete > this message. > Thank you. > > CONFIDENTIALITY NOTICE: This email and any attachments are for the > exclusive and confidential use of the intended recipient. If you are not > the intended recipient, please do not read, distribute or take action in > reliance upon this message. If you have received this in error, please > notify us immediately by return email and promptly delete this message > and its attachments from your computer system. We do not waive > attorney-client or work product privilege by the transmission of this > message. >