IC67043: ANS4013E ERROR PROCESSING '<NODE>\SYSTEMSTATE\NULL\SYSTEM STATE\SYSTEMSTATE': INVALID FILE HANDLE DURING SYSTEM STATE BACKUP

IBM Tivoli Storage Manager (TSM) client V6.1.3.x interim fix downloads
IBM Tivoli Storage Manager (TSM) Client 6.2.2 Downloads and READMEs

APAR status

• Closed as change to accomodate OEM Vendor's code.

Error description

• During backup of Windows 2008 systems, if Windows Deployment
  Service (WDS) is running, then the VSS WDS Writer might
  enumerate directories that do not exist. As a result, the
  system state backup will stop.
  
  This APAR is distinguished from IC65828, which addressed files
  reported by the VSS System Writer that do not exist.
  

Local fix

• Create the directory that is reported as missing, then try the
  backup operation again.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Windows 2008 with Windows Deployment         *
  *                 Service (WDS) installed with default         *
  *                 configuration.                               *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.1.4 and 6.2.2. Note that until   *
  *                 the fixes are actually available, this       *
  *                 information is suject to change at the       *
  *                 discretion of IBM.                           *
  ****************************************************************
  The IBM Tivoli Storage Manager (TSM) backup-archive client
  leverages Microsoft's Volume Shadowcopy Service (VSS) to back
  up system state. Besides providing volume snapshot
  functionality, VSS is also used to enumerate which system
  state components, and their respective files, to back up.
  
  Normally the files that are enumerated by VSS on a given
  system should exist. However, there are occasions when a VSS
  writer enumerates files that do not exist on the system. This
  represents an inconsistency in the system state that, if not
  addressed, could possibly lead to an un-bootable or otherwise
  unstable operating system or application. Because TSM cannot
  determine whether the missing file is vital to a successful
  restore, the system state backup is deemed invalid, and thus
  stops.
  
  For this particular APAR, it is a directory enumerated by the
  Windows Deployment Service (WDS) writer that does not exist.
  Under this condition, the backup-archive client will issue
  messages similar to these during the backup:
  
   07/22/2010 21:44:29 ANS5250E An unexpected error was
    encountered.
     TSM function name : objEnumGetNextObj
     TSM function      : psFileEnumEntries() failed for path
   '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7\
    RemoteInstall\Setup' file '*.*' recursive 'YES'
     TSM return code   : 110
     TSM file          : objenum.cpp (613)
   07/22/2010 21:44:29 ANS5250E An unexpected error was
    encountered.
     TSM function name : PrivObjEnumBack
     TSM function      : objEnumGetNextObj() failed.
     TSM return code   : 110
     TSM file          : incrdrv.cpp (10010)
    07/22/2010 21:44:34 ANS1999E Incremental processing of
    '<machine>\SystemState\NULL\System State\SystemState'
     stopped.
   07/22/2010 21:44:37 ANS4013E Error processing
    '<machine>\SystemState\NULL\System State\SystemState':
    invalid file handle
   07/22/2010 21:44:37 ANS1512E Scheduled event '<event>'
    failed.  Return code = 12.
  

Problem conclusion

• The backup-archive client has been changed so that if the
  option SKIPMISSINGSYSWFILES YES is in effect, the client will
  log a warning message regarding the missing directory, then
  continue with the system state backup. Assuming no other errors
  occur during the backup, the operation should complete with a
  status of "Successful" and return code 8.
  
  The warning message that will be logged is ANS4251W. For
  example:
  
   ANS4251W WDS VSS Writer file
    '\\<machine>\c$\RemoteInstall\Setup\*.*': not found.
  
  ANS4251W was introduced with the changes addressed by APAR
  IC65828. This message was specific to the VSS System Writer,
  but has been enhanced so that it can be used for missing files
  or directories from the Windows Deployment Service, as
  illustrated above.
  

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:

Modules/Macros

• DSM      DSMAGENT DSMCSVC
  

Fix information

Applicable component levels

• R61D PSY

     UP

• R61F PSY

     UP

• R61W PSY

     UP

• R62W PSY

     UP