I already performed the move data from the primary pool to another primary
pool. I guess TSM cant figure out that the primary copies are in a
different primary storage pool than where they were origianlly backed up
from.
A "DELETE FILES node filespace STG=stgpool" sure would be nice....or a
"DELETE NODEDATA STG=stgpool"..... (sigh)
Dave Nicholson
Whirlpool Corporation
"Stapleton, Mark" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
06/09/2004 10:44 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Hey Big Blue....Why not MOVE DATA across copy pools?!?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of David Nicholson
> I tried a MOVE DATA for offsite data...it did not go after the
>data in the primary pool...it wanted to mount the volume in the copy
>pool...which was offsite.
> Am I missing something?
Something is wrong. MOVE DATA will only call for offsite volumes if the
required files are not available in the primary pool. Do you have
volumes in unavailable status?
--
Mark Stapleton
