ADSM-L

Re: [ADSM-L] Reclamation of Virtual Tapes

2012-12-18 15:43:25
Subject: Re: [ADSM-L] Reclamation of Virtual Tapes
From: "Ehresman,David E." <deehre01 AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 18 Dec 2012 20:37:57 +0000
We reclaim our virtual tapes.  They have the same waste patterns as physical 
tape and are certainly as expensive.

David

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Lee, Gary
Sent: Tuesday, December 18, 2012 2:10 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Reclamation of Virtual Tapes

Sounds like someone set the reclaim storage pool on the virtual tape pool to 
the physical tape pool.

I know of no reason why not to reclaim virtual tapes.

Wish I had one to play with.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Welton, Charles
Sent: Tuesday, December 18, 2012 11:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Reclamation of Virtual Tapes

Hello:

We have a TSM instance that uses virtual tapes as our primary backup data pool. 
 The data on the virtual tapes are eventually migrated to tape.  We are 
currently down to 3 virtual scratch tapes and 6 physical scratch tapes.  I 
noticed that we are not running any reclamation processes on our virtual tape 
pool.  It seems we have a hand-full of under-utilized virtual tapes.  I went 
ahead and ran a manual reclamation on the virtual tape pool and I noticed the 
output tape pool is a physical tape.  I assumed that the virtual tape would 
reclaim to another virtual tape.  Is that not the case?

Could there be a reason why reclamation shouldn't be ran on a virtual tape pool?

Thank you...


Charles

This email contains information which may be PROPRIETARY IN NATURE OR OTHERWISE 
PROTECTED BY LAW FROM DISCLOSURE and is intended only for the use of the 
addresses(s) named above.  If you have received this email in error, please 
contact the sender immediately.

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