Ruichard, I tried the SQL query below that you gave, but got an error "where status='filling'" at the '=' bit
Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Richard Sims Sent: 05 March 2005 19:44 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] LTO Volume Akash - I term this "Tape leak", as I summarize in http://people.bu.edu/rbs/ADSM.QuickFacts . We had a good discussion of this about 6 months ago on ADSM-L. One member was pursuing it with IBM as a problem. For administration at my site, I created a macro called "filling", which does the following: SELECT STGPOOL_NAME AS " STORAGE POOL ", CHAR(VOLUME_NAME,6) AS "VOLNAME", PCT_UTILIZED as "PCT UTIL", DEC(EST_CAPACITY_MB,6) AS "MB_CAPACITY", CHAR(ACCESS,11) AS "ACCESS", LEFT(CHAR(LAST_WRITE_DATE),19) AS "LAST_WRITE_DATE " FROM VOLUMES WHERE STATUS='FILLING' ORDER BY STGPOOL_NAME This is handy for monitoring tapes which are in Filling state, and also watching for tapes which become Readonly due to events occurring as they are filling. Richard Sims On Mar 5, 2005, at 12:27 PM, Akash Jain wrote: > Hi experts, > > I have one simple query. > > While taking backups on LTO through, it occupies new LTO volume only > after the used and in process volume will display status as 'FULL'. > > But in my case I had observed that it had started taking backup on > other LTO volume in spite of the previous one in 'FILLING' status. > > BTO557 TAPEPOOL LTOCLASS 528,305.3 100.0 > Filling > BT0558 TAPEPOOL LTOCLASS 200,000.0 15.5 > Filling > > Kindly provide the logical reasoning if any for the same. > > > Regards > Akash
