ADSM-L

[ADSM-L] Clarification of statement concerning upgrading to Spectrum Protect 7.1.3

2015-10-20 15:40:20
Subject: [ADSM-L] Clarification of statement concerning upgrading to Spectrum Protect 7.1.3
From: Ron Delaware <ron.delaware AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 20 Oct 2015 12:38:14 -0700

To All,

Yesterday I replied to a question concerning upgrading to the latest version of Spectrum Protect v7.1.3 (formerly known as Tivoli Storage Manager). In my attempt to be brief, my comment may have caused more confusion.  
The patch that was applied was an efix for APAR  IT11581, it is not a GA patch. In order to receive the efix patch,  you need to have an open PMR and the symptoms that you are experiencing are present in the APAR.
After the efix is applied running a 'show banner' command will display this:

The 7.1.3.200 deliverable reveals a banner at startup  the following:   ( is also echoed using SHOW BANNER )
*********************************************************************
* This is a Limited Availability TEMPORARY fix for                  *
* IT11581  REPLICATE NODE TO TARGET DIRECTORY-CONTAINER STORAGE     *
*          POOL CAN HANG CAUSING HIGH TARGET SYSTEM CPU MEMORY      *
*          USAGE.                                                   *
* It is based on fixes made generally                               *
* available with patch level 7.1.3.000                              *

You'll see that APAR IT11581 is the bug mentioned and symptoms which may not occur because it's
a timing issue.  It can only occur when replicating from a source replication server non-container stgpool to a 7.1.3 target replication
server hosting a container pool, the target server may exhibit high CPU.  In fact the high CPU on the target replication server is a non-preemptive loop that exhibits a hang symptom on the target server preventing replication from completing.

The movement of data that I referred to, was indeed using the method where you have your primary (production) server perform a node replication to a secondary SP server that has the identical Domain structure as the primary (perform export policy), with the copygroup destination pointing to a container storage pool.

Currently there is no 'move in' command available to move non-container data into a 7.1.3 container, our Development Team is working on delivering that functionality sometime in 1st half of 2016  ( "Subject to change at the discretion of IBM") .

I hope that this clarifies any confusion I might have caused with my brief statement.



 

Best Regards,

_________________________________________________________
    
email:
ron.delaware AT us.ibm DOT com

 

<Prev in Thread] Current Thread [Next in Thread>
  • [ADSM-L] Clarification of statement concerning upgrading to Spectrum Protect 7.1.3, Ron Delaware <=