Daniel,
Ok, so you are saying that by changing the replication target of an
instance you also change the replication key, why would you want that to
happen with the same command, it seems a bit odd but ok.
I tried it (it's a lab setup anyway), I also gave the command at the
tsm63node3 server but then used a different target and it does not appear
to work, I still get the same message ;
11/08/2011 12:03:48 ANR2017I Administrator ADMIN issued command: SET
REPLSERVER tsm63node3 (SESSION: 281)
11/08/2011 12:03:48 ANR1634I Default replication server name set to
TSM63NODE3. (SESSION: 281)
11/08/2011 12:03:48 ANR0405I Session 281 ended for administrator ADMIN
(WinNT). (SESSION: 281)
11/08/2011 12:03:52 ANR0407I Session 282 started for administrator ADMIN
(WinNT) (Tcp/Ip 172.28.15.16(3564)). (SESSION: 282)
11/08/2011 12:03:52 ANR2017I Administrator ADMIN issued command: REPLICATE
NODE REPGROUP01 (SESSION: 282)
11/08/2011 12:03:52 ANR0984I Process 10 for Replicate Node started in the
BACKGROUND at 12:03:52 PM. (SESSION: 282, PROCESS:
10)
11/08/2011 12:03:52 ANR2110I REPLICATE NODE started as process 10.
(SESSION:
282, PROCESS: 10)
11/08/2011 12:03:52 ANR0405I Session 282 ended for administrator ADMIN
(WinNT). (SESSION: 282)
11/08/2011 12:03:52 ANR0408I Session 283 started for server TSM63NODE3
(Linux/x86_64) (Tcp/Ip) for replication. (SESSION:
282,
PROCESS: 10)
11/08/2011 12:03:52 ANR3181E Replication server TSM63NODE3 has the same
replication key as this server. (SESSION: 282,
PROCESS:
10)
11/08/2011 12:03:52 ANR0409I Session 283 ended for server TSM63NODE3
(Linux/x86_64). (SESSION: 282, PROCESS: 10)
11/08/2011 12:03:52 ANR3179E Server TSM63NODE3 does not support
replication or is not initialized for replication.
(SESSION: 282,
PROCESS: 10)
11/08/2011 12:03:52 ANR0327I Replication of node LOADGEN completed. Files
current: 0. Files replicated: 0 of 0. Files updated:
0 of
0. Files deleted: 0 of 0. Amount replicated: 0 KB of
0
KB. Amount transferred: 0 KB. Elapsed time: 0 Day(s),
0
Hour(s), 0 Minute(s). (SESSION: 282, PROCESS: 10)
11/08/2011 12:03:52 ANR0985I Process 10 for Replicate Node running in the
BACKGROUND completed with completion state FAILURE at
12:03:52 PM. (SESSION: 282, PROCESS: 10)
11/08/2011 12:03:52 ANR1893E Process 10 for Replicate Node completed with
a
completion state of FAILURE. (SESSION: 282, PROCESS:
10)
11/08/2011 12:03:52 ANR0408I Session 284 started for server TSM63NODE3
(Linux/x86_64) (Tcp/Ip) for replication. (SESSION:
282)
11/08/2011 12:03:52 ANR3181E Replication server TSM63NODE3 has the same
replication key as this server. (SESSION: 282)
11/08/2011 12:03:52 ANR0409I Session 284 ended for server TSM63NODE3
(Linux/x86_64). (SESSION: 282)
On Tue, Nov 8, 2011 at 11:03 AM, Daniel Sparrman
<daniel.sparrman AT exist DOT se>wrote:
> Hi Stefan
>
> I assume that you have changed the TSM servername of the cloned TSM server
> to something else? And that you have registred the new name as a server on
> the old TSM server?
>
> In that case, you need to update the replication key by issuing the below
> command. This will also update the replication key. There is no command to
> just "set" the replication key.
>
> Regards
>
> Daniel Sparrman
>
>
> Daniel Sparrman
> Exist i Stockholm AB
> Växel: 08-754 98 00
> Fax: 08-754 97 30
> daniel.sparrman AT exist DOT se
> http://www.existgruppen.se
> Posthusgatan 1 761 30 NORRTÄLJE
>
> -----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> skrev: -----
> Till: ADSM-L AT VM.MARIST DOT EDU
> Från: Stefan Folkerts
> Sänt av: "ADSM: Dist Stor Manager"
> Datum: 11/08/2011 10:57
> Ärende: Re: Ang: [ADSM-L] ANR3181E: Replication server server name has the
> same replication key as this server.
>
> This is only valid if you defined the source as the replication target,
> this doesn't update the replication key of the TSM server but changes the
> replication server to a new target server..I don't want to to do this.
>
> Because I cloned the VM the whole TSM configuration is copied including
> something new..the replication key, I can't find a command or setting to
> change this, I'm hoping it's not generated at install and fixed because
> that would break the ability to clone TSM servers on a VM level.
>
>
> On Tue, Nov 8, 2011 at 10:38 AM, Daniel Sparrman
> <daniel.sparrman AT exist DOT se>wrote:
>
> > ANR3181E: Replication server server name has the same replication key as
> > this server.
> > Explanation During replication initialization, the server detected that
> > the replication key of the target server is the same as this server. Each
> > server must have a unique replication key.
> >
> > System action Replication to the specified server is stopped.
> >
> > User response Issue the SET REPLSERVER command to specify a different
> > server for the target of the replication.
> >
> >
> >
> > Parent topic: Version 6.3.0 ANR messages
> >
> >
> > Daniel Sparrman
> > Exist i Stockholm AB
> > Växel: 08-754 98 00
> > Fax: 08-754 97 30
> > daniel.sparrman AT exist DOT se
> > http://www.existgruppen.se
> > Posthusgatan 1 761 30 NORRTÄLJE
> >
> > -----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> skrev: -----
> > Till: ADSM-L AT VM.MARIST DOT EDU
> > Från: Stefan Folkerts
> > Sänt av: "ADSM: Dist Stor Manager"
> > Datum: 11/08/2011 10:31
> > Ärende: [ADSM-L] ANR3181E: Replication server server name has the same
> > replication key as this server.
> >
> > After cloning a virtual machine with TSM installed and setting up
> > replication I got this error message ;
> >
> > ANR3181E: Replication server server name has the same replication key as
> > this server.
> > Explanation
> >
> > During replication initialization, the server detected that the
> replication
> > key of the target server is the same as this server. Each server must
> have
> > a unique replication key.
> > System action
> >
> > Replication to the specified server is stopped.
> > User response
> >
> > My question is ; How can i change the replication key of a TSM instance?
> >
>
|
