The backup job is setup to run 4 sessions and the system is limited to 8 mount points.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Maurice van 't Loo Sent: Saturday, November 17, 2012 3:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] HP/UX SAP backup Sometimes a new tape is requested while the full tape is not completly dismounted. So you can try to use a higher maximum number of mountpoints in the node definition. TDP`s can give a no space available when there are not enough mountpoints available. Regards, Maurice van `t Loo http://mvantloo.nl Op 16 nov. 2012 16:13 schreef "Richard Rhodes" <rrho...@firstenergycorp.com> het volgende: > One thing would be if you hit the max scratch setting on your pools. > That's the common thing we hit when we that the " no space available " > messge. > > Rick > > > > > > From: "Huebner, Andy" <andy.hueb...@alcon.com> > To: ADSM-L@VM.MARIST.EDU > Date: 11/15/2012 03:57 PM > Subject: HP/UX SAP backup > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > I am trying to get SAP LAN free backups working. Everything seems > fine until it reaches the end of a tape, then we get : > 11/14/2012 12:50:10 ANR0522W (Session: 189263, Origin: HP-SAP) > Transaction failed for session 63740 for node > HP-SAP (TDP R3 HP) - no space available in storage > pool DB_D_VIRTP_09 and all successor pools. > (SESSION: > 189263) > > We have looked at everything we can think of with no luck. The backup > will not go to the next tape. Does anyone have any ideas on what I am > missing? > > AIX 6.1 > TSM version 5.4.6.2 (built just for this) HP/UX 11.11 (cannot be > upgraded) Storage Agent 5.4.6.2 (newest available) DataDomain VTL - > LTO1 tape drives. > > We have tried 1 - 8 mount points. It will fill the first tapes then > will fail to mount any more tapes. > > We are not out of space in the pool: > tsm: TSMServer>q stg db_d_virtp_09 f=d > > Storage Pool Name: DB_D_VIRTP_09 > Storage Pool Type: Primary > Device Class Name: LTO-5 > Estimated Capacity: 204,800 G > Space Trigger Util: > Pct Util: 0.1 > Pct Migr: 0.1 > Pct Logical: 100.0 > High Mig Pct: 90 > Low Mig Pct: 70 > Migration Delay: 0 > Migration Continue: Yes > Migration Processes: 1 > Reclamation Processes: 1 > Next Storage Pool: > Reclaim Storage Pool: > Maximum Size Threshold: No Limit > Access: Read/Write > Description: > Overflow Location: > Cache Migrated Files?: > Collocate?: No > Reclamation Threshold: 60 > Offsite Reclamation Limit: > Maximum Scratch Volumes Allowed: 1,000 > Number of Scratch Volumes Used: 1 > Delay Period for Volume Reuse: 0 Day(s) > Migration in Progress?: No > Amount Migrated (MB): 0.00 Elapsed Migration Time > (seconds): 0 > Reclamation in Progress?: No > Last Update by (administrator): ANDY > Last Update Date/Time: 11/15/2012 09:03:03 > Storage Pool Data Format: Native > Copy Storage Pool(s): > Active Data Pool(s): > Continue Copy on Error?: Yes > CRC Data: No > Reclamation Type: Threshold > Overwrite Data when Deleted: > > show sspool > -> Pool DB_D_VIRTP_09(76): Strategy=30, ClassId=2, ClassName=LTO-5, > Next=0, ReclaimPool=0, HighMig=90, LowMig=70, MigProcess=1, > Access=0, > MaxSize=0, Cache=0, Collocate=0, Reclaim=60, MaxScratch=1000, > ReuseDelay=0, crcData=False, verifyData=True, > ReclaimProcess=1, OffsiteReclaimLimit=NoLimit, ReclamationType=0 > Index=11, OpenCount=0, CreatePending=False, DeletePending=False > CopyPoolCount=0, CopyPoolIdList=, CopyContinue=Yes > Shreddable=False, shredCount=0 > AS Extension: NumDefVols=1, NumEmptyVols=0, > NumScratchVols=1, NumRsvdScratch=0 > > > > Andy Huebner > > > > > > > ----------------------------------------- > The information contained in this message is intended only for the > personal and confidential use of the recipient(s) named above. If the > reader of this message is not the intended recipient or an agent > responsible for delivering it to the intended recipient, you are > hereby notified that you have received this document in error and that > any review, dissemination, distribution, or copying of this message is > strictly prohibited. If you have received this communication in error, > please notify us immediately, and delete the original message. >
