Have you tried to lower the number of processes to 3 or increase it to 5
to see how they end up picking volumes? If it goes away in 3 and you
get two CDLPOOL output volumes, that could mean a silly limitation
somebody left in. However, if it's always 1, whether 2, 3, or 9,
there's still something misprogrammed -- just somethingdifferent.
If it goes away with 3, workaround discovered and contact IBM to yell
at.
I'm assuming it's reliably picking 3 and 1.
Many thanks!
Bruce
--
Bruce T. Harvey
UNIX System Administrator, SAIC | DHS/ICE OCIO
1120 Vermont Ave, Suite 300, Washington, DC 20005
202.261.9589 (office) - 202.465.9537 (cell) | harveyb AT saic-dc DOT com
| -----Original Message-----
| From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
Of
| Wanda Prather
| Sent: Wednesday, January 06, 2010 11:52 AM
| To: ADSM-L AT VM.MARIST DOT EDU
| Subject: [ADSM-L] Migration choosing output volume in the SAME POOL?!?
|
| Oh, my head hurts.
| Haven't seen this before.
|
| TSM server AIX 5.5.2 with no disk pool.
| Clients back up to a VTL (which is an EMC CDL)
| The VTL migrates to an LTO tape pool.
|
| So the data flow is
| clients => CDLPOOL => TAPEPOOL
|
| CDLPOOL has MIGPROCESS=4
|
| MIGRATE STGPOOL CDLPOOL kicks of 4 migration processes, as one would
| expect.
|
| Except 3 of the processes choose a CDLPOOL volume as the input volume,
and
| an LTO2 TAPEPOOL volume as the output volume.
| The 4th process chooses a CDLPOOL volume as the input volume, AND
chooses
| a
| CDLPOOL volume as the OUTPUT volume.
|
| WHAT circumstance causes migration to choose an output volume in the
SAME
| POOL as the input volume?
| .
|
| W
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
|
