Decommission VM using OC doesn't decommission on Replication target

[Nicke]

My environment:
2 x AIX 7,2 full partion servers with one Primary and one as the D/R server.
TSM server level 8.1.1.109
TDP for WMware 7.1.6


The main problem was that the Target server database and container pool increased more than it should and compared with the Primary server.

The work-around solution was to manually search for and remove old Out Of Production (oop) data from decommissioned VMs on the Target side:
query filesp VM_server2 f=d > /tmp/vminfo.txt
Manual compare of the decommissioned vm names seen in O.C and finding those filespace in vminfo.txt and then on the Target: decommission vm VM_server2 <oop vm name>
On the Target: delete filespace VM_server2 126 nametype=fsid

Question: is this a known problem or could it be a bug in SSP / TSM 8.1.1.109 or with TDP for VMware 7.1.6 ?

Regards,
Nicke

 

[marclant]

There's an APAR:
https://www-01.ibm.com/support/docview.wss?uid=swg1IT24242

Upgrade your server to the latest and you'll be good to go. 8.1.7 is coming out this week, or use 8.1.6.100.

Since you are below 8.1.2, read this before upgrading to a release greater than 8.1.2:
https://www-01.ibm.com/support/docview.wss?uid=swg22004844

 

[Nicke]

Thanks for your answer!

We know that we should plan an upgrade of TSM Server but a bit afraid of the security enhancements and the SSL key exchange that will slow down the backup performance for all our Oracle DB systems (TDP for Oracle).

Kind Regards,
Nicke

 

[marclant]

The SSL doesn’t affect performance, it’s just for the login (passing credentials), not for the backup data.

Still using TCP for data unless you enable SSL for data too.