I agree !
I've moved environments all around and unless you can detatch the disks and
put them on the new environment and import the volume group (which would be
hard on NT :-/ ) You are best off in doing just that... clear the volumes,
delete them, then add in new ones in your new environment. Sure if you
don't delete them in the old environment they won't be there in the new and
they won't come online but you might end up where I am and have volumes you
can't delete :-(
In case you have a lot of storage pool volumes, you can create macro's to do
update the vols reado, do move data's (to clear cached files if need be),
and then delete the volumes... in your new environment you may also set up a
macro with all your new volumes to be assigned... this way if you are
pressed with time you just issue a macro and all is done !
I did this when I recently moved 5 tsm environments to new equipment in a
new location...
Dwight
-----Original Message-----
From: Steven Chaba [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 04, 2001 9:45 AM
To: [EMAIL PROTECTED]
Subject: Moving to new hardware
One other item I forgot to mention: I laid out different logical volumes for
my
disk pools, with different sizes and such on the new server. The test copy
of
the database didn't seem too happy with that, even though they had the same
names, so before I did the final move of the database and logs, I migrated
all
the data off the disk pools and deleted all the disk volumes, then defined
the
new ones where I wanted them on the new server.
Date: Tue, 3 Apr 2001 12:43:09 -0400
From: Tomas Hallin <[EMAIL PROTECTED]>
Subject: Moving to new hardware
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
People,
we have now outgrown our NT ADSM server and need to move to new
hardware. Could anyone with experience in doing this recommend the
best way to do so? Is EXPORT SERVER the way to go?
thanks,
/Tomas
Tomas Hallin
Affinity Technology Group
Columbia, SC
