IC65828: ENHANCE SYSTEM STATE BACKUP SO THAT IT CAN SKIP FILES ENUMERATED BY THE SYSTEM WRITER THAT DO NOT ACTUALLY EXIST ON THE SYSTEM

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During system state backup, the TSM backup-archive client uses
    Microsoft Volume Shadowcopy Service (VSS) to determine which
    system state components to back up, and for each component,
    which files to back up.
    
    Normally the files that are enumerated by VSS should exist on
    the given Windows system. However, there are occasions when the
    System Writer VSS component enumerates files that do not exist
    on the system. Because it is possible that a missing file can
    lead to an unbootable or otherwise unstable system or
    application, the TSM client stops the system state backup. The
    following messages are seen:
    
    11/01/2009 04:10:25 ANS5279E Error processing '<file name>':
     file not found.11/01/2009 04:10:31
    11/01/2009 04:10:31 ANS1999E Backup processing of
     'MYSYSTEM\SystemState\NULL\System State\SystemState' stopped.
    11/01/2009 04:10:32 ANS5280E Object enumeration from a file
     set or file list failed.
    
    The system state backup stops because it is not possible for
    TSM to determine whether the missing file can be safely
    skipped, or if skipping the file would yield an invalid
    system state backup. This was consistent with Microsoft's
    position that Windows system state backup is an "all or
    nothing" operation.
    
    Microsoft has recently changed their position so that it can
    be acceptable for a system state backup to skip files that
    are enumerated by the System Writer, but do  not exist on the
    system. However, it should be understood that this does not
    guarantee that the system will be recoverable if, in fact,
    the missing file is vital to the operating system or your
    applications.
    
    This is a development APAR to enhance the TSM backup-archive
    client with an option to permit system state backup to
    continue when a file reported by the System Writer cannot be
    found on the system.
    

Local fix

  • One of the following:
    
    - Contact the vendor for the missing file and work with them to
      either reinstate the file or deregister it from the Windows
      System Writer, depending on the reason why the file cannot be
      found. This is the preferred remedy.
    
    - Create a "dummy" of the missing file (the content is
      unimportant), then try the system state backup operation
      again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Backup-archive client verions 5.5 and 6.1    *
    *                 running on the following operating systems:  *
    *                                                              *
    *                 * Microsoft Windows 2003                     *
    *                 * Microsoft Windows 2003 R2                  *
    *                 * Microsoft Windows Vista                    *
    *                 * Microsoft Windows 2008                     *
    *                 * Microsoft Windows 2008 R2                  *
    *                 * Microsoft Windows 7                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION                   *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in level 6.1.4. Note that this is subject    *
    *                 to change at the discretion of IBM.          *
    *                                                              *
    *                 If you use TSM server version 5.5 or higher  *
    *                 then you can also install the version        *
    *                 6.2 client.                                  *
    ****************************************************************
    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. When this occurs, the TSM client issues the following
    messages:
    
    ANS5279E Error processing 'filename': file not found.
    ANS1999E Backup processing of
    'machinename\SystemState\NULL\System State\SystemState'
    stopped.
    ANS5280E Object enumeration from a file set or file list
    failed.
    
    You are more likely to see this after installing TSM
    backup-archive client version 5.5.2.2 and higher, or 6.1.0.2
    and higher. These client levels include the fix for IC60709,
    which provides for more rigorous validation of the files
    enumerated by the VSS writers.
    

Problem conclusion

  • Missing system state files represent an inconsistency in your
    system state that should be resolved. Skipping missing system
    state files is a circumvention only, and does not correct the
    inconsistency in your system state. An inconsistent system
    state can potentially lead to an un-bootable or otherwise
    unstable operating system or application.
    
    While an inconsistent system state is undesirable, it is also
    not easy to fix. Repair of the inconsistencies in system state
    are beyond the scope of Tivoli Storage Manager functionality,
    and should only be attempted with the assistance of the vendor
    of the missing file or with the assistance of Microsoft.
    
    If a system writer file is missing but the operating system and
    its applications are otherwise bootable and functional, then it
    is possible that the impact of the missing file is benign. In
    such cases it is preferable to allow the system state backup to
    continue, but issue appropriate messages indicating which
    system writer files are missing, and that the resulting system
    state backup represents an inconsistent system state.
    
    To that end, a new option, SKIPMISSINGSYSWFILES YES | NO has
    been added to the client so that it can skip missing system
    writer files during system state backup. The default is YES.
    
    When this option is set to YES, missing system writer files
    will be skipped and the system state backup will continue.
    For each skipped file, a message will be issued indicating that
    the file was skipped. The return code from dsmc.exe and for
    scheduled backup operations will be 8.
    
    When this option is set to NO, missing system writer files
    will not be skipped, and the system state backup will stop.
    
    Files missing from other system state components are not
    skipped. If other system state components report files that
    do not exist, then the system state backup will stop.
    

Temporary fix

  • Version 6.1.3.1 (and higher 6.1.3.x levels) include an early
    version of the fix for this problem. After applying the code,
    add the following options to your client options file
    (dsm.opt):
    
      SKIPMISSINGSYSWFILES YES
      TESTFLAGS SKIPMISSINGSYSWFILES
    
    Note: In order to use these options, you must put them in the
    client options file. They cannot be used in a TSM server
    schedule definition or client option set.
    
    After upgrading to 6.1.4 (or higher) or 6.2 (or higher),
    remove the above TESTFLAGS option. You can also remove the
    SKIPMISSINGSYSWFILES option if you want to assume the default
    value of YES.
    

Comments

APAR Information

  • APAR number

    IC65828

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    61W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-27

  • Closed date

    2010-03-29

  • Last modified date

    2010-03-29

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

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

Modules/Macros

  • DSM      DSMAGENT DSMC     DSMCSVC
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R61D PSY

       UP

  • R61F PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

61W

Reference #:

IC65828

Modified date:

2010-03-29

Translate my page

Machine Translation

Content navigation