im sorry to, i can see the problem.....no way
greetings
Joachim
-----Ursprüngliche Nachricht-----
Von: Warren, Matthew (Retail) [mailto:Matthew.Warren AT POWERGEN.CO DOT UK]
Gesendet: Mittwoch, 7. Januar 2004 13:44
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: delete a specific nodes data from a copy stg pool
Sorry Joachim, I'm not sure I follow what you mean.
The problem as far as I see it is this;
(from help move nodedata) if the source storage pool is a
copy storage pool the destination must be the same copy storage pool
As my source storage pool is a copy pool, the move nodedata
must move to volumes within that pool.
I was wondering if there are any alternate methods to
accomplishing the delete of the data.
-----Original Message-----
From: Schaub Joachim Paul ABX-SECE-ZH
<joachim.schaub AT ABRAXAS DOT CH>@EME
Sent: Wednesday, January 07, 2004 11:53 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: AW: delete a specific nodes data from a copy stg
pool
wrong storage pool type, take an sequential access storage
pool with the
device class you did prefer.
regards
joachim
-----Ursprüngliche Nachricht-----
Von: Warren, Matthew (Retail)
[mailto:Matthew.Warren AT POWERGEN.CO DOT UK]
Gesendet: Mittwoch, 7. Januar 2004 12:28
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: delete a specific nodes data from a copy stg
pool
That's what I've tried so far, but issuing the move nodedata
gives this
response;
ANR1719E Storage pool TEMP_DELPOOL specified on the MOVE
NODEDATA command is
not a valid pool name or pool type.
ANS8001I Return code 3.
And here are the definitions of the two copypools;
tsm: CARSINGTON>q stg uks_copy_phnx f=d
Storage Pool Name: UKS_COPY_PHNX
Storage Pool Type: Copy
Device Class Name: ULTRIUM_PHNX
Estimated Capacity (MB): 19,708,902.2
Pct Util: 18.4
Pct Migr:
Pct Logical: 99.3
High Mig Pct:
Low Mig Pct:
Migration Delay:
Migration Continue:
Migration Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold:
Access: Read/Write
Description: UKS_PHNX_COPYPOOL
Overflow Location:
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 50
Maximum Scratch Volumes Allowed: 100
Delay Period for Volume Reuse: 7 Day(s)
Migration in Progress?:
Amount Migrated (MB):
Elapsed Migration Time (seconds):
Reclamation in Progress?: No
Volume Being Migrated/Reclaimed:
Last Update by (administrator): REESCHR
Last Update Date/Time: 06/01/04 16:05:32
Storage Pool Data Format: Native
Copy Storage Pool(s):
Continue Copy on Error?:
CRC Data: No
tsm: CARSINGTON>q stg temp_delpool f=d
Storage Pool Name: TEMP_DELPOOL
Storage Pool Type: Copy
Device Class Name: ULTRIUM_PHNX
Estimated Capacity (MB): 0.0
Pct Util: 0.0
Pct Migr:
Pct Logical: 100.0
High Mig Pct:
Low Mig Pct:
Migration Delay:
Migration Continue:
Migration Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold:
Access: Read/Write
Description: Temp pool for node dta
deletes
Overflow Location:
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 100
Maximum Scratch Volumes Allowed: 999
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?:
Amount Migrated (MB):
Elapsed Migration Time (seconds):
Reclamation in Progress?: No
Volume Being Migrated/Reclaimed:
Last Update by (administrator): MATT
Last Update Date/Time: 07/01/04 10:54:31
Storage Pool Data Format: Native
Copy Storage Pool(s):
Continue Copy on Error?:
CRC Data: No
..And the section from help move nodedata talking about
copypool moves;
TOstgpool
Specifies the name of a storage pool to which data will be
moved. This
storage
pool must be in the NATIVE or NONBLOCK data format. This
parameter is
optional
and does not apply when the source storage pool is a copy
storage pool.
That
is, if the source storage pool is a copy storage pool the
destination must
be
the same copy storage pool. If a value is not specified,
data is moved to
other volumes within the source pool.
:/
Thanks,
Matt.
-----Original Message-----
From: Schaub Joachim Paul ABX-SECE-ZH
<joachim.schaub AT ABRAXAS DOT CH>@EME
Sent: Wednesday, January 07, 2004 11:21 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: AW: delete a specific nodes data
from a copy stg
pool
move node data to a backuppool (cart) with
the same dev
class as the
copypool has....
regards
joachim
-----Ursprüngliche Nachricht-----
Von: Warren, Matthew (Retail)
[mailto:Matthew.Warren AT POWERGEN.CO DOT UK]
Gesendet: Mittwoch, 7. Januar 2004 12:10
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: delete a specific nodes data from a
copy stg pool
Hi TSM'ers
I need to delete the data for a specific
node from a certain
copy pool.
Originally the following process was
occurring;
Turn co-location on for the pool
Move node data within the pool
Turn off co-location for the pool
Delete the written volumes discard=yes
Now, I thought I could do this instead;
Creat new copystg pool
Move node data from old copypool to new
copypool
Delete the volumes in the pool
Unfortunatley TSM doesn't let you move
nodedata from one
copy pool to
another.
Is the first method the most effective way
of achieving
this, or is
there a simpler / quicker / less fiddly way?
Thanks,
Matt.
___________________________ Disclaimer
Notice
__________________________
This message and any attachments are
confidential and should
only be read
by those to whom they are addressed. If you
are not the
intended recipient,
please contact us, delete the message from
your computer and
destroy any
copies. Any distribution or copying without
our prior
permission is
prohibited.
Internet communications are not always
secure and therefore
the Powergen
Group does not accept legal responsibility
for this message.
The recipient
is responsible for verifying its
authenticity before acting
on the
contents. Any views or opinions presented
are solely those
of the author
and do not necessarily represent those of
the Powergen
Group.
Registered addresses:
Powergen UK plc, 53 New Broad Street,
London, EC2M 1SL
Registered in England & Wales No. 2366970
Powergen Retail Limited, Westwood Way,
Westwood Business
Park,
Coventry CV4 8LG.
Registered in England and Wales No: 3407430
Telephone +44 (0) 2476 42 4000
Fax +44 (0) 2476 42 5432
|
