ADSM-L

Re: MAXNUMMP

2006-09-14 12:20:23
Subject: Re: MAXNUMMP
From: "Smith, I (Ian)" <Ian.Smith AT RABOBANK DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Sep 2006 17:18:43 +0100
 
Oracle Enterprise Edition can parallelise the backup- i.e there are
multiple channels opened to the SBT_TAPE.

This is defined in the backup script or repository. Usually as a rule of
thumb, limited by the number of CPUs on the server.

MAXNUMMP should match the number of channels allocated by the RMAN
backup scripts. The MAXNUMMP specifies the number of tape mounts
required in the TSM subsystem.

_____________________________
Ian Smith
SAN/TSM Specialist
Hitachi Data Systems Certified Professional
IBM Tivoli Storage Manager Certified Consultant



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Anker Lerret
Sent: 14 September 2006 16:54
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] MAXNUMMP

This is my first post here after months of lurking.  I'd like to start
by thanking Richard Sims for his marvelous ADSM.QuickFacts.  Because of
that file, my employer thinks that I'm far smarter that I am.  Thank
you!

There's one thing, though, that I haven't been able to figure out in the
TSM doco, the ADSM-L archive or even ADSM.QuickFacts.  Can someone
explain (using one syllable words) what MAXNUMMP is?

We have ongoing intermittent problems with Oracle TDP and Windows
backups.
 Here's a typical error:

ORA-19511: Error received from media manager layer, error text:
   ANS0326E (RC41)   This node has exceeded its maximum number of mount
points.

When this first started happening (after we upgraded to TSM 5.3), I set
MAXNUMMP to the number of tape drives, but that turned out to be A Very
Bad Thing (though I forget why).  Now we bump up the MAXNUMMP number by
one each night that a backup fails until we get a number that works. 
Surely someone can give me a formula that will take me directly to the
right value.

Actually, I don't understand why these backups are calling for multiple
drives anyway.  They're routine Oracle log backups that happen many
times a day and run successfully 99.9% of the time.  Similarly, the
Windows backups are routine nightly backups.  I'm not trying to stream
to multiple tapes.  Why shouldn't MAXNUMMP=1 do the job?

Our environment is TSM server 5.3.3.0 running on AIX 5.3 at ML04 on a
p550.  We have 8 T10K drives in an STK SL8500 library.  The Oracle TDPs
are mostly on Sun boxes and the Windows boxes are a variety of Redmond
versions (though the errors aren't specific to any version).  We have
upgraded the TSM clients to the bleeding edge and still see these
errors.

Thanks for any help and for all I've learned in this forum, anker
_____________________________________________________________

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_____________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>