IC64887: VSS FAST RESTORE FROM SVC 5.1 SEV VOLUMES MAY FAIL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • VSS Fast Restore from SVC 5.1 SEV volumescan produce invalid
    files and cause recovery to fail under certain conditions.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the following software              *
    *                 combinations:                                *
    *                                                              *
    *                 - Exchange environment users of Tivoli       *
    *                   Storage FlashCopy Manager V2.1.0           *
    *                 - SQL environment users of Tivoli Storage    *
    *                   FlashCopy Manager V2.1.0                   *
    *                 - DP for Exchange V6.1.1 used in             *
    *                   combination with TSM for Copy Services     *
    *                   V6.1 and the TSM BA Client 6.1.1           *
    *                 - DP for SQL V5.5.3 used in combination      *
    *                   with TSM for Copy Services V6.1 and the    *
    *                   TSM BA Client 6.1.1                        *
    *                 - IBM System Storage Support for Microsoft   *
    *                   Volume Shadow Copy Service and Virtual     *
    *                   Disk Service version 4.0                   *
    *                                                              *
    *                 with either:                                 *
    *                                                              *
    *                 1) SVC version 4.2.x or 4.3.x, and DS8000    *
    *                 who                                          *
    *                    run VSS Instant Restore on volumes that   *
    *                    have snapshots on Space-Efficient target  *
    *                    vdisks                                    *
    *                                                              *
    *                 2) SVC version 5.1 who run VSS Instant       *
    *                    Restore on volumes that have snapshots    *
    *                    on vdisks which are a part of standard    *
    *                    (non-incremental) FlashCopy               *
    *                    relationships having dependent FlashCopy  *
    *                    mappings.                                 *
    *                                                              *
    *                 Note: To find out more about Multiple        *
    *                 Target FlashCopy mappings in SVC Customer    *
    *                 Information Center web page                  *
    *                 http://publib.boulder.ibm.com/infocenter/    *
    *                 svcic/v3r1m0/topic/com.ibm.storage.svc.      *
    *                 console.doc/svc_flashmapovr_21i9wu.html      *
    ****************************************************************
    * PROBLEM DESCRIPTION: While performing a Data Protection for  *
    *                      SQL, or respective for Data Protection  *
    *                      for Exchange, VSS Instant Restore, the  *
    *                      underlying TSM Client/ FlashCopy        *
    *                      Manager VSS Component code attempts to  *
    *                      perform a VSS Fast Restore instead      *
    *                      (that is, a volume-level restore)       *
    *                      although the operation is not           *
    *                      supported for the attached              *
    *                      storage subsystem disks.                *
    *                                                              *
    *                      Because of this issue, the restored     *
    *                      volumes contains errors that are        *
    *                      reported by "chkdsk" system tool and    *
    *                      as a result, the restored data is       *
    *                      unusable.                               *
    *                                                              *
    *                      Here is an example of the behavior      *
    *                      that may be seen using the restore      *
    *                      of an Exchange database.                *
    *                                                              *
    *                      After the restore operation completes,  *
    *                      the Exchange server fails to recover    *
    *                      the mailbox database stored on those    *
    *                      disks.                                  *
    *                                                              *
    *                      Event ID 440 is logged in Windows       *
    *                      Application log:                        *
    *                                                              *
    *                      Event Type: Error                       *
    *                      Event Source: ESE                       *
    *                      Event Category: Logging/Recovery        *
    *                      Event ID: 440                           *
    *                      Date:  8/28/2009                        *
    *                      Time:  5:16:16 PM                       *
    *                      User:  N/A                              *
    *                      Computer: MALTA                         *
    *                      Description:                            *
    *                      Information Store (4648) Logfile        *
    *                      Integrity-Check (I:\exchange_STG\       *
    *                      svcsev_i_basic_stg1\E00): The log file  *
    *                      I:\exchange_STG\svcsev_i_basic_stg1\    *
    *                      E000000000B.log is damaged, invalid,    *
    *                      or inaccessible (error -501) and        *
    *                      cannot                                  *
    *                      be used. If this log file is required   *
    *                      for recovery, a good copy of the log    *
    *                      file will be needed for recovery to     *
    *                      complete successfully.                  *
    *                                                              *
    *                      In this situation the fail-over to      *
    *                      file-level copy restore must be         *
    *                      performed.                              *
    *                                                              *
    *                      =======================                 *
    *                      =======================                 *
    *                                                              *
    *                      Below are examples of the logged error  *
    *                      messages that may be seen in the case   *
    *                      of using a Space-Efficient target       *
    *                      vdisk from a SVC v4.3.1 storage sub-    *
    *                      system. Assume that the original        *
    *                      target vdisk has vdisk_id               *
    *                      60050768018280479000000000000287.       *
    *                                                              *
    *                      THE DSM AGENT LOG aka dsmerror.log      *
    *                      located in the TSM Client installation  *
    *                      directory (by default, "C:\Program      *
    *                      Files\Tivoli\tsm\baclient\")            *
    *                                                              *
    *                      10/23/2009 05:06:04 ANS1252W The        *
    *                      server you are connected to does not    *
    *                      support this function.                  *
    *                      10/23/2009 06:35:48 ANS5262I Snapshot   *
    *                      restore will failover to file-level     *
    *                      copy from snapshot volume.              *
    *                      10/23/2009 06:35:56 ANS5250E An         *
    *                      unexpected error was encountered.       *
    *                       TSM function name : vssIBMSnapRestore  *
    *                       TSM function      : IIbmVssProv::      *
    *                      revertSnapshots failed, hr =            *
    *                      0x000002ca.                             *
    *                      Look in IBM VSS provider log            *
    *                      'IBMVss.log' for detailed error in      *
    *                      formation.                              *
    *                         TSM return code   : 6052             *
    *                         TSM file          : vssrest.cpp      *
    *                      (3559)                                  *
    *                      10/23/2009 06:35:56 ANS5263E Snapshot   *
    *                      module for 'IBM VSS Hardware Provider'  *
    *                      failed with error 'Failed to restore    *
    *                      the snapshots'. 10/23/2009 06:35:56     *
    *                      Snapshot restore failed. Please see     *
    *                      TSM error log for more details.         *
    *                                                              *
    *                      ====================================    *
    *                      THE IBM VSS PROVIDER LOG aka IBMVss.log *
    *                                                              *
    *                      located in the installation directory   *
    *                      of IBM VSS provider (by default,        *
    *                      "C:\Program Files\IBM\Hardware Provider *
    *                                                              *
    *                      for VSS-VDS") contains:                 *
    *                                                              *
    *                      Fri Oct 23 06:35:40.414 - Entered       *
    *                      reverseRestore() 1   <-- Verify if      *
    *                      volume-level support is supported       *
    *                      ...                                     *
    *                      Fri Oct 23 06:35:48.149 - SVC ver:      *
    *                      4.3 does NOT support restoring          *
    *                      flashcopy for Space Efficient Volume:   *
    *                      60050768018280479000000000000287        *
    *                      ...                                     *
    *                      Fri Oct 23 06:35:48.665 - Entered       *
    *                      reverseRestore() 0   <-- Volume level   *
    *                      restore is called                       *
    *                      ...                                     *
    *                      Fri Oct 23 06:35:56.978 - SVC ver: 4.3  *
    *                      does NOT support restoring flashcopy    *
    *                      for Space Efficient Volume:             *
    *                      60050768018280479000000000000287        *
    *                                                              *
    *                      =====================================   *
    *                                                              *
    *                      In the case where Data Protection for   *
    *                      Microsoft SQL Server is used....        *
    *                      THE DP FOR SQL LOG aka tdpsql.log       *
    *                      located, by default, in directory       *
    *                      "C:\Program Files\Tivoli\tsm\tdpsql\")  *
    *                                                              *
    *                                                              *
    *                      10/23/2009 06:35:33                     *
    *                      10/23/2009 06:35:33 Request:            *
    *                      VSS RESTORE                             *
    *                      10/23/2009 06:35:33 Component List:     *
    *                      'DB_K'(full, Local)                     *
    *                      10/23/2009 06:35:33 LocalDSMAGENTNode:  *
    *                      TAHITI1                                 *
    *                      10/23/2009 06:35:33 Mount Wait:         *
    *                      Yes                                     *
    *                      10/23/2009 06:35:33 -----------------   *
    *                      10/23/2009 06:35:37 Backup(s) to        *
    *                      be restored:                            *
    *                      10/23/2009 06:35:37 <DB_K : VSS : full  *
    *                      : 10/23/2009 06:19:58>                  *
    *                      10/23/2009 06:35:40 Restoring 'DB_K'    *
    *                      using volume-level-copy snapshot.       *
    *                      10/23/2009 06:35:48 Starting snapshot   *
    *                      restore process. This process may take  *
    *                      several minutes.                        *
    *                      10/23/2009 06:35:59 VSS Restore         *
    *                      operation completed with rc = 0         *
    *                      10/23/2009 06:35:59 Files Examined: 2   *
    *                      10/23/2009 06:35:59 Files Completed: 2  *
    *                      10/23/2009 06:35:59 Files Failed: 0     *
    *                      10/23/2009 06:35:59 Total Bytes:        *
    *                      5243190                                 *
    *                      10/23/2009 06:51:36                     *
    *                      ======================================  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ************************************************************
    USERS AFFECTED:
    Please refer to the Users Affected section of this PMR for
    details.
    ************************************************************
    PROBLEM DESCRIPTION:
    Please refer to the Problem Description section of this
    PMR for details.
    ************************************************************
    RECOMMENDATION:
    
    Apply CSD when available. The fix for this APAR will be
    available via the following products, depending on your
    environment:
    
    Tivoli Storage FlashCopy Manager 2.1.0.1
    TSM BA Client 6.1.2
    

Problem conclusion

  • The code used by the TSM BA Client / FlashCopy Manager VSS
    component has been modified to:
    
    1) For SVC version 4.2.x or 4.3.x, and DS8000: ?????
    2) For SVC 5.1: allow fail-over to file-level copy
    restore in the cases where SVC dependent mappings exist.
    
    After applying the fix, the messages in the software logs
    should now look similar to this:
    
    =======================
    THE DSM AGENT LOG aka dsmerror.log
    located in the TSM Client installation directory
    (by default, "C:\Program Files\Tivoli\tsm\baclient\")
    
    10/23/2009 07:33:10 ANS1252W The server you are connected
    to does not support this function.
    10/23/2009 07:35:30 ANS5262I Snapshot restore will failover
    to file-level copy from snapshot volume.
    10/23/2009 07:37:08 ANS1577I The Windows console event handler
    received a 'Ctrl-C' console event.
    10/23/2009 07:37:09 ANS1577I The Windows console event handler
    received a 'Ctrl-C' console event.
    
    =======================
    THE IBM VSS PROVIDER LOG aka IBMVss.log
    located in the installation directory of IBM VSS provider
    (by default, "C:\Program Files\IBM\Hardware Provider for
    VSS-VDS") contains:
    
    Fri oct 23 07:35:22.466 - Entered reverseRestore() 1
    Fri oct 23 07:35:22.466 - Entered getTargetSVC()
    Fri oct 23 07:35:23.468 - root/ibm:IBMTSSVC_StorageVolume:
    1002ms
    Fri oct 23 07:35:24.579 - Current Using: 9.52.171.144
    (tivoli_clust2) code level:4.3.1.1 (build 9.14.0811200000)
    Fri oct 23 07:35:24.579 - Exit getTargetSVC()
    Fri oct 23 07:35:24.579 - Source Volume Target Volume
    Fri oct 23 07:35:24.579 - [60050768018280479000000000000287]
    =>[60050768018280479000000000000286]
    Fri oct 23 07:35:24.579 - IBMTSSVC_StorageConfigurationService
    : 0ms
    Fri oct 23 07:35:24.908 - IBMTSSVC_Cluster: 329ms
    Fri oct 23 07:35:24.908 - Entered checkCascadingFCMaps()
    Fri oct 23 07:35:25.957 - IBMTSSVC_StorageVolume: 1049ms
    Fri oct 23 07:35:27.647 - IBMTSSVC_LocalStorageSynchronized:
    673ms
    Fri oct 23 07:35:30.637 - SVC ver: 4.3 does NOT support
    restoring falshcopy for Space Efficient Volume:
    60050768018280479000000000000287
    Fri Oct 23 07:35:30.637 - IBMVSS: Provider reference count 1
    Fri Oct 23 07:39:51.649 - IBMVSS: OnUnload
    Fri Oct 23 07:39:51.649 - IBMVSS: Provider reference count 0
    Fri oct 23 07:39:51.649 - SVCPegService connection is closed.
    Fri Oct 23 07:39:51.649 - IBMVSS: Closing output file,
    then Unloading will be finished
    
    =======================
    In the case where Data Protection for Microsoft SQL Server
    is used....
    
    THE DP FOR SQL LOG aka tdpsql.log
    located, by default, in directory "C:\Program Files\Tivoli\
    tsm\tdpsql\")
    
    10/23/2009 07:35:17 Request: VSS RESTORE
    10/23/2009 07:35:17 Component List: 'DB_K'(full, Local)
    10/23/2009 07:35:17 Local DSMAGENT Node: TAHITI1
    10/23/2009 07:35:17 Mount Wait: Yes
    10/23/2009 07:35:17 -----------------------------------------
    10/23/2009 07:35:19 Backup(s) to be restored:
    10/23/2009 07:35:19 <DB_K : VSS : full : 10/23/2009 06:19:58>
    10/23/2009 07:35:23 Restoring 'DB_K' using volume-level-copy
    snapshot.
    10/23/2009 07:35:31 Starting file-level copy restore
    10/23/2009 07:35:34 VSS Restore operation completed with
    rc = 0
    10/23/2009 07:35:34    Files Examined   : 2
    10/23/2009 07:35:34    Files Completed  : 2
    10/23/2009 07:35:34    Files Failed     : 0
    10/23/2009 07:35:34    Total Bytes      : 5243190
    10/23/2009 07:36:48
    =========================================================
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC64887

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-11-30

  • Closed date

    2009-11-30

  • Last modified date

    2009-11-30

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

    IC63872

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

Modules/Macros

  • VSSREST
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC64887

Modified date:

2009-11-30

Translate my page

Machine Translation

Content navigation