IC94316: STUB RESTORE IS NOT ALLOWED FROM SECONDARY TSM SERVER IN NODE REPLICATION ENVIRONMENT

APAR status

• Closed as documentation error.

Error description

• With TSM Server 6.3 the functionality "Node Replication" was
  introduced.
  A primary TSM Server can replicate to an secondary TSM server.
  In case of a failure of the primary server the administrator can
  switch the TSM client
  to the secondary server. The secondary server doesn't allow the
  creation of new objects
  on the server. Only recall, restore or retrieve is supported.
  
  The backup of HSM migrated files allows the so called
  stub-restore of a file if the
  copy of the file in the file system is gone and needs to be
  recovered. It is not allowed
  to use the stub-restore mechanism to restore data from the
  secondary server in such
  an environment.
  
  To disable the stub-restore function in terms of a file restore
  the TSM Backup Archive
  command line client must be called with the argument
  "-restoremigstate=no".
  
  Furthermore it is not allowed to use the TSM for Space
  Management function "dsmmigundelete"
  to create stub files based on information stored on the
  secondary server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM Tivoli Storage Manager                   *
  *                 Administrator's Guide                        *
  *                 (For all operating systems, for V6.3.1,      *
  *                 V6.3.3, V6.3.4, and V7.1)                    *
  *                                                              *
  *                 IBM Tivoli Storage Manager                   *
  *                 Backup-Archive Clients Installation and      *
  *                 User's Guide                                 *
  *                 (For all operating systems, for V6.3,        *
  *                 V6.4,and V7.1)                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: The documentation for replication of    *
  *                      HSM data is not complete.               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  *
  

Problem conclusion

• The following information is added:
  
  "If you restore a file from the Tivoli Storage Manager target
  server, and the file system is managed by Tivoli Storage
  Manager for Space Management, you must not restore the file as
  a stub file.  You must restore the complete file. Use the
  restoremigstate=no option to restore the complete file.  If
  you restore the file as a stub from the target server, the
  following consequences can occur:
  - You cannot recall the file from the Tivoli Storage Manager
  source server by using the Tivoli Storage Manager for Space
  Management client.
  - A Tivoli Storage Manager for Space Management reconciliation
  process that runs against the Tivoli Storage Manager source
  server expires the file.  If the file is expired by a
  reconciliation process, you can restore the complete file with
  the backup-archive client and the restoremigstate=no option.
  
  
  The information is added to two topics in the
  Tivoli Storage Manager Administrator's Guides:
  "Node replication restrictions"
  "Restoring, retrieving, and recalling data from a target
  replication server".
  
  
  The information is added to the "Restoremigstate" topic in
  the Tivoli Storage Manager Backup-Archive Clients Installation
  and User's Guide.
  
  In the V7.1 version of the Backup-Archive Clients
  Installation and User's Guide, the information is also added
  to the topic "Restrictions for automated client failover".
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels