That is just TOO weird.
I can't think of anthing else to do other than call support and run a trace.
If you figure it out, inquiring minds want to know!
Wanda
On 3/13/08, Kauffman, Tom <KauffmanT AT nibco DOT com> wrote:
>
> The 38 GB filesystem was an internal RAID array; the 206 GB file went to a
> SAN-attached ESS.
>
> But we tried restoring the 38 GB file to the ESS filesystem - and got the
> same result. We also tried to restore on a different Windows server - and
> hung at about the same point.
>
> Tom
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Wanda Prather
> Sent: Wednesday, March 12, 2008 8:38 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen
> something like this before?
>
> Good point - I assume a tape error (one of those cases where TSM is doing
> lots and lots of retries to read the same marginal tape) would show the
> session in RUN state, not in SENDW.
>
> I've seen this issue before when the client wasn't set to full duplex, but
> then you wouldn't have gotten your 206 GB file restored. Same with the
> TCP
> Chimney Offload issue (and I think that is only for Win2K3 SP2).
>
> So: what is different about the 36GB file vs. the 206 GB file!?? Is the
> output destination on the same physical drive?
>
>
>
>
> On 3/11/08, Kauffman, Tom <KauffmanT AT nibco DOT com> wrote:
> >
> > I'll have to look -- I *think* they're both on the same tape, LTO-4.
> We've
> > only got one LTO-4 in the library showing errors, and it's in a
> different
> > storage pool.
> >
> > I'm still bothered by the fact that the TSM server goes into 'sendw' and
> > shows 300 to 500 Bytes per second transfer rate to the Win2003 system --
> > which is showing 99% CPU usage in System Idle Processes (and I'd love to
> > kill the MickeySoft idiot who decided to report network overhead as
> 'system
> > idle').
> >
> > Tom
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> > Behalf Of
> > Wanda Prather
> > Sent: Tuesday, March 11, 2008 4:12 PM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen
> > something like this before?
> >
> > 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 <KauffmanT AT nibco DOT com> 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:ADSM-L AT VM.MARIST DOT EDU] On
> > > Behalf
> Of
> > > Henrik Vahlstedt
> > > Sent: Tuesday, March 11, 2008 3:05 PM
> > > To: ADSM-L AT VM.MARIST DOT 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:ADSM-L AT VM.MARIST DOT EDU] On
> > > Behalf
> Of
> > > Stefan Holzwarth
> > > Sent: 10. mars 2008 20:33
> > > To: ADSM-L AT VM.MARIST DOT 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:ADSM-L AT VM.MARIST DOT EDU] Im
> Auftrag
> > > > von Kauffman, Tom
> > > > Gesendet: Montag, 10. März 2008 15:05
> > > > An: ADSM-L AT VM.MARIST DOT 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.
> > >
> >
> > 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.
> >
>
> 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.
>
|
