ADSM-L

[ADSM-L] AW: Replicate Node design change?

2014-05-01 17:14:56
Subject: [ADSM-L] AW: Replicate Node design change?
From: Michael malitz <michael.malitz AT MM-IT DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 1 May 2014 23:12:55 +0200
Hallo Harald,

Have a try (and test)  the following procedure....

1.)  on S2 SRS:   q replnode *  --> to find out all relevant nodes
2.)  on S3 TRS:   remove replnode  nodes,group   --> convert nodes to target
and as result change replstate and replmode to none
3.)  on S3 TRS:   remove replserver GUID-of SRS-S2 
4.)  on S2 SRS:   remove replserver GUID-of TRS-S3
5.)  on S2 SRS:  set replserver New-TRS-S4
6.)  on S3 TRS/and new S4 TRS:  export nodes from S3 / import to S4 with
dates=absolute(=default anyway)
7.)  on S2 SRS:   remove replnode  nodes,group   --> convert nodes on
SOURCE-SRS as well so that replstate and replmode are changed to none and
next update command is possible!!
8.)  on S2 SRS:   update  node <node> replstate=enabled   replmode=syncsend
9.)  on S4 new TRS:   update  node <node> replstate=enabled
replmode=syncreceive
10.) on S2 SRS:  replicate node <node>  (and may be check other parameters
before like maxsessions etc.)

--> check the results (and let us know pls)


Good luck and best regards Michael

Michael Malitz
Michael.Malitz AT tsmpoweradmin DOT com
Tel.:  +43 (0) 664 1415275


-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag von
Vandeventer, Harold [BS]
Gesendet: Donnerstag, 1. Mai 2014 16:01
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Replicate Node design change?

I've setup node replication from two servers (S1 and S2) toward a single
target server (S3) off-site.  A bit of latency; but it's been working fine.

I've been granted permission to build another TSM server (S4) at the target
site.

I'd like to re-work my replication design so that S2 pushes to S4 (the new
server).

Is it possible to do something like this:

1.       Cease replication for nodes on S2.  (a simple commenting of script
commands)

2.       EXPORT selected nodes from S3 to S4.

3.       When all export done, define S4 as the replication destination from
S2.

4.       Re-enable replication from S2, now pushing to S4, by un-commenting
script commands).

The goal is to use the new server as a replication target, but avoid pushing
all that data across the WAN link again.

------------------------------------------------------------
Harold Vandeventer
Systems Programmer
State of Kansas - Office of Information Technology Services STE 751-S
910 SW Jackson
(785) 296-0631


[Confidentiality notice:]
***********************************************************************
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential or
privileged information.  Any unauthorized review, use, or disclosure is
prohibited.  If you are not the intended recipient, please contact the
sender and destroy the original message, including all copies, Thank you.
***********************************************************************

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