Hello,
Assuming for nodeX the "q occ nodex /filespace" output looks like this:
NODEX Bkup /filespace 5 NEWPOOL-COPY 1,047
278,526.2 278,526.2
NODEX Bkup /filespace 5 NEWPOOL 1,047
278,526.2 278,526.2
NODEX Bkup /filespace 5 OLDPOOL-COPY 986
262,209.0 262,205.9
1. Upd stgp OLDPOOL-COPY collocate=fi
2. move nodedata nodex fromstgpool=oldpool-copy fi=/filespace
This will move all data in the old copy pool for that filespace to its
own tape. After the process ends, run:
3. select volume_name from volumeusage where node_name='NODEX' and
copy_type='BACKUP' and filespace_name='/filespace' and
stgpool_name='OLDPOOL-COPY'
The volume(s) listed should contain data only for the filespace you
moved. Sanity check this with:
4. select distinct(node_name) from contents where volume_name='VOLXYZ'
5. del vol VOLXYZ discarddata=yes
Now q occ should show:
NODEX Bkup /filespace 5 NEWPOOL-COPY 1,047
278,526.2 278,526.2
NODEX Bkup /filespace 5 NEWPOOL 1,047
278,526.2 278,526.2
6. Upd stgp OLDPOOL-COPY collocate=no
(or whatever collocation was originally set to...)
This process is quite long winded and if your retention is only 30 days
(or whatever) its less effort to simply wait for the stuff to expire.
Cheers,
Paul.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Barnes, Kenny
Sent: Tuesday 05 October 2004 22:09
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Node data in wrong stgpool
We are not talking about any one client having a lot data, but rather
large number of clients with smaller filespaces that add up.
Thanks,
Kenny Barnes
Systems Analyst
GmacInsurance
336-770-8280
kenny.barnes AT gmacinsurnace DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, October 05, 2004 4:03 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Node data in wrong stgpool
You can't exactly do that, but you don't really have to.
If you do:
backup stgpool correctonsitepool correctoffsitecopypool
TSM will copy the data for that node to the desired offsite copy pool,
because TSM is happy to put a node's data in multiple copy pools.
Then you are covered for DR of that client, which is, after all, the
highest
priority.
I don't know any way to get rid of the stuff that is already in the
wrong
copy pool except to:
1) bring back the tapes and mark them readonly
2) MOVE NODEDATA to force TSM to put the data for that node on a new
copy
pool tape
3) delete the new copy pool tape with discarddata=yes
Unless you are talking about a client with HUGE amounts of data, it's
not
worth your time to bother with the delete.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Barnes, Kenny
Sent: Tuesday, October 05, 2004 3:44 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Node data in wrong stgpool
How can I delete data stored in the wrong off-site copy_pool for a
certain node? Move nodedata works for on-site copies, but I do not want
to move data for off-site copies. I would rather delete the data and
copy data from the correct on-site pool to correct off-site copy_pool.
Any help appreciated.
Kenny Barnes
Systems Analyst
GmacInsurance
336-770-8280
kenny.barnes AT gmacinsurnace DOT com
------------------------------------------------------------------------
----
----------------------------------------------------------------------
Note: The information contained in this message may be privileged and
confidential
and protected from disclosure. If the reader of this message is not the
intended recipient,
or an employee or agent responsible for delivering this message to the
intended recipient,
you are hereby notified that any dissemination, distribution or copying
of
this communication
is strictly prohibited. If you have received this communication in
error,
please notify us
immediately by replying to the message and deleting it from your
computer.
Thank you.
------------------------------------------------------------------------
----
----------------------------------------------------------------------
Any e-mail message from the European Central Bank (ECB) is sent in good faith
but shall neither be binding nor construed as constituting a commitment by the
ECB except where provided for in a written agreement.
This e-mail is intended only for the use of the recipient(s) named above. Any
unauthorised disclosure, use or dissemination, either in whole or in part, is
prohibited.
If you have received this e-mail in error, please notify the sender immediately
via e-mail and delete this e-mail from your system.
|
