ADSM-L

Re: TDP for MS SQL and cached storage pools

2004-01-30 14:04:03
Subject: Re: TDP for MS SQL and cached storage pools
From: Steve Schaub <Steve.Schaub AT HAWORTH DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 30 Jan 2004 14:03:39 -0500
Actually, based on my experience with TDP for Mail, I would guess that
Tim is right on.  We were forced to turn caching off on the diskpool
that we used for mail backups due to this "feature" in TSM-TDP (support
claims that this is not a bug and is working exactly as designed, they
just don't bother to let anyone know that caching is not an option with
TDP).

Apparantly TDP cant trust the calculation it does before sending,
therefor, it will not send if the %util in the diskpool meets the
requirement, rather than factoring in the %reclaimable.

Steve Schaub
Systems Engineer
Haworth, Inc
616-393-1457 (desk)
616-886-8821 (cell phone)
6168868821 AT messaging.nextel DOT com (text page)
WWJWMTD


-----Original Message-----
From: Stapleton, Mark [mailto:stapleto AT BERBEE DOT COM] 
Sent: Friday, January 30, 2004 1:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TDP for MS SQL and cached storage pools


You've jumped to *way* too large a conclusion. This has nothing to do
with the disk storage pool, cached or otherwise.
 
You need to check the dsierror.log for API-related errors, and you also
need to check your error message against the listing for it in
http://people.bu.edu/rbs/ADSM.QuickFacts.
 
--
Mark Stapleton (stapleton AT berbee DOT com)

        -----Original Message----- 
        From: Tim Melly [mailto:tim.melly.b AT BAYER DOT COM] 
        Sent: Fri 1/30/2004 12:42 
        To: ADSM-L AT VM.MARIST DOT EDU 
        Cc: 
        Subject: TDP for MS SQL and cached storage pools
        
        

        To *,
        
        I'm getting the following error from an NT TSM client (v 5.1.6)
using TDP for MS
        SQL:
        
        01/23/2004 10:08:08 ACO5436E A failure occurred on stripe number
(0), rc = 418
        01/23/2004 10:08:08 ANS1311E (RC11)   Server out of data storage
space
        
        The TSM server (AIX 4.3.3 ML10, TSM 5.1.6) has sufficient
primary storage pool
        space (350 GB) to handle this backup request (70 GBs) but I'm
still getting the
        error. I'm using "disk caching" on my primary storage pool. Has
anyone
        encountered a situation where disk caching would cause an
incorrect calculation
        of available storage pool space???
        
        
        Regards, Tim
        NAFTA IS Technical Operations
        (203) 812-3469
        tim.melly.b AT bayer DOT com
        

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