As I understood your question you're talking about copypool volumes
(sending primary pool volumes off-site is not an option).
But maybe you are missing that any operations (MOVE DATA and reclamation)
on copy pool volumes is performed using primary pool copies. So when you
try to move data files are taken from primary pools and if those pools are
not collocated you will need to mount several tapes.
Zlatko Krastev
IT Consultant
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: ADSM sees 'readwrite' as 'offsite'
ADSM Smart People,
AIX: 4.3.2
ADSM: 3.1.2.1 (I know it's old, but we are upgrading!)
======================================================
I have an ongoing problem that I haven't found the
solution to in the ADSM archives.
I will bring a volume onsite, will set that volume
acc=readw (from 'offsite'). So far, so good. However,
when I attempt to move data from that volume to another,
ADSM continues to see it as 'offsite' (even though if
I do: 'q vo acc=readw', the volume will show up in the
list AND if I do: 'q vo acc=offsite', the volume will
NOT show up in that list).
Consequently, in order to do a 'move data', multiple tape
mounts are usually required (from the primary pool)--sometimes
as many as 30 or more tapes to empty the data from one volume!.
This happens to about 1/3 of the volumes I bring onsite.
Obviously, it gets very painful after a while, and I would
love to know if there is a workaround for this little 'problem'.
Thanks.
Jim
Jim Coen
[EMAIL PROTECTED]
Manager, Application Software Services
ADSM Administrator
Listserv Administrator/News Administrator
================================ <>< ================================
Information Technology Services Washburn University
785-231-1010 Ext 2304 Topeka, KS 66621
Wisdom has two parts: 1) Having a lot to say
2) Not saying it
