ADSM-L

Re: [ADSM-L] tsm v6 DR server setup

2013-08-15 14:15:03
Subject: Re: [ADSM-L] tsm v6 DR server setup
From: Remco Post <r.post AT PLCS DOT NL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Aug 2013 20:13:07 +0200
I prefer to not use dsmicfgx (IBM, can we please have a CLI version!), but set 
up the TSM server manually. On the dr site you can then run dsmserv loadformat 
in stead of dsmserv format. If you choose to use dsmicfgx, (which does do a few 
nice things for you), you can then 'su - tsmsrvr1' (or whatever your instance 
user is called), run 'dsmserv loadformat' and restore the prod db after you've 
copied over the volhist and devconf. I've even done a restore without the 
loadformat IIRC, and never had any problems.
 
Op 15 aug. 2013, om 19:52 heeft Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT 
COM> het volgende geschreven:

> what/How do you get a stand alone DR server set up for TSM v6 and DB2?
> 
> We are setting up our first TSM v6 server (aix).  It's up and running.
> At a second site we have a dedicated DR server (aix) for this TSM
> instance.
> I'm not sure what I need to do.
> 
> I ran install.bin which dumped the TSM and DB2 binaries onto the system.
> I have all the filesystems created, user/group created, permissions set,
> etc.
> I'm ready to run the dsmicfgx.
> I can run this all the way to completion and have a running TSM instance.
> Is this what I should do?
> If I do that, what do I do to get the box ready for the DR restore?  Do I
> delete the contents of the db2 filesystems?
> 
> Any help is appreciated.
> 
> Thanks
> 
> Rick
> 
> 
> 
> 
> -----------------------------------------
> 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.

<Prev in Thread] Current Thread [Next in Thread>