db2
----- Original Message -----
From: "Richard Rhodes" <[EMAIL PROTECTED]>
To: <ADSM-L@VM.MARIST.EDU>
Sent: Friday, February 08, 2008 7:21 AM
Subject: Re: [ADSM-L] migrateing .9TB of data
What kind of data is it?
If mostly static files, we like to use rdist (robocopy on windows). Run
it
every so often, then a final run at cutover. You can multiple parallel
cmds
if need be.
If a database you can use a backup/restore with rollinig logs (at least
for
oracle). We have moved Multi TB Oracle databases this way with only a few
min of downtime at cutover.
In general, a TSm backup/restore is about the last thing we look at to
migrate servers. It's usually too big of an outage.
Rick
Larry Clark
<[EMAIL PROTECTED]
R.COM> To
Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> migrateing .9TB of data
02/07/2008 06:13
PM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
Currently I am migrating servers for a customer. In all instances but one
I
am using a combination of mksysb and sysback on uservgs to do this.
One node has .9TB of data, however and would take too long using sysback.
Someone has suggested using TSM. Can the client node be exported to tape
and
imported on a TSM server at the target site?
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
