Re: Node Replication Change

Ah, correct, I miss-read the syntax on UPDATE NODE. Replication is already running from TSM02 to TSM01, so nothing to worry about there. So, the following: On TSM01: REMOVE REPLNODE On TSM02: REMOVE REPLNODE On TSM02: UPDATE NODE REPLSTATE=ENABLED REPLMODE=SYNCSEND On TSM01: UPDATE NODE

Re: TSM Server 7.1.4 woes

PERSISTENCE PAYS OFF! Well done, both of you! Best regards, Mike, x7942 RMD IT Client Services On Thu, May 5, 2016 at 1:54 PM, Andrew Raibeck wrote: > Hello all, > > Neil took me up on my offer to look at a trace, and thanks to his > persistence, that indeed led to

Re: TSM Server 7.1.4 woes

Hello all, Neil took me up on my offer to look at a trace, and thanks to his persistence, that indeed led to unmasking a problem in the 7.1.4 server. APAR IT15117 has been opened for this issue. It may take a day or so before it is visible on the web. As discussed previously, the files can be

Re: Node Replication Change

Hi, you can't update node with parameters: REPLM=RECEIVE and SEND (according administration guide). Those parameters will set automatically after first replication completed. I think the right way is remove replnode and when set REPLM=SYNCSEND for source and REPLM=SYNCRECEIVE for target node.

Node Replication Change

I'm using Spectrum Protect 6.3.4.300 on Windows servers. I've been running NODE replication for months, but need to make a change for a node. The current setup: Server TSM01 replicates to Server TSM02 and TSM02 replicates to TSM01. The change: a node is to be "relocated" to the DR site; thus

Re: multipath tape support and device naming

Big delay but probably it is still actual. I check the dual path using the following: after lin_tape configuratiin you can see the similar output: Changer output: # cat /proc/scsi/IBM* lin_tape version: 3.0.6 lin_tape major number: 242 Attached Changer Devices: Number model SN