replication node failed

[jon2007]

i have this scenario
2 sites (Primary site ,DR site )
TSM 6.3.4
node replication configured
the node_A hace many filespace replicated
there is any way to delete a file space of the node A from the replication
for example a commande like
del replnode node_A \filespace1 !!!!

thanks in advance

 

[marclant]

Do you want to delete the replicated data because you no longer wish to replicate that node or because you think it may solve the issue? If the latter, I'd recommend you troubleshoot the issue instead and start by applying fix pack 6.3.5. 100 (or ideally 7.1.3) to make sure you are not encountering known APARs.

If you want to stop the replication, you have to do it in two steps, stop the replication of that node using REMOVE REPLNODE, and then delete the filespace from the target using DELETE FILESPACE.

 

[jon2007]

thanks marclant
there is a procedure to migrate my servers TSM from 6.3.4 to 7.1.3
primary site is a cluster windows 2012

i wouldn't remove all the filespaces of this node because is the for the Virtual environement


the detail :

on the source site (site1)

SITE1> q files VM_DZ1600SITE1
Node Name Filespace FSID Platform Filespace Is Files- Capacity Pct
Name Type pace Util
Unicode?
--------------- ----------- ---- -------- --------- --------- ----------- -----
VM_DZ1600SITE1 \VMFULL-DZ- 1 ?? API:TSMVM No 0 KB 0.0
1600SRV1
VM_DZ1600SITE1 \VMFULL-DZ- 2 ?? API:TSMVM No 0 KB 0.0
1600SRV2
VM_DZ1600SITE1 \VMFULL-DZ- 3 ?? API:TSMVM No 0 KB 0.0
1600SRV3
VM_DZ1600SITE1 \VMFULL-DZ- 4 ?? API:TSMVM No 0 KB 0.0
1600SRV4
VM_DZ1600SITE1 \VMFULL-DZ- 5 ?? API:TSMVM No 0 KB 0.0
1600SRV5
VM_DZ1600SITE1 \VMFULL-DZ- 6 ?? API:TSMVM No 0 KB 0.0
1600SRV6
VM_DZ1600SITE1 \VMFULL-DZ- 7 ?? API:TSMVM No 0 KB 0.0
1600SRV7
VM_DZ1600SITE1 \VMFULL-DZ- 8 ?? API:TSMVM No 0 KB 0.0
1600SRV8
VM_DZ1600SITE1 \VMFULL-DZ- 9 ?? API:TSMVM No 0 KB 0.0
1600SRV9

whene i would like replicate the filespace \VMFULL-DZ1600SRV9 the repplication failed


tsm: SITE1 >replicate node VM_DZ1600SITE1 \VMFULL-DZ1600SRV9 wait=yes
Session established with server SITE1: Windows
Server Version 6, Release 3, Level 4.300
Server date/time: 10/06/2015 15:47:18 Last access: 10/06/2015 15:43:49

ANR0984I Process 74 for Replicate Node started in the FOREGROUND at 15:47:21.
ANR2110I REPLICATE NODE started as process 74.
ANR0327I Replication of node VM_DZ1600SITE1 completed. Files current: 0. Files replicated: 1,777 of 9,993. Files updated: 0 of 0. Files deleted: 0 of
0. Amount replicated: 122 MB of 152 GB. Amount transferred: 122 MB. Elapsed time: 0 Day(s), 0 Hour(s), 1 Minute(s).
ANR0986I Process 74 for Replicate Node running in the FOREGROUND processed 1,777 items for a total of 128,863,933 bytes with a completion state of
FAILURE at 15:47:44.
ANR1893E Process 74 for Replicate Node completed with a completion state of FAILURE.
ANS8001I Return code 14.



how can initiate the replication only for this filespace ?
on the target server i'am deleting the filespace
SITE2> del files VM_DZ1600SITE1 \VMFULL-DZ1600SRV9

but on the primary site (site1) i have still the information about the filespace \VMFULL-DZ1600SRV9 (show the last line of the command)
Node Name Type Filespace Name FSID Files on Replication Files on
Server Server (1) Server (1)
--------------- ---- --------------- ---- ---------- --------------- ----------

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 1 3,209 SITE2 725
SRV1

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 2 3,048 SITE22 575
SRV2

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 3 6,315 SITE22 6,315
SRV3

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 4 7,654 SITE22 7,654
SRV4

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 5 4,129 SITE22 293
SRV5

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 6 526 SITE22 526
SRV6

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 7 6,125 SITE22 2,029
SRV7

VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 8 2,485 SITE22 937
SRV8


VM_DZ1600SITE1 Bkup \VMFULL-DZ1600- 9 5,879
SRV9


how i can delete this information and restart properly a replication for this filespace

 

[marclant]

You shouldn't have to delete anything to fix the replication and depending on the cause of the failure, you may be creating yourself more work than needed.

Check the activity log to see why the replication failed in the first place. Lookup those errors and maybe there is already a simple solution for it.

 

[jon2007]

exactly sir
the i find in the activity log that a volume had the ACCESS="UNAVAILABLE" , i would first restore this volume.

you can tel the best procedure to do the migration of TSM server from 6.3.4 to 7.1
and if i start by migrate first the DR site server, that will impact the replication node ?
i e
site 1 TSM server 6.3.4
site 2 TSM server 7.1

thanks a lot

 

[marclant]

The steps to upgrade are here: http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/srv.install/t_srv_upgrade.html

However, that will not fix the access=unavailable. Make sure the volume is available, then update the volume status to readwrite, then retry the replication.