Excellent, thanks. If I try to move nodedata before the new diskpool is in
place, which would have migrated off to the new tapepool, will the node have
issues after it's backup when it tries to migrate data to the tapepool I am
moving it off of?
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andy Huebner
Sent: Thursday, July 12, 2007 2:45 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] separation of copypool tapes
When we move single nodes to balance the pools, we run this query to
locate tapes with the moved node's data and delete them a few at a time
allowing backup storage pool to recreate the tapes with the correct
data.
select distinct volume_name from volumeusage where stgpool_name =
'Copy_Pool' and node_name = 'NODE_ABC'
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 12, 2007 2:15 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] separation of copypool tapes
Deleting all of my copypool volumes could be a problem since I am only
moving half of the tapepool data and have over 600 copypool tapes. I
will need to find a better way to remove the data. Thanks for the answer
about the data still being there, I wasn't sure how that would work.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Andy Huebner
Sent: Thursday, July 12, 2007 2:01 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] separation of copypool tapes
When we rearranged our tape pools, we did a move node. We did not look
for a way to move the tape because we where changing tape technology.
Recreating the copy pool is easy; a backup storage pool to a new copy
pool will work fine. Beware that the data will remain in the old copy
pool, to fix this you will need to delete the copy pool volumes. We
moved all of the nodes and deleted every volume in the copy pool (about
1000 tapes) and let backup storage pool create new volumes. (about 50
tapes)
Andy Huebner
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 12, 2007 1:02 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] separation of copypool tapes
We have a large database, 170Gb and are proposing to our customer that
it be separated into multiple servers. Unfortunately when the system
was designed, more than half of the nodes were directed to the same
tapepool and copypool. The tapepool is collocated by node, the copypool
is not. Before migration, I would like to setup new disk,tape and copy
pools and split the nodes so they can be easily moved to the new servers
since multiple servers cannot own the same tape (the library will be
shared). It is easy enough to change the diskpool and write new data to
the new tape/copypools, but I have a couple questions about the tapepool
and copypool moves of the old data.
Is there an easy way to move the tapepool tapes to a new tapepool or do
I need to use the move nodedata commands. I can't rename them since not
all of the nodes currently in a pool will be on the same server. I also
don't see an update volume command that would allow me to change the
pool name.
Second, once I have the data on the new tapepool tapes, can I simply
run a backup tapepool to the new copypool or do I need to do a move
nodedata specifying the old copypool to new copypool. If I do a backup
of the new tapepool, what happens to the data currently on the existing
copypool, does it disappear or do I need to delete it. Thanks.
Debbie Haberstroh
Server Administration
Northrop Grumman Information Technology
Commercial, State & Local (CSL)
This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments. If you have received this e-mail in error, please
notify the sender immediately by return e-mail and delete all copies of
this message and any attachments.
Thank you.
This e-mail (including any attachments) is confidential and may be legally
privileged. If you are not an intended recipient or an authorized
representative of an intended recipient, you are prohibited from using, copying
or distributing the information in this e-mail or its attachments. If you have
received this e-mail in error, please notify the sender immediately by return
e-mail and delete all copies of this message and any attachments.
Thank you.
|
