Ben Bullock wrote:
> This methodology has me really interested.
>
> I am about to try to move a 100GB AIX TSM database to another host. The
> disks are totally incompatible, so my option is a db backup and restore.
> I assumed I was going to have to disable all sessions, drain all the
> disk pools to the tapes, run a db backup, restore the db to the new
> host, recreate the diskpools and then let the customers in.
>
> On a 100 GB db on slow disks, I was thinking 6 hours or so of no
> customer access.
>
> Your suggestion of doing a db restore and then an incremental
> has me thinking.
>
> when you do the restore of the full DB backup to the new TSM
> server, do you just leave off the "commit=yes" option?
>
correct
> Then, once I have all the disk pools drained, I could do an
> incremental backup, run a DB restore of the incremental DBbackup on the
> new host with the "commit=yes" option and then I could bring up the new
> server?
>
correct.
> It should know that all the client data that is on the tapes,
> and know that the disk pools are empty when it comes up, right? So I
> should not need to audit any volumes.
>
I delete all diskpool volumes before the last incremental db backup, so
the are no diskvolumes. This allows you to resize them as you like as a
side-effect. On the new server in the preparation steps I use 'dsmfmt
-data' to prepare the new volumes, so adding them is quick once the new
server is up.
> Thanks,
> Ben
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Remco Post
> Sent: Wednesday, May 31, 2006 2:24 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Migrating TSM (5.3.2.0) to new Windows box
>
> Dennis, Melburn W IT743 wrote:
>> Our old TSM server is EOL and we are replacing it with a new one.
>> They are both W2K3. What is the safest/best way to migrate? I was
>> planning on installing TSM on the new box and then using a recent
>> database copy on tape to restore the db on the new box using a point
>> in time restore (since the log volumes will not be on the new box).
>> Is this a valid way to do this? Am I missing something?
>>
>
> what I've done just yesterday is:
>
> on the new box:
> format log and db volumes
> restore most recent full dbbackup
> copy over start/stop scripts and dsmserv.opt
>
> old server:
> stop and start with 'DISABLESCHEDS YES' and 'NOMIGRRECL' in dsmserv.opt
> disable sessions empty out all disk and file volumes delete them all
> make incremental dbbackup halt old server
>
> new server:
> retore incermental on new box (commit=yes) start tsm on the new box
> recreate disk and file volumes
>
> We usually only do full dbbackups, so I had no intermediate
> incrementals...
>
> If you empty out all you disk/file volumes before you restart your
> server, your downtime might be as short as one incremental backup and
> one incremental resore, minutes....
>
>
>> Mel Dennis
>> Systems Engineer - IT743
>> Siemens Power Generation
>> 4400 Alafaya Trail
>> Orlando, FL 32826
>> MC Q1-108
>> Tel: (407) 736-2360
>> Win: 439-2360
>> Fax: (407) 243-0260
>> Email: melburn.dennis AT siemens DOT com
>
>
> --
> Met vriendelijke groeten,
>
> Remco Post
>
> SARA - Reken- en Netwerkdiensten http://www.sara.nl
> High Performance Computing Tel. +31 20 592 3000 Fax. +31 20 668 3167
> PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC
>
> "I really didn't foresee the Internet. But then, neither did the
> computer industry. Not that that tells us very much of course - the
> computer industry didn't even foresee that the century was going to
> end." -- Douglas Adams
--
Met vriendelijke groeten,
Remco Post
SARA - Reken- en Netwerkdiensten http://www.sara.nl
High Performance Computing Tel. +31 20 592 3000 Fax. +31 20 668 3167
PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC
"I really didn't foresee the Internet. But then, neither did the
computer industry. Not that that tells us very much of course - the
computer industry didn't even foresee that the century was going to
end." -- Douglas Adams
|
