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) [EMAIL PROTECTED] (text page) WWJWMTD -----Original Message----- From: Stapleton, Mark [mailto:[EMAIL PROTECTED] Sent: Friday, January 30, 2004 1:57 PM To: [EMAIL PROTECTED] 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 ([EMAIL PROTECTED]) -----Original Message----- From: Tim Melly [mailto:[EMAIL PROTECTED] Sent: Fri 1/30/2004 12:42 To: [EMAIL PROTECTED] 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 [EMAIL PROTECTED]
