Author: Daniel Swan/TM <Daniel.Swan AT TELUS DOT COM>
Date: Thu, 13 Jul 2000 16:03:30 -0700
As mentioned previously, I'm an ADSM newbie taking over the ADSM of a regional company. There have been ongoing problems with our offsite-tape rotation. Since I've taken over, I've put in 110 tapes,
Dan, There were several versions of server code that did not expire data as it should so check with TSM support. Also check for tapes in filling status. If you have quite a few tapes in filling statu
Author: "Thomas A. La Porte" <tlaporte AT ANIM.DREAMWORKS DOT COM>
Date: Thu, 13 Jul 2000 17:11:29 -0700
The first thing that I would do is look through your activity log and see when and why scratch tapes are being defined into your storage pools. Collocation is a common reason for swallowing up loads
Definitely verify that ADSM is expiring your backup/archive data properly. I upgraded to 3.1.2.50 to solve a Netware long file name support problem and now I have an expiration problem which has resu
look into "filling" tapes... "q vol stg=xxxxx status=filling" if collocation is turned on there will be as many "filling" tapes as there are nodes (if scratch tapes are available). You might have bee
Author: "Taylor, Damon M" <taylordm AT BP DOT COM>
Date: Fri, 14 Jul 2000 06:51:14 -0500
Add the following to your query command "q vol access='reado,unavailable,destroyed' You probably haven't lost all your scratch tapes to these 'statuses' but it's a little more complete than just 'rea
Author: Rick Marshall <Richard.Marshall AT BMO DOT COM>
Date: Fri, 14 Jul 2000 08:28:53 -0400
Check the value of Reusedelay parm in your tape storage pool(s). This tells the TSM server how many days to wait after a tape becomes empty before it is returned to the scratch pool for reuse. The de
Author: "Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>
Date: Fri, 14 Jul 2000 10:09:26 -0400
And the way to stop it is to set a MAXSCRATCH value for the storage pool. That will make ADSM collocate the data (i.e., put all today's incoming data for a client on the same tape it used yesterday f
Author: Nick Cassimatis <nickpc AT US.IBM DOT COM>
Date: Fri, 14 Jul 2000 10:23:52 -0400
When you put the new tapes in, did you label them? If you didn't, the tapes aren't usable to ADSM. When I first started with ADSM, I was told to make sure the tapes (3590's) had labels on them. Well,
Author: James SPORER <james.sporer AT CCMAIL.ADP.WISC DOT EDU>
Date: Fri, 14 Jul 2000 09:49:41 -0500
If colocation is causing this problem it might help to reduce the maximum scratch value for the storage pool. ADSM will then start using the filling tapes for multiple nodes. Jim Sporer look into "fi
Author: Daniel Swan/TM [mailto:Daniel.Swan AT TELUS DOT COM]
Date: Sun, 04 Oct 2015 17:29:33 -0500
As mentioned previously, I'm an ADSM newbie taking over the ADSM of a regional company. There have been ongoing problems with our offsite-tape rotation. Since I've taken over, I've put in 110 tapes,
Author: Daniel Swan/TM <Daniel.Swan AT TELUS DOT COM>
Date: Fri, 14 Jul 2000 15:40:29 -0700
Thank you everyone for your replies. The problem has been solved, but the information you have all provided is invaluable to me in understanding other potential issues I should investigate, or may en
Author: Joe Faracchio <brother AT SOCRATES.BERKELEY DOT EDU>
Date: Fri, 14 Jul 2000 16:27:12 -0700
We have recently discovered that our automated checkin script in perl is failing because of the drive availability issues. By default a checkin command uses checklabel=yes which requires a mount of t
Author: "Slaughter, Bill" <BillSlaughter AT TUPPERWARE DOT COM>
Date: Sat, 15 Jul 2000 09:16:51 -0400
I recently had a server that normally does not have many scratch tapes start to run out of tapes. I discovered 1 tape that was erroring doing the "Move Drmedia" and found (When I did the individual m