System State ANS5279E Error processing 'filename': file not found

Technote (troubleshooting)


Problem(Abstract)

System state backup stops when a file that is defined as being part of the system state does not exist on the system. Messages ANS5279E, ANS1999E and ANS5280E are issued. Scheduled backup operations end with a status of "failed" and return code 12.

Symptom

When the IBM Tivoli Storage Manager backup-archive client for Microsoft Windows backs up system state, you might see the following error messages:

ANS5279E Error processing 'filename': file not found.
ANS1999E Incremental processing of 'machinename\SystemState\NULL\System State\SystemState' stopped.
ANS5280E Object enumeration from a file set or file list failed.



Cause

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.


Resolving the problem

Resolve the inconsistency in the system state as follows:


Step 1: Identify the component to which the file belongs.

Step 2: Determine whether the missing file affects the ability for the operating system to boot (or otherwise affects stability of the operating system), or whether it impacts an application that runs on the system. It is possible that the file belongs to an application, driver, or other component that is no longer installed on the operating system. You might need to consult with the component vendor to make this determination.

Step 3: Depending on the outcome of the previous step, either reinstall the missing file, or de-register it from Windows so that it will no longer be enumerated by VSS. The component vendor might need to assist you with this step.

Step 4: Use the TSM backup-archive client to back up system state. Barring any further issues, the system state backup should run to completion.


Either of the following alternatives can be used to circumvent ("work around") the inconsistency in system state:

CAUTION: These are circumventions only, and do not correct the inconsistency in your system state. As noted earlier in this article, an inconsistent system state can lead to an un-bootable or otherwise unstable operating system or application.

Alternative 1: Create a "dummy" of the missing file (the content is unimportant). That is, create a file with the same name, and in the same directory, as the file cited in the ANS5279E message that accompanies this problem. Note that this alternative does not require installing any new TSM code.

Alternative 2: Install TSM client version 6.1.4 (or higher 6.1.x level) or version 6.2 (any level).

Attention: All version 6.1 and 6.2 clients are compatible with version 5.5, 6.1 and 6.2 TSM servers only. If your TSM server version is 5.4 or older, do not install any 6.1 or 6.2. Instead you need to use Alternative 1. See http://www.ibm.com/support/docview.wss?uid=swg21053218 for further information on TSM client and server version compatibility.

These client versions include the enhancement described by APAR IC65828. This enhancement adds a new option called SKIPMISSINGSYSWFILES. The option can be set to YES or NO; the default is YES. When SKIPMISSINGSYSWFILES YES in effect, the following statements describe how system state backup behaves if a System Writer file cannot be found:

* As before, message ANS5279E is issued if the TSM backup-archive client cannot back up a system state file because it is missing.

* If the missing file belongs to the Windows System Writer, then the system state backup will continue.

* Barring any other issues that could stop the system state backup, the system state backup will run to completion.

* Barring any other issues that could stop the system state backup, ANS1999E will no longer be issued.

* Barring any other issues that could stop the system state backup, the backup operation will end with a status of "Complete" and return code 4. The return code 4 indicates that one or more files were skipped during the backup. Note: If some other warning or error occurs during backup processing, the return code might be higher (for example, 8 or 12). If the return code is 12, the backup operation will end with a status of 'Failed'.

At this time, the TSM client will only skip files that belong to the Windows System Writer. If a missing file belongs to a different writer, then use Alternative 1 instead for that file.

Refer to the Tivoli Storage Manager version 6.2 documentation for further information about the SKIPMISSINGSYSWFILES option.


Related information

IC65828

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager
Client

Software version:

All Supported Versions

Operating system(s):

Windows

Reference #:

1419884

Modified date:

2011-06-10

Translate my page

Machine Translation

Content navigation