Re: [ADSM-L] reclamation question
2011-04-12 08:42:06
That sounds interesting, I might need to give that a shot.
thanks
David Tyree
Interface Analyst
South Georgia Medical Center
229.333.1155
Confidential Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Prather, Wanda
Sent: Monday, April 11, 2011 1:38 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] reclamation question
Or just mark them offsite, even though they are still in the library.
You could create a script that does "update vol * wherestgpool=onsitecopy
access=offsite" before you start reclamation, then reverse it when reclamation
finishes.
W
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Lee, Gary D.
Sent: Monday, April 11, 2011 1:26 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] reclamation question
About the only way I can think of to do this is to mark the onsite copy pool
volumes as unavailable. This would force data to be pulled from the primary
file pool.
The reason it does this for the offsite pool, is that offsite volumes are
presumed to be unavailable, thus data must be pulled from the primary source.
Hope this helps.
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
Tyree, David
Sent: Monday, April 11, 2011 12:54 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] reclamation question
We have three storage pools, the primary pool is a devtype FILE
and the two copy pools are devtype LTO3. The offsite copy pools gets
transferred offsite via DRM.
Whenever I run a reclamation on the offsite copy pool the
system grabs a scratch tape and then copies files from the primary pool and
starts filling up tapes. I'm perfectly happy with that process.
I have an issue when I do the reclamation of onsite tapes. It
loads up a tape (might be scratch) and then another tape to copy the data from.
It ends up doing a tape to tape copy. In a way it uses twice as many tape
mounts as an offsite reclamation. And since I only have 6 drives it kinda
cramps up my options sometimes.
Is there a way to do a reclamation of the onsite copy pool and
have it pull data from the primary pool instead of doing a tape to tape copy? I
mean it can do it for the offsite pool, why not the onsite as well?
David Tyree
Interface Analyst
South Georgia Medical Center
229.333.1155
Confidential Notice: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
|
|
|