Hi
Have you considered using migrate to move the data, or is the storagepool
containing data that you don't want to move? Else if, you could set your
new storagepool as the next storage pool for the old one, and then lower
the hi/lo to 0/0, and the migrate process would automatically move the
data to the new storagepool.
If you are using collocation, you could also use move data vol name to
move the data from one storagepool to another.
With TSM 5.1, you have move node data command, which would make it
possible to move the archive data for particular nodes to another storage
pool.
Best Regards
Daniel Sparrman
---
Daniel Sparrman
Exist i Stockholm AB
Propellervägen 6B
183 62 HÄGERNÄS
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
chris rees [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
2002-04-29 14:38
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:please advise best procedure..export/import
Hi
Could you tell me if there is a better way to achieve the following.
Basically we had a period where archive data was going to the wrong
storage
pools. The archive copygroup setting has now been fixed but I have archive
data that I want to move to the archive storage pools. To get the archive
data into the correct storage pools I an planning to do the following
1) export node A filedata=archive devclass=3590class
2) delete filespace A * type=archive
3) import node A domain=samsp filedata=archive devclass=3590class
dates=absolute vol=volume names
I presume the import will look at the copygroup settings and put the
archive
data into the correct storage pool.
Any hints/tips greatly appreciated
Chris
_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
